• Kanav Bhatnagar's job title, forward deployed engineer, has been described as the "hottest role in AI."
• He said his job is to be a customer-facing engineer who tailors products for clients.
• Context-switching and communication are important skills for FDEs, he said.

This as-told-to essay is based on a conversation with Kanav Bhatnagar, 24, a forward-deployed engineer at Rippling, an HR tech company, who lives and works in New York City. The following has been edited for length and clarity.

I got into software development because I wanted to build cool stuff.

Amazon hired me as a software engineer out of college, and it was a big learning opportunity, teaching me the fundamentals of engineering.

But it was a behemoth of a company, and I eventually wanted to work in a smaller environment where I could take more personal ownership over product decisions and learn more on the job.

After 2 ½ years at Amazon, I interviewed at a sales startup called Actively AI, where I landed a role in forward-deployed engineering.

The "FDE" role was popularized by Palantir, and it has been described as the "hottest role in AI." I liked that it combined software engineering with understanding business.

I spent roughly six months at Actively AI before I joined the AI-forward HR tech company Rippling as a senior FDE, in October 2025.

I've now been an FDE for roughly a year. Put simply, I'm a customer-facing engineer who tailors our product to each client. They describe their challenges and needs, and I build solutions and customizations.

Here's what my day-to-day is like, and the skills you need to break into this role.

My primary job is listening to customers. The results are very rewarding.

Software engineers can feel far removed from customers, because they often can't see their impact. In this job, I'm closer to the front lines.

A core software engineer can build something that serves the majority of use cases, but AI tools usually need more customization to work properly than regular software features. That's when an FDE steps in.

For example, a restaurant chain might have a labor-intensive process for tracking their payroll data that involves spreadsheets and manual data entry, which I'd help them to eliminate within Rippling's platform by using custom code and AI.

My primary job is listening to customers and understanding their problems, which was a learning curve for me, coming from a software engineering background. On a day-to-day basis, I'm in a lot of customer meetings, including visiting businesses who use our product to talk with employees about their experience with it. I probably spend an equal amount of time coding solutions and interacting with our core product teams.

Context-switching is an important skill to master in this job, where you could go from talking to a customer to debugging something to jumping onto another customer call shortly after.

I don't rely on an engineer to code something for me. I make a lot of decisions about the shape of the product and how to execute on it, which I really enjoy. It's very rewarding when a customer looks at what I've built after multiple iterations and says, "This is exactly what I wanted."

Technical and communication skills are equally important as an FDE

I think it would be pretty hard, although not impossible, to become an FDE without a technical background. With the dawn of vibe coding, it might become easier, though.

In my experience, FDE interviews feature technical rounds that test your coding skills, like in traditional software engineering interviews. You also have to show you can talk with any customer, including non-technical people, by asking the right questions to understand a customer's problem, and talk through how you'd design the solution.

To prepare for interviews, I have used consulting industry interview questions, which require you to explain how you'd meet client requests. I think both fields overlap, requiring rapid diagnosis, clarifying questions, and a clear plan of action.

There's probably more breadth than depth of technical knowledge required. In today's age of rapidly evolving technology, I try to spend time outside of work understanding what's new in the AI world and what new AI tools I can be using in my workflow by talking to colleagues and researching online.

I think my job is preparing me to be a founder one day

I'm interested in founding my own company one day, and I've previously heard someone describing the FDE role as a founder bootcamp. It provides a good foundational layer for entrepreneurship, helping you understand how a business functions from the sales process to how to build things.

The FDE role is evolving and no one really knows what direction it's heading in. Even if AI turns out to be unprofitable, I think FDEs will still have a place because of the demand for customer software. Products are becoming easier to build, and people in this role will be needed to handle large contracts with clients.

Palantir is an example of a company that's had FDEs since the 2010s, even before AI was mainstream.

• Tejal Rives hoped adopting AI at work would help keep her safe from tech layoffs.
• However, she lost her job at Amazon during layoffs in October 2025.
• Rives was disheartened but was glad the experience taught her about AI.

This as-told-to essay is based on a conversation with Tejal Rives, 35, who lives in Arizona. The following has been edited for length and clarity.

In October 2025, I read a news article that Amazon was planning to cut jobs. I'd survived other layoffs, but this time my gut told me I'd be affected. Sure enough, not long after, I received an email that my position as a product marketer was being eliminated.

I was one of 14,000 people impacted, and even though I understood the decision wasn't personal, it was very disheartening. I thought up-skilling in AI would make me safer from layoffs, but even though it didn't, I still think professionals should focus on learning this one important AI skill: prompt engineering.

I thought working on AI could safeguard my job

At the time of the October layoffs, there was debate around whether AI was the reason.

The company was encouraging us to use AI at the time, but I don't think it took my job. I wrote descriptions for internal products at Amazon, and when I used AI to help, I'd need to ask it to rewrite its output without fluff words. It didn't sound like how people talk. Despite my ethical qualms, I used AI, but, in my opinion, it was nowhere close to replacing my role.

Before I was laid off, I helped build an internal site for Amazon using AI. I hadn't really coded before, but with a colleague's help, I learned how to vibe code with a lot of trial and error.

I thought using AI for this project and showcasing different skills would make me more valuable to the company, but in the end, it didn't keep me from being laid off.

Initially, I felt like I'd wasted time by learning something I likely wouldn't use again, but overall, I don't think my efforts were wasted. The most important thing the experience taught me was prompt engineering, the practice of asking AI the right questions. I want to be minimal with my use of AI for ethical reasons, including around the water resources needed to power data centers. Efficient prompt engineering helps me ask AI my question once, without needing to clarify three or more times.

I'd highly recommend that other professionals learn prompt engineering to up-skill themselves in the age of AI.

The workforce has shifted, and you're likely going to need to learn AI and use it at your job, regardless of your moral qualms. We need to up-skill to survive.

I have my own business, and use AI very rarely

My husband and I already agreed that if I were laid off, I'd focus on being the primary parent to our child as well as on my career coaching business, called Do My Resume LLC, which I was running on the side of my Amazon job. Before being laid off, I planned to eventually quit my job and focus on it full-time.

I didn't realize how burnt out I was after four years at Amazon, though, and it took me a while to pivot into working on my business. For roughly three weeks, I didn't touch my computer. I took up sewing and house-cleaning projects because I needed separation from my screen.

Now, my life is slower than it was at Amazon. I spend roughly four hours a day, six days a week, on the business, and spend the rest of my time taking care of the house and my family.

The business provides career coaching and résumé-writing services, but we don't use AI to write résumés, because it's humans who read them. Recently, I used AI to give me advice about starting a YouTube series for my business, so I will use this technology to help me flesh out ideas, but very rarely. I haven't vibe-coded since the project at Amazon.

My husband is the breadwinner, and we can survive on his income, but the business is bringing in some fun money for me.

I think people should prepare for layoffs in the age of AI

Being laid off helped me remember that, at the end of the day, your job and company shouldn't be your entire life. It shouldn't come before your well-being.

I wish I hadn't sacrificed time with my child to get projects done towards the end of my time at Amazon. I'm glad I'm no longer sacrificing that time.

I think there will be more layoffs that will be attributed to AI's efficiency, and professionals should always be prepared. Reskilling in the age of AI won't necessarily stop a company from laying you off, but it might help you land a role faster.

Amazon did not provide a statement in response to a request for comment from Business Insider.

Do you have a story to share about being laid off in 2026? Contact this reporter at ccheong@businessinsider.com