Rohan and Kavya graduated from the same engineering college in 2019. Same branch, same CGPA range, same campus placement season. Rohan took a job at a Series B fintech startup in Bangalore. Kavya joined Infosys. Four years later, they are sitting across from each other at a bar in Koramangala, catching up for the first time in months, and the conversation has turned -- as it always does with engineers -- to work.
"You would not believe the chaos," Rohan is saying, three drinks in. "Our CTO changed the entire product roadmap. Again. Third time this year. We had spent two months building a feature and then -- poof -- it is not a priority anymore." He does not look angry exactly. More like someone who has made peace with a recurring earthquake.
Kavya stirs her drink. "We just completed a reorganization. My new manager is in a different city. I have met him once on a video call. My project is the same project I was on a year ago. Same client. Same codebase. Same everything." She pauses. "I got a 7% hike, though."
"Seven percent," Rohan repeats. "I got 22% when I switched roles internally. But also I did not get a bonus last quarter because the startup missed its revenue target. And my equity... do not even get me started on the equity."
This is the startup vs MNC conversation. I have been on both sides of it -- three years at a large consulting firm, two years at a startup that failed, and now as an analyst who talks to people on both sides regularly. I have opinions. But I do not think either side is right, and the real trade-offs are messier than most articles make them sound.
The Money Question (It Is Never Simple)
Let us start with money because that is usually what people care about most, even when they say they do not.
At an MNC -- and by MNC I mean the large Indian IT companies too, your TCS, Infosys, Wipro, as well as the product MNCs like Google, Microsoft, Amazon -- the salary structure is predictable. You know your CTC. You know your in-hand. You know roughly what the hike cycle looks like (7-12% in service companies, potentially more in product companies). There is a provident fund, gratuity, insurance. The money is boring in the best possible way. It shows up. It is what you were told it would be.
At a startup, the conversation gets weird fast. Rohan's CTC looked impressive on paper -- 18 lakhs, which was higher than Kavya's starting 3.6 lakhs at Infosys (though she has climbed to about 8 now). But Rohan's 18 included a "performance bonus" that materialized exactly once in four years and "stock options" that deserve their own section in this article because the way startups talk about equity is -- and I am being polite here -- misleading.
Let us talk about equity honestly. Rohan was given 500 stock options when he joined. His offer letter said the strike price was 10 rupees per share and the "current valuation" implied each share was worth 200 rupees. So on paper, he had options worth about 1 lakh. Not bad for a signing bonus, right? Except: those options vest over four years (so he only "owns" a fraction each year). They are in a private company (so he cannot sell them until there is an IPO or acquisition). The valuation was set during a fundraising round (which is an optimistic number by definition). And if the company goes under -- which about 90% of Indian startups eventually do -- those options are worth exactly zero.
Rohan's startup has not gone under. But it has also not had an IPO. And in the latest funding round, the valuation actually went down (a "down round," which dilutes existing shareholders). His options are now worth less on paper than they were when he got them. He cannot sell them. He cannot use them for a home loan. They are Monopoly money until proven otherwise.
"But what if the startup succeeds?" Kavya asks, genuinely curious.
"Then I am rich," Rohan says. "If the company goes public at 10x the current valuation, my shares are worth maybe 50 lakhs after dilution. That is life-changing money."
"And the probability of that?"
"Honestly? Maybe 5%. Maybe less." He shrugs. "It is a lottery ticket I am working 60-hour weeks to earn."
What You Actually Learn (And What You Do Not)
This is the thing startup people always bring up, and they are not wrong about it -- you learn faster at a startup. You learn faster because there is nobody else to do the thing, so you have to do the thing, whatever the thing is. Rohan, who was hired as a backend developer, has in four years also done frontend work, set up CI/CD pipelines, written product requirement documents, interviewed candidates, handled a client escalation, and once (memorably) helped assemble office furniture when they moved to a new co-working space.
"I can genuinely do five different jobs now," he says. "My resume looks insane."
But Kavya pushes back. "You can do five different jobs at a surface level. I can do one job at a deep level." She has spent four years on enterprise Java applications. She understands distributed systems, transaction management, database optimization at a level that Rohan, by his own admission, does not. She has worked on systems that handle millions of transactions. She has seen what happens when code runs at scale for years, not months.
"Which is more valuable?" she asks.
Honestly? It depends on where they go next. If Rohan applies to another startup, his breadth is gold. If Kavya applies to a senior developer role at a large product company, her depth is gold. Neither is universally better. But the job market has a slight bias toward breadth right now (because startups are hiring more aggressively than large companies), which gives Rohan an edge in terms of options. In terms of getting interviews. In terms of appearing "interesting" on a resume.
What nobody tells you about MNC learning, though, is the process knowledge. Kavya knows how large organizations work. She understands approval hierarchies, compliance requirements, audit trails. She has navigated a bureaucracy and come out the other side functional. When she eventually moves to a senior role -- whether at an MNC or a startup that has grown large enough to need process -- that knowledge will matter. Startups do not teach process because they do not have any. And when they grow to 500 people and suddenly need some, they desperately hire people like Kavya.
The Day-to-Day (Be Honest With Yourself)
Rohan describes his typical day: Wake up, check Slack (messages from people in different time zones who were working while he slept). Standup at 10. Then code. Then a product meeting that turns into a strategy debate that turns into a philosophical argument about the company's direction. Then more code. Then a demo for the founder. Then some fire to put out -- a bug in production, a client complaint, a vendor who has not delivered. Leave sometime between 8 and 10 PM.
Kavya describes hers: Badge in at 9:30. Team standup. Code, mostly. Maybe a meeting or two about requirements. Lunch (actually leaving her desk for lunch -- "Rohan, do you even eat lunch?"). More code. Leave at 6:30 unless there is a release, in which case maybe 8.
"I have a gym routine," Kavya says. "I play badminton on weekends. I am learning Korean from YouTube. I have a life outside work."
"I have a ping pong table in my office," Rohan counters. "And free dinner if I stay past 8. Which is... every day. So I guess the company is feeding me dinner as compensation for taking my evening."
They both laugh, but there is something real in that exchange. Startups often blur the line between "perk" and "incentive to stay longer." Free food, office games, bean bags, a "fun" culture -- these things are nice, but they also serve a purpose. If the office is comfortable enough, you will not go home. If dinner is provided at 8 PM, you will stay until 8. The perks are not generosity. They are infrastructure for long hours.
MNCs, especially the service companies, have a different problem. The work can be monotonous. The pace can be slow. You might spend weeks waiting for a requirement to be finalized, or months maintaining a system that does not need much maintenance. The boredom is real. Some people handle it fine -- they do their hours, go home, pursue other interests. Others slowly go mad. "I feel like I am wasting my brain," someone told me once about her job at a large service company. "Everything I learned in college is irrelevant here. I run the same scripts every week."
Job Security (The Elephant in the Room)
"What keeps you at Infosys?" Rohan asks.
Kavya does not hesitate. "Job security. I know that word sounds boring. But my parents... they are from a generation where a 'permanent job' meant everything. When I told them I got placed at Infosys, my mother cried. Actually cried. If I told them I was leaving for a startup, they would not sleep for a month."
This is something that startup-vs-MNC articles written by people in their twenties tend to dismiss. "Job security is an illusion," they say. "No job is truly secure." And technically that is true -- MNCs also do layoffs. But the probability and the scale are different. A startup can run out of funding and shut down in a quarter. I have seen it happen. I have talked to people who showed up to work on a Monday and found out the company was folding by Friday. Their stock options, their notice period, their pending reimbursements -- all gone. Some of them had quit stable MNC jobs to join these startups.
At a large company, even when layoffs happen, there is a structure. Notice periods are honored. Severance is paid. There is time to find something else. The social safety net -- such as it is in India -- works better when your employer is a large, visible company that cannot afford the reputation damage of treating laid-off employees badly.
"But you are trading security for growth," Rohan argues. "If Infosys goes through a bad quarter, your hike is 5% instead of 7%. At a startup, a good quarter could mean a promotion, a new role, equity that actually becomes worth something."
"Could. Could. Could," Kavya says. "A lot of coulds."
The Brand Name Problem
Here is something practical that people do not talk about enough. When Kavya puts "Infosys" on her resume, every recruiter in India (and most outside India) recognizes it. It is a signal. It says: this person cleared a hiring process, worked in a professional environment, understands corporate norms. Whether the signal is accurate or not, it opens doors.
When Rohan puts "FinPay Technologies" (made-up name, you get the idea) on his resume, the recruiter's first question is: "What is FinPay Technologies?" He has to explain the company before he can explain his role. If the startup is well-known -- a Razorpay, a Zerodha, a CRED -- this is not a problem. But most startups are not well-known. Most startups are small companies that nobody outside their niche has heard of.
This matters less as you gain experience. After 8-10 years, your work matters more than where you did it. But for the first few jobs, brand name carries weight, especially in the Indian market where parents, in-laws, and society at large still assess your career by the name of your employer.
"My neighbor's aunt still asks my mom why I did not join TCS," Rohan says.
Culture and People
Rohan knows his CEO personally. They have had arguments. Actual, heated disagreements about product direction, where Rohan -- a relatively junior engineer -- told the CEO he thought a feature was a bad idea. In most MNCs, the gap between a junior engineer and the CEO is approximately seven organizational layers and a locked elevator.
Startup culture at its best is flat, direct, fast. You can have an idea in the morning and ship it by evening. Decisions happen in Slack threads, not in 47-slide PowerPoint presentations reviewed by three levels of management. When the product changes direction, you find out in a team meeting, not from a company-wide email two months later. The energy is real. The sense of building something that did not exist before is real.
But startup culture at its worst is chaotic, political, and personality-driven. When the CEO is having a bad week, the whole company is having a bad week. There is no HR department to go to if your manager is being unreasonable -- your manager might BE the HR department. Processes are invented on the fly and changed the next day. "We are agile" sometimes just means "we have no plan." The same flatness that lets a junior engineer argue with the CEO also means there is no buffer between you and the CEO's mood.
MNC culture at its best is stable, professional, and well-structured. You know what is expected of you. There are clear paths for growth, formal training programs, mentorship structures, employee resource groups. The cafeteria is good. The campus is nice. You feel like a professional working at a professional place.
MNC culture at its worst is stifling. You are a resource number. Your manager's manager does not know your name. You sit in meetings where nothing is decided. You fill out timesheets. You wait for approvals. Innovation is something that happens in the company's annual report, not in your daily work. The process that protects you also constrains you.
What Nobody Asks: What Do You Actually Want?
"OK but which one is BETTER?" People ask me this constantly, and I always want to say: better for what? Better for whom? At what stage of life?
If you are 22, single, no EMIs, curious, high energy, and can absorb risk -- a startup might be the right call. The learning is real. The experience is dense. And if it fails, you are 25 and you have stories and skills and you start over. The cost of failure is low.
If you are 30, married, have a home loan, a kid on the way, parents depending on you -- the calculation changes. Stability matters more. Predictable income matters more. The thrill of "we might be building the next unicorn" matters less when the question keeping you up at night is "can I make next month's EMI."
If you are technically brilliant and want to go deep into a specific domain -- large companies give you that space. Google's infrastructure team, Amazon's AWS division, TCS's research labs -- these places let you work on problems at a scale that startups simply cannot offer.
If you are someone who gets bored easily, hates repetition, and wants to wear multiple hats -- startups will keep you stimulated. Maybe too stimulated. But you will not be bored.
The honest answer is that most people will work at both during their career. Start at an MNC, learn the basics, build credibility. Jump to a startup for growth and excitement. Come back to a large company when life needs stability. Or the reverse. Or some other combination entirely. The idea that you have to pick one lane and stay in it -- that is the real myth, not "startup vs MNC."
What They Do Not Tell You in Either Case
Nobody at a startup will tell you how lonely it can be. When your company is 40 people and something goes wrong -- a funding round falls through, a key client leaves -- there is no corporate communications team to manage the narrative. There is a WhatsApp group where people are panicking. There is your manager, who is also panicking but trying not to show it. There is you, wondering if you should start updating your resume.
Nobody at an MNC will tell you how slowly your identity can merge with the company until you do not remember who you are without it. I have met people who spent 15 years at the same company and were terrified of leaving -- not because they could not find another job, but because their entire professional identity was wrapped up in that one organization. "I am a Wipro person" or "I am an Accenture person." The company becomes a personality trait. That is comfortable but also a kind of trap.
There is also the question of what happens when things go wrong. At an MNC, if your project fails, the company absorbs it. You might get reassigned. At a startup, if the product fails, the company might die. Your project failure is the company's failure is your unemployment. The stakes are higher, and that changes how failure feels.
Last Call
It is getting late at the bar. Rohan and Kavya have been going back and forth for two hours. The table is cluttered with glasses and appetizer plates and the remnants of a debate that has no winner.
"You should join a startup," Rohan says, for maybe the fifth time.
"You should join an MNC," Kavya says, like she always does.
They will not convince each other. They never do. Because the choice is not about which option is objectively better -- it is about which set of trade-offs you can live with, which downsides you would rather endure, which version of professional discomfort feels more like growth and less like suffering. And that is different for everyone. That is different for the same person at different points in their life.
Rohan pays the bill. (Kavya notes, silently, that he uses a credit card. She wonders about his cash flow.) They walk out into the Bangalore night, the IT park lights still glowing across the road. Somewhere up there, someone is deploying code at midnight. Could be a startup. Could be an MNC. From down here, the lights look the same.
Comments