Envié una solicitud electrónica. Acudí a una entrevista en DigitalOcean en sept 2020
Entrevista
1. 45 minute talk with the hiring manager on cultural/behavioral questions
2. 45 minute talk with the team's lead engineer, on technical topics, but more from a cultural perspective as opposed to a purely technical one
3. 45 minute talk with the team's UX designer on working with designs (still quite cultural/behavioral)
4. 45 minute talk with the team's product manager on collaborating with the product team (again, cultural/behavioral)
5. 45 minute talk with an engineer on the team during which I was asked technical questions
6. 45 minute talk with another engineer on the team during which we reviewed some code I had written in preparation for the interview (I had been told not to spend more than an hour on the code sample, and I was given the option to write the code during the interview, instead of preparing it beforehand)
I found the cultural/behavioral questions to be fairly standard and what I expected (based on past interviews and some Googling), but I found the technical questions difficult and I didn't believe I had done very well on those. It just goes to show that you never know exactly what they're looking for, so if you're interested in the role and the company, you should go for it!
Envié una solicitud electrónica. Acudí a una entrevista en DigitalOcean
Entrevista
I applied online for a remote role in the US. The process began with a recruiter call that was nothing short of unprofessional. Instead of sharing any background about the company or role, the recruiter focused only on my compensation expectations and made it clear they would proceed only if my range fit the hiring team.
They quickly scheduled technical rounds, I completed multiple standard SDE interviews with the hiring manager and team, and was later informed that I had cleared all rounds and that they were ready to extend an offer. Then complete silence for two weeks.
When the recruiter finally resurfaced to “discuss” the offer, no numbers were presented. Instead, I was again asked for my salary expectations (the same ones I had already shared in the first call). To make matters worse, the recruiter even asked if my expectations were in INR or USD, despite this being a US-based remote role. I was told an official offer would follow within two days, but they completely ghosted afterward.
This was by far one of the most unprofessional recruiting experiences I’ve ever had. A month-long process wasted, marked by poor communication, blatant disregard for the candidate’s time, and ultimately, zero follow-through. Based on this experience, I would strongly advise others to think twice before interviewing here.
Envié una solicitud electrónica. El proceso duró 4 semanas. Acudí a una entrevista en DigitalOcean
Entrevista
Basic Introduction, Projects you worked on (Discussion around the same), Technology you are passionate about, Lastly, problem solving for 45 minutes, walkthrough & discussion around the approach TC/SC you will be asked to use your own IDE or coderpad
Preguntas de entrevista [1]
Pregunta 1
Question Similar to Cheapest Flights Within K Stops (Spin off)
Solicité el puesto por otro medio. Acudí a una entrevista en DigitalOcean (Lahore) en may 2022
Entrevista
Initial HR Call: During this call, you will engage in discussions mainly about the role, on high-level things. You'll cover your background, salary expectations, and cultural fit. Hiring Manager Call: In this call, you will interact with a tech lead or a senior team member who will ask you behavioral questions. Topics will include your career goals, conflict-resolution approach, personality traits, and other non-technical aspects. Development and System Design Interview: During this stage, you'll work with a senior engineer to collaboratively find a viable solution to a problem. It will involve a live coding session, testing your general problem-solving skills and algorithmic knowledge. (Best part is they might tell you about the problem before the interview via an email so you can prepare stuff before hand) Additionally, they might inquire about your system design capabilities, either related to the same coding problem or other scenarios. Debugging and Diagnostic Interview: This segment comprises a verbal conversation with a senior engineer or architect. They will ask you questions related to identifying and resolving performance bottlenecks in web services. You'll also discuss your approach to debugging and how you handle production issues right from the initial stages. Team Collaboration Call: Although this call was scheduled, it didn't take place, got rejection before this.
Preguntas de entrevista [1]
Pregunta 1
- Write an http service that shortens the big URLs. - System design related questions related to above service. - Race conditions related questions like types of locks and how to use them. - General questions to assess your debugging skills