Eine vollständige Bewerbung in einer Minute
Maßgeschneiderter Lebenslauf und Anschreiben – versandbereit.
dynamism in San Francisco is hiring a Full-Stack Engineering Lead for Public Works to own the customer workflow, from design to production, and to guide a small, skilled team.
You will ship map and asset workflows using React, TypeScript, Mapbox, and Express, connecting imagery and GIS data to clear product views while setting robust tests and release practices. equity offered.
Full-Stack Engineering Lead, Public Works
Base salary: $175K to $250K plus equity
Location: San Francisco, 4 days in person | Full time
Build software a public works team can use from the street to the budget meeting. In Boone County, Kentucky, a team reported finding streets and exploring the data within minutes. In Port Lavaca, Texas, the platform has supported capital improvement planning. Your full-stack work would connect those everyday interactions to decisions that shape public infrastructure.
We are hiring for a company building the operating layer for the infrastructure cities maintain. Roads are the starting point: imagery, vehicle data, GIS records, engineering documents, and local knowledge become a living map of assets and their condition. Public works teams can use that evidence to plan capital, explain priorities, and manage work. The longer ambition reaches sidewalks, drainage, signs, bridges, and other public assets.
The product has customers, revenue, and funding, while the engineering choices that define the next phase are still open. You would join a world-class engineering team that includes a founding software engineer formerly at Brex and a machine learning engineer formerly at X, Google's moonshot factory.
Own a complete customer workflow, from interaction design through frontend, backend, data model, release, and production support. You will lead technical choices while continuing to build alongside a small, experienced team.
The interface must make uncertain road data understandable to people under real operational pressure. The backend must preserve source context and support workflows that differ by city without turning every deployment into custom software.