Software Engineer, Product

What You’ll Own
Full-stack features from zero to shipped – scoping, architecture, build, iteration
AI-powered product surfaces: intelligent intake flows, real-time constituent assistants, automated case routing, agency operator dashboards
Direct engagement with federal agency stakeholders – translating messy real-world requirements into clean, shippable product
Platform reliability and performance at government scale – real users, real SLAs, no hiding
Code quality that the next engineer will respect: clean, tested, maintainable

What You’ll Bring
2–4 years of professional engineering experience – or work that makes the years irrelevant
Deep fluency in React / Next.js and Node.js / TypeScript / Postgres – not just comfortable, but fast
AI coding tools (Cursor, Copilot, Claude) are already baked into how you work – you’re not planning to explore them someday, you’ve shipped with them
Something real you’ve built – a product, an open source project, a thing you couldn’t stop working on
You operate well with ambiguity. You don’t wait to be handed the answer.
You actually care whether the person on the other end of the screen has a good experience

Strong Candidates May Also…
You’ve touched federal, state, or local government tech – or you understand the constraints of building for regulated, high-stakes environments
Cloud deployment experience (AWS, Vercel, GitHub Actions, ECS/Fargate)
Exposure to design systems and component libraries – you know the difference between a component that’s functional and one that’s right
You’ve worked in an early-stage environment where figuring it out was the job