Engineering
Skills, systems & how I ship.
I work as a true full-stack engineer — shipping native mobile apps, responsive web interfaces, backend systems and the APIs that connect them all together.
Expertise
Four layers of the stack
Detailed breakdown of each engineering area with the specific tools, patterns and systems I work with in production.
01 · Mobile Engineering
Production mobile apps across iOS and Android with a focus on native feel, performance and reliable offline behaviour. Built ride-hailing, safety, messaging and booking platforms end-to-end.
- React Native — Expo & bare React Native, navigation, state management
- Flutter — Stateless/Stateful, Riverpod, custom UI kits
- iOS & Android — Native build configuration, signing, App Store & Play Store deployment
- Push Notifications — FCM, APNs, rich notifications, silent pushes
- Camera & Media — Image capture, video, compression, uploads, silent evidence capture
- Maps & Location — Google Maps, MapKit, realtime tracking, geocoding, routes
- Device Permissions — Runtime permission flows, background location, camera, contacts
- Deep Linking & App Links — Branch, universal links and custom schemes
- Offline & Syncing — Local storage, caching, optimistic UI, background sync
02 · Frontend Engineering
Responsive web apps and dashboards — client-side performance, accessibility and strong component architecture. Used for admin panels, booking UIs and marketing surfaces for products with companion web apps.
- React — Hooks, Context, composition patterns, component libraries
- Next.js — SSR, SSG, App Router, image optimization, routing
- TypeScript — Strict typing, generics, interfaces across API boundaries
- JavaScript (ES6+) — Async patterns, module systems, modern APIs
- Responsive UI — Mobile-first, fluid layouts, accessibility-first markup
- State Management — Redux, Zustand, React Query, SWR
- Performance — Bundle sizing, code splitting, Lighthouse, Core Web Vitals
- Tailwind CSS — Utility-first styling, design systems, theming
03 · Backend Engineering
API and data-layer systems that actually run the product. Comfortable across two ecosystems (Node.js, PHP) with pragmatic database design, query performance and strong API contracts as priorities.
- Node.js — Express, Fastify, middleware patterns, async/await architecture
- PHP — Modern PHP, Composer ecosystem, PSR standards
- Laravel — Eloquent, Sanctum, queues, events, Horizon, Blade/Inertia
- REST APIs — Clear contracts, resource naming, versioning, consistent payload shapes
- WebSockets — Socket.io, event-driven realtime updates and presence channels
- MySQL — Schema design, indexing, migrations, query optimization
- MongoDB — Document modelling, indexes, aggregation pipelines
- Firebase — Auth, Firestore, Realtime DB, Cloud Functions, Storage, FCM
04 · Product & Systems Engineering
Cross-cutting concerns that make a product production-grade — auth, payments, realtime, reliability and deployments. The difference between a prototype and something that runs reliably.
- API Architecture — Endpoint design, rate limits, caching, error semantics
- Authentication — JWT, sessions, OAuth, social login, password hashing, 2FA
- Payments — Razorpay, Stripe, UPI integrations, webhooks, order lifecycle
- Real-time Systems — Event busses, pub/sub, presence, live updates
- Caching — Redis, HTTP caching, CDN strategy, query result caching
- Queues & Workers — Background jobs, retries, scheduled tasks
- Cloud Services — AWS, cPanel, VPS, Nginx, serverless functions
- Third-party Integrations — Maps, SMS, email, SMS gateways, REST & GraphQL APIs
- Deployment — CI/CD pipelines, zero-downtime deploys, SSL, monitoring, backups
Process
How I'd approach a typical project
A repeatable four-step framework I apply — flexible enough for MVPs, startups and growing products.
Discovery & Scope
Understand the product, its users and the actual problems being solved. Translate requirements into scope, boundaries and a realistic delivery plan. Agree on priorities and MVP surface before writing code.
Architecture
Choose stack and architecture that match the product stage and team. Design data model, API contracts and deployment shape. Set up authentication, payments, deployment and CI from day one.
Build & Iterate
Build in small, reviewable chunks. Ship vertical slices of working product early. Review together. Iterate on UX flows, performance and scope as product learns. Keep deployments frequent and low-risk.
Deploy & Maintain
Ship to production. Instrument basic monitoring and observability from the start. Respond to issues, iterate on feedback, keep dependencies patched. Support the product as it grows.