The Alpha Deal Engineering Vibe
We've been asked to describe our engineering culture, and we want to do that honestly — which means not describing what we aspire to be, but what we actually are right now, at this stage.
What's true about how we work
We're small. The engineering team is small enough that everyone knows what everyone else is building. There's no functional siloing, no separate platform team, no layer of process between an engineer and a product decision. If you're working on something, you own it end-to-end — the architecture, the edge cases, the relationship with the users who depend on it.
We write code that goes to production. This sounds obvious, but it's worth saying: the things we build are being used on real sites by real practitioners making real decisions. There's no internal tools to build, no experimental features that nobody sees. The feedback loops are short and real. When something breaks, we know immediately. When something works particularly well, we know that too.
We have technical debt. The codebase is young and it was built fast. Some parts of it are cleaner than others. There are architectural decisions we made early that we'd make differently today — and some of them are on the list to address, and some of them are going to stay wrong for longer than we'd like because there are higher priorities. We're not going to pretend otherwise.
We move fast by being precise about what we're shipping. We don't move fast by shipping things that aren't ready. We move fast by being very clear about what a feature does and doesn't do, and by shipping that scope quickly rather than letting features expand until they're "fully done." Full done in a complex domain is a moving target; useful now is something we can ship.
We don't have everything figured out. The data model is still evolving. There are problems we haven't fully solved — how to handle zoning edge cases, how to represent uncertainty in program eligibility assessments, how to make the capital stack modeling fast enough for first-pass screening. We know what we're trying to do. We don't always know exactly how yet.
What we're building toward
Alpha Deal is an early company working on a hard problem in a domain that doesn't have many software precedents. We're building infrastructure for affordable housing pre-development — a category that hasn't had purpose-built software before. We're doing it with a small team that has deep domain knowledge and genuine conviction that the problem matters.
That means the work ahead involves real architectural decisions with long-term consequences, real product decisions that affect how practitioners work, and real domain learning that shapes what we build and how. If you're the kind of engineer who finds that combination motivating — hard problems, real stakes, genuine ownership — this is that.
It also means that the work is sometimes ambiguous, sometimes frustrating, and sometimes slower than you'd like because the domain is genuinely complex and the right answer isn't always obvious. We think that's the nature of building in a hard space, not a management failure. But it's worth being honest about.
What we look for
We look for engineers who are good at what they do and care about what they're building. Not in an abstract way — in the specific sense that the outcome of the software matters to them, not just the quality of the code.
We look for engineers who are curious about the domain — who want to understand why affordable housing development is hard and what role software can play in making it less hard, not just what the API should look like.
We look for engineers who communicate well, because the work requires close collaboration with practitioners who aren't engineers, and the gap between technical clarity and domain knowledge has to be bridged constantly.
And we look for engineers who want to build something real — something that ends up in buildings, in neighborhoods, in housing that people actually live in. That's a longer chain of causality than most software produces. We find it motivating. If you do too, we'd like to talk.
We're a small engineering team working on a hard problem that matters. If this sounds like the right environment for you, reach out.