Solicité el puesto a través de un captador. Acudí a una entrevista en DocSend (San Francisco, CA) en ene 2021
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 1
Behavioral and OOP design questions involving some database queries
Solicité el puesto a través de un captador. El proceso duró 1 semana. Acudí a una entrevista en DocSend (San Francisco, CA) en dic 2019
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 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.
Envié una solicitud electrónica. Acudí a una entrevista en DocSend en abr 2019
Entrevista
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.
