Taro Logo

Senior Data Engineer Interview Experience - Chicago, Illinois

February 1, 2018
Negative ExperienceNo Offer

Process

Talking with the recruiter was great, but the technical phone screen not as much.

The recruiter hyped up the company as a fast moving startup, but with the stability and resources of a large company. He said the collaborative environment and work life balance was unmatched with anywhere he's ever seen before. He set me up with a different role than what I applied for after talking to me about my background and what I was interested in, which I really appreciated. Was told the next step would be a quick 20-30 minute call with the hiring manager.

Next step was a couple days later, but with a different manager and was told that it would be an hour long technical assessment. I was upfront about not appreciating that miscommunication since I didn't prepare an hour of time, but I pushed off my other meeting and continued the call anyway. The interview started casually, asking for my background and experience.

It was clear that there was a huge discrepancy between my work (ETL using tools like AWS and EMR, Airflow, Kubernetes, and Ansible and Terraform) and what he was expecting (self managed data centers and 24 hour long running map reduce jobs on Hadoop). I thought I could make it work by explaining why we used some of more modern tools and why I thought they were worth the upgrade, plus a little about how they work... But he didn't really care. He straight up told me that the company isn't really like a startup, they don't actually get to pick their tools, and that most projects they work on take about 6 months of planning and budgeting before they ever get started.

After that I was no longer as pumped about the role, but tried to spin it as maybe being able to provide a lot of experience and perspective different from the current data engineers. Instead we moved into a technical question they ask every candidate -- something about probability of finding a matching card between two equal decks. I told him I thought it was a stupid question and didn't see how it related to data engineer role. He agreed, but pushed me to try. I told him if I had a Jupyter notebook I could probably figure it out, but that I didn't think it was worth my time trying to work through it in my head and describe over the phone.

I got a response the next day from the recruiter that they decided it wasn't a good fit. I agreed and gave him my feedback. I recommended that they move the technical assignment to a take home test or portfolio review rather than an hour long phone screen than didn't test ability to do the job interviewing for.

Either way, people I've met who work here seem to like it. The office is nice. It sounds like the company might just be a fun experiment to get better talent with the underlying goal of having a spin off that AllState can use to resell the data it gets from drivers using the plug in telematics device to other insurance companies.

Questions

What's the sum of the cards between a random card in one deck and its matching pair in a second deck stacked on top?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Allstate Senior Data Engineer role in Chicago, Illinois.

Success Rate

0%
Pass Rate

Allstate's interview process for their Senior Data Engineer roles in Chicago, Illinois is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Allstate's Senior Data Engineer interview process in Chicago, Illinois.

Allstate Work Experiences