Kraken Digital Asset Exchange Data Analyst interview questions

The process took about three weeks. The recruiter was genuinely nice and very responsive—10/10 on that front. However, similar to other reviews for this role, the technical portion felt underprepared. I was told to expect questions on dbt, statistics, SQL, and product thinking. In practice, we barely touched product, and there was just one SQL question typed into a shared Google Doc/Notepad without a proper prompt—the first time I’ve experienced something like that. Because of this, it was unclear how they were actually assessing core skills: How was dbt knowledge verified? How were statistics tested? How was SQL evaluated beyond the basics? There’s also a take-home case study with a 24–72 hour window. The hiring manager only appeared in the final stage, which felt unusual. Overall, the analytics interview process seemed improvised and rushed, with limited attention to detail. There aren’t many Glassdoor reviews about the analytics interview yet, and the process feels like it’s still being figured out. Even when you cover thoughtful product angles, the decision can still be a ‘no,’ which may give the impression the process is still evolving Suggestion: It’d be great if candidates had the chance to briefly defend or discuss their work/case study rather than a yes/no outcome—they may have more to say than the format allows.

The recruiter had given me a pretty large list of things that might be asked during the interview including SQL/Python questions, ETL, code optimization, product metrics, and specifically said there would not be a live coding aspect. Naturally I spent quite a lot of time brushing up on these topics, all of which are quite large areas of study and only about 10% was asked about in the interview (only product metrics and SQL). When I got to the interview I found out that this role was not on a team that I thought I thought I was interviewing for. Overall I had a really hard time understanding what the interviewers were asking and even after clarifying (which took most of my time) it seemed like we were not on the same page. Also the interviewer asked me to pull up a code editor, share my screen, and live code. This was a privacy concern considering I was on a work computer. Despite this being an averagely difficult interview, I was left with a sour taste in my mouth and over the weekend decided that I would not proceed even if I were to magically make it through to the 'take home assignment' which apparently takes 24hours of work. I thought the prep topics and study was a waste of time generally which is my biggest complaint. The company seems like they are in a weird place direction-wise with being so close to IPO and it might be a awkward time to join.