Home › Blog › Founder Journey
Founder Post

From T-Mobile USA to Building a Software Startup in India

How working inside one of America's largest telecoms taught me more about enterprise software than any course, and why I came back to India to build something of my own.

By Sainath Mitalakar, Founder — T-Mat Global April 20, 2026 8 min read

Why I'm Writing This

I get asked the same question often enough that it deserves a proper answer: why leave a stable role at a US telecom giant to start a software company in India from scratch? The short answer is that I didn't leave because I was dissatisfied. I left because working at T-Mobile USA gave me a clear view of what enterprise software actually looks like at scale — and I wanted to build it myself.

This is not a rags-to-riches story. It is a story about paying attention to what you are learning, waiting until you know enough to do the work properly, and then starting.

The T-Mobile USA Years

T-Mobile USA is not a typical employer. It runs some of the most complex distributed infrastructure in North America — millions of active subscribers, real-time billing, network orchestration, and a CI/CD pipeline that needs to handle deployments without service interruption. Working there as a DevOps Engineer meant being responsible for systems where downtime is measured in revenue per second.

What working at T-Mobile USA actually teaches you
  • How enterprise CI/CD works at scale — not tutorial scale, but hundreds-of-services scale
  • What infrastructure-as-code discipline looks like when the stakes are real
  • How observability (Prometheus, Grafana, alerting) prevents 2am incidents
  • What it means to own a system — not just deploy it, but be responsible for it running
  • How engineering teams communicate under pressure when something breaks in production

I earned my AWS certification during this period — not as a box to check, but because understanding cloud architecture made me better at the job. The certification is a credential. The understanding is what I brought back to India.

"The thing T-Mobile gave me wasn't a resume line. It was a visceral understanding of what breaks, what doesn't, and why the difference matters."

The Decision to Come Back

The decision wasn't sudden. I had been watching the Indian software market from the inside out — seeing what clients in the US expected, what "offshore" meant to them, and where the gap was between what they received and what they actually needed.

The gap was not skill. India has extraordinary engineering talent. The gap was credibility, process, and accountability. Clients didn't trust offshore vendors not because of technical capability but because of experiences with communication theatre, scope creep, and teams that disappeared after handoff.

I came back to India to build the kind of software company that I would have hired as a client — with verifiable credentials, milestone-based contracts, direct access to the technical team, and work that ships and runs in production.

What T-Mat Global Is — and Is Not

T-Mat Global is not an IT staffing company. It is not a body shop. We do not subcontract to other vendors and pass the work off as ours. We are a small, focused engineering team that takes on projects we can deliver, staffs them with people who have worked on the relevant technology stack, and owns the outcome.

3
Active projects across 3 countries
DPIIT
Recognized startup — government verified
AWS
Certified cloud architecture

The DPIIT recognition matters more than it sounds. It means T-Mat Global is a verified legal entity — CIN registered, government-audited, with a documented founding history. For international clients, this is the difference between a vendor with a LinkedIn page and a vendor with a paper trail.

What I Have Learned as a Founder

The hardest part of running a software company is not the code. It is the judgment calls that happen before and after the code — scoping a project so it is actually deliverable, writing a contract that protects both parties, managing a client's expectations when requirements change mid-flight, and building the kind of working relationship where the client trusts you enough to tell you when something is not right before it becomes a problem.

The T-Mobile years helped with this more than I expected. Working inside an enterprise means you understand the pressures your client is under — the internal stakeholders, the budget cycles, the executive expectations. When a client tells me they need a demo for a board meeting in three weeks, I understand exactly what that means because I have been on the other side of that meeting.

What I bring to every project from the T-Mobile years
  • Architecture decisions made for production, not prototyping
  • CI/CD pipelines built to run unattended, not to pass a demo
  • Security thinking baked in at the design layer, not bolted on later
  • Observability as a first-class deliverable — dashboards, alerts, runbooks
  • Honest timelines: enterprise software takes as long as it takes, and I will tell you that upfront

What Comes Next

Three projects in year two is not a lot by volume, but it is the right number for the quality standard I hold. Every system we build carries the T-Mat Global name — that means it needs to run in production, not just in a staging environment, and the client needs to be able to maintain it after we hand it over.

The goal is not to grow fast. The goal is to build a track record of systems that work. When that track record is three systems, then five, then ten — the company earns the right to grow.

If you are evaluating software vendors for an enterprise project and you want to have a direct technical conversation — not a sales call — I am available. The contact form on this site reaches me directly.

Let's Talk About Your Project

I respond personally to every inquiry. Bring your requirements — I'll give you an honest scope and cost estimate with no sales pressure.

Contact Sainath Directly