Full Stack Engineer

Location: MumbaiExperience: 3+ yearsEmployment: Full-timeThe RoleYou will own our production stack end to end.Backend: PHP + MySQL powering our API, admin panel and content deliveryApp: Flutter with BLoC architecture, optimized for Android devices including low-end phonesPayments: Razorpay (UPI AutoPay) and Google Play through RevenueCat — subscriptions, webhooks, renewals, trials, cancellations and reconciliationInfrastructure: AWS EC2, S3, CloudFront, deployments, logs and backupsThis is a production-ownership role, not a feature-factory role.When a paying customer says, "The app says my account is not active," you should be able to open the database, check webhook logs and gateway records, find the actual problem, fix the customer issue and then fix the underlying bug.What you'll actually doMaintain the subscription lifecycle across Razorpay and Google PlayBuild reliable, idempotent webhook handlingHandle renewals, trials, cancellations, refunds and entitlement syncingDevelop and maintain Flutter featuresDesign MySQL schemas and safe database migrationsDebug production issues across app → API → database → payment gatewayManage deployments, logs, cron jobs and backupsWork on video delivery using HLS, S3, CloudFront and signed URLsImprove app performance, stability and reliabilityYou should have3+ years PHP experience, comfortable with raw PHP/PDOStrong MySQL/SQL knowledge — indexes, transactions, migrations and EXPLAINProduction experience with FlutterExperience with state management such as BLoCExperience shipping and maintaining a real consumer appPayment gateway experience, especially webhooks and idempotencyStrong production debugging and problem-solving skillsAbility to work independently and take ownershipNice to haveRazorpay / Google Play Billing / RevenueCat experienceHLS, CDN and video streaming knowledgeAWS experienceFirebase — FCM, Crashlytics, AnalyticsAdMobMeta / Google attribution and analyticsPrevious OTT, subscription or consumer-app experienceWho we're looking forSomeone who takes ownership when things break.You should be comfortable checking the data before making changes, taking backups before migrations and saying "I don't know, but here's how I'll find out" rather than guessing.If you've built and maintained production systems where payments, subscriptions and customer entitlements actually matter, we'd like to hear from you.