Engineer's front-line role reshapes rippling, and maybe startups
Kanav Bhatnagar isn’t your typical software engineer. He’s a ‘Field Delivery Engineer’ – a role popularized by Palantir and now gaining traction at companies like Rippling – and his days are spent immersed in the messy reality of how clients actually use software, not just building it. It's a hybrid role, demanding coding prowess and an unusual empathy for the user, and Bhatnagar believes it could become a breeding ground for future founders.
From amazon's scale to actively ai's focus
Bhatnagar’s journey began at Amazon, a classic starting point for many aspiring engineers. “It was a fantastic learning experience, teaching me the fundamentals,” he explains. But the sheer scale of the organization left him yearning for a more intimate environment, where he could directly influence product decisions. After two and a half years, he sought a change, landing at Actively AI, a sales startup. The role of Field Delivery Engineer, or FDE, beckoned – a position blending software engineering with deep business acumen. He describes it as “the hottest role in AI,” and it resonated with his desire for a more holistic understanding.
Decoding client needs, one line of code at a time
Now, at Rippling, Bhatnagar spends his days translating client challenges into actionable code. Forget abstract requirements documents; he’s on the front lines, talking to employees, observing workflows, and ultimately delivering bespoke solutions. “My main job is to listen,” he says. “Software engineers can often feel disconnected from the end-user, but in this role, I’m right there, understanding their pain points firsthand.” He cites an example of a restaurant chain struggling with cumbersome payroll data tracking – a process reliant on spreadsheets and manual entry. Bhatnagar’s task is to eliminate that friction, integrating automation and AI directly into Rippling’s platform.
The work isn’t solely about coding. It’s about rapid context switching, moving from client meetings to debugging sessions to product discussions. He emphasizes the importance of strong communication skills, the ability to articulate technical concepts to non-technical stakeholders, and the capacity to diagnose problems quickly, much like a consultant navigating complex business scenarios. Bhatnagar leverages experience with consulting interview questions to hone his abilities, focusing on “rapid diagnosis, clarifying questions, and a clear action plan.”
The satisfaction, he notes, comes from seeing a client’s reaction after multiple iterations: “'This is exactly what I wanted’ – that’s incredibly rewarding.
A training ground for entrepreneurs?
Bhatnagar sees his FDE role as more than just a job; it’s a potential launchpad for his entrepreneurial ambitions. “Someone described the FDE role as a training ground for founders,” he muses. The exposure to the entire business lifecycle—from sales to product development—provides a unique perspective that’s rarely accessible to engineers deeply embedded in code. Even if the current AI hype subsides, Bhatnagar believes FDEs will remain valuable, serving as crucial liaisons between clients and software, managing complex contracts and ensuring seamless integrations. Palantir’s long-standing use of FDEs, predating the current AI frenzy, is a testament to the role's enduring relevance.
As Bhatnagar continues to evolve within Rippling, he’s keenly aware that the FDE landscape remains undefined, a frontier of innovation. But one thing is clear: the ability to bridge the gap between Technology and the human experience—to listen, adapt, and build—will be invaluable, regardless of what the future holds.