Product Engineer (Contract)

There is a working product. There is one founder. There is no team yet.

The product needs someone to take it the rest of the way finish the build harden it test it put it in front of the first real users and stay close enough to those users to know what to fix next.

Thats the job. It is not a well-defined ticket queue. Its closer to: here is the thing here is what done means go.

This is a paid contract role. Were paying for your time and your expertise and we expect to pay properly for both.

What were building

An orchestration layer that sits above the frontier AI models Claude GPT Gemini and coordinates them rather than picking one.

It is aimed at people whose work product is judgment where being wrong is expensive and the AI said so is not an acceptable answer.

Where things actually stand

• The core product works end to end.
• Theres a real documentation and decision-log discipline in place architecture invariants contracts a decision record going back months git hooks enforcing some of it. You will not be reverse-engineering a mystery.
• There are known open bugs known unfinished surfaces and a UI that needs an aesthetics pass.
• It has never had a user who wasnt the founder.

The gap between works and someone else can use this without me sitting next to them is the gap youre being hired to close.

What youd own

Phase 1 Close it out (first weeks)

• Finish the remaining feature work; hide or cut what isnt ready
• Aesthetics and UX pass it needs to feel like a product not a prototype
• Fix the open bug list; expand test coverage
• Security hardening pass ahead of real users (external review budgeted separately youll work with it not carry it alone)

Phase 2 Alpha

• Ship it to real users
• Onboarding: get people from signup to first genuine use without hand-holding
• Support them directly. Youll be answering the emails. This is a feature of the job not a chore attached to it.
• Instrument it enough to know what people actually do versus what they say they do

Phase 3 Beta and beyond

• Turn alpha behaviour into the beta roadmap
• Help make the call on who this ships to first: individual professionals small firms or enterprise
• Build the systems and documentation that let a bigger team pick this up later

Stack

• Frontend: vanilla JS HTML CSS a single-file monolith no framework. Deliberate. Itll be broken up when theres a reason not before.
• Backend: Supabase (Postgres auth storage)
• Hosting: Netlify deploy on push
• Provider APIs: Anthropic OpenAI Google
• Node for tooling and tests

If you need a framework to be effective this isnt your project. If reading 5000 lines of someone elses JavaScript and immediately knowing where the bodies are buried sounds fine keep reading.

Who were looking for

Someone who uses both sides of their brain.

One side reads code carefully. Spots the branch that swallows an error without telling anyone. Doesnt trust a function just because of its name. Can hold the whole system in their head and work out what a change will break three files away.

The other side thinks about the person on the other side of the screen. Why they gave up at step three. Which feature theyll ask for and never use. What would make them tell a colleague about this.

Most people are good at one. We want someone who is genuinely strong on the code side and has real instinct for the user side someone who can look at a screen and say this works and nobody will use it and be right.

Hard requirement: you have shipped something real inside an agentic coding harness.

We mean you have worked inside Claude Code Cursor Codex Aider or something equivalent as your main development environment and something you built that way exists runs and has been used by someone other than you. You know how these tools fail. You know what theyll confidently get wrong. Youve built your own habits around checking what they produce because youve been burned by not doing it.

Using AI to look things up or to explain code is not the same thing and isnt what were asking about.

And you finish things. One small project that shipped got users and was supported for months tells us more than ten impressive repos that stopped at 80%. Were being direct about this because the failure mode of this role is a beautiful elaborate unlaunched product.

What we are not asking for

• A degree or a degree in progress or a degree completed
• A specific number of years. Second-year student and twenty-five-year veteran are both entirely welcome and will be assessed identically.
• A recognisable logo on your CV
• Deep security or infrastructure specialisation thats brought in as expertise where its needed
• Prior startup experience

The founder covers strategy product direction positioning and go-to-market. Whats missing is build capacity and someone who owns getting it in front of users.

Qualifications :

Hard requirement: youve shipped something real inside an agentic harness Claude Code Cursor Codex Aider. As your actual dev environment not as a lookup tool. And someone other than you has used what you built.

Dont care about your degree your years or your logos. Student or twenty-year veteran same bar.

Stack: vanilla JS single-file monolith Supabase Netlify. No framework. If that sounds fine we should talk.

Full-time 40 hours a week remote with overlap into US morning or evening hours. Two months to start with the possibility to continue.

To apply send me one thing you shipped with an agentic harness whether anyone else ever used it and in five lines the first three things youd do with a working product and zero users.

Send an email with:

1. One thing you shipped using an agentic coding harness. Link to it live if possible. Tell us which harness what it got wrong and how you caught it.

2. Whether anyone other than you ever used it  how many people for how long and what broke when they did.

3. Five lines no more: youve just been handed a working product with zero users. What are the first three things you do

4. One thing youve killed. A feature a project an approach youd invested real time in and cut anyway. Why.

No cover letter. No CV unless you want to send one. Were reading for judgment not formatting.

Shortlisted candidates get a full walkthrough of whats been built followed by a coding interview.

Additional Information :

Terms

• Engagement: Contract
• Commitment: Full-time 40 hours per week
• Duration: 2 months starting immediately with the possibility to continue
• Location: Remote. Overlap with US morning and/or evening hours required.

Remote Work :

Yes

Employment Type :

Contract