Capital One Data Scientist Interview Experience — 45-Minute Hiring Manager Screen, Rejected Within Days

The whole thing was 45 minutes, and it felt weird overall.

The interviewer showed up 6 minutes late. It felt like he was looking at my CV for the first time right there. Then he spent five or six minutes introducing himself: 4 years of experience, used to be on the fraud detection team, then moved to his current team doing marketing content, which splits into three areas: email text, prediction, and platform. And so on.

Then I chatted with him about two papers his larger group published this year and last year, and said that even though I don't work on NLP, I thought the papers were pretty good and interesting. (One was a GNN paper and one was an LLM paper on GEO, and honestly I couldn't say anything specific about them.)

Then he asked me to introduce my background. We chatted a bit in the middle about my master's school, UMD, which is in the DMV area, so he is probably based at the C1 headquarters in McLean, Virginia.

Then he asked which project would go into my PhD thesis, and he mostly asked about that one project. But it was an early piece of work from 2024, pure prompt engineering. Anyway he just kept asking and we kept talking about it. He didn't ask about any of my other projects...

Question: what was the task? I said binary classification.
Question: what metrics would I use? I said confusion matrix / AUC, ROC, that kind of thing.
Question: if the classification needs a metric and you have to set a threshold, what do you do? My answer: look at other baselines, run a basic model first, and normalize and shuffle the data to make sure it's balanced. In the end he said it depends on the specific problem (but I felt I had made that exact point at the very beginning and he hadn't been listening...).

Then he asked what I mainly did during my PhD. I said: using ML for medical image analysis.

For the last five minutes he let me ask questions. I asked about the work in that GEO paper, the split between research and engineering, the hardware on the team, and their workflow (he mentioned there may be more presentations).

His attitude was pretty good, and he even gave a few hints along the way. But I couldn't really tell what he actually wanted. Maybe I'm just not professional enough and don't know what a DS interviewer wants to hear.

But C1 responded fast: I interviewed on Friday and they rejected me on Tuesday, so at least I didn't waste a lot of time.