Product Engineer
Design the surfaces operators actually trust — where the model's work shows itself.
The role
You will build the product layer that sits between our models and the operators who use them. The decision surface, the citation UI, the abstention experience, the explanation that a regulator can read months later. You write the code, you talk to the operators, and you own the resulting interface.
About Neuralcraft
In regulated work, the product surface defines the model. Latency budgets, abstention behavior, citation density, override flow — these are product decisions, made before training starts.
This role is for someone who can sit with an underwriter, a clinician, or an auditor for an afternoon, then come back and ship the right surface. You're as comfortable in a customer's claims tool as you are in TypeScript.
What you'll do
- Design and build decision surfaces — citation-grounded panels, explanation layouts, abstention flows, override paths — inside customer applications and as standalone tools.
- Define the product contract for each engagement: latency budget, accuracy threshold, when the model is allowed to abstain, what an explanation must contain.
- Run customer interviews and shadow operators in their existing tools. Translate that fieldwork into product specs and shipped UI.
- Own the front-end stack: SvelteKit, TypeScript, design system. Write maintainable, accessible, fast code; mentor on it.
- Work alongside modeling and evaluation — every product decision implies a model decision, and you should be able to argue both sides.
What we're looking for
- 5+ years building production web applications. Strong TypeScript and one major framework (Svelte, React, Vue) at depth.
- A track record of shipping product into operator-facing or internal-tool environments — not just consumer surfaces.
- Design literacy. You can read a Figma file, push back on a spec, or build the UI directly when needed.
- Customer-facing range. You can hold a discovery interview and translate it into a build plan without losing the thread.
Bonus
- SvelteKit (we use Svelte 5 + runes).
- Background in regulated, operator-heavy software (claims tooling, EMR, audit, casework).
- Comfort with AI-product specifics: streaming responses, calibrated confidence display, citation rendering, abstention UX.
- Design background, even informal — past time as a designer, contributions to a design system, or strong opinions on density and information design.
How we hire
- 01 Intro call 30 min with one of the founders.
- 02 Product conversation 60 min walking through a real customer surface. We ask how you would design it. Bring screenshots, sketches, or words.
- 03 Paid work trial 1–2 days, paid at market rate. Ship a small but real piece of UI on a sanitized engagement.
- 04 Founder-team conversation 90 min with both founders.
- 05 Offer Within 48 hours of the final round.
How to apply
Hit the button below and you'll land on a short form where you can upload your CV and add a few links to work you'd point us at — a paper, a system you shipped, a write-up. No cover letter required.
- 01 Click every link. Open each project, paper, repo, or write-up linked from your CV and confirm it resolves to the right page. Broken links and dead deploys are the most common reason a strong CV gets passed over.
- 02 Verify your contact details. Email, phone number, location, and the best handle to find you on (LinkedIn, GitHub, X, your own site) — make sure each one is current. We will use exactly what's on your CV to reach you.
- 03 Name your file properly.
FirstName-LastName-CV.pdfis enough. PDF only, under 10 MB.
We reply to every application within five working days, including the ones that aren't a fit.