Me postulé a través de un reclutador. El proceso tomó 4 semanas. Acudí a una entrevista en Venmo (San Francisco, CA) en oct 2013
Entrevista
The interview process had 3 stages: programming challenge, 1hour phone interview, and a full-day on-site interview with the team which included some pair programming and design discussions.
I felt Venmo's interview was not tricky or difficult but intelligent!
For example, the programming challenge was straight forward and no specific language was required, but since there are many ways of writing software for a simple problem and I felt this was how Venmo evaluate your skill level and maturity as a sw developer.
Similarly, for the phone and on-site interview, the Venmo team took the approach of having a technical conversation with you, either in the context of designing an application or musing about sw languages, design, and methodologies. I felt this was a smart way to evaluate a candidate's depth and breadth of knowledge, compare to other companies that ask "tricky" questions just to see if you know some nifty methods in Ruby Array class.
The team at Venmo seemed genuinely enthusiastic and interested in software. Their engineers could go on musing and discussing about a particular topic even after you've answered the interview question. Again this is a contrast with other companies, where the interviewer seems uninterested and is only asking for the sake of the interview.
Overall, I felt the software team at Venmo is of a high caliber.
Me postulé a través de un reclutador. El proceso tomó 1 semana. Acudí a una entrevista en Venmo (Chicago, IL) en may 2019
Entrevista
Recruiter reached out to me, there was some back and forth, and a phone call that ended the process. The tech interviewer was very friendly and pleasant to talk to, but it was pretty clear that they were unimpressed with my skill set and background. That's life in the big city for ya lol.
I have contempt for the recruiter for being pushy and lacking the decency to follow up after the interview. Call me old fashioned, but writing a paragraph takes all of a minute and given they started the process it seems appropriate that they end it. This was really the only thing about this process that annoyed me; the engineer I spoke with was cool.
I didn't really think this was an interview that was worth my time given the experience I had, but I guess it was my fault for following through with it at all. Overall it was a useless distraction for everyone involved which is unfortunate, but a reality of dealing with larger tech companies.
Preguntas de entrevista [1]
Pregunta 1
Usual stuff, what's your background and what have you done?
Me postulé a través de un reclutador. El proceso tomó 3 meses. Acudí a una entrevista en Venmo (New York, NY) en oct 2015
Entrevista
Generic email from tech recruiter (Stan?) while I was on the hunt so I responded. Had a 10 minute or so phone screen with Stan where he had no idea where the company was headed or even what stack they worked on. Needless to say I went into the first technical call blind, but still passed. No response, but 6 weeks (?) later they ask me to come onsite. Asked the tech recruiter again what to expect onsite and he still gave nothing -- completely blindsided again.I felt ignored.
Not trying to be pretentious but every tech recruiter I've worked with has at least had an ounce of information about what to prepare for during interviews Not a good look for a company infamous for losing talent.
Preguntas de entrevista [1]
Pregunta 1
In what ways will you work with or against PayPal's rules?
Me postulé a través de una recomendación de un empleado. Acudí a una entrevista en Venmo
Entrevista
First you apply online, then there's phone interviews, then a coding challenge that they send you, and then an onsite. Fairly straightforward. The onsite has both technical interviews and behavioral. They want to check for culture fit above almost everything.