J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Heap (San Francisco, CA) en sept. 2016
Entretien
Interview has 3 stages: online problem solving, home task and work with them for a whole day. You can move as fast as you can on that process.
On fist stage you need to solve algorithmic task in realtime and respond on questions about "how to build system to solve that task". You're not required to write whole code alone, you have some support and hints, so you should listen carefully and explain what you want to do.
Second stage is home task. You have 2-3 hours to solve it. You can't prepare to it, because there is no information about what kind of task it could be. I thought it'd be task for testing my coding skills, but it was 90% algorithmic. It's impossible to solve it without specific algorithm.
If you have used that algorithm before or remember it from University - it'd be easy for you. Otherwise you should find that algorithm by yourself, understand and modify it to specific requirements, which is really hard to do in that time limits.
Totally I spend 5 hours to make working solution, which was not best in terms of code quality, because I failed time limits. It was unaccepted and interview process finished.
My advice is to not spend any time for naive approach, just start searching of algorithm immediately and make sure you understand it. After that start writing clean code with comments and OOP.
Overall, interview was very well organized and good, with a lot of support and help.
J'ai postulé via une autre source. Le processus a pris 2 semaines. J'ai passé un entretien chez Heap (San Francisco, CA)
Entretien
Skipped resume review via interviewing.io; which by itself said great things about diversity in the company. Clever technical questions; but the last one (about databases) kind of dragged out. Database-related-experience wasn't in either their job description or my resume, but they kept on it well past the point where I ran out of prior knowledge to use and examples to list; just spending >10 minutes poking without hints. Confusing ending to an otherwise pleasant process.
Le processus a pris 3 semaines. J'ai passé un entretien chez Heap
Entretien
Overall, this process was very thorough:
- initial interview
- coding interview
- virtual on-site:
- - 2 more coding interviews
- - systems design
- - product demo
- - pm interview
- - values interview
I learned a lot about the company, product, and development process, and I had a chance to talk with a lot of people. Everyone was really friendly and smart. It took a lot of time, but I think it was worth it.
However, I was a little miffed about how they handled my cohort. After completing the virtual on-site (and spending a lot of time on this process), I was told that they had already filled all the current engineer reqs, and they would have to ask for more money to potentially hire ahead for next year. I felt like they should have finished the interview process with all candidates before proceeding to make offers, and it wasn’t fair to those of us who interviewed after they filled all their reqs. In the end, they told me I didn’t quite make it, which is fine, and I guess I’ll never know about the details. I just felt a little shorted that they made a bunch of offers the week before I finished my six interview on-site.
Despite that, I thought it was a great company with really smart, friendly people. Seems like it would be a great place to work.
Questions d'entretien [1]
Question 1
I was going to write a question here but eh, that seems a little unfair to Heap.
- Regular Behavior questions
- Matrix exercise
It was an average experience, you should practice the kind of questions I just put above. This Glassdoor rule of 50 word minimum is really stupid.