I applied through an employee referral and the process took 6 weeks - interviewed at SendGrid in October 2013.
Interview Details –
I applied through the website, and received an email back with options for scheduling an initial phone screen with one of their recruiters. After the 1/2 hour phone screen, I had a 45 minute technical screen, which involved doing a couple of programming exercises on CollabEdit.
I passed the phone technical screen, and was invited to an in-person technical interview at their Orange County, California office. It was a three-hour interview.
The in-person interview was technically challenging right from the beginning. Although I had studied up on core computer science concepts prior to the interview, the first question was on a topic I hadn't reviewed (merge sort), and it threw me off. Later, I was asked to write a binary search algorithm. I wrote the base algorithm, but I had a logic error that took me a long time to find.
There were four interviewers - three software engineers and the VP of engineering.
Interview Question – Given two arrays of numbers, write a method to combine and sort the two arrays. View Answer
I applied through an employee referral and the process took 3 weeks - interviewed at SendGrid in September 2013.
Interview Details –
An employee gave my contact information to their local recruiter, who contacted me. We set up a time to talk. It was a one-hour conversation, very chill, mostly focused on cultural fit and personality. He explained the interview process, was forthcoming with details about the position and why it was open.
Very shortly after talking to him, a coordinator contacted me to set up a phone interview with a potential peer. It lasted ~45 minutes and questions started out kind of crazy (ice breakers, maybe?) but then focused specifically on the role. Some behavioral, some about philosophy/approach behind the role, some tactical. Wasn't sure how I did after hanging up and was worried that I'd bombed.
The next business day, I was contacted and scheduled to come in for the final round of interviews. The interviews included a peer, the hiring manager, a lead developer from another group, and a lead developer from the group I would be working with. All went very well and I left feeling confident that I had a good shot at an offer.
Within a few days, was contacted by a more senior HR person to gather information about my past salary. The note implied they were putting together an offer, but of course left plausible deniability in case they decided not to. They also asked for references, and sent spreadsheet surveys to them. At that point I knew they were serious and an offer followed in about a week.
Interview Question – Behavioral questions around working with difficult people, setting up the scenarios so that there weren't any win-win answers. Answer Question
Negotiation Details – Not much room for negotiation. Offer was nontrivially lower than past salary, and did not include a bonus. They explained how compensation is determined and it seems they are constrained by paying within a narrow range to all employees of a certain job. Equality is good, but some people have more experience than others and should be compensated for it, IMO. Was able to bring them up about 5% on compensation and no more.
I applied through college or university and the process took 4+ weeks - interviewed at SendGrid in June 2013.
Interview Details –
I was contacted by the HR of company. The process is straightforward, which is a Phone interview and followed by an on site interview. Phone interview is just a process of knowing each other. Two engineer interviewed me during the on site interview. First one asked some general questions. For example, how to shuffle an array (programming) and some other OOP concepts such as difference between instance and class, what is constructor, inheritance, abstract class, pure virtual function. The second engineer asked retrieve several email lists from different url and return what email address occurs multiple time in these url. The email address are stored in the JASON format in the urls. I used a python package to retrieve the information. Everything goes very well during the interview.
I solved the problem very quickly and was told by the HR that the decision will be made in a week.
However, I was declined a month later after sending couple emails to the HR.
The process took 4 weeks - interviewed at SendGrid.
Interview Details – Seemed like a great company. Lots of perks such as a casual work environment. The culture seemed fun. Had a phone interview with the recruiter, which went well. Was called in for an in person interview. Thought the interview went very well and was told that I would be contacted within a few days about their decision. In fact there were many things that led me to believe I had the job, but 2 weeks later I received the standard reject email.
Interview Question – Very generic personality questions. Answer Question
I applied through a recruiter and the process took 5 weeks - interviewed at SendGrid.
Interview Details –
First recruiter called and after introduction interview over phone, he said that he like to arrange an on site interview for me.
I went to Anaheim office and there two employee interviewed me.
First interview was very general questions of do you know this do you know that plus one simple programming question which i needed to write on the board (binary search on an array).
Second was another simple programming question on the board plus an database design with ER diagrams.
The feedback process is slow. although they told me that they will inform me in 2 days, it took them 10 days to tell me about decision and took me 3 emails asking "did you make your decision?" and geting the reply "sorry it will be finalize within 2 days" every time
Interview Question –
Non programming questions like what is sql injection, which I barely could remember.
Programming questions were simple:
1. binary search
2. finding weather or not there are two numbers in a given array that their sum is equal to a given value. Answer Question
I applied online and the process took 4 weeks - interviewed at SendGrid in May 2013.
Interview Details – First had a half hour phone screen, very basic stuff running through my resume and a couple behavioral questions. Followed a week later by a 15 minute skype call, similar things. Came in for in person interviews. Had 6 half hour interviews in a row. Questions were mostly behavioral and culture fit questions, really nothing technical.
Interview Question – Tell me about a time you've made a mistake or been wrong. Answer Question
I applied through an employee referral and the process took 4 weeks - interviewed at SendGrid.
Interview Details – Had two phone interviews, one with company recruiter and one with a developer. Both seemed to go okay. In the developer interview I had coded with collabedit. Then I was given a relatively complex coding assignment and was asked to return it in one or two days. I did that at a large amount of inconvenience. Didn't hear back for two weeks and then was given a generated email rejection.
Interview Question – Culture seems to be big here, so there's lots of unexpected questions around that. View Answer
I applied online and the process took 3 weeks - interviewed at SendGrid in March 2013.
Interview Details –
the feedback of the interview process is slow.
Interview started with walking through resume. OO terminologies. then a coding problem on collabedit. I solved it and gave a production code in the first attempt without any hint. I was asked to improve the solution. I improved it and then again gave a production code. The interviewer was satisfied. Still i got rejected.
I applied online and the process took 5 days - interviewed at SendGrid.
Interview Details –
Went through the HR screening process and was later scheduled to have a technical interview with one of their senior software engineers. The technical interview went over generic questions about design patterns like "what is polymorphism", etc. and later went on to use a collaborative text editor only to be asked to implement a binary search method. The description of the position listed PHP as the primary language and made no mention of any language were you would ever need to [re-]implement something like this, thus I ended the interview. Forming this same question as a pre-interview exercise would have been much more appropriate. I would never take a position where I had to solve difficult problems that require concentration while having someone breathing down my neck, and for the same reason I would never take a position that screens employees utilizing this setting.
There is an unlimited list of programming concepts that one needs to selectively navigate depending on the requirements of the specific role or craft you want to work in/with. Asking questions that do not apply to that role during an interview is poor form. Test the knowledge and experience relative to the role instead of just trying to test what a candidate doesn't know (you'll pass up on plenty of great programmers). I've worked with plenty of people in the past that were better at reading technical articles and explaining design patterns while not knowing when and when not to apply them, much less being able to get work done in a reasonable time-frame.
Interview Question – Implement a binary search method; I fully expected the next question to be "describe a btree structure and it's variants". :) View Answers (2)
I applied through an employee referral and the process took 2 weeks - interviewed at SendGrid in July 2012.
Interview Details – Recommend in through a trusted connection. Phone interview w/ CFO to learn more about the role. Met VP Sales, CFO and CEO all in one day. Decision to hire came within 1 week. Overall a great process.
Interview Question – Tell me a time when you had to bend or break the rules Answer Question
Negotiation Details – Easy and collaborative, a win/win
Pros: Good people, good resources, good perks, good product. – Full Review
Your feedback has been sent to the team and we'll look into it.
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.
Your response will be removed from the review – this cannot be undone.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks –