Senior Software Engineer

• We are rethinking how that software should work when AI is part of the product and part of how the product gets built, and the engineering pod you would join is at the center of that work
• You will join a product engineering pod as a developer. The pod is small and senior, and works inside our Agentic SDLC framework: agent specs, orchestration workflows, reusable prompts, and eval harnesses that let a handful of engineers deliver at multiples of traditional velocity
• You will not be typing every line yourself. You will be directing, reviewing, and shaping the work of coding agents, then owning the result as if you had written it, because you are accountable for it either way
• This is a product engineering role. Your job is to ship products: features cities will use to issue permits, run inspections, and serve residents, delivered to the quality bar government software demands
• Ship product. Take features from spec through delivery in production, working within the pod’s agentic workflow. Own the outcome end to end: correctness, performance, security, and the experience of the person at the counter who has to use it
• Work agent-first. Write clear specs and acceptance criteria, direct coding agents to implement them, review the output critically, and iterate. Your leverage is judgment, not keystrokes
• Hold the quality bar. Government software is scrutinized differently than consumer software. You test what agents produce, you understand what you ship, and you do not merge what you cannot explain
• Improve how the pod works. Feed what you learn about the framework, the workflows, and the agents back to the pod and to the Applied AI team that owns the framework. Velocity is a shared asset; you help keep it high
• Learn the domain. Permitting, licensing, plan review, inspections, and the rules cities live under. The best engineers here understand why a workflow exists before they change it
• How success is measured:
• 90 days: you understand the codebase, the pod’s agentic workflow, and the permitting domain well enough to take features from spec to production without close supervision, at the pod’s quality bar and without slowing the team down. You are shipping at the pod’s average throughput: not a first feature or two, but a steady stream of production features every week, at the same pace and quality as the developers who were here before you
• 12 months: you are a dependable owner of meaningful parts of the product, trusted to take ambiguous problems from a customer conversation through to a shipped, well-tested feature. Your specs and reviews raise the quality of the pod’s output, and you have made at least one lasting improvement to how the pod works, not just what it ships

Benefits

• Flexible Work Culture
• Professional Development
• Team Building Events/Outings
• Motivated Team
• Corporate Bonus Plan

• Real experience building with coding agents and AI-assisted development tools, and a clear-eyed view of what they are good at and where they fail. You have shipped production code this way, not just experimented
• The habit of reading and understanding what you ship, including code you did not type. You verify; you do not assume
• 7+ years as a software developer shipping production web applications, with deep fundamentals in API design, data modeling, testing, and cloud infrastructure
• Comfort with pace and ambiguity. The roadmap is ambitious and the pod moves quickly
• Strong written communication. In an agent-first pod, the quality of your specs determines the quality of the code
• Experience in government, civic, or other regulated software, where auditability and accessibility are requirements rather than preferences
• Experience with eval-driven development or building evaluation harnesses for AI-generated code
• Experience with permitting, land management, or community development systems, or with the operations of a municipal government