🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
About the Company 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. The Opportunity 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. What the Role Involves Ingestion and data modeling. Designing and owning the connectors, pipelines, and normalization layer that turn mainframe exports, Oracle databases, flat files, and proprietary vendor APIs into a consistent, queryable foundation. AI workflow infrastructure. Building the machinery behind long-running, multi-step agentic workflows — task queuing, state management, retry semantics, human-in-the-loop approval gates, and the audit trails public-sector compliance demands. Core platform primitives. Building and maintaining the workflow engine, role-based permission model, form and action framework, and event system that let a non-engineer stand up a permitting portal or case management tool without rebuilding the plumbing each time. Security and compliance by default. Treating tenant data isolation, granular access control, and end-to-end auditability as first-class platform features, with a deliberate path toward FedRAMP, CJIS, and HIPAA certification as the company scales. Architecture with the founder. Partnering directly with the CEO on decisions that compound across every deployment the company ever ships. What the Team Is Looking For A track record of building. Real systems, taken from blank page to production, ideally under real constraints. Portfolio and shipped work matter more than pedigree. Strong backend fundamentals in Python and/or Node, with sound judgment around data modeling, API design, and building systems that remain reliable and extensible as requirements shift. Enough frontend capability to build and reason about an interface, even though this role will not own the UI. Daily, hands-on use of AI coding tools — Claude Code, Codex, Gemini CLI, Factory, or similar — as a genuine part of how the candidate works, not an occasional experiment. Good instincts for abstraction: knowing when a pattern deserves to become a platform primitive and when it should just ship. US citizenship, required for government work. Willingness to work on-site in Flatiron five days per week. Nice to Have 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. This role sits on a small, in-person engineering team in Flatiron. Compensation includes a base salary plus meaningful early-stage equity.
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.