Tocka A.

Have an idea or a prototype that needs to become real software? Or a platform that's getting slow and fragile as you grow? You don't just need someone to write code. You need a full stack developer who works as your technical partner: someone who cares where your business is heading and owns the result from the first version through launch and into growth. That way your users get software they can rely on, and you get a product that doesn't need a rewrite the moment your customer base starts to grow. Here is the scale my team and I have worked at in production: ✔️ 40M+ orders from 1.4M+ active customers on a grocery delivery marketplace, with 20M deliveries in 2026 so far ✔️ 5M+ requests a day on each of two telecom systems (Etisalat and Vodafone) ✔️ 8,000+ deliveries a day across 100+ delivery hubs and 1,000+ active shops on a fleet management platform, with live driver tracking ✔️ 10+ major warehouses serving 5,000+ businesses across 3 countries on a warehouse-as-a-service platform ✔️ 12+ years of production engineering, backend and frontend ✔️ 4.9/5 rating across 8 rated Upwork contracts I'm a Full Stack Developer and SaaS Developer, and I lead the team that builds your product. You'll always talk to me directly, never a middleman, and I'm the one responsible for the whole build, backend and frontend. WHAT HAPPENS FIRST Working together starts with a conversation about your business. Tell me how it runs today and what's been hurting most, in plain words, no brief or technical terms needed. Before anything gets built, you get a clear plan: what we'd build, how we'd structure it, and where we'd start. You see the approach and the trade-offs before you commit to anything. THE RIGHT TECHNOLOGY FOR YOUR PRODUCT On the technology, I'll recommend whatever fits your product best, and I'll explain why: ✔️ For most new products, that means Node.js with Express.js on the backend and React with Next.js on the frontend, which gets you in front of users quickly ✔️ If you expect heavy traffic or your business rules are complicated, we go with Spring Boot in Java or Kotlin. Java is behind our telecom systems, at 5M+ requests a day Under the hood, we use the same architecture and infrastructure we've relied on at scale: microservices and event-driven systems only where they help, microfrontends for larger interfaces, and AWS or GCP with Docker and Kubernetes to run it all. In my experience, products rarely struggle on launch day. They struggle when the customers arrive. So I design yours from the first version to stay fast and reliable when they do. WHAT YOU KEEP WHEN WE'RE DONE Your product will keep evolving long after our project ends, so I make sure you're ready for that. You get documented code, tests, and a walkthrough, so your team or the next developer you hire can pick it up without starting from scratch. You're welcome to keep working with me, but you should never feel stuck with me. WHAT IT'S LIKE TO WORK WITH ME On a project at Etisalat, the technical requirements were hard to reconcile and the deadline was very tight. When we delivered, the client told me: "I knew you would not stop until you reach THE solution, not any solution but THE solution." That's what I mean by owning the result. YOUR NEXT STEP Send me a message with two or three lines about what you're running today and what's been frustrating you. You don't need a perfect brief, just tell me in your own words. We'll set up a free, no-obligation consultation here on Upwork, talk it through, and see whether we're a good match. If we are, we'll take it from there. If I'm not the right fit, I'll tell you that too.