Netic is the AI revenue engine for essential services who are the backbone of the American economy.

With $43M in funding from Founders Fund, Greylock, Hanabi, and Dylan Field who led our Series B, we helped our customers book hundreds of thousands of jobs across services industries in North America. There are now companies operating entirely AI-first on Netic.

You'll join our team with relentless builders from Scale, Databricks, HRT, Meta, MIT, Stanford, and Harvard in bringing frontier AI to the physical economy, where the problems are hard, the data is complex, and the impact is immediate and tangible.

As a Founding Product Infrastructure Engineer, you'll own and evolve the backbone that powers our autonomous AI agents in production. What makes this role different at Netic is the shape of the problem. You are not building infrastructure for a single product or a single industry. You are building a shared foundation that must support very different workflows and traffic patterns across multiple verticals. Some requests are low latency and real time. Others are long running, stateful, and failure prone. The same system needs to handle spikes, partial failures, and external dependencies without becoming fragile or hard to reason about.

You'll work closely with product and application engineers to make infrastructure a force multiplier: fast to change, reliable under load, and designed with clear tradeoffs. If you enjoy building systems from first principles, operating them in the real world, and setting standards others will build on, this role is for you.

What You'll Do

• Define deployment and environment strategy
• Own databases and performance at scale
• Raise the operational bar
• Plan for growth, not just today

What You'll Bring

• Strong infrastructure foundations
• Infrastructure automation expertise
• Database and performance judgment
• Observability fluency
• Security and reliability awareness
• Product-minded infrastructure thinking
• Live to build
• Run through walls and win
• Obsess over customers in each line of code
• Lose sleep over the "almost perfect"
• Show internal locus of control
• Prioritize finesse: refinement of first principles thinking, execution, and craftsmanship