Ho sostenuto un colloquio presso Gametime United (Seattle, WA)
Colloquio
The process starts with a short screening. And then a 5 question take home for sql and Python screening and then 3 interviews with a mix of technical team members and non technical stakeholders.
Domande di colloquio [1]
Domanda 1
Imagine that the CFO tells you that nfl sales are down you. How would you investigate that issue and what hypothesis would you test?
Process was easy enough. First call with recruiter is just asking about background. For the role should know financial topics, seemed to really emphasize knowing forecasting, time series modeling and analysis, and Experimentation of A/B testing and Analytics. Take home was 6 questions, 4 mysql and 2 open ended asking to analyze data. Be careful reading the questions as they can be unclear, got 1 question wrong and didn't move forward
Domande di colloquio [1]
Domanda 1
Mainly just aggregation questions of SQL data (avg, count(*), etc.)
Ho presentato la mia candidatura online. La procedura ha richiesto 8 settimane. Ho sostenuto un colloquio presso Gametime United
Colloquio
The data team that has been there the longest is incredibly nice, but also super-junior. They conduct the interviews! I have no idea why but leetcode easy (this was Oct/Nov 2022) and she thought it was a challenge or something. I have 8 years of experience, so multi-tasked with a seperate conversation while doing the coding round. The company's big issue at the time was ETL, so felt I could demo something in the SQL code that would be optimized for a pipeline as well. I'd heard afterwards they'd flagged my coding round because I'd created an outer query to the easy SQL question so that nulls are handled a certain way or something, even though I discussed that it will help for when any ETL would be scaled / modified downstream. The interviewer (one of their first hires) was so junior that we'd started to naturally assume a student/teacher role, but in a respectful way and very cool, while asking questions about their pain points and proposing solutions to them. I was excited to join the team and felt like I could be impactful help. For whatever reason she flagged me on it. I'm guessing it was due to a junior/senior thing and they may have needed a junior/junior thing. They'd had a follow up round with another interviewer and asked another easy question I had not done using SQL in x years (it's usually handled by python). I blanked, was completely focused on the realization that the team needed to be convinced to hire more senior people. Just sat there thinking about the flight I was going to catch that day, and empathy for the company's ETL issues. Tried not to look back - ETL issues with an ecommerce site that handles realtime transactions are a sign of stressful tech debt they likely dealt with this year.
Domande di colloquio [1]
Domanda 1
Some ecommerce aggregate SQL - average order value vs median order value, but off a table that has an extremely small grain so that it is a long SQL query. Usually this stuff is handled in python and I'd blanked (thinking back 6 years prior when I did this w SQL instead of python).