SACHIN / 01
I build customer-facing products across web, Android and iOS — then the platform tooling that makes the next feature cheaper. React, React Native, TypeScript. Travel and fintech.
Who I am
I started by shipping production mobile apps end to end. Then enterprise controllers. Then fintech payments at scale. Now I build travel product and the developer platforms underneath it.
The through-line is ownership: shape the contract, build the feature, ship behind flags, instrument it, learn — then build tools so the next cycle is cheaper.
2019
GreenPrint
Mobile foundations
2021
Honeywell
Enterprise IoT
2022
NIUM
Fintech / payments
2025
Omio
Travel · Platform · DevEx
2026
Now
Product + platform engineering
EDU · B.E. Computer Science & Engineering · 2019
Vivekananda College of Engineering and Technology
Languages · English · Kannada · Tulu
Focus
Domains — not a project grid. The shape of work a product engineer with strong mobile depth actually lives in.
Ship the path users actually walk.
End-to-end product work across web and mobile — flows, edge cases, localization, and the boring states that decide whether people trust the app.
Native where it earns its keep.
Cross-platform apps with selective native modules — performance, secure storage, platform APIs, and store-safe release habits.
Make the next feature cheaper.
Shared infrastructure, debugging tooling, and workflows that reduce friction for product teams — adoption without forcing roadmap trade-offs.
Contracts are product surface area.
GraphQL, REST, and BFF collaboration — shaping client-friendly models, migrations that stay reversible, and clear failure modes.
Experience
Select a release. Roles are honest to each company — Senior where it was held, Software Engineer at Omio.
Jun 2025 — Present · Travel technology · Product & platform
Software Engineer (Frontend)
Multi-modal travel booking across web, Android and iOS — many markets, languages, currencies, and hundreds of transport operators.
Currently
Travel technology across web, Android and iOS — customer-facing features, shared frontend systems, and the developer experience that keeps multi-platform work sane.
Stack
Grouped by capability — the way engineers actually think about tools.
Engineering DNA
Product engineer with deep React Native — the instincts that travel between companies.
Users feel latency as distrust. Startup, interaction delay, and stability belong in the product brief — not as polish.
Prefer constraints that make classes of bugs impossible: typed boundaries, clear module edges, and defaults that survive deadline pressure.
Own the path from API shape to instrumentation. Shipping and learning in production is part of the job.
Internal tools compete with roadmaps. If adoption costs anything meaningful, the tool loses.
If you cannot inspect state, network, and product signals while building, you will guess under pressure later.
Influence designs you do not own with evidence — usage, latency, duplication — not taste arguments.
Practice
The topics a senior React / React Native engineer is expected to reason about — open any for a short take.
Shared business logic with platform-specific presentation. Native modules when the OS capability is the product — not by default. Design for install bases you cannot force-update.
Principles
General convictions from years of shipping product on web and mobile — not slogans tied to a single ticket.
Every abstraction, dependency, and layer must pay rent. If it only looks elegant on a whiteboard, it is debt.
Speed and stability shape trust. Treat them as requirements with owners — not as a cleanup sprint.
When modules, APIs, and platform seams are right, feature work feels boring in the best way.
Design, build, release, observe, iterate. A solution that cannot ship safely is incomplete.
What you can see, you can improve. Blind systems invite folklore and late nights.
Deadline pressure erodes checklists. Make the safe path the easy path — types, gates, and defaults.
Wrong quickly and cheaply beats right slowly. Flags, rollback, and incremental migration are craft, not fear.
Loading, empty, error, offline, and multi-language layouts are where products earn respect.
Lab
Explorations beyond the day job — interfaces, mobile sketches, tooling ideas, and continuous learning.
WEB
Motion, typography, and interaction studies — treating the portfolio itself as a product surface.
MOBILE
Small React Native explorations: navigation patterns, performance profiles, and native module sketches.
EXPERIMENT
Prototypes around debugging, locale switching, and inspection workflows for multi-platform teams.
AI
Practical use of AI in day-to-day coding, review, and documentation — without outsourcing judgment.
WRITING
Notes on architecture trade-offs, API design, and mobile constraints — written to clarify thinking.
HARDWARE
Side explorations in scripting, Raspberry Pi, and small physical builds when time allows.
Outside the code
Places, culture, and how products feel when the market changes under your feet.
Hiking and altitude — the reset that makes long engineering weeks sustainable.
Consistency compounds — same discipline as shipping software.
Deliberately growing backend and distributed systems depth toward Staff/Principal.
Contact
Let's build something worth shipping.
Bengaluru · Open to Senior / Staff-track product & platform conversations.
+91 81050 61586 · Bengaluru, India