Engineer's field work: how actively ai's bhatnagar bridges code and clients

The relentless churn of AI development often leaves a critical gap: understanding how algorithms actually work for the people who use them. Kanav Bhatnagar, a Senior Field Delivery Engineer at Rippling, isn’t just building code; he’s translating business needs into bespoke AI solutions, a role he describes as a crucial bridge between engineering and the messy reality of client operations.

From amazon's scale to actively ai's focus

Bhatnagar’s journey began at Amazon, a baptism by fire in the world of large-scale engineering. “It was a fantastic learning experience, teaching me the fundamentals,” he told Business Insider, “but I felt a pull towards a smaller environment, one where I could own more of the product decisions and accelerate my learning.” That desire led him to Actively AI, a sales-focused startup, where he embraced the burgeoning “Field Delivery Engineer” (FDE) role – a title popularized by Palantir and now considered a hot commodity in the AI space.

The FDE position, as Bhatnagar explains, is about more than just writing code. It's about deeply understanding the client's challenges. “My day-to-day involves a lot of listening,” he notes. “Software engineers can often feel disconnected from the impact of their work. In this role, I’m on the front lines.” He’s essentially a bespoke AI architect, tailoring solutions to specific needs – a task that requires both technical prowess and a keen ability to communicate with non-technical stakeholders.

Decoding the fde role: customization and client immersion

Decoding the fde role: customization and client immersion

Consider the scenario Bhatnagar describes: a restaurant chain struggling with cumbersome payroll tracking processes, reliant on spreadsheets and manual data entry. “I would help them eliminate that within Rippling, using custom code and AI,” he says. It’s a blend of engineering, problem-solving, and a relentless focus on the client experience. A significant portion of his time is spent in meetings – sometimes even visiting client sites to speak with employees directly, gauging their experience with Rippling’s product. He splits his time roughly evenly between coding and client interaction, a testament to the demanding, yet rewarding, nature of the role.

What separates a successful FDE? Bhatnagar stresses the importance of adaptability. “It’s a constant context switch – you might be debugging something, then jump into a client call, and then back to coding.” The ability to make independent decisions about product direction is a key differentiator, and the satisfaction of delivering a solution that precisely meets a client's needs – “'This is exactly what I wanted' – is immensely gratifying.

Beyond coding: the skills of a client-facing engineer

Beyond coding: the skills of a client-facing engineer

While a technical foundation is undoubtedly necessary, Bhatnagar emphasizes that it’s not the only requirement. “I think it would be difficult, though not impossible, to become an FDE without some technical background.” However, he believes the rise of low-code and no-code tools could democratize the role somewhat. Interview preparation, he notes, involves both technical coding assessments and the ability to articulate solutions clearly to clients, skills he hones using consulting interview questions – a surprisingly effective parallel. The focus is less on deep technical expertise and more on breadth of understanding and rapid problem diagnosis.

Bhatnagar views his current role as a training ground for future entrepreneurial endeavors. “Someone described the FDE role as a ‘founder bootcamp,’ and I think that’s apt. It gives you a really solid understanding of how a business works, from sales to product development.” While the long-term viability of AI remains a subject of debate, Bhatnagar believes the demand for client-facing software experts, like FDEs, will persist – even if AI itself proves less profitable. Companies will always need skilled individuals to manage complex client relationships and tailor software solutions, a legacy Palantir has cultivated since the early 2010s.

As Bhatnagar puts it, “The role is evolving, and nobody really knows where it’s headed. But I’m enjoying the ride – and the invaluable lessons it’s teaching me.”