Dev versus Delta: Demystifying engineering roles at Palantir
<p>As a Hiring Manager for engineers, I get a lot of questions about our unique engineering model. Specifically, people want to know: what’s the difference between a <strong>Software Engineer</strong> and a <strong>Forward Deployed Software Engineer</strong>? I polled Palantirians from around the globe for their answers to these and other common questions from candidates. Whether you’re applying for a job here or you’re just curious about how we operate, I hope this post helps you understand how we build and deploy software, and what it’s like to work in these two roles.</p>
<h1>Wait, what’s a Delta?</h1>
<p><strong>Software Engineers </strong>and<strong> Forward Deployed Software Engineers </strong>are our biggest engineering roles by headcount. Internally, we call them “Devs” and “Deltas.” (While you can guess the origin of “Dev,” “Delta” is a throwback to our early days, when each team in Business Development was named after a letter in the NATO alphabet.)</p>
<p><strong>Devs (Software Engineers) develop and engineer our software platforms, Palantir Foundry and Palantir Gotham.</strong> Devs are part of Product Development, one of our four main divisions (the others being Business Development, Internal Development, and Sales). A Dev is part of a team that owns a platform component, such as Foundry Storage Infrastructure or Gotham UX, from end to end. Devs spend their time writing code and working with their team to make design and architecture decisions that impact code that will ultimately be deployed to many different customers for many different use cases.</p>
<p><a href="https://blog.palantir.com/dev-versus-delta-demystifying-engineering-roles-at-palantir-ad44c2a6e87">Visit Now</a></p>