Founding Engineer - LA preferred | SF considered

We’re hiring the first full-time engineer at Millee.

We have a deployed V1, two active customers, and we’re raising a $3M Seed round. The founders have each spent 10+ years inside the industry we’re serving. We didn’t start with an idea and go looking for a problem. We built V1 around problems we’ve personally faced in our market.

Early users are already incorporating it into daily decision-making. Our V2's is aimed at cementing our position as an essential part of their daily tooling vs a nice to have. That’s where you come in. You would own the technical direction from V1 to V2 as we move through early go-to-market. The architectural decisions made now will shape how deeply the system embeds into customer workflows. Our goal from there is to scale into enterprise, which will of course require a candidate who's comfortable building a tool that can withstand pressure under a much larger user base.

We know that with vertical AI companies, the first engineering hires disproportionately influence outcomes. We already have market-aligned UI and workflow. We now need someone who can translate that into a durable product that competes as our category matures.

You’ll work directly with me (CEO, product-led founder) and alongside a fractional CTO who is currently a Senior Staff Engineer at Intuit. V1 was built with support from a Principal Engineer at Workday.

We’re looking for a senior or staff-level engineer who wants ownership and an entrepreneurial journey with a high growth startup. Someone comfortable making architectural calls, shipping production systems, and thinking about how applied AI changes professional behavior over time. Experience with workflow software, data-rich systems, or AI-native products is useful, but sound judgment matters more. This is a role for someone who is ready to go all in on our mission.

Location preference is Los Angeles. San Francisco works for the right person. Compensation includes competitive salary and meaningful founding equity.

If you want to build from a validated starting point rather than a blank doc, and you care about shaping the core of a company rather than a small surface area, we should talk.

Side note - we want someone motivated to build a category-shaping product from the ground up, not someone interested in assembling surface-level features. Feel free to add me on LinkedIn for even greater application visibility.