Ashwini Kumar

🚀 What I’m Building Now at Omio

🌏 Asia Expansion

Scaling Omio’s presence in Asia, starting with Japan and South East Asia. Multi-modal travel options across trains, buses, flights, and ferries — plus AI-powered products like Japan Rail Pass, Japan Travel Planner, and more. Backed by a team I’m building in India.

⛴️ Ferries

Own the engineering for Omio’s global Ferries business — provider integrations, booking flows, everything from search to ticket.

🧭 Leadership & Strategy

🧭 Strategy & Direction

I own the technical roadmap and architectural decisions for systems serving millions of travelers. Half the job is figuring out what not to build.

👥 People & Teams

Built an engineering team in India from scratch — hiring, mentoring, career frameworks, on-call rotations. The kind of environment where engineers stick around and grow.

⚙️ Engineering Culture

Spec-driven development, strong code reviews, observability baked in, rollback-first deployments. The team ships fast because they trust the process.

🤖 Making the Team AI-Native

Not just adding copilots and calling it a day. I’m rethinking how we build software so AI is useful at every step.

AI copilots and agents in daily workflows — less boilerplate, more time on real problems
Automated first-pass code reviews that catch bugs, security gaps, and style issues before a human looks at the PR
Every feature starts with a spec.md (goals, non-goals, acceptance criteria, rollback plan) that drives both implementation and AI-assisted testing
n8n pipelines and agentic workflows to cut through ops toil and manual glue work
Working toward one-touch deploys — production shipping as a single, safe, observable action
Tracing LLM-powered features with LangFuse so we know what’s working, not just what feels fast

AI doesn’t replace good engineering — it makes good engineers faster. The goal is building the right guardrails so a small team can do outsized work.

👨‍💻 About

13+ years building products across FinTech, Gaming, Entertainment, Healthcare, and eCommerce. Working across that many domains taught me that architecture decisions always depend on the problem — there’s no universal playbook. Before Omio, I led engineering at PayU Finance.