Rakesh More
I build backend systems that handle real money and real concurrency — a multi-tenant Travel ERP at QTech, and two solo-owned production platforms of my own.
- Experience
- 7+ yrs
- Companies
- 2
- Domain
- Travel ERP
- Status
- Open to opportunities
About
7+ years building backend systems in PHP and Laravel — currently maintaining and extending a shared, multi-tenant Travel ERP platform at QTech Software, after six years progressing from frontend to Laravel to full-stack, client-facing delivery at Mirackle Solutions. Core strength is business logic that touches money and concurrency: booking flows, payment gateway integration, account/ledger systems, and the third-party integrations that connect them.
Outside of employment, solo-designed and shipped two production platforms — see Projects below. AI-assisted development (Claude Code) is part of the workflow: directed and reviewed a three-service build — a Laravel API, a Python face-recognition microservice, and a Vue PWA — public on GitHub.
Experience
QTech Software Pvt. Ltd.
2024 – Present- Maintain and extend a shared, multi-tenant B2B platform — resolving production issues without regressing other clients on the same codebase.
- Diagnosed and fixed a complex concurrency bug affecting a core account/rewards feature, using a temporary resource-hold pattern to prevent double-processing under simultaneous requests.
- Integrated a third-party payment gateway directly into a core transaction flow.
- Built internal automation replacing manual data-reconciliation work between systems.
Kept generic per employer confidentiality policy — no internal system or vendor names.
Mirackle Solutions
2018 – 2024- Years 1-2: frontend development (HTML/CSS/JS). Years 3-4: PHP, including WordPress theme build/conversion work. Years 5-6: blended Laravel and full-stack ownership of client projects.
- Delivered a high volume of small-to-medium client projects across 6 years — breadth across many engagements rather than one large system.
- Worked directly with India-based clients — gathered requirements and delivered without a PM/BA layer in between.
Skills
Projects
Freelance work, solo-owned end to end — architecture, development, deployment. Verified directly from each project's own codebase and documentation, not from memory.
StudioK3 Booking
booking.studiok3.us ↗Theater & live-event ticketing platform — seat selection, checkout, payments, e-tickets with QR check-in, for cultural performances across the US and India.
- Concurrency-safe checkout: 20-minute seat hold with DB transactions + row locking to prevent double-booking
- Discount/coupon engine that resolves conflicts by comparing savings and automatically keeping whichever is best for the customer
- General Admission bookings modeled as virtual seats — reused the entire seat-based pipeline instead of building a parallel system
- Installable Volunteer Check-In PWA, Sanctum-authenticated, separate from the main admin panel
- PHPUnit test suite + GitHub Actions CI/CD with separate staging and production deploys
Spinart Series
spinartseries.in ↗Competitive table tennis tournament platform with an internal wallet and settlement system — not just registration and brackets.
- Wallet & transaction ledger with commission/markup logic and prize-money settlement, built to the client's tournament and payout rules
- Season-based rankings computed from set-level match results
- Versioned REST API (
/api/v1) with OTP-based auth, a properly unauthenticated Razorpay webhook route, and rate limiting - WhatsApp and SMS notification integrations for tournament/registration updates
- Subscription billing via Razorpay
AI Face Attendance
github.com/rakesh-mirackle/attendace ↗Face-recognition attendance for coaching-class batches — a classroom group photo replaces roll call. Directed the architecture and reviewed the AI-generated code across three services; real debugging visible in the commit history, not one-shot generation.
- Laravel 12 REST API + Filament 4 admin, role-scoped (admin vs. staff, staff restricted to assigned batches), 11 backend test files
- Separate, stateless Python FastAPI microservice — InsightFace detects and embeds faces, matches by cosine similarity
- Mid-project architecture pivot: dropped an already-working Flutter app for a Vue PWA once attendance marking was scoped as staff-only — reasoning documented in the repo's own roadmap
- Real fixes in the commit history: a face-image deletion bug, a queue-naming bug on a health check, failure-reason capture for failed registrations
Case Studies
Condensed versions — problem, the one decision worth defending, and the honest impact. Full write-ups (database design, security, lessons learned) available on request.
StudioK3 — reusing one pipeline instead of building two
Needed to sell both seat-mapped tickets and general-admission (quantity-based) tickets, without maintaining two separate checkout systems that would drift out of sync over time.
Modeled GA tickets as virtual seats — pooled inventory rows with no physical seat number. The entire existing checkout, coupon, payment, and ticketing pipeline works on them unmodified, because it was always keyed on seat_id → {type, price}, never on physical position.
One pipeline instead of two, live in production across 8 US shows and 2 in India, with DB::transaction() + lockForUpdate() preventing double-booking under concurrent demand.
Spinart Series — a ledger, not a balance field
The platform needed to move real money both ways — subscriptions in, prize settlements out — with a commission taken on the way, and stay auditable.
Modeled balance as a derived value from a typed WalletTransaction history (with explicit type/status enums), not a single mutable balance field — every change traces back to a specific, typed event instead of being an unauditable number that just changes.
453 registered users · 361 subscriptions sold in the first season, on a system where every rupee is traceable to a transaction record.
Achievements
Independently solved the same hard concurrency problem twice, in two unrelated codebases — a temporary resource hold with an expiry, so a second concurrent request can't claim what's already in use.
In my current role: fixed a race condition affecting a core account/rewards feature on a shared, multi-tenant platform. On StudioK3, a system I architected myself: a 20-minute seat hold preventing double-booking during checkout. Same pattern, arrived at independently in an employer codebase and a from-scratch design. Not luck — a repeatable instinct.
QTech Software
- Fixed a production concurrency bug on a shared, multi-tenant platform
- Maintains a shared codebase serving multiple B2B clients without cross-client regressions
- Directly integrated a third-party payment gateway into a core transaction flow
- Built internal automation replacing manual data-reconciliation work
Generic per employer confidentiality policy.
Mirackle Solutions
- Six-year self-driven growth arc: frontend → PHP/WordPress → Laravel → full-stack ownership
- Direct client ownership — requirements to delivery, no PM/BA layer, across many projects
StudioK3 (freelance, solo)
- Solo-designed and shipped a production ticketing platform, live: 8 shows US, 2 India
- Self-directed architecture call: General Admission modeled as virtual seats, reusing the entire existing pipeline instead of duplicating it
- PHPUnit suite + GitHub Actions CI/CD across staging and production
- Second product surface: an installable Volunteer Check-In PWA sharing logic with the admin panel
Spinart Series (freelance, solo)
- Solo-built a wallet/settlement ledger — commission logic and prize-money settlement, not just payment collection
- Built a versioned REST API from scratch: OTP auth, rate limiting, a correctly-unauthenticated payment webhook
- WhatsApp and SMS integrated as real notification channels
- 453 registered users · 361 subscriptions sold in first season
AI Face Attendance (personal, AI-assisted)
- Directed and reviewed an AI-assisted build (Claude Code) of a three-service system — not a single generated script
- Real post-generation debugging visible in the commit history, plus a documented mid-project architecture pivot (Flutter → PWA)
- First public GitHub project
Résumé
1-page version, generated from the same verified work history as this site.
Contact
Open to Senior Backend Engineer / Backend Engineer (Payments & Platform) / Product Engineer roles.