Product Engineer; FDE

Note: Partly is headquartered in Austin, TX with offices in London, UK, Christchurch, NZ and Auckland, NZ. Wherever you're based, we'll connect you with your nearest office for onboarding, and fly you to join the full team for our quarterly "Season Openers" (we cover travel and accommodation). If you're relocating to join us, we can also assist with relocation costs.

Partly is building the infrastructure for anyone to repair anything. We believe everything built should be repairable, and we're building frontier AI to put repair knowledge to work, starting with the $2tn automotive market.

Our model, Interpreter, is the first AI purpose-built to understand repair. Trained on 1M+ car models and 1B+ parts, it reads a repair job the way an estimator does, resolves damage into the exact purchasable part, and shows its reasoning with a confidence score. On real production jobs, an estimator working with Interpreter reaches 98.8% parts-list accuracy, against 92.1% with today's tools.

It powers Partly Repair, used by collision shops, workshops and suppliers to take the admin off the job;
Partly Labs, the agentic infrastructure enterprises use to deploy Interpreter across their own workflows; and a developer API.

Founded by ex-Rocket Lab engineers, we've raised a $50m Series B led by DST Global (Anthropic, Airbnb, Meta, Tik Tok, Spotify), with Blackbird Ventures, WNDR, Activant Capital, Icehouse Ventures, Square Peg, Airtree and Ecliptic Venture Capital. Hear it from the team:
Why Partly exists and AI at Partly .

Build, not just specify. Prototype new product iterations yourself using AI-assisted and LLM-assisted tooling—fast, disposable, real. Treat the prototype as the hypothesis and put it in front of real customers before writing the spec. Ship production code, instrument it, and watch how it actually gets used.

Stay close to customers. Spend time where the work happens. Understand what estimators, parts managers, and others actually do, where they lose time, and what "better" would feel like. This is a core weekly activity, not an occasional input.

Reconcile signal. Combine what you see with what the data says, and reconcile the two when they disagree. Turn that understanding straight into what you build next.

Own the outcome. Steer by your surface's metrics; adoption and value delivered are yours. Make the call on priority and explain the reasoning, especially when the answer is no. When something is broken, own it, diagnose it precisely, and fix it.

Make the trade-off. Weigh product impact against engineering effort in the same breath, and find the cheaper path to the same outcome.

Build the agentic experience. Move your surface from manual operation toward supervised delegation: capture intent, decide where the human stays in the loop, and earn trust step by step so users never lose the thread of a high-stakes job.

Hold the craft. The surface feels fast, clear, and considered. You push back when something doesn't feel right, even when it technically works.

Raise the bar. Pair with SW Engineers on the harder systems work behind your surface, and contribute beyond your boundary: shared components, product craft, and what excellent building looks like here as the team grows.

You ship end to end: A track record of taking features from idea to production, code included, with clear accountability for whether they worked. Roughly 3+ years building and shipping software in production.

Genuine customer obsession: A real habit of spending time with users in their work context, with a track record of that depth driving what you build.

Product taste and craft: The bar is experiences that feel effortless to time-pressured, non-technical users across fragmented, high-stakes workflows.…