Taro Logo

Senior Data Engineer Interview Experience - United States

September 9, 2021
Negative ExperienceGot Offer

Process

The entire process, from the recruiter call to the final result, took one month. In between, you have to prompt them for the next steps.

  1. Home assignment - Dimensional modeling
  • They asked me to model their GitLab process with fact tables and dimensions. I created it with the data I had and made a few assumptions.

Overall, it was a waste of time. No one asked about it during the interview. It took more than 8 hours, but they claimed it would take 3 hours. One could ask them for payment for those hours.

Screening was done by a junior-level person with little experience.

  1. SQL query - a simple one, but she asked open-ended questions that made no sense.

One should ask for the score breakdown for the SQL query and other questions. If you get any wrong, you fail, so why waste 60 minutes?

  1. Next steps were all functional and open-ended questions.

Overall, a very bad experience. They will make you wait for a month, so ask the recruiter to complete everything in two days or forget it.

Questions

  1. Have you done any complex data models in your life?
  2. Anything which didn't work, and what alternative did you implement?
  3. Two SQL queries - very easy ones, using LEFT JOIN and RIGHT JOIN.
  4. What are the types of fact tables?
  5. Mention Ralph Kimball 10 times so that they hire you. :-)

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the GitLab Senior Data Engineer role in United States.

Success Rate

0%
Pass Rate

GitLab's interview process for their Senior Data Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for GitLab's Senior Data Engineer interview process in United States.

GitLab Work Experiences