Senior Software Engineer applicants have rated the interview process at SendGrid with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 29% positive. To compare, the company-average is 41.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 22 days to get hired, when considering 7 user submitted interviews for this role. To compare, the hiring process at SendGrid overall takes an average of 22 days.
Common stages of the interview process at SendGrid as a Senior Software Engineer according to 7 Glassdoor interviews include:
Phone interview: 35%
One on one interview: 24%
Group panel interview: 18%
Presentation: 12%
Skills test: 12%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 2 weeks. I interviewed at SendGrid (Denver, CO) in Jan 2016
Interview
Phone screen with HR / Recruiting, Phone screen with manager, screen share coding interview, in person technical interview.
Screen Share coding interview was straightforward and not difficult. Basically, they give you a jUnit suite and some stub code, you have to write the method bodies to make the tests pass.
Group coding exercise was difficult for me. Multithreaded programming question, not necessarily difficult in itself but I'm most comfortable with Java and the machine was not really set up as a Java dev box so that took some time, and on top of that, I don't really mess with low-level Java thread code too much, so I had to spend a lot of time Googling. Was a bit nerve wracking.
Whiteboard architectural talk went OK, I felt like the interview team had pretty much made up their minds already by that point.
Finished with 1:1 interview with a manager, more of the soft skills interview questions. Lots of things that felt like trick questions. Really pays to think carefully about why interviewer is asking these questions.
Eventually rejected saying they wanted a candidate with "more coding experience" which I take to mean, they wanted someone who gives the aura of being able to handle multithreaded code with ease. Fair enough, from talking to them they run a very high volume operation and I'm sure threading / parallelism is a big day to day concern.
Interview questions [1]
Question 1
How do you think your co-workers would finish the sentence "<candidate name> is great, EXCEPT..."
I applied through a recruiter. The process took 1 week. I interviewed at SendGrid (Denver, CO) in Oct 2019
Interview
The fastest process ever. I was contacted by recruiter through linkedin, quick intro call, hackerrank.
Next day after I passed hackerrank I was invited 4 hours long onsite with 4 people.
All interviewers were friendly and generally very nice persons to talk with, definitely one of the better experience so far.
Interview questions [1]
Question 1
1. Hackerrank with easy to medium questions.
2. onsite with design, coding, hiring manager and culture match
I applied online. The process took 3 weeks. I interviewed at SendGrid in Dec 2018
Interview
Initial screen call with HR rep. Hour long call with hiring manager.
A lot of out of context questions on certain skills and experience. I finally realized they wanted to hire me for past experience and skills that were not part of the job description.
I asked about it, and then let them know I wanted to use my current skills and not deprecated ones. The interview tone changed to a formal politically correct blow off. The interview ended a bit early. No further response even after 3 followup emails from me.
Interview questions [1]
Question 1
Can we pretend to hire you for what you want to do, then move you to a dead end role?
I applied in-person. The process took 2 weeks. I interviewed at SendGrid
Interview
Overall, it’s a 4 step process.
Recruiter call, followed by hiring manager (discussed about projects, tech background and small coding problem). Once it is through, there is a online coding challenge.
The final round is onsite interview:
Team is very friendly and helpful all the time.
It’s a 4 round interview:
Hiring manager interview
Cultural fit interview
Coding interview (not so complex, but I could not make it on time with some hints)
Design interview (distributed caching design, and some questions on consistent hashing and on AWS)
Overall, interview/questions are so not tough and it’s a positive experience with all interviewers.
One thing I think they could do better is: provide feedback or response (at least after few days) after the interview is complete.
Interview questions [1]
Question 1
Design distributed caching system?
How to handle hot keys?
How to handle node failure, rebalancing?