Envié una solicitud electrónica. Acudí a una entrevista en Block
Entrevista
Applied via LinkedIn. The recruiter was nice. The first round was a SQL and a python/R tech screen. When they say python or R they really mean python. The questions are absolutely not made for R users. The question was about strings and dictionary which does not translate well to R. Had to use a very twisted apply function to get to the answer which I'm pretty sure the interviewer had no clue about the effort involved.
The onsite rounds were a couple of case studies and product metric rounds. Pretty straightforward. Two onsite tech rounds - process data and build a model. The problems which should have been take home projects were meant to be coded in 60 min. I don't know who can build meaningful models on data you have little context on in 60 min but it's not me. Overall the tech rounds were stupid and felt like a waste of time.
Interviewers and recruiters were nice
Preguntas de entrevista [1]
Pregunta 1
Python easy problem about strings (does not translate well to R)
Solicité el puesto a través de la recomendación de un empleado. El proceso duró 6 semanas. Acudí a una entrevista en Block en dic 2023
Entrevista
The interview process was pretty good up until the final FOUR HOUR 'on-site' which included technical components and lots of scenario discussion. One interview expected you to write a rhetorical SQL code with a schema outline but no actual IDE to write or execute the SQL.
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Block en oct 2023
Entrevista
Spoke with the recruiter about previous work experience. Asks you to describe a project in detail and explained the interview process with consists of a technical assessment and meeting with the hiring team
Envié una solicitud electrónica. El proceso duró 4 semanas. Acudí a una entrevista en Block
Entrevista
It was streamlined and clear. Got to onsite. For the technical onsite The interviewers were somewhat unprepared for the cases and the emphasis was on how on the fly you can write code which I think is a very strange criterion for a role that needs time and experimentation ... it was rushed and disorganised. The nontechnical was just based on churn analysis. Based on my feedback I did a great job on the technical part. I was lacking in the other part so shouldn't comment on that.
Preguntas de entrevista [1]
Pregunta 1
Technical: fast coding round they expect you to clean and model data in 50 min. Non-tech: churn analysis
