Advertisement
fogleman

I interviewed at Adzerk.

Oct 8th, 2013
3,673
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.07 KB | None | 0 0
  1. I interviewed at Adzerk. They serve reddit's and Stack Overflow's ads, among many others of course.
  2.  
  3. I saw a job opening on Stack Overflow. It was for a DevOps position, which is not for me, but it looked like an interesting startup in the area. Their website detailed a Software Engineer position, among others. It looked great.
  4.  
  5. I emailed them information about myself and expressed interest in talking with them, even if they weren't officially hiring for that position.
  6.  
  7. I got a response in one hour.
  8.  
  9. The next day I had a phone interview with the CTO, Nate. The call was about half an hour long and went great. He seemed to get that I was a very strong developer, having seen my portfolio online. I made it clear that I didn't have any real experience with the type of large-scale internet infrastructure that they use, but he assured me that it was no big deal as long as I am a quick learner. We even discussed salary ranges and when I could start. They scheduled me to come in for an in-person interview. I was very excited.
  10.  
  11. A couple weeks elapsed before the in-person interview due to scheduling conflicts. No big deal, but I was anxious to meet with them.
  12.  
  13. I came in on a Tuesday around 3pm. I was actually 20 minutes early, but we started as soon as I arrived. I met with Nate, Pat and Sean, all technical folks, together in the conference room.
  14.  
  15. I explained why I was looking for a job - my company was recently acquired and I either had to relocate to San Diego or find a new job. I also wanted to move on to something new (I'd been at my current job for five years) and Adzerk was working on interesting things that would really broaden my experience.
  16.  
  17. They only really asked me one semi-technical question. It was about infrastructure - load balancing, replication, sharding, etc. I thought I answered it okay. I wasn't trying to make it look like I had done things that I hadn't done before.
  18.  
  19. For the rest of the interview I showed off all sorts of things I had worked on, both in my spare time and at work. I figured this would make it clear how passionate I am about programming and highlight the range of skills that I possess, out-weighing any lack of experience in other areas.
  20.  
  21. After an hour and a half (longer than scheduled), I briefly met the rest of the team and then left.
  22.  
  23. A few days later, I received a rejection email from Nate. While I'm clearly very skilled, he said, I don't have enough experience in big data or big web to justify opening a position just for me.
  24.  
  25. Makes sense from a business perspective, I guess, except I had made this clear from the beginning. Maybe there was more to it that they weren't telling me. Or maybe Nate liked me but someone else didn't.
  26.  
  27. I wonder if they would have hired me had the position actually been open?
  28.  
  29. I wonder if they'll consider me if the position opens in the future?
  30.  
  31. It felt like a good cultural fit. They seemed to like me in general.
  32.  
  33. It still feels like a rejection.
  34.  
  35. A small blow to my ego is good. I need to be challenged. Some of my weaknesses have been revealed. I can work on them now.
  36.  
  37. http://www.michaelfogleman.com/
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement