How To Realize The Ultimate Rendition Of The American Dream (Journey From Indian Railways To SpaceX) - w/ Sanjeev edited transcript

Naman introduces Sanjeev Sharma, a principal engineer at SpaceX whose path runs from Indian Railways in the 1990s to hard-drive engineering in the United States and, eventually, reusable rockets. The conversation begins with the version of India in which Sanjeev entered engineering, then follows the technical knowledge, immigration decisions, financial risks, and career bets that made each transition possible.

Naman asks Sanjeev to begin with his decade in Indian Railways and explain what engineering work felt like in India during the early 1990s. He is especially interested in how someone working inside a large government system eventually arrived at SpaceX without treating the two careers as unrelated chapters.

Sanjeev says his father was an engineer, so machines and the way people designed them interested him early. He began at the University of Roorkee, now IIT Roorkee, but moved after being admitted through the UPSC process to the railway institute in Jamalpur. The institute recruited students after Class 12 for a four-year mechanical engineering program with both theory and practical railway training. Because the selection process took months, he was already well into his first year at Roorkee when the railway offer arrived.

After graduating, Sanjeev spent two years in Dhanbad with Eastern Railway, mostly in operations. That experience convinced him that design sat upstream of the systems he was operating. He moved to the newly established Rail Coach Factory in Punjab, where computerization was entering design and manufacturing. The factory had modern tools, strong funding, and colleagues who were willing to learn together. That environment turned a general interest in engineering into a specific commitment to design and analysis.

The new factory mattered because it let the team build methods at the same time it built products. Computer-aided design and manufacturing tools were entering the organization, and Sanjeev could learn directly from senior engineers while experimenting with a new technical workflow. He remembers being surprised that a government factory could provide state-of-the-art technology and enough funding to use it seriously. The experience complicated the easy story that innovation was impossible in public service: the larger system could be slow, but the right local team still created exceptional work.

Naman asks why Sanjeev would leave a prestigious place like Roorkee for a railway college. From a present-day perspective, the choice is not obvious, so he asks Sanjeev to reconstruct the labor market and social incentives that existed when he made it.

Sanjeev explains that India was only beginning to emerge from a deeply socialist economic model. Private-sector opportunities were scarce, many ambitious engineers left for the United States, and those who stayed often viewed government service as the strongest available destination. The railway institute was not a fallback. It was a selective, fully funded route into a prestigious government engineering career, taking roughly 30 to 40 students from an applicant pool he remembers as being in the tens of thousands. In that India, choosing it over Roorkee was rational even though the same student might decide differently today.

To show how different that economy was, Sanjeev recalls an India where only a tiny number of car models could be manufactured and buyers could wait years after securing permission to purchase one. Large-scale engineering opportunities were concentrated in government because the government made or controlled products across many categories. His broader point is that career decisions cannot be copied outside their historical context. People pursue the best path visible in the environment they actually inhabit.

The railway institute also removed financial uncertainty. The government funded the education and attached it to a defined professional path. For a student deciding in the late 1980s, that combination of selectivity, training, status, and employment carried a kind of prestige that is easy to miss when the decision is viewed through today's much larger private-sector market. Sanjeev says the pendulum has moved: government careers still matter in India, but a technically ambitious student now has enough private options that the same choice requires a more nuanced comparison.

He describes socialism as a supply-side system in which the state controls production, competition stays weak, and the pressure to innovate disappears. Multinational companies could not freely build research centers in India, so engineers had fewer places to do advanced technical work. Liberalization changed those options. A young engineer with Sanjeev's motivations today might make the opposite institutional choice because the private technical ecosystem is now far broader.

One thing that troubled Sanjeev was looking around and seeing that much of the modern engineering world had been designed elsewhere. Indian organizations often reverse-engineered imported technology or continued using old methods rather than investing in original research and design. He was fortunate to belong to a generation that began changing that pattern in both public and private institutions, but the gap itself pushed him toward deeper technical learning.

At the Rail Coach Factory, Sanjeev found the kind of opportunity he wanted: a new design center, serious investment, modern computers, supportive superiors, and peers who were willing to execute quickly. The team designed rail cars and shortened design cycles in ways he considered unusual for a government organization at the time. He also worked on an indigenous higher-speed train that ran between Delhi and Amritsar years before today's Vande Bharat program. He calls the opportunity lucky, but defines luck as preparation meeting a real opening.

A United Nations Development Programme project brought international PhD-level design experts into the railway design group around 1995. They taught first-principles rail-car design, vehicle dynamics, structural analysis, and mechanical design. Sanjeev found the subjects fascinating, but also realized there were limits to what he could absorb without returning to school. That gap between the work he wanted to understand and the education he had became the reason to pursue a mechanical engineering master's degree.

The higher-speed train project was one example of what the team could do when engineering talent, money, and institutional permission arrived together. The service ran for years between Delhi and Amritsar, and Sanjeev sees it as an earlier chapter in India's continuing effort to build faster indigenous passenger rail. He does not claim that his project and current train programs are identical. The connection is that a generation of railway engineers was already developing local design capability, shortening cycles, and proving that government teams could do more than maintain inherited systems.

Sanjeev traces his railway titles from assistant mechanical engineer in Dhanbad to divisional mechanical engineer and then deputy chief mechanical engineer for design at the Rail Coach Factory. In the design role, he was responsible for a group of roughly 70 engineers working across research, design, and implementation. The scale gave him leadership experience without removing him from the technical work that motivated him.

The job did not end when a rail car left the CAD screen. His team designed both vehicles and factory tooling, then helped turn the design into a prototype on the shop floor. Sanjeev spent time with workers, wrote assembly and process instructions, planned materials, ordered parts, developed vendors, coordinated quality, and worked through prototype manufacturing. Because rail transportation is heavily regulated, the team also participated in laboratory and field testing with authorities inside and outside the railway organization. That end-to-end ownership later translated well across industries.

Depending on the project phase, Sanjeev might spend half a day each week inside the factory discussing manufacturability with workers. That contact forced design decisions to survive contact with tools, parts, suppliers, process instructions, and the people assembling the prototype. He learned that engineering ownership includes the unglamorous chain between an analysis and a functioning product. Years later, when interviewers asked whether he had really owned the work on his resume, this was the kind of detail he could explain because he had followed projects from calculations through testing.

Naman asks about the two criticisms that often follow large public infrastructure systems: bureaucracy and corruption. He wants to know whether either one constrained the design and manufacturing work Sanjeev was trying to move forward.

Sanjeev says both problems existed across public and private organizations. He compares everyday corruption to denying oxygen to a marathon runner: the organization may continue moving, but everything becomes harder and slower. He distinguishes this from corruption concentrated only at the top of a political or financial hierarchy. The more damaging version, in his view, is routine middle-class corruption that people normalize in ordinary transactions and government work. He argues that citizens cannot blame only politicians; they also have to examine their own choices.

He uses an ordinary traffic stop to make the distinction concrete. In the United States, a driver generally expects the ticket to follow a defined process and understands that offering the officer money would create a much larger problem. In the system Sanjeev remembers, too many jobs came with an unofficial method for extracting extra income from routine authority. He believes that possibility partly fed the rush for secure, high-status government roles. His criticism is aimed at the social layer participating in the practice, not at one organization or political party alone.

Bureaucracy also dampened progress because rules could be interpreted to punish anyone who took an unusual initiative. Nothing in the formal code prohibited good work, but a cautious culture made sticking your neck out feel dangerous. Well-wishers warned Sanjeev privately that he could ruffle powerful groups by signing decisions and pushing new projects. He moved ahead anyway, helped by being junior enough to execute without becoming the main political target. His working rule was to focus more on what could go right than on every possible backlash.

When Sanjeev led projects, he documented decisions clearly, signed the files that came to him, and took responsibility instead of waiting for complete political safety. There were lobbies and internal groups he could have spent all his energy trying to predict. He chose not to make those fears the center of the engineering process. The lesson is not that bureaucracy disappeared or that risk-taking was costless. It is that a public-sector engineer could still create room for initiative when a capable team shared the risk and the person doing the work remained focused on execution.

Sanjeev wanted to remain a technical engineer and leader, but the structure of Indian government services often pushed technical officers toward general administration. He traces part of that design to colonial civil-service institutions built to govern rather than cultivate specialists. He notes important exceptions, including ISRO and DRDO, where exceptional people created technical progress despite the broader convention. Still, he did not want his own future to depend on whether a rotation moved him from design into procurement, human resources, or another administrative function.

His objection is not that administration has no value. Large organizations need people who understand operations, budgets, hiring, procurement, and policy. The problem is assuming that every strong technical officer should eventually become a general administrator. Deep engineering capability takes years to accumulate, and rotating specialists away from their craft can keep institutions from building durable research cultures. Sanjeev wanted a path where technical leadership meant becoming better at engineering and guiding engineers, not leaving the technical body of knowledge behind as the price of seniority.

That is why Sanjeev chose a mechanical engineering master's instead of an MBA. Cost made graduate school difficult, but US programs offered the possibility of a research assistantship, tuition support, and a stipend. He enrolled at the University of Colorado Boulder and selected the thesis route. The local engineering ecosystem included IBM, Seagate, and other hard-drive companies, which funded university research. His thesis work on computer hard drives was strong enough that the company later offered him a job.

The thesis option linked the university to a regional industrial problem. Boulder-area companies needed research on hard-drive mechanics, and the university could give a student access to that problem while covering tuition and living costs through funded work. Sanjeev did not arrive because hard drives had always been his dream industry. He arrived because the research used dynamics and mechanical analysis he already understood, then discovered how sophisticated the product was. The eventual job offer grew out of work the company had already seen rather than a cold career pivot built only on a new credential.

Sanjeev says his Indian Railways experience directly helped at Boulder and in hard-drive engineering. Vehicle dynamics, vibration, structural analysis, simulations, statistical quality control, prototyping, experimental design, and process control all carried across. The physical scale changed dramatically, but the engineering principles did not. His master's added theory to a decade of ownership and manufacturing experience; it did not replace everything he already knew. That combination, rather than the two-year degree alone, made him effective in the new industry.

Sanjeev rejects the idea that the master's created a completely new professional identity. A two-year course could not by itself have made him successful in a specialized industry. The degree sharpened the theory and introduced a new research environment, while his railway years supplied judgment about prototypes, quality, vendors, experiments, and systems that fail in the physical world. That is why he describes the move as a domain change rather than a change in the underlying body of engineering knowledge. New graduates can use the same framing when explaining apparently unrelated experience.

He does not minimize the domain gap. Hard drives had evolved over decades into a deep, narrow field with its own jargon and highly specialized problems. For roughly six months, Sanjeev sat in meetings with experts and struggled to follow what they meant. First principles gave him a bridge, not instant expertise. The transferable foundation made it possible to learn the new domain, but he still had to earn fluency in the details.

Naman asks how Sanjeev evaluated the fork in the road after graduation. He had planned to return to Indian Railways, but now had a rare opportunity to work at the cutting edge of hard-drive research in the United States. The question is not whether the decision looks correct in hindsight; it is what mattered before the outcome was known.

Sanjeev begins with the idea that once basic needs are met, a person's work should move toward excellence and purpose. The hard-drive company offered advanced research in a field producing genuinely important technology. Returning to Railways could have meant leaving design for procurement or human resources because officers were deliberately rotated to become general administrators. If he had been returning to a specialist organization such as ISRO or DRDO, he says his choice might have been completely different. The decision was about preserving a technical life, not simply choosing the United States over India.

The likely railway rotation made the comparison unusually stark. One path kept him near frontier electromechanical research; the other could move him away from design precisely when he had returned with stronger technical training. Sanjeev says the organizational structure, not a lack of affection for Indian Railways, changed the answer. Had the system guaranteed a continuing specialist role, the decision might have favored returning. That caveat matters because it prevents the story from becoming a generic claim that ambitious engineers always need to leave India to do meaningful work.

His decision rule has two parts. Think very hard before choosing, because a career-defining fork deserves serious analysis. After choosing, trust that you made the best decision available to the person you were, with the information and constraints you had. Do not spend the next decade maintaining grievances against the road not taken. The opportunity may not work for everyone, but repeatedly reopening a closed decision makes it harder to build the life you actually selected.

For people with Indian roots, staying abroad can be emotionally complicated because returning remains a real and attractive option. There is always an argument that the same impact could have been created by staying inside the Indian system and fighting to improve it. Sanjeev does not offer a universal answer. He says each person must decide where they can be most effective, understand that the answer may change after five years, and avoid treating a later change as proof that the first move was a mistake. Consistent passions can make even detours cumulative.

He contrasts Indian migrants with people who come from places they are determined never to revisit. India can keep exerting a strong emotional pull because family, culture, professional opportunity, and a plausible life all remain there. That makes the stay-or-return decision harder, not easier. Sanjeev advises people to judge impact and alignment rather than use someone else's migration as a template. A decision can be honest at one stage and change later as the person's responsibilities, industry, or sense of purpose changes.

Naman asks about the immigration and citizenship path behind the story. Contemporary Indian students can face extraordinarily long employment-based green-card waits, so he wants Sanjeev to separate his own timeline from what a student should expect now.

Sanjeev calls the current system broken and emphasizes that he arrived in a different period. He came to the United States in 2001. In his recollection, his green card took roughly six or seven years, followed by the required five years as a permanent resident before citizenship. From arrival through citizenship, he describes the overall arc as approaching two decades. Those numbers are his historical experience, not current immigration guidance, and he explicitly contrasts them with the much more difficult backlog later applicants face.

He says he still loves India and remains Indian in heritage, but once he committed to the United States and crossed that bridge, he embraced citizenship rather than living indefinitely in regret. For him, adopting a country was part of accepting the consequences of the earlier decision. He does not present that choice as a verdict on what someone else should do.

Naman notices that Sanjeev arrived in 2001 and asks what the September 11 attacks changed for an incoming international student whose financing plan depended on engineering work and tuition support.

Sanjeev had applied to only four universities, largely using prospectuses left behind by a relative who had recently moved to the United States. He was working a demanding railway job and did not conduct the kind of extensive program research applicants now consider normal. He chose Boulder after a dean explained that local aerospace companies often offered internships aligned with his experience, which could help make the degree financially possible because his government salary and savings could not comfortably cover US tuition.

Then September 11 changed the plan. Off-campus aerospace internship options for international students disappeared, and Sanjeev arrived without the tuition waiver or assistantship he had expected to pursue. The remaining option was on-campus research. A hard-drive project was available, even though he had no direct hard-drive background. He argued that he had done related dynamics and mechanical work, accepted a three-to-four-week hourly trial, and earned a research assistantship for the following semester after his adviser evaluated the work.

The research assistantship was therefore not guaranteed at admission. Sanjeev had to make himself useful on a project outside his named specialty while knowing that the next semester's tuition depended on the result. He approached the hard-drive problem through similarities in vibration and dynamics rather than presenting himself as an instant expert. The adviser gave him a bounded test instead of a promise, and Sanjeev converted that test into funding. It is a practical example of how transferable experience becomes credible: identify the shared problem, then demonstrate the transfer under evaluation.

The academic return was intimidating after nearly a decade in professional work. In his first advanced mathematics class, the professor filled the board with differential equations while classmates ten years younger moved quickly through material Sanjeev had not used recently. He remembers trying to recall basic trigonometric relationships and wondering whether he had made the wrong decision. Grades mattered because a poor first semester could end his chance of receiving an assistantship or tuition waiver.

Sanjeev responded by recognizing the seriousness of the situation and betting on his ability to catch up. He worked intensely and took a seven-dollar-an-hour campus mailroom job to cover daily expenses. The contrast was sharp: in Indian Railways he had been an officer who rarely carried his own files; in Boulder he sorted mail, loaded a van, and delivered it across campus for four hours at a time.

The mailroom work also stripped status out of the decision. A title from one country did not pay rent or complete assignments in another. Sanjeev had to accept beginner conditions while protecting the long-term reason he had returned to school. He presents the shift from railway officer to hourly campus worker as part of the real cost of the American-dream story, not a motivational montage. The impressive outcome came later; at the time, he was simply trying to remain solvent, perform well enough to secure funding, and rebuild academic speed.

He had arrived in January without understanding Colorado weather and owned only dress pants and leather shoes. He walked through snow with wet socks to reach class and the mailroom. Sanjeev tells the story without pretending that poor preparation was noble. It created avoidable difficulty. What mattered was that he accepted the conditions, kept learning, and made the larger gamble work rather than treating discomfort as evidence he should quit immediately.

After graduate school, Sanjeev stayed at Seagate for years, became a senior manager, worked on challenging products, and helped deploy manufacturing technology in Singapore. The work was rewarding, but the industry was consolidating. Solid-state storage was taking market share from electromechanical hard drives, layoffs came in cycles, and an industry that once held more than 20 hard-drive companies had narrowed to only a few. His management-of-technology coursework taught him to read road maps and recognize when one technology was overtaking another.

Sanjeev explains the technological pressure behind that consolidation. A traditional hard drive uses a spinning aluminum or glass platter coated with magnetic media and a read-write head moving across it. The product is an intricate electromechanical system. A solid-state drive has no moving parts and behaves much more like integrated-circuit storage. As solid state improved, the mechanical industry's long-term position weakened. He did not leave because his current job had already collapsed; he left because the road map suggested that repeated layoffs and shrinking opportunity would continue.

He began applying outside the hard-drive industry and received a call from SpaceX in 2013. SpaceX had Falcon 9, Dragon, and a major NASA achievement behind it, but it was not yet the obvious giant people recognize now. Only a handful of Falcon 9 missions had flown, earlier launch failures were well documented, and whether the company would survive was still an open question. Sanjeev's supportive Seagate boss warned that the move was risky and offered to take him back if SpaceX failed within a year or two.

The NASA cargo mission proved SpaceX could reach the International Space Station and bring a Dragon capsule back, but it did not make joining risk-free. Sanjeev's boss had watched Silicon Valley companies rise and disappear, so the warning came from experience rather than resistance to Sanjeev's growth. The offer to return if SpaceX failed gave him a partial safety net and also reflected the culture he valued at Seagate. He remembers the people there as supportive enough to separate concern for his future from the company's desire to retain him.

SpaceX employed roughly 2,000 people then, and Elon Musk still interviewed candidates for roles like Sanjeev's. Sanjeev remembers Musk as distracted but very sharp and concise. The probing questions seemed designed to distinguish what a candidate had personally done from accomplishments merely associated with their team. Someone can claim to have led a project on a resume, but an expert asking detailed follow-ups can quickly determine whether that person owned the difficult decisions or was only present.

Sanjeev declines to dramatize the Musk interview or repeat private details. The useful lesson he does share is about technical credibility. A resume can attribute an organization's achievement to an individual with one polished bullet. The interviewer tests beneath the bullet: what exactly broke, which tradeoff the candidate made, what evidence supported it, and where their responsibility ended. Sanjeev could answer because his earlier roles had included analysis, manufacturing, quality, vendors, testing, and deployment rather than a title detached from the work.

Sanjeev joined a multidisciplinary team working to recover the Falcon 9 first stage intact and eventually reuse it. He arrived with no aerospace or rocket background. What he did have was a common engineering foundation: structural dynamics, vibration, mechanical analysis, experimentation, manufacturing, and years of learning unfamiliar systems. He had crossed from rail cars to hard drives before, so he understood that transferable principles do not erase a domain gap; they give an engineer a disciplined way to close it.

Even after receiving and accepting the SpaceX offer, Sanjeev nearly declined. A family home might cost around $300,000 in Minneapolis while the Los Angeles market approached $1 million. He had a young child and needed to consider housing, college costs, job security, savings, and career progression. He built a spreadsheet comparing compensation and likely savings at SpaceX with a more predictable future at Seagate. On a house-hunting trip to Los Angeles, he came close to sending a regret note and staying in Minnesota.

The spreadsheet was an attempt to make the invisible costs explicit. Salary alone could not answer the question because housing, the probability of a young company failing, family stability, and the value of future promotions all changed the comparison. In a straight-line financial projection, remaining at Seagate could look safer and perhaps better. Joining SpaceX required assigning value to learning, technical ambition, and an opportunity that might not appear again. Sanjeev nearly let the safer calculation decide, then concluded that he wanted the experience enough to accept the risk.

His advice is to analyze a major decision rigorously before committing: write down the variables, run the financial numbers, ask people who understand different parts of the risk, and notice where their advice conflicts. But do not follow any one person's recommendation completely. Advisers have different incentives, fears, and definitions of success. Sanjeev believes the final answer has to survive both analysis and the internal voice that tells you which future you actually want to build.

He remembers a University of Colorado commencement speaker using a quantum-mechanics metaphor. A difficult decision is like a closed box whose answer may be yes or no. You clarify the motivations and surrounding variables as far as possible, but the final state becomes real only when you choose and open the box. Sanjeev does not mean that evidence is irrelevant. He means that evidence cannot remove every uncertainty from a life decision, so the person living with the outcome has to make the final call.

At the time of the interview, Sanjeev was applying the same structural dynamics, vibration, and mechanical-strength principles to Starship. Looking back, he sees one continuous technical progression rather than disconnected careers. Rail cars, hard drives, Falcon 9 recovery, and Starship operate at different scales and inside different industries, but each chapter added to the same core body of knowledge. The detours strengthened the path because he kept choosing domains where that foundation could compound.

His Starship team focuses on structural dynamics and the problem of making a much larger rocket reusable. The nouns changed from railway vehicles and storage devices to launch systems, but vibration, loads, mechanical strength, testing, and the behavior of physical structures remained central. Sanjeev's career therefore argues for a precise version of transferable skills. Transfer does not mean every engineering job is interchangeable. It means a durable foundation can keep earning value when the person is willing to learn the new physics, language, and operating constraints around it.

Sanjeev closes with three ideas he calls the three I's. First, stay informed: keep building knowledge and excellence in whatever craft you practice, whether engineering, music, athletics, writing, or performance. Second, stay inspired: seek people and work that make you want to get out of bed and attempt something difficult. Inspiration does not have to come from your own profession; an engineer can learn drive from an athlete or artist.

Third, stay involved. Skill and inspiration need a purpose or they remain private potential. Sanjeev wants his technical work to improve an infrastructure layer that benefits many people. Lower data-storage costs can expand access for enormous numbers of users; lowering the cost of reaching space can create another broad set of possibilities. His preferred engineering problems are rising-tide problems, where better infrastructure creates value beyond a small group at the top.

Naman thanks Sanjeev for making unfamiliar worlds such as railways, hard drives, and rockets accessible without flattening their complexity. Sanjeev says his profile had recently spread online and brought many questions about the same transitions. He appreciates having one conversation where the decisions, technical through-line, and risks can be explained together rather than reduced to a job-title comparison.