Don’t send a generic resume — generate a resume and cover letter tailored to this exact role.
Underdog seeks a Platform Engineer to own data ingestion, AI workflow orchestration, and core platform primitives. You will enable scalable, auditable pipelines powering government-focused products, while collaborating with a founder on architectural decisions.
Expect to work hands-on with backend systems in Python/Node.js, maintain security and compliance by default, and contribute to a growing, equity-rich early-stage environment. On-site in Flatiron, NYC; US citizenship required.
A venture-backed, early-stage software company is building AI-native operating software for state and local government. Founded by a repeat founder following a successful exit, the company is already generating meaningful and accelerating revenue.
State and local government is a $100B+ software market that modernization largely skipped. Legacy vendors designed their systems for Fortune 500 enterprises. Defense-oriented platforms were built for agencies with effectively unlimited budgets. Meanwhile, thousands of counties, municipalities, school districts, and utilities deliver essential public services on infrastructure that predates the commercial internet. This team is building the platform those agencies should have had all along.
This is a foundational engineering role, not a feature assignment. The Platform Engineer owns the layer everything else is built on: data ingestion pipelines, the AI workflow orchestration engine, and the configurable primitives that hundreds of downstream products depend on.
Those downstream products are assembled by Forward-Deployed Product Managers who embed directly with city and county teams — a pretrial release system for a county court, a helpdesk for a school district, an operations dashboard for a municipal water utility, a lightweight ERP for a mid-sized city. The FDPMs configure and ship those solutions. The Platform Engineer makes that possible.
The problems are genuinely unsolved. How does a modern platform pull clean, reliable data out of a mainframe that has been running since the Reagan administration? How do multi-step AI workflows stay auditable enough for a public agency to defend them in a records request? How do primitives stay expressive enough to model any government process while remaining simple enough for a non-engineer to build on?
Whoever answers those questions well will shape how government software works for the next decade.
Experience building developer platforms or internal tooling; devops and infrastructure depth; agentic AI orchestration; or prior work in a regulated environment such as healthcare, financial services, or legal.