Software Engineer, Backend Developer

About the Company

At Flow, we're reimagining what it means to live, work, and connect. More than just a real estate company, Flow is a brand, a technology platform, and an operations ecosystem spanning condominiums, hotels, multifamily residences, and office spaces. We're building a new kind of living experience: one that's flexible, connected, and designed to create genuine community and real value for the people who call Flow home.

Our mission is oneness: prioritizing our residents and their experiences, and fostering connection with ourselves, their neighbors, and the natural world. By putting people at the center of everything we do, we're creating vibrant, human-centered communities where life, work, creativity, and play all come together in one place.

As a member of Flow's Engineering team, you'll build practical, high-impact software and work directly with the people who use them every day - operators, neighbors, business leaders, and cross-functional teams trying to move faster and work smarter.

This is not a role where you build in isolation and toss work over the wall. You'll be embedded with teams across the business, translating real operational friction into elegant software, intelligent workflows, and AI-powered products that meaningfully improve how work gets done and how our neighbors live.

We're hiring a software engineer, but the role is really that of a builder. Our title says "software engineer," but the mindset we're looking for is closer to a product engineer: someone who wants to deeply understand what our end users - neighbors and operators - actually need, and who treats technology as a tool in service of that outcome rather than an end in itself.

You'll move across the stack as the problem demands it: backend, frontend, data, infrastructure, automation, AI. Strong backend fundamentals are a great foundation, but this role is not a fit for someone who only wants to live in the backend. If touching a frontend, wiring up a workflow, or picking up a new part of the stack makes you uneasy rather than curious, this isn't the right seat.

We care much more about slope than about y-intercept. In other words, we're less interested in exactly how much you already know on day one, and far more interested in how fast you learn, how willingly you expand into unfamiliar territory, and how you respond when the job asks you to pick up something new. We're looking for people who treat their own skill set as something to keep building, not something to protect.

You should be genuinely AI-native - not someone who has used an AI coding assistant a few times, but someone who has internalized what it means to build with AI as a core part of the craft. You use tools like Claude Code and Cursor as force multipliers, which means strong written communication is part of the job: clear prompts, clear documentation, clear stakeholder updates.

You know how to move fast with AI without sacrificing quality - when to trust generated output, when to slow down and apply deeper engineering judgment, and how to hold your own work to a high bar even as the pace increases.

We build and iterate quickly,