
InVision Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 15 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at InVision.
Software Engineer
I was contacted by a very friendly recruiter and we set up a meeting to chat over the phone. The chat was casual, and we discussed some job details and how the rest of the interview process would go. I was then sent a JavaScript programming exercise with no strict time limits, and was also promised payment upon completion which I thought was very different and extremely considerate. The programming exercise was a fairly challenging, modern implementation of the producer/consumer problem. It was about 4 days before I heard back, but my solution was good enough to allow me to move to the second interview with a few engineers and the director of engineering via Google Hangouts. For the first 40 minutes or so, we discussed the programming exercise and they prodded my knowledge on front-end and back-end development, but it wasn't 'firing squad' style, it was very relaxed and casual. I was then given time to ask questions and hear more about InVision. We ended the call with some talk about what everyone does for fun, and I was told I'd hear back from the recruiter soon. There was some delay in hearing back, I think it took a week or so, but eventually I was told I'd made it to the third and final interview with the CTO on Google Hangouts and we scheduled it for a week out. There was one rescheduling of the meeting, but it was only a couple more days out. The interview was less technical then with the engineers and was more focused on my software development principles, why I wanted to work for InVision, and learning more about the company at a high level. Overall, InVision definitely sets themselves apart in the way they interview engineers by valuing their time and providing clear expectations. It was definitely a positive experience.
- Can you explain what full-stack means to you?
- Explain an SQL join and how you would do something similar in NoSQL.
- What are the differences and similarities between various front-end frameworks?
Software Engineer
I applied online in October 2018 and the whole thing took about two weeks. First, there was a 30-45 minute recruiter chat. Then, a 1-hour technical interview with another technical lead where we talked about my background and the job, plus I had to walk through building a basic SaaS service. That one ran long, 1.5 hours, because I had tons of questions about InVision. Next up were two back-to-back "behavioral" interviews with managers, each lasting an hour. The first one felt great, the second was just okay. They both asked about handling tough situations and past work problems. Finally, a 45-minute interview with a director of engineering, which was pretty similar to the manager chats and also felt just okay. The recruiter was really helpful and made everything smooth, always replying quickly about benefits and stuff. The two manager interviews back-to-back were a bit tiring because they asked similar questions and I gave similar answers twice over two hours. After five long interviews, and getting some hints that things were going well, I was expecting an offer or at least a chat about compensation and a role. Instead, I got a standard rejection email with no explanation. It was strange because around the end of my process, most engineering jobs vanished from their careers page, though they added new, more generic ones a few weeks later.
- Can you provide an example of a good manager from your past and explain what made them good?
- Can you provide an example of a poor manager from your past and explain what made them poor?
Software Engineer
The interview process involved a phone screen, followed by technical questions/interviews, and then a final interview with a Director. It felt like the Director's opinion was the only one that mattered; if they didn't like you, the rest of the interview was basically pointless. The feedback I got afterward was terrible, really subjective, and just seemed like a way to justify the Director's decision.
- Regarding the system you designed, how would you approach scaling it, and would cloud solutions be a consideration?
- Would you consider using the cloud to scale the system you designed?
InVision Software Engineer Interview Questions
Quoted word for word from InVision interview reports.
“Can you explain the Cassandra compaction process in detail?”
Read reports →“Can you explain the difference between HTTP Get and Post requests, and what situations each is best suited for?”
Read reports →“What are the differences and similarities between various front-end frameworks?”
Read reports →“Explain an SQL join and how you would do something similar in NoSQL.”
Read reports →“What's an inaccurate impression people have of you?”
Read report →“Can you explain what a closure is and provide an example of its utility?”
Read report →“Could you describe how you would design an RSS reader?”
Read report →“Would you consider using the cloud to scale the system you designed?”
Read report →“Can you provide an example of a poor manager from your past and explain what made them poor?”
Read report →Formats, difficulty and experience
Across all 15 InVision interview reports.