Senior Platform Engineer (Founding Team)

About the Company

\n

Our client is an applied AI company rebuilding how civil, structural, and MEP engineering firms do their work. Their thesis is blunt: most of what a practicing engineer does today is theoretically automatable, and almost none of it has been touched by AI. The company is venture backed, the team is small, and the foundational technical decisions are still being made. This is their highest-priority engineering hire.

\n\n

The Opportunity

\n

Every engineering firm that joins the platform arrives with its own systems, identities, data sources, and workflows. Your job is to turn that variety into shared software, so the fifth firm comes online in days instead of the weeks the first one took. You will own the technical substrate everything runs on: the platform architecture, the backend services, the path from commit to production, and the operating practices that keep it reliable as the company scales.

\n\n

You will work directly with the CTO and hold real influence over architecture and engineering practice from day one. This is a backend engineering role that includes infrastructure ownership. This role is not a DevOps or SRE seat, and it is not an architecture-only position. You will write production code.

\n\n

Because collaboration is key to their culture, this role is 5 days a week in their NYC office.

\n\n

What You'll Own

\n

\n
• Platform architecture: design and evolve the shared platform across forward-deployed teams and partner firms, including tenant isolation, identity, permissions, integrations, APIs, and data flows.
\n
• Production software: write and review backend and platform code across services, internal tools, integrations, and the infrastructure surrounding them.
\n
• Delivery and developer experience: own the path from commit to production, including CI/CD, preview environments, testing infrastructure, local development, and repeatable release workflows.
\n
• Distributed systems and reliability: define service boundaries, failure modes, observability, incident response, and reusable patterns that make every new firm easier to onboard.
\n
• Technical direction: make pragmatic build-versus-buy decisions, establish engineering standards, and improve systems while the company is actively operating and growing.
\n
• Bespoke-to-platform leverage: identify which customer-specific solutions should become shared capabilities and prevent the platform from turning into disconnected consulting work.
\n
• Cross-functional execution: work directly with the CTO, forward-deployed engineers, and domain experts; troubleshoot production issues, unblock implementations, and occasionally travel when needed.
\n

\n\n

What We're Looking For

\n

\n
• At least 5 years of professional software engineering experience, with meaningful ownership of production systems. Actual level will be based on scope and judgment, not title alone.
\n
• Strong software engineering fundamentals and the ability to reason about architecture, distributed systems, APIs, data flows, security, reliability, and operational tradeoffs.
\n
• Experience operating systems in production and judgment shaped by real incidents, scale constraints, imperfect information, and competing business needs.
\n
• A record of broad ownership in an earlier-stage or high-growth company, ideally Series B/C or earlier. Founding, first-platform-hire, or Staff-level scope is especially relevant.
\n
• The ability to move between architecture and implementation: define the approach, write the code, debug the system, and improve the engineering practice around it.
\n
• High communication ability and EQ. You explain tradeoffs clearly, ask good questions, receive feedback without ego, and build trust across technical and nontechnical teams.
\n
• Comfort working on-site in New York City five days per week in a small, high-accountability environment.
\n

\n\n

Relevant Experience

\n

Helpful backgrounds include internal developer platforms, multitenant products, enterprise integrations, identity and access management, observability, applied AI, distributed backend systems, or customer-facing engineering.

\n\n

Strong technical judgment, systems thinking, and evidence of ownership matter more than experience with every tool in the current stack.

\n\n

What This Role Is Not

\n

\n
• It is not primarily Kubernetes, Terraform, CI/CD, or cloud administration.
\n
• It is not a ticket-based operations role focused only on keeping existing infrastructure running.
\n
• It is not an architecture-only position; the person in this seat will remain hands-on and write production code.
\n
• Kubernetes expertise, prior M&A integration experience, AEC industry experience, and exact stack match are not required.
\n

\n\n

Technology

\n

The current stack includes React and Next.js on the frontend, Kotlin for core backend services, Python for data and AI services, and multitenant infrastructure on AWS. These technologies are not key as judgment and ownership matter more than exact stack match.

\n\n

How the Team Works

\n

The team values people who are humble, hungry, and smart: low ego, intellectually honest, strong in judgment and communication, and motivated by ownership. The pace is urgent and accountability is high, but the culture is not built around extreme or unsustainable hours.

\n\n

Compensation and Benefits

\n

\n
• Expected base salary of $200,000-$300,000, depending on experience and scope.
\n
• Profit-interest equity participation with dilution protection.
\n
• Full healthcare benefits.
\n
• Direct access to the CTO and significant influence over platform architecture and engineering practices from an early stage.
\n

\n