Full-Stack Engineer for SaaS Billing System
Budget: $30 – $250 USD
We are looking for an experienced full-stack developer to help us debug and stabilize a subscription billing issue in our SaaS platform.
Our product is a learning and onboarding platform (B2B SaaS) that recently gained its first paying customer. However, we’ve encountered a critical issue in the payment/subscription flow where a user may have been charged multiple times.
We need someone who can quickly understand the codebase, identify the root cause, and help ensure the billing system is reliable and production-safe.
Current situation:
- Live SaaS platform with working core functionality
- First paying customer acquired via Stripe-based subscription flow
- Suspected duplicate/multiple charges on a single subscription signup
- Likely cause: webhook handling, idempotency, or session state mismatch
- Codebase is early-stage (monorepo, not yet fully decoupled)
What we need help with:
- Audit the Stripe subscription and webhook flow end-to-end
- Identify why duplicate charges are occurring
- Fix webhook/event handling and ensure idempotency
- Stabilize the full subscription lifecycle (create, renew, cancel, retry)
- Suggest minimal architectural improvements only where needed, no over-engineering
Tech stack:
- React (frontend)
- Node.js (backend)
- Stripe (subscriptions and payments)
- GitHub-based workflow (PRs, issues, branches)
Ideal candidate:
- Strong hands-on experience with Stripe billing and subscriptions
- Has shipped SaaS subscription flows to production before
- Understands webhook architecture and idempotency patterns
- Comfortable moving fast in an early-stage codebase
- Communicates clearly and works async-friendly
Nice to have:
- Experience with B2B SaaS or multi-tenant systems
- Interest in longer-term collaboration, we are actively scaling this platform and the right person could grow with it
This is a pragmatic fix first, not a rewrite. If you have debugged Stripe webhook issues before, you will feel right at home.
Our product is a learning and onboarding platform (B2B SaaS) that recently gained its first paying customer. However, we’ve encountered a critical issue in the payment/subscription flow where a user may have been charged multiple times.
We need someone who can quickly understand the codebase, identify the root cause, and help ensure the billing system is reliable and production-safe.
Current situation:
- Live SaaS platform with working core functionality
- First paying customer acquired via Stripe-based subscription flow
- Suspected duplicate/multiple charges on a single subscription signup
- Likely cause: webhook handling, idempotency, or session state mismatch
- Codebase is early-stage (monorepo, not yet fully decoupled)
What we need help with:
- Audit the Stripe subscription and webhook flow end-to-end
- Identify why duplicate charges are occurring
- Fix webhook/event handling and ensure idempotency
- Stabilize the full subscription lifecycle (create, renew, cancel, retry)
- Suggest minimal architectural improvements only where needed, no over-engineering
Tech stack:
- React (frontend)
- Node.js (backend)
- Stripe (subscriptions and payments)
- GitHub-based workflow (PRs, issues, branches)
Ideal candidate:
- Strong hands-on experience with Stripe billing and subscriptions
- Has shipped SaaS subscription flows to production before
- Understands webhook architecture and idempotency patterns
- Comfortable moving fast in an early-stage codebase
- Communicates clearly and works async-friendly
Nice to have:
- Experience with B2B SaaS or multi-tenant systems
- Interest in longer-term collaboration, we are actively scaling this platform and the right person could grow with it
This is a pragmatic fix first, not a rewrite. If you have debugged Stripe webhook issues before, you will feel right at home.