Get more replies from employers
Send a job-specific resume in minutes.
Syntro is building the first agentic procurement platform for modern hardware manufacturing. We're looking for a founding engineer to help lay the technical foundation, decide how major parts work, and build systems that scale from prototype to production.
You'll own end-to-end systems across the stack, turn emails, quotes, ERP data into actionable context, and design reliable agents that can operate with uncertainty.
AI is walking, driving and flying into the physical world: humanoids, robotaxis, drones and a new class of autonomous machines. Each machine is built from thousands of parts. Sourcing just one still means trade shows, cold calls and endless scrolling on distributor sites. Supplier quotes land in a dozen formats, get re-keyed by hand into spreadsheets, and 100+ email threads follow just to confirm whether a part lands on time. It's 2026, and the most important machines of the next decade are still being sourced the way they were before the internet.
Syntro is building the first agentic procurement platform purpose-built for the realities of modern hardware manufacturing. We give manufacturers the ability to discover, select, and manage suppliers across the entire hardware lifecycle, from first prototype to production, at the speed and intelligence of AI.
We're an all-Stanford team that's experienced this problem firsthand at Apple, Dell, and Peloton. We're backed by Pear VC and Accel, alongside angels including Diane Greene (Founder, VMware) and Jeff Epstein (former CFO, Oracle).
We're looking for a founding engineer to help build the technical foundation of Syntro.
The context needed to make a procurement decision is scattered across emails, spreadsheets, ERPs, quotes, designs, and the heads of individual buyers. You'll build the systems that pull this together: giving teams visibility across their procurement operation, bringing in outside intelligence, and surfacing what needs attention next. Over time, agents will increasingly act on it directly.
This isn't a role where the architecture has already been decided and the roadmap has been broken into tickets. You'll decide how major parts of Syntro should work, build them, operate them in production, and change your mind when the first approach is wrong. You'll also help define how we build as a company: our engineering standards, infrastructure, technical decisions, and eventually the engineering team itself.
We're early enough that decisions you make now will still be visible in Syntro years from now.