Olyad B.

Most backend developers build the happy path and hope. I build the part that decides whether your product survives real users: what happens when a payment webhook fires twice, a provider times out halfway through a transaction, or a background job fails at 3 AM and nobody notices. I am Top Rated with a 100% Job Success Score across 35 jobs, and I spent over a year as a software engineer, a production payment platform, where a failed integration means missing money, not just a bug report. That is the standard I bring to every client project. When you hire me, you get an engineer who takes ownership. I design for failure first, with idempotency keys, retries with backoff, dead letter queues and reconciliation jobs, so your system fixes itself instead of waking your team. I write tested code, give honest estimates, tell you early when something is risky, and hand over work you can maintain without me. My main stack is Node.js, NestJS, TypeScript and PostgreSQL, and I use Go when a service needs heavy concurrency or high transaction throughput, such as webhook processors, API connectors and background workers. On the cloud side I am AWS Certified (DevOps Engineer Professional, Developer Associate, Cloud Practitioner), and I ship and run systems on AWS with Docker, CI/CD on GitHub Actions, monitoring and automated backups. I can also review an existing AWS setup for cost, security and reliability gaps. I have delivered REST APIs, Stripe subscriptions, African mobile money integrations (M-Pesa, MTN, Telebirr, PawaPay, Flutterwave, Paystack), multi tenant SaaS backends with tenant isolation and audit logging, real time WebSocket systems, and AI features with OpenAI and Claude. I work best with fintech teams that need payment flows they can audit, SaaS companies whose API or background jobs have become a reliability problem, and startups adding payments, AI or real time features to a product that already has users. Have a payment flow that double charges, a webhook that drops events, or a backend that breaks under load? Message me the symptom and I will tell you where I would look first, before you decide anything. Include your stack, your timeline and whether this is a fix or a new build, and I can answer much faster. I reply within four hours.