Founding Engineer, Platform

Job Description

About Synthetiq \n

Synthetiq is a platform for building production software from a conversation. Business users describe what they need; we generate full-stack apps connected to their data, running on their infrastructure, with enterprise access control built in. 

\n

Each organization builds up its own internal app store, with every app on the same stack, sharing auth and access control, deployable in one click. And because every app is also an API and MCP server, the apps customers build today become building blocks for the ones they build tomorrow.

\n

Founded by the team behind BenchPrep, AdBasis (acquired by Airbnb), and Evergage (acquired by Salesforce).

The Role \n

We're building application frameworks from the ground up so AI agents can produce reliable production systems that non-engineers can trust without reviewing code. As a founding engineer, you'll work directly with the founders to shape the platform that makes this possible.

\n

You'll work across the full stack: our App, Service, and Workflow Frameworks (our novel approach to building production-ready applications with AI), platform APIs, data connectivity, app composition and deployment pipelines, our desktop application, and MCP server infrastructure. You'll write code, make architectural calls, and talk to customers.

\n

What We're Looking For

\n

\n
• 10+ years in software engineering, including 2-4 years with system-wide architectural scope.
\n
• Experience building platforms where extensibility, composability, and multi-tenancy were first-class concerns. Bonus points for designing composable frameworks, application infrastructure, and APIs with enterprise-grade security and access control.
\n
• Hands-on experience with LLMs in production: ie code generation, agentic workflows…etc, and familiarity with MCP.  You don't need to be an ML researcher, but you should understand capabilities and failure modes well enough to build reliably on top of them.
\n
• A track record of making good architectural tradeoffs under uncertainty, and the communication skills to explain those tradeoffs to engineers and non-technical stakeholders alike.
\n
• Comfort with the messiness of an early-stage product where the right answer often isn't obvious yet.
\n

Why This Role \n

As a founding engineer you will shape what gets built and how. You'll have direct input on foundational decisions like architecture, product, and what we ship and what we don't. This is an exciting problem space as the technology is genuinely new: there isn't a playbook for making AI-generated software reliable enough for enterprise production, and figuring that out is the job.

\n