Take-home code challenge, chat with recruiter, chat with manager, chat with rest of tech team.
The onsite interview was very casual and I was mostly asked situational type questions and one system design question.
Questions d'entretien [1]
Question 1
Name one time you estimated a project incorrectly and how you communicated it to the team.
J'ai postulé en ligne. J'ai passé un entretien chez Ro (New York, NY) en juin 2020
Entretien
The process started with a phone screen with a recruiter. After that there was a video chat for 45 minutes with a Hiring Manager to discuss the role and what I was looking for. Finally there was a take home assessment.
This assessment mentions that it should take a few hours. This is a gross oversimplification of the ask. Rate Limiting/Concurrency/Pagination/etc on a working terminal prompt starting from absolute scratch is going to take more than 3 hours to accomplish. This level of complexity for a take home assessment is quite frankly disrespectful of the candidate's time.
Questions d'entretien [1]
Question 1
design a working terminal prompt that accepts arguments via user input. this prompt requests data from github v3 api. the application must respect concurrency, rate limits, and pagination. display the top contributors across all the repos under an owner.
J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Ro (Jersey City, NJ) en juin 2020
Entretien
Ro’s hiring process is pretty standard as per industry standard. Recruiter call, call with hiring manager, take home test, on-site interview meeting with different members of the team and cross functional teams. Finally followed with meeting CTO and co founders. All the people I met with were very well prepared and knew exactly what they were looking for. Questions turned more into 2 way discussions which I enjoyed a lot. They are looking for engineers with solid fundamentals and deep experience.
Questions d'entretien [1]
Question 1
Interview questions are more centered around real world problems, software engineering best practices, design, team fit and past experiences. If you have strong grip on core fundamentals of computer science, it shouldn't be difficult. Learnings from previous experiences can help answer questions around best practices.
