This as-told-to essay is based on a conversation with Abhinav Bohra, a senior applied scientist at Amazon. He's in his 30s and lives in Seattle. The following has been edited for length and clarity.

For most of my career, everything I built lived and died inside Amazon.

I joined Amazon in 2019 as a data scientist and eventually became a senior applied scientist in 2024. My background is in AI recommendation systems, and I work on models that help determine which products shoppers see on Amazon.

While I was building a reputation inside the company, I wasn't building much of one outside it. People in the industry outside Amazon were publishing research papers on the same problems I was solving, and I never joined the conversation.

I eventually realized that without a public record of my work, I was missing opportunities to speak at industry events, serve on conference committees, and build a reputation that could help me if I ever needed to find a new job. When it came to professional opportunities outside Amazon, it felt like I was starting from zero.

The lesson I learned was that internal reputation doesn't travel. My biggest career regret is how long I took to show up outside the company. I'd be a few years further along if I'd realized this sooner.

At first, I was hesitant to publish externally. I treated anything within a mile of my day job as radioactive, which meant I shared nothing publicly. There are processes for publishing company work externally, but they can require documentation and review, and I didn't want to go through that process.

Eventually, I realized I could do external work without using the company's proprietary data or information. The data was proprietary, but my ideas and research were not.

Take a problem I worked on a few years ago: How do you train a good AI model when you have almost no labeled data? Research teams everywhere hit that wall.

Create a BI Job Scout and get opportunities matched to your goals.

Take a smarter break in your day – and see how far you get.

Add BI in Google so our reporting is easier to find when you’re searching for what matters.

I developed some rules for myself. If a problem exists in published research, it's a conversation. If it only exists in our codebase, it's not. Nonpublic data, internal metrics, customers, code, roadmaps, and unreleased products are all off the table. If I'm still unsure, I won't share it.

Business Insider is speaking with tech workers who've found themselves at a corporate crossroads — whether due to a layoff, resignation, job search, or shifting workplace expectations.

It surprised me how much meaningful technical discussion was still possible without revealing anything proprietary.

Source: Read the original article on www.businessinsider.com