Product Engineer

bule.ai is real-time English conversation practice. You talk, and a tutor hears you, sees you on camera, and replies like a patient teacher who remembers you from last time. Under the hood it is a live voice pipeline: speech recognition, a language model that also looks at your camera, then text to speech, running on a GPU and wired together over WebRTC.

People study English for years and still freeze when they have to speak it. The missing piece is not grammar, it is practice with someone patient who will not judge you for pausing mid-sentence. Real tutors are expensive and hard to schedule. A tutor that is always available, remembers last week, and waits while you find the word turns speaking practice into something you do daily instead of something you save up for.

You would be the only engineer on it. Not the second engineer, not part of a team. You pick things up, decide how to build them, and ship them, and most days you will not be waiting on me.

The codebase is small, roughly 17,000 lines across a Next.js web client, a Python voice agent, native iOS and Android apps, and some Terraform. You can hold all of it in your head inside a week.

The surface is wide. In one month you might write Python for the voice agent, TypeScript for the web app, Swift or Kotlin for mobile, and touch some infra. I do not expect you to be an expert in all of it. I expect you to be quick at picking up whatever the task needs.

1. 1Ship subscriptions: payments, plans, the whole flow, end to end.
2. 2Ship the paid features that sit behind them.
3. 3Launch one mobile client. iOS or Android, your call after you look at both.

That is an aggressive month, and I would rather say so than pretend otherwise. After that we decide together what comes next. I want someone who argues with me about the roadmap.

• You have shipped something real. Not a tutorial project. Something people who are not your friends actually used.
• You can architect complex software. Agents write most of the code now. Deciding what to build, how the pieces fit, and which tradeoffs to take is the part that is still yours, and it is the part I am actually hiring for.
• You think about the product, not the ticket. When I describe a feature, I want you to tell me why it is the wrong one.
• You get a lot done with tools like Claude Code, Codex, or Cursor. Not autocomplete. Real working sessions where features come out the other end.
• You have gone from an empty repo to something launched, more than once.
• You write clear English. You will read and write docs in it daily, and you will need real opinions about whether the tutor sounds natural.
• You care about language learning, or you are at least curious why someone would build this.

Not what I am looking for: someone to hand tickets to. What exists is written down in ADRs so you will not be guessing, but everything after that is yours to design. I will have opinions. I will not have time to make every call.

Unusual freedom for a role at this rate. A product with real users that you can point at for the rest of your career. Almost no process, one person to talk to, and no meetings that could have been a message. If you have been waiting for a chance to run a product mostly on your own, this is one.