Loyalty Cost 10 Tech Workers — Here's What They Regret Most

Ten tech professionals from Amazon, Google, Meta, and Microsoft told Business Insider what they wish they had done differently. The most common regrets cluster around three themes: staying too long at one company, missing the window into machine learning, and failing to build a professional presence beyond their employer's walls.

Mike Kostersitz, a senior director at Nike, spent 31 years at Microsoft before being laid off last year. He said he kept believing loyalty was a two-way street. "In the end I learned the hard way that it wasn't; the market shift hit me anyway, loyalty or not." Kostersitz, in his early 60s, added that if he could do it over, he would have started testing the market well before the layoff.

Microsoft carries an Alpha Score of 71 at $496.88, reflecting moderate institutional positioning. The layoff of a 31-year veteran underscores how tenure no longer shields tech employees from restructuring.

A software engineer at Meta said his biggest regret was not sticking with machine learning when he had the chance. In 2019 and 2020 he built ML models at an edtech startup. The direction of the field felt clear even then. But in graduate school he chose systems and infrastructure instead, calling it the safer, more rigorous path. "If I had stayed on the machine learning side, I would have been years into it by the time the field took off," he said. He does not regret the systems background – it makes him valuable now – but wonders what the other path would have looked like.

Sneja Shah, a senior technical program manager at Red Hat, said she wished she had immersed herself in AI even earlier. Her career began in data analytics, where she built a foundation in data engineering and business intelligence. Those years gave her the skills to transition into AI strategy, but she wants she had started working directly on generative AI sooner. The pattern suggests tech workers who delayed the AI pivot now face a steeper catch-up in the hottest labor market segment.

Abhinav Bohra, a senior applied scientist at Amazon, said for most of his career everything he built lived and died inside Amazon. People outside were publishing on the exact problems he was solving, and he never joined the conversation. He told himself the work was proprietary. "Honestly, the data was proprietary. The ideas never were." He has since started speaking at industry events, reviewing papers, and becoming more involved at conferences. "Internal reputation doesn't travel," he said.

Nikhil Singh, a data scientist at Amazon, echoed that regret. He spent over a decade building products and solving problems but very little time writing or speaking publicly. "Within an organization, people may know the ideas you developed. But outside it, you can easily be seen as simply another person with a title on LinkedIn." He wished he had started building a public body of work sooner, to create a broader professional identity beyond the companies where he worked.

A tech lead at a company in the insurance industry said his biggest regret was turning down a great job offer from his former boss, a vice president at his previous company. He declined because he had made a commitment to a client and wanted to see it through. Five months later, he was reassigned to a different client anyway. He missed the opportunity to work for a leader who knew his strengths. "I think I could have grown alongside him had I accepted the offer," he said.

An engineer at Amazon said her biggest regret was focusing too much on execution early in her career. She spent a lot of time making sure she built things well but not enough time stepping back and asking what customer problem she was solving, why it mattered, or what impact it would have. She now views that as the difference between a good engineer and someone who builds products people truly value.

Sachin Jain, a data analyst at Google, regretted the timing and location of his master's degree. As an international student, he came to the U.S. during a period of significant policy shifts and one of the toughest tech hiring markets in years. He wished he had chosen a university more embedded in a major tech ecosystem like Silicon Valley. He does not regret the degree itself but says the experience reinforced how much environment and timing matter alongside individual effort.

Aimen Moten, a software engineer at Google, said she regretted not exploring more career paths in tech. She focused so heavily on software engineering that she never explored roles like product management, solutions engineering, or cybersecurity. When she talks to people in those roles, she sometimes wonders what her career would have looked like if she had taken a different path.

For investors, these interviews highlight several shifts in the tech labor market. The loyalty regret points to higher expected turnover among long-tenured staff – workers who once stayed for decades now plan to test the market earlier. The AI regret suggests a supply-demand imbalance for machine learning talent, as workers who pivoted late compete with those who stayed in the field. The public reputation regret indicates that personal branding and external contributions are becoming leverage points for salary negotiation and job mobility.

Companies that encourage internal mobility, public speaking, and conference participation may retain talent better than those that keep employees behind walls. The engineer at Meta summed it up: he does not regret the systems background, but he knows he would be years ahead had he stayed on the machine learning side.