Product Engineer

CreditBooster.ai's mission is to help every American understand, build, and own their credit. We're an AI-native credit improvement platform, live on the App Store and Google Play, with paying customers and a small remote team across the US and Europe.
 

About the role

We're hiring for a mindset more than for a stack: the engineer who treats a piece of the product as theirs and holds themselves to whether it actually works for the person using it.

That means ownership that follows the experience wherever it lives. A flow starts on a mobile screen, continues on the web, and runs through the API behind both, and we want someone who goes all the way down rather than stopping at a repo boundary. That's usually where the quality of an experience is won or lost.

AI is not a slogan here, it's how we build. Our designer shipped the referral page that's live in production today working with an agent. Our CPO built one of our web apps the same way. The standard we hold ourselves to is not handing a ticket to an agent and approving the result: you plan with it, read the plan properly, push back, iterate, and stay responsible for what ships.

We move fast and we're deliberately not over-gated, even in fintech. Freedom to move, judged on results.

Fully remote, with morning Chicago overlap for standups and demos. Our working overlap is only about four hours a day, so being genuinely effective asynchronously matters here. We'd rather say that plainly than have you discover it in month two.
 

Responsibilities

• Own a product surface end to end: the mobile screen, the web equivalent, and the API behind both, with accountability for whether it works and not just for whether it shipped
• Ship across React Native (Expo) on iOS and Android, our web app, and our Astro landing site
• Cross the boundary rather than filing a ticket at it: Node.js, Fastify, TypeScript, and PostgreSQL are within reach when the surface you own needs them
• Hold the quality bar on what you own, from symptom to root cause to a fix you can prove held
• Use Claude Code, MCP servers, and your own agents to compress engineering work that used to take days into hours, while staying responsible for everything that merges
• Manage releases across App Store and Google Play: EAS builds, rollouts, OTA updates
   

The kind of work you'll see in your first sprint

• Taking one user-facing flow end to end and coming back with your own read on where it should be better, across mobile, web, and API
• A recurring production bug traced to root cause rather than patched at the symptom
• A view on the React Native versus native question, argued from the codebase rather than from preference
   

What we're looking for

• You've owned something, not just contributed to it. You can point at a surface in a product and say it was yours, describe what would have gone wrong without you, and separate what you owned from what your team delivered. This is the single thing we're screening hardest for
• You work across mobile and web. React Native is the centre of gravity, but a surface that stops at the repo boundary isn't owned. You're comfortable in a web codebase and not helpless behind an API
• You're AI-native in how you build. Claude Code or an equivalent agentic CLI is part of your daily workflow. You've built your own skills, agents, or MCP servers that automate real engineering work. You see agents as your primary collaborator, and you can also tell us about a time one was confidently wrong and how you caught it
• You debug for real. You go symptom to root cause to verification, and you know the difference between a bug that stopped reproducing and a bug that got fixed
• You're not attached to a framework as an identity. We may move to Swift. We may not. Either way we want someone who argues it from the codebase and then commits
• You ship without waiting for a spec. Often there's a problem and an owner, not a written specification
   

You may be a good fit if you have

• 4+ years building product software, with real React Native (Expo strongly preferred) shipped to both the App Store and Google Play
• A product area you owned in production. Be ready to walk us through it: what it was supposed to do, what broke, what you changed, and how you knew things got better
• Real web experience alongside mobile: React or a modern web framework, in production
• TypeScript strict-mode discipline
• Enough Node.js and SQL fluency to fix the endpoint behind your own screen
• Effective written communication in English (B2 or higher). Our team works in Russian and Ukrainian internally, but Linear, code, and customer-facing copy are English
   

Bonus

Native iOS in Swift or SwiftUI. Fintech, lending, KYC, or other regulated-domain work. Expo EAS pipeline ownership and store release experience. Astro or comparable modern web frameworks. A public Claude Code skill, MCP server, or contribution to an open-source agent harness. Founding engineer or first-few-hires experience at a small company, where owning the whole thing was the default.