Talking About Your Projects as a New Grad
Present a new-grad project in a Palantir FDSE interview in a way that stands up to detailed probing. Organize your account around the problem, your own role, your collaborators, a key engineering decision, how you validated it and what you learned. Defend a design choice with a concrete counterexample, credit shared work accurately, report test results without overstating impact, and give a crisp 90-second overview that holds up under follow-up questions.
We'll cover the following...
A three-person equipment-booking prototype gives a new grad enough material for a substantive engineering conversation. The substance comes from explaining why the conflict detector behaves correctly, who built it and what the tests actually showed. For your own project, choose work whose decisions you can reconstruct when the interviewer asks for details.
What project evidence should I lead with?
Suppose your project record contains this evidence card:
Problem: An academic assignment required conflicting equipment reservations to be flagged for a lab coordinator’s review.
Your contribution: CSV validation, conflict detection and six local tests in Python.
Collaborators: One teammate built the interface; another prepared sample CSVs.
Observed result: Six tests passed. A sample run produced two conflict pairs and one rejected row.
Limits: No deployment or measured user benefit.
Academic, personal, research and internship work can all supply concrete evidence. Choose a project you understand well enough to explain its problem, contribution, decisions, validation, results and learning. A small contribution with reconstructable reasoning gives the listener more to investigate than a large feature list.
The supplied US Government Forward Deployed Software Engineer (FDSE) posting values understanding how technical decisions affect users, collaborating with technical and non-technical people, continuous learning and independent decision-making. Those are statements from the posting, rather than an official project-interview scoring rubric.
Technical depth comes from explaining behavior under a stated requirement and connecting it to evidence you can substantiate.
How do I turn six notes into a project account?
Prepare your account in this order:
Problem and intended user: A lab coordinator needed ...