Anduril · Primly Community

Anduril data scientist interview (SQL + case + stats), what the loop looks like

ds_dmitri · 5 replies

Just went through Anduril's DS loop for a data scientist role on their autonomy analytics team. The loop is not what I expected, partly because Anduril's data science function is closer to applied research than business intelligence.

Loop structure: Recruiter screen (30 min, standard motivation + background) Technical phone screen with a DS (45 min, SQL + stats) Onsite: 4 rounds over a day (SQL deep dive, case study, ML/stats, behavioral)

SQL round:

Harder than average. They gave me a schema representing event logs from an autonomous system. Window functions, CTEs, and aggregation were all in play. One question had a subtle gotcha around NULLs in a join that I almost missed. They're testing whether you can actually use SQL to analyze real messy data, not whether you know the syntax. Practice writing queries against normalized schemas with missing data, not toy examples.

Case study:

This was the most Anduril-specific part. The scenario: a sensor fusion algorithm is producing more false positives than expected in certain environmental conditions. How would you investigate this, what data would you pull, what analysis would you run, and how would you communicate findings to engineers? I think they're really evaluating whether you can bridge between data and engineering and whether your analysis would actually drive a decision.

Stats/ML round:

Fairly standard: A/B testing (what's your minimum detectable effect, how do you handle interference between units), bias-variance tradeoff, discuss a model you've built end-to-end. No whiteboard coding of ML algorithms but be ready to explain what's happening under the hood of gradient boosting if they ask.

Comp I saw: A friend who joined as DS2 in early 2026 in the Costa Mesa office said their total comp was around $180-195K with a meaningful equity component. That's not FAANG-level but it's strong for defense tech, and the mission draw is real for some people.

5 replies

analyst_ana

The NULL gotcha thing is so annoying. That's always where I get tripped up too. Was it NULL in a left join situation or something more obscure?

ds_dmitri

Left join where they were summing a value from the right-side table. NULLs from unmatched rows were being treated as 0 in one version of the query but the correct answer was to exclude them from the denominator. Classic gotcha but embarrassingly easy to miss when you're nervous.

ml_mike

The 'bridge between data and engineering' framing in the case study is exactly right for defense tech DS. You're not presenting to a marketing team. Your consumer is engineers and operators who will act on what you say. Writing skills and precision matter a lot more than at a consumer tech company.

ds_dmitri

Agree. My interviewer explicitly asked how I'd communicate the analysis to a skeptical engineer who doesn't trust models. Having a clear answer to that was more important than the specific methodology I chose.

de_derek

The comp number tracks with what I've heard. Not FAANG, but the interesting problems and the mission make up for some of that gap for the people who go there. Equity upside is real if the defense tech wave continues.