Product Engineer
Full-stack · One-person product owner · AI-first workflow
Take a fuzzy product idea, design the screens, build the API, wire it all together, and ship something a real user can try the same day.
The essentials at a glance
We hire on demonstrated ability, not years of experience.
Role
Product Engineer (full-stack).
Location
Fully remote, async-friendly.
Seniority
Open — we hire on demonstrated ability, not years of experience.
Stack
Frontend: React or Svelte/SvelteKit, TypeScript. Backend: Go. Storage: Postgres / SQLite.
Reports to
Founder.
Hiring process
30-min intro call → take-home assignment (~8–12 hrs) → live code-review & product-discussion session → founder chat & offer.
A child-safe AI learning product
JurneeGo is building a child-safe AI learning product. We believe AI can be one of the most powerful learning tools ever made for kids — but only if it is built with care, with strong safety as a default, and by people who genuinely sweat the product details. We are early, well-supported, and moving fast.
A one-person-army role by design
We are looking for a Product Engineer who can take a fuzzy product idea, design the screens, build the API, wire it all together, and ship something a real user can try the same day. You will own features end to end — frontend, backend, the contract between them, and the small product decisions no PM is going to make for you. This is a one-person-army role by design: small team, large surface area, real ownership.
How we work
We use AI coding tools (Cursor, Claude Code, Copilot) as a core part of our development workflow. We expect you to use them too — and to be the engineer who reviews every line, owns the architecture, and can defend any file in the codebase. We are hiring people who use AI to go 3× faster without shipping code they don’t understand.
Own features end to end
Large surface area, real ownership — here is what the work looks like day to day.
Ship full features end to end
Design the UX, build the React or Svelte frontend, write the Go backend, deploy it, watch it work.
Make small product decisions on your own
We will give you the problem and the constraints; you choose what to build and what to cut.
Use AI coding tools as a primary workflow
Review every line, push back when the suggestion is wrong, and stay the engineer of record on the codebase.
Build with child safety in mind
Even when you are not working on the safety layer directly, every feature touches kids — defaults, copy, and edge cases all matter.
Help define the engineering culture as we grow
The patterns you set now will shape what the team looks like in twelve months.
Talk to users when it helps
Watch a kid use what you built. Adjust accordingly.
Builders with product taste
The must-haves we will dig into, and the nice-to-haves that help you stand out.
Must-haves
Own both frontend and backend in production
You should be able to point to features you have shipped end to end.
Strong frontend skills in React or Svelte, with TypeScript
Good instincts for component structure, state, loading and error states, and basic accessibility.
Solid Go on the backend
Clear code, sensible API design, thoughtful data modeling. (Strong experience in another typed backend language plus a willingness to ramp on Go quickly is acceptable.)
Demonstrated AI-assisted development
A real workflow with AI tools, not just casual use. You can talk concretely about prompts that worked, output you rejected, and how you keep AI from drifting your codebase.
Product taste
You notice when something feels off. You care about the difference between “works” and “feels good.”
Pragmatism
You can ship the 80% version, mark the rest as a tradeoff, and move on.
Comfortable working remotely
Strong written communication and a high degree of self-direction.
Nice-to-haves
Early-stage or solo-builder experience
Experience at an early-stage startup or as a solo builder of real products.
A high care-bar background
Background in education, kids’ products, or any consumer product with a high care-bar.
LLM familiarity
Familiarity with LLM APIs, prompt design, or basic safety/moderation patterns.
Light DevOps comfort
Docker, a CI pipeline, basic cloud deploy. We will not test you deeply on this, but you should not be afraid of it.
Design sensibility
You do not need to be a designer, but you should be able to make a screen look reasonable without one.
A few things we skip
So you know what not to worry about going in.
A specific number of years of experience
We have hired strong builders 2 years out of school and strong builders 15 years in.
FAANG-style algorithm interviews
We will look at code you have shipped and code you ship for us.
Deep ML or model-training experience
We are an AI product company, not a research lab.
Full ownership, real impact
Early hires shape the company — the patterns, the culture, and the bar all get set now.
Full ownership
You will not be the third frontend engineer working on someone else’s component library. You build it, you own it.
Real impact on kids
Education products that work change lives. Education products that go wrong cause real harm. Both directions are motivating.
AI-native by default
You are not retrofitting AI into your day. It is part of how we work, and we will give you the tools, time, and judgment to use it well.
Founding-team trajectory
Early hires shape the company. The patterns, the culture, the bar — all of it gets set now.
Fully remote, async-friendly
We hire adults who manage their own time.
How we’ll get to know you
Be ready to defend any file in the repo, line by line.
Intro call (30 min)
We get to know each other and you ask us anything.
Take-home assignment (~8–12 hrs)
A small full-stack product, built with AI tooling. You will have one week to submit.
Live review session (60–90 min)
We run your app together, walk through your code, and discuss your decisions and your AI workflow. Be ready to defend any file in the repo, line by line.
Founder conversation
Talk about the company, the next 12 months, and whether the fit is mutual.
Offer
If the fit is mutual, we make you an offer.
Send us a short email
Send a short email to aiden@jurneego.com with: a one-paragraph intro telling us why this role, links to anything you have shipped that you are proud of (a GitHub repo, a side project, a product you led), and — if you have one — a brief note on how you currently use AI in your development workflow. A CV is welcome but not required if your links speak for themselves.
We read every application. We reply to every application.
Ready to build a child-safe AI learning product?
Own features end to end, work AI-first, and help set the bar for the team. We read — and reply to — every application.