Palantir's own posting has no findings-back sentence, yet accounts of its earlier years describe findings reaching the product side.
A 2019 Palantir post describes two engineering roles. Devs, the product engineers, build the product: their focus, it says, is "one capability, many customers." Deltas, the company's Forward Deployed Software Engineers, work at customers: theirs is "one customer, many capabilities." Devs sit in Product Development. Deltas sit in a different division, Business Development.
So the people closest to the customer sit apart from the people who build the product. Two accounts describe how the work crossed over.
Nabeel Qureshi, who joined Palantir in 2015, writes that FDEs were typically expected to work onsite three to four days a week, and that product engineers then turn what the FDEs build into product. Gergely Orosz, a newsletter writer, reports that after Palantir launched Foundry, its data platform, more FDEs went back to engineering to work on it, bringing field experience with them. Neither account describes a schedule, so they show part of a return path, not a full one.
Where the Deltas sat did not settle it. They sat outside Product, and findings still reached it.
Marc Andrusko, an investor at a16z, warns about the other half: FDEs in a separate professional-services unit lose the link back to the product team and drift toward a services business. That is a warning, not outcome data. Placement alone does not decide it. The link does.
My reading of what this costs: with a return path, the second customer starts from what the first one needed. Without one, the second starts over, and you are running a services business, one that sells engineers' time customer by customer.