Really long process:
- Online IQ test
- Recruiter phone screen
- Take home challenge
- CoderPad coding interview
- Systems design interview
- CTO interview
- Bar raiser
Applied online and two weeks later I got reached out to solve an IQ test. It was a 15 minute IQ test. 50 questions that involved math, patterns, vocabulary, logic — all the likes of any standardized test.
Shortly after I get reached out by the recruiter for a 30 min phone interview to talk about my experience and the role I'm applying for.
I was given a take home challenge which was building a web app where you take a rest api for photos and make a photo album app. Fairly simple, the challenge was mainly SSR and creating pagination.
Two weeks later I have my "on-sites" through Google hangouts. First is a CoderPad coding interview with one of the directors. Question was about string manipulation and pattern matching. He was kind and helpful when I was getting stuck with the problem but I couldn't help but feel like he did not want to be there interviewing me lol.
Second is a systems design interview with another director. He was a really easy going person. Asked me about my background and front-end technologies I use. Interview consisted of him displaying a figma mockup from their design team and proceeding to ask about how to design and implement the front end system. My fav bit of the interview tbh, he was really engaging and fun to talk to.
Last for the on-site is an interview with the CTO. Briefly asked me about my experience and projects and then mainly wanted me to just ask him questions about the company. Appreciated his down-to-earth and real personality. I could tell he was very smart and he seemed like a great lead. Only thing that rubbed me off in a weird way was that the moment I joined the call, he starts by mentioning that he doesn't have a lot of time.
Recruiter calls me about the interview and my interest. Then I'm told that I'll be reached out to see if I made it to the next and final round of the interview which is a bar-raiser (behavioral interview with someone outside of the engineering team), which I did not.
Objectively, it was a good interview experience. A bit too long and I don't agree with an IQ test but it was a fair interview overall. Subjectively though, it was 'meh'. I wish the on-sites were a bit more "personable" if that makes sense. Their team in New York is very small right now and I get that they're probably going through a lot of interviewee's but I could not help the fact that they didn't want to really get to know me or my story
Questions d'entretien [1]
Question 1
Pattern matching: creating a function to see if two strings are matching based on a set of rules
Pretty long interview process.
A cognitive pre-assessment, a 30 minute meeting with a hiring manager, a takehome assignment that takes at least one full day of dedicated work, then a power day with one hour of algorithms, one hour of front end system design, and finally a 45 minute behavioral with the CTO.
It's a lot, but the package is highly competitive and the interviewers were all down to earth people.
Questions d'entretien [1]
Question 1
Design a marketing campaign dashboard's front end.
J'ai postulé via une agence de recrutement. Le processus a pris 1 jour. J'ai passé un entretien chez Rokt (Sydney) en oct. 2019
Entretien
First, it was the online testing, mostly are Angular questions. Then the on-site interview. Two interviewers. First I was asked to talk about my current project. Then they gave me a few front-end topics and I can choose any of them to talk about. The next day was a backend interview (maybe it was because they thought I was more suitable for a backend role). The interview was purely C# and .Net specifics, very detailed. Nothing about the algorithm or system design.
Questions d'entretien [1]
Question 1
Talk about the project you're working on.
What is the most complex front-end page you've worked on?