Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Arena (New York, NY) en nov 2016
Entrevista
I went through a phone screen, coding challenge, and 5 interviews.
I was contacted by an outside recruiter via LinkedIn. He was very interesting to talk to and really made me interested in the company. My fit interview was with the VP of Engineering, who seemed very smart and passionate about the company. The coding challenge was a 3 hour timed exercise and interesting to do.
After passing the first three rounds, I went into the NY office for my final round. The interview was mostly in Python so I would recommend brushing up on Python beforehand.
The final round interview experience felt impersonal. I was put in a conference room floors away from the office, and a majority of my interviews were conducted via Google Hangout. Employees I had previously spoken to did not reach out to say hello either. In the end, I found out I didn't get the position through an outside recruiter. I think something more personal should be included when you make it that far.
Overall my experience was mixed, very positive at the beginning and less so during the final round.
6
Otras opiniones sobre las entrevistas para el puesto de Software Engineer en Arena
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Arena
Entrevista
I would avoid this employer.
TLDR: No context on goal, no mention of obscure API framework. Write 3 endpoints in this framework you don't know and we didn't mention. "New" codebase is very poor quality.
While the company and premise is interesting, the interview went poorly for a multitude of reasons.
For starters, we pretty much jumped right into the "coding exercise" with no context on what we were trying to achieve. The repo provided was a pared down version of their "new" codebase. With about two sentences on what we were trying to achieve, they turned the mic over to me. Naturally, I was asking clarifying questions and trying to identify the goal here. The interviewer started getting somewhat short and annoyed. As I started getting an idea of what we were actually doing, most of our time had passed.
Not only was the problem not described, but the context entirely hidden. There was no mention that they were using an obscure API framework, which they fully expected interviewees to write 3 endpoints for.
They mentioned this repo is a pared down version of their new codebase, which itself was (to put it politely...) a disorganized heap of code.
I walked away from the interview knowing I would not want to work for an employer like this. But best of luck to them in their search!
