I applied through a recruiter. The process took 2 weeks. I interviewed at Gladly
Easy interview
Application
I interviewed at Gladly
Interview
Total waste of time to think about a topic and give a presentation when you are not sure about getting an offer. People who are interviewing are busy and stressed for this fun activity.
Initially talked with the recruiter, then next step was a remote coding interview question with one of their engineers. After that I was invited to their onsite which was around 3-4 hours, split into hour sessions with a presentation at then end where you present a topic.
I applied through a recruiter. The process took 2 weeks. I interviewed at Gladly (San Francisco, CA) in Mar 2018
Interview
I was contacted through AngelList's A-List platform by the Director of Talent of Gladly. First we set up an introductory phone screen where we discussed Gladly's product, culture, and the position. Next was a technical screen with 2 Gladly engineers, which was over video chat and utilized coderpen. There was one question, which involved pretty straightforward string manipulation.
I was invited to an onsite interview shortly after the technical phone screen. The onsite had 4 components and took 3.5 hours. The first hour was a design based interview, which involved discussing what kind of data an endpoint would need to return to create a component on the front end, as well as sketching out the component in my preferred JS framework. The second hour was a deep dive into a past project I had worked on. The third hour was a non-technical interview that focused on how I approach working on a team and what experiences I had working on teams previously. The last half hour I gave a presentation on a topic of my choosing, with a Q&A after. This was attended by the entire interview team. I was told I should have a decision by the next day.
Instead of a decision, I got a call from the Director of Talent the next day that the team would like me to complete a take home project in order to see if my technical skills are a fit for the team. Essentially, all components of my onsite went well besides the first hour, so they would like to give me another chance to show my skills. In my opinion, if you can't glean if a candidate is a good fit for a role from a 3.5 hour interview, perhaps you should revisit the process.
In any case, I completed the assignment (a problem involving parsing strings, which could be achieved in as little as 40 lines) and turned it in. A few days later I got the news that my solution was not "production ready" and I would not be getting the job.
Interview questions [1]
Question 1
What is your biggest challenge in working with a team?