How I got a job at Stack Overflow

i just got a job at stack exchange. the experience was interesting enough and i learned a few things that could be valuable to others.

we are still hiring another developer if you are interested after reading.

motivation

my previous job was good. some interesting work, some boring work, and a potentially awesome project coming down the pipeline. i was making internal web apps for the firmware department of a hard drive company, and had opportunities to do anything i wanted (stay, work on firmware or other cool stuff). however, the town i was living in (longmont, co) was downright boring for a single person, and i wanted to leave as soon as possible just to get out.

the bug

i visited a friend who lives in new york city over thanksgiving. i visited top of the rock, which is an observation deck on top of one of the taller buildings right in the middle of the city. you can see almost all of manhattan up there, and it's mesmerizing. while i was there i decided that new york was the place for me. the next few weeks i became more and more convinced that that was where i wanted to live. i decided to start applying for jobs at the start of the new year. and i had to get out of my city.

(this is not a plug)

being a programmer, i use stack overflow. i had thus seen the displays for the careers site. hey, why not use that to find a job? ok. i made a profile, which i got to do because of my github activity, and started applying for jobs. (yes, i ended up finding a job on the same site i am currently employed to work on. i thought it was the best way to find an awesome job, and it was. so, this isn't a plug, it's just the truth.)

i applied for around 7 jobs near the first of the year. two said to take an online test, two never replied or disappeared, and one scheduled a phone interview. the phone interview went horribly. the guy asked me one of the questions verbatim from joel's article and i had no idea what to say. no callback. i started studying programming pearls.

progress

i did one of the online code tests and got a phone interview a while later from that company. after a second phone interview (both were writing code on a shared document) they flew me out for a few days. thursday was interviews (coding on a laptop, really hard and fun problems) all day. they asked me to return friday to work on their product like a normal developer. i thought this was brilliant. a way to see how a candidate actually does the job. i liked them a lot because of how rigorous the interviews were. i wanted to work at a place that was highly demanding of everyone who worked there. they said they'd get in touch in a day or two. two weeks later (about a month total) they declined to make an offer, and i was still stuck in a city i hated.

i had suspected i wasn't going to get an offer, so i applied (early february) to four more companies. lots of phone interviews later and i have two onsite interviews scheduled for the same weekend. of note is that neither of these two companies had had me write any code. i know that not everyone likes code writing interviews, but i do. they're difficult. i want to work with people who can do that kind of difficult thing. the first company is a very small startup. they had me do some thinking out loud, database, and design questions. cool product; i liked them, and they seemed to like me. second company is more established. they just finished their new office. they had me do an hour-long written test which covered a wide range of stuff. i met with people from various organizations. they were nice, and i was okay, but not thrilled, with their product. each said they'd get back to me very soon. two weeks later, both declined. at this point i was ready to just up and move to new york i wanted to leave so badly.

first round of lessons

the count at this point was around 10 applications, phone screens with 7 companies, on site interviews with 3, and 0 offers. what was i doing wrong? i honestly wasn't sure. why did they all take two weeks to figure out they didn't want me? is it that hard?

my guess is that there was a culture mismatch. i think i did well in the interviews and was technically qualified for all three jobs. but something about our interaction didn't convince them that i was "the guy". i think they had a two week process of saying back and forth to themselves: "he's qualified: hire him." "but he won't love working here: no hire." "so? he'll still do good work." "but not awesome work." after two weeks, they either got bored or found someone else who was a better fit. my internal dialogue, however, was going like this: "i thought i knew how to program good." "no, clearly you don't." "but look at all the typing i did on github!" "even cats can type." ":(".

proof of concept

at this point i was crazy to move to new york. but during the double interview weekend, stack exchange asked for a phone interview. i was shocked. i have read all of joel's articles, and i know how hard it seems to get a job there. i figured getting a job at stack exchange is at least as difficult at getting a job at google (to which i did not apply, because i thought i wasn't smart enough).

phone interview went, well, pretty much like their article describes. fizzbuzz-like question. easy pass. harder, fun, thoughtful question with coding. pass. same thing with another guy. pass. fly out for interviews and meet joel. cool. things were happening.

on site interviews also went exactly like their articles describe. no written schedule, just one interview after the next, all coding and experience questions. lunch downstairs with the fog creek guys. gape and drool at their office space a little, but pretend like i'm used to it. joel was sick that day, so i spoke with michael pryor. i'm not sure whether i should be happy with myself or not, but he asked a question that he has been asking for years, and i came up with a solution that he has never seen. i had to stop at points to carefully explain something i thought was obvious that was apparently not. again, i'm not sure to interpret this as a good or a bad thing. (maybe all the smart guys come up with the same smart solution. maybe i'm so untrained that i just made something up that really isn't that great.)

apparently it was good enough. i walked out of their offices feeling good, used the restroom, and went to the elevator to catch the car back to the airport. during the one minute that i was waiting for the elevator, the vp of engineering came out and told me that they were going to make me an offer, which i accepted a week later. i was living in new york less than two weeks after that. (i resigned and decided to move before i had a job offer. i really wanted to leave.)

more lessons

let's compare: the first three declined offers took two weeks to respond to me. stack exchange took two minutes. culture mismatch? not in the slightest. love the company and the product? definitely. i get to work on something that helps developers find better jobs. something i desperately needed and got.

i am thrilled that those first three companies didn't hire me. i am happier here than i would have been there. technical ability is important, but not everything.

most important lesson

but the most important lesson i got from all of this? anyone can work for a dream company. i say this because i do not feel that i'm some rockstar programmer. i've just worked and learned like everyone else. i studied writings from some smart programmers, learned a few languages and systems, and in the end got a job at a place that i had been dreaming of working at for over 10 years, when i first heard of them (that is, any company run by joel and michael).

want a job at a dream company? work and study, and it's possible. not getting offers? maybe it's not evidence that you aren't that great, it's just that you would fit better somewhere else.

From:  blog.mattjibson.com

Add Comment

Cancel

Not comments yet.

More
About author
Posts
0
Answers
0
Follows
1

About Privacy Terms faq

@2017 CareerAnswers