J'ai postulé en ligne. J'ai passé un entretien chez Block
Entretien
The interview process was insulting, when it came time for the technical interview I told the recruiter multiple times that I program in R (the job posting and interview request said R/Python). When it came time for the interview the interviewer said it would be in Python, I said that I told the recruiter I program in R and the interviewer said that she didn’t even think the interview question could transfer to R. It did not. I guess I should’ve prepped Python instead, the question was easy enough that had I prepped my 5 year old Python notes that I could’ve easily passed it. I prepped a bunch of stats and data transformations in R instead, since that’s what I currently do in my DS job. The interviewer didn’t even know enough R to help me along with the question. For the second part, I got every SQL question right. Then I got a generic rejection from a no-reply, not even from the recruiter I was in contact with. The whole process was extremely insulting and I won’t be applying to Square again.
J'ai postulé via la recommandation d'un employé. Le processus a pris 6 semaines. J'ai passé un entretien chez Block en déc. 2023
Entretien
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.
J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Block en oct. 2023
Entretien
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
J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Block
Entretien
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.
Questions d'entretien [1]
Question 1
Technical: fast coding round they expect you to clean and model data in 50 min. Non-tech: churn analysis