CreditBooster.ai’s mission is to help every American understand, build, and own their credit. We’re an AI-native credit platform, live on the App Store and Google Play, with real paying customers and a small remote team across the US, Europe, and now the Americas.
About the role
This is the seat that anchors our engineering day in the Americas.
Our backend runs on European hours today. We want the product covered across a much longer working day, so that a production issue at 3pm Chicago has an owner who is awake, and so that work moves while the other half of the team sleeps. You’d own that side of the clock.
That means real autonomy, not a night shift. For most of your day you’ll be the senior backend engineer on duty: you’ll make the call, ship it, and hand off cleanly. We’re looking for someone comfortable being the most senior person online for a stretch of the day, who writes things down well enough that the handoff actually works.
It also means a platform flavor, not just feature work. Centralized logging, monitoring, alerting, and notification infrastructure are part of this seat. We are past the point where a small team can run on hope and a message in chat.
AI is not a slogan here, it’s how we build. Our designer shipped the referral page that’s live in production working with an agent. Our CPO built one of our web apps the same way. The standard 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.
The kind of problems this seat owns
Long-running processes that have to survive. Significant parts of our backend are not request and response. They are processes that run for weeks, depend on outside parties answering on their own schedule, and where the outcome of one step determines the next. They have to be resumable, idempotent, and survive a deploy in the middle. We orchestrate this on AWS Step Functions. If your instinct for “this takes three weeks and can fail at any step” is a cron job and a status column, this role will be uncomfortable.
Third-party integrations where the vendor is the unreliable part. We depend on external providers for regulated data and for delivery into the physical world. Payloads are messy, contracts change under you, and failures are quiet rather than loud. Building the layer that makes an unreliable dependency safe to build on is a large and permanent part of this seat: error taxonomies you can act on, reconciliation between our state and theirs, and detection when something silently never completed. This is the thing we talk about most.
Centralized logging, monitoring, and alerting. We’re consolidating observability onto PostHog, with Sentry on errors, and building out alerting properly: service outages, volume anomalies, and the silent failures that today only surface when a customer writes in. Making those loud is part of the job.
Notification infrastructure. A real event model with types, priorities, batching, and dedup, across push, email, and in-app. This is infrastructure, not a feature.
LLM work with an actual job to do. We run on AWS Bedrock, replacing deterministic logic with model-backed logic where it earns its place. This is not chat: it’s structured output, validation, and evaluation on data that has to be right, in a regulated domain where a fabricated claim is a compliance problem rather than a polish bug.
Payments and subscriptions. RevenueCat across the App Store and Google Play, entitlement webhooks, and the reconciliation nobody enjoys. Billing bugs are the ones users notice first and forgive least.
Email that actually arrives. Resend, with deliverability treated as an engineering problem: bounce rates, sender warm-up, segmentation.
Our stack
Core: Node.js 22, Fastify, TypeScript, PostgreSQL 17
AWS: Step Functions, Bedrock, EC2, RDS, S3, ECR,
