J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez DocSend (San Francisco, CA) en déc. 2019
Entretien
I had an open-ended phone chat with the CTO. It went well.
A week later, I had a technical phone interview, which I bombed.
They have a great developer culture. Devs are responsible for quality: No dedicated QA. They actually hire juniors and train them. I missed a great opportunity.
Questions d'entretien [1]
Question 1
Don't want to spoil their interview, but there were no LeetCode-style riddles.
I had to do very simple things that I do all the time in Rails, like make endpoints, design classes, and so forth.
If you normally copy-paste your company's code and make necessary changes so you don't have to write boilerplate, stop doing that for a bit before interviewing here. Lesson learned.
The job posting didn't mention jQuery and I was asked a jQuery question, though the recruiter told me that I'd be asked about it in the technical interview a week beforehand so I should have been prepared.
J'ai postulé via un recruteur. J'ai passé un entretien chez DocSend (San Francisco, CA) en janv. 2021
Entretien
It was a basic interview process. Recruiter reached out to me on LinkedIn.
- Initial phone screen with Recruiter
- Casual get to know each other round with a team member, mostly behavioral questions.
- Some design question with an Engineer
I didn't get past this and not sure what their expectations were since I got a standard reject email. If I recall correctly, the next steps included a take home/onsite.
Questions d'entretien [1]
Question 1
Behavioral and OOP design questions involving some database queries
J'ai postulé en ligne. J'ai passé un entretien chez DocSend en avr. 2019
Entretien
30 minute chat with hiring manager followed by a take home. Take home takes several hours. After submission didn't get any response, when I asked for feedback I got one or two vague sentences. This is a big reason why most engineers don't do take homes.