Managing Partner at Dragonfly Capital. Effective Altruist. Airbnb, Earn.com (acquired by Coinbase) alum. Instructor @ Bradfield. Writer. Former poker pro. Donate 33% of my income to charity.
(Note: this is the second part of this story. You can read the first part here.)
Despite the rejection from 23AndMe, I kept pushing.
I applied to the all the big hiring websites. Hired rejected me from their platform. I got no bites anywhere on AngelList or LinkedIn—not even cold e-mails from recruiters. Nothing from WhiteTruffle or SmartHires.
Not a breath of interest anywhere.
I kept on. I asked friends, students, anyone I knew for referrals. I started reaching out to non-engineers. I asked anyone at all who worked at all at a tech company I found compelling.
I was nervous. Was I a fraud? At App Academy I might have seemed like a paragon, but to the rest of the world…was I simply not good enough?
Credentials should not be used as a proxy for talent. Education and work history are meaningful but relying solely on them results in missing good programmers. Good programmers come from all types of background. It’s what you can do that matters, not where you went to school.
Their interview process is completely blind to credentials. They decide to work with you purely on the basis of a technical assessment, then they learn about your credentials and then introduce you to startups they determine are a good match. Though they mostly work with experienced software engineers, I decided to give them a try.
To my surprise, I was able to pass their anonymous programming quiz and I was automatically invited to an onsite assessment. I showed up sheepishly to their office on King Street, and over an intense three hours I was grilled by my interviewer on coding, data structures, algorithms, and system design. At the end of the interview, he asked me what my computer science background was. None, I told him. I’d learned this stuff on my own and from teaching at App Academy. He was taken aback, and told me I was incredibly strong for only having studied this material less than a year.
The next day, TripleByte called me. They wanted to work with me! They’d introduce me directly to startups in the YC network. This was exciting—there were a ton of companies in YC network I wanted to talk to: Stripe, Twitch, Airbnb, to name a few.
Well, as it turned out, those companies weren’t really looking for someone like me. Since TripleByte is a two-sided process, they matched me up with companies for which there was a good mutual fit—Stripe, Twitch, or Airbnb were nowhere on that list. However, one of the companies they matched me with was Gusto, formerly Zenpayroll (and now a timely Zenefits competitor). I’d previously had my eye on them, so I was excited to see them matched up with me. They also lined up an onsite at a small YC startup called Flexport.
TripleByte had gotten things moving. But even more importantly, they had given me back some confidence. TripleByte wanting to work with me was a small affirmation, to be sure—it wasn’t even a job offer yet. But it felt like I’d finally pierced the membrane. If these guys thought I was good…I must have it. I just gotta prove that to everyone else now.
I set off to the onsites. The first of the two, Flexport, was a freight company. In many ways, it seemed more like a logistics company than it was about technology company. But I felt like I performed well in the onsite.
A couple days later: no offer.
I was supposed to be upset, but by now this was an old game. I brushed it off. Each interview I could feel was making me better at interviewing. It was getting easier and easier to relax, to ask for what I needed, to make jokes, to grill my interviewers. I was getting into my rhythm now.
Rejected? It is what it is. Just keep putting in the practice, I told myself.
Next was Gusto. They were a groovy company (no shoes in the office!), and the interview was a delight. They told me they’d get back to me within a week.
Shortly afterward, an onsite from Yelp pulled through (my referral was through a non-engineer!). I went onsite and completely rocked it. Every interviewer was clearly impressed, and they immediately asked me for my references afterward. Perhaps things were looking up! It seemed like one of Gusto or Yelp might actually convert into an offer.
All the while, I kept putting more irons in the grill (gotta keep that kitchen running), and kept studying up on algorithms and system design. Around then, I got an e-mail in my inbox from TripleByte:
Saw you’re starting to get some interviews booked with companies!
I actually wanted to throw another company option into the mix, us :) We’re hiring to build out our engineering team, we really enjoyed meeting you and would love to talk more about that if its of interest. Just let me know and I can give you a call tomorrow!
I hadn’t considered joining a super small company. I’d already spent the last year at a 25 person startup; TripleByte was only 5 people. But I knew entrepreneurship was somewhere in my future, and eventually I’d be joining a super early stage startup (if not founding it myself). TripleByte was a fantastic company, already with huge traction in the tech hiring space. Their founder, Harj Taggar, was a former YC partner, and one of the most charismatic and capable people I’ve met.
They wanted me. A company actually wanted me! A good one! I laugh now, but it was a revelation to me. They invited me in for another onsite so the rest of the team could vet me.
Before I could savor it too long, I received a phone call soon after. Yelp recruiter. Yelp wanted to make an offer.
And with that, the first domino fell.
Then came the Gusto recruiter. Gusto wanted to make an offer.
A TripleByte offer came soon in tow. First I had nothing, now I had three offers in front of me.
And yet, it was a little bittersweet. Yelp’s offer was 105K salary with ~17K/yr in equity. Gusto hit around 115K with comparable equity in options, and TripleByte was in the same ballpark.
Now, if you’re outside tech (or the Bay Area), those might sound like knock-down amazing offers. But all of these offers were lower than I was currently making, and they were all for explicitly junior roles.
Still, 105K might sound like a lot of money to be miffed about. But in San Francisco, with the second highest cost of living in the US (behind only Manhattan), the purchasing power of $105K in SF is the same as making about $57K in Austin, Texas. I also still owed App Academy tuition (18% of my first year’s salary), which was deferred because of my employment by App Academy. That 18% would come due on whatever offer I accepted. And of course on top of that, I’d also be donating a third of my income.
But really, what stuck out most to me is that I’d be leaving App Academy to a downgrade. I would be no better off than if I’d just joined those companies a year before. My goal, somewhere in my head, was to make at least more than I was making now. An arbitrary benchmark in a lot of ways, but it was hard to give up.
Was what I’d learned over the last year working at App Academy not worth anything on the market?
Maybe not. Perhaps I just had to accept it.
Now that I had offers in hand, it was time to turn the crank. I reached out to every company I was talking to and told them I’d just received several offers, but was very much interested in moving forward. With that, suddenly recruiters started tripping over themselves to get me on site. I was no longer the ugly boy at the party.
I started mowing down onsites. My performance and experience were no different, yet I was treated completely differently. Phone screen from Google. Gusto raised their offer. Phone screen from Stripe. Yelp raised their offer. TripleByte raised their offer. Then the phone screen at Google converted to onsite.
Bam. Suddenly Google was in sight. I felt like Captain Ahab: for me, Google was the Big One.
My Google recruiter worked for the Youtube team (headquartered in San Bruno). That meant if I were to receive an offer, the Youtube team would have first dibs on me. The interview process is standardized Google-wide though, and Google would ultimately be my employer. I spent the weekend before practicing and took the day off from work so I could head down to San Bruno for the interview.
I arrived that morning at the San Bruno BART stop, hardly having gotten any sleep the night before, and walked 30 minutes to the Youtube campus in downtown San Bruno. It was still early, so I sat in the lobby and read over my notes from Cracking the Coding Interview for some thirty minutes, trying to keep my cool. Finally, the recruiter came out and met me and brought me to the interview room.
Unequivocally, Google was the toughest and most nerve-wracking interview I’ve ever done. The problems were complex and challenging, all abstract and extremely algorithms-heavy. They didn’t ask me a single thing about architecture, systems design, web development—all they cared was that I could solve hard abstract computer science problems. All the interviewers—clearly brilliant (and all older white men)—were stony and tight-lipped about my performance.
I walked back to the BART station that evening, exhausted and completely drained, without any idea whether I’d done well or bombed.
A week later, I got a phone call from the Google recruiter.
I was in. Google wanted me.
Their offer was reasonably strong—120K salary with a 15% guaranteed end-of-year bonus and 24K/yr in RSUs. The total package came out to 162K/yr annualized—much stronger than my other offers, but around the ballpark of what fresh graduates of App Academy who landed at Google would earn. In other words, it seemed they didn’t place me very high on their spectrum. But whatever, right? It was Google! I got Google!
With that, the floodgates opened. Just the whiff of the Google name got recruiters into a frenzy. Companies that wouldn’t even look at me now bent over backwards to expedite me through their funnels.
Stripe onsite. Uber phone screen. Twitch phone screen. Uber onsite. Stripe offer. Twitch onsite. Uber offer. Twitch offer. The offers came in, stronger and stronger. All the irons I’d put in the fire were now going off like Roman candles.
Which left me with the question of: well, shit, what do I do with them?
As the offers came in, I weighed them seriously. Every single company I talked to was compelling and had aspects that made me want to work there.
But in the end, it was hard to argue against Google being the best choice.
The first and most visceral reason was I’d never have to deal with this BS again. Google would be a golden mark on my resume—like the Harvard of software engineering. Never again would I have to worry about credentials, or people tossing my resume without reading it. Google is the one name I’d be able to brandish anywhere as undeniable proof of my legitimacy as an engineer.
Part of it had to do with my ego, no doubt. But this job search had shown me that part of it was very real and material.
Of course, then there was the compensation. Google would be hard to beat. Like Yelp, Google was a mature public company, so its equity compensation was as solid as cash. That liquidity is an important factor when it comes to earning-to-give—it means I can give sooner, which has compounding positive impact and flow-through effects.
On top of that, Google was the only company to do a donation matching program, up to $6,000. That’s an extra $6,000 a year that goes to charity that otherwise wouldn’t. When it came to earning-to-give and building my career, when I looked at the numbers, it seemed clear I couldn’t justify choosing any company other than Google.
At that point, it seemed like a done deal. Companies like Uber, Twitch, Stripe, TripleByte, were all awesome companies. But it had to be Google.
Google! I was on cloud nine. I was ready for everything to wrap up as I figured out which bus I would be taking to San Bruno, planned out my morning workout regimen, and all the rest.
But the irons in the fire were still shooting off sparks. Offers improved, sometimes without any prompting on my part. They became increasingly stronger and stronger. Soon, they started overtaking Google’s.
I hadn’t negotiated with Google at all, so I knew the Google offer would move upward. I expected Google to settle somewhere around 180K all-in, which would be a healthy jump upward. But I started to really think: what would it take for me to turn down Google?
It was a tough question. Because I was in a competitive situation, Google had allowed me to start chatting with Youtube hiring managers and essentially pick my team.
I was offered a spot on the Youtube Red team, doing back-end work in C++. A small and fast-moving team in one of Youtube’s shiniest new projects. It would be tough, certainly, to learn the technology and start becoming productive. But I’d be doing world-class engineering, and have a world-class company on my resume.
And yet, I couldn’t deny: there was something energetically captivating about each and every startup I talked to. There was something deeper about them that attracted me, something was missing from Google. Not just the growth and the responsibility, or the greater self-determination. Each of these companies were innovators, creating new value in an uncertain future, and—they needed my help.
They actually needed my help. That was captivating. And it was hard to ignore that I didn’t really feel that in my interactions with Google.
But Google continually assured me that they’d be able to beat any other startup’s offers. It seemed like a decision they were happy to make for me. As other companies kept bidding up, the Google offer moved up to 185K. And as I was moving into final negotiations, they assured me there was still more room for the offer to grow.
More room to grow? How bad did Google actually want me?
It’s funny. I had initially been rejected by an Airbnb recruiter for a different position more than a month before. Airbnb wasn’t even on my radar. So when Ned, the CTO of App Academy told me he’d put me in touch with his friend David at Airbnb, I mostly brushed it off.
Upon Ned’s glowing recommendation, David met with me and agreed to refer me into Airbnb. With his referral, I was promptly un-rejected. David was a senior engineer there, and his recommendation seemed to carry a lot of clout (the Google offer helped of course), so I was quickly shuffled through to the phone screen.
I wasn’t expecting to do too well—I’d read in many places that Airbnb had an extremely challenging interview, and that they were more credentials-focused than other companies. So much so that I’d never heard of a bootcamp student getting placed at Airbnb. Apparently they used to post on their job listings: “no bootcampers, please.”
On the phone interview, I received a pretty challenging problem—I remember thinking when I got it that I was going to mess it up. But somehow I solved it with ease, and all of my outputs were correct. I’m not sure whether to attribute it to the accruing notches on my belt or to blind luck, but I aced the phone screen and they eagerly brought me on-site.
I’ve always had a lot of respect for Airbnb as a company—I was an early Airbnb user myself—but even as I was walking into their large and beautiful campus, my mind was already made up. I was joining Google.
The Airbnb interview was long and challenging. But, unlike the Google interview, it was invigorating. I met with payments engineers, infrastructure engineers, even a political analyst who worked on European Airbnb regulation. I was challenged on my understanding of algorithms, of caching layers and database indices, I was questioned on my beliefs about the human right of free movement across borders and on the future of travel.
I loved it. I loved everyone I met. Even more, I loved the spirit of Airbnb. Everything about it—the beautiful cosmopolitan office built as an homage to Airbnbs around the world, the people, the technology, the raw energy and drive toward connecting the world more tightly together.
Airbnb’s mission is simply, “Belong Anywhere.” I’ve been both an Airbnb guest and a host for years, and before that I was an avid Couchsurfer and Couchsurfing host. I believe strongly in the culture of sharing and interconnection.
But even so. Yeah, Airbnb was pretty cool. (And walking distance to my house!) But still, Google is Google—the tech equivalent of getting an invitation to the Justice League. How could I turn that down?
After the interview, Airbnb was slow to get back to me. Being a challenging interview, I was unsure whether an offer would come through—much less, if it could change anything. I’d already finished my last day working at App Academy, and was now officially between jobs. I decided to head home for a bit to wrap up my negotiations and rest up before starting my next gig. I had a short deadline until I wanted to start, and let each of the companies know. It was now time to go into final negotiations.
I get the phone call. Airbnb wants to make an offer. I have less than a week, but they’re scrambling to piece everything together to meet my deadline. They’ll get back to me.
They get back. Initial offer, 220K.
What on earth are they doing offering me 220K? This company must be out of its goddamn mind. No wonder tech is so overvalued. I lost my shit.
I had to take this really seriously now. Airbnb’s offer was highly illiquid, but they were offering me a very strong base salary: 130K, 25K signing bonus, and 65K worth of RSUs a year. Not as liquid as Google, no doubt. But Airbnb as a company was barreling toward an IPO, already worth more than 23B, and was of the most robust tech companies from a business and revenue perspective. Besides, if I’m risk-neutral—which I think I am—then it’s a clearly better deal.
I began really weighing things. Google…was Google. I already knew its advantages.
But at Airbnb, I’d clearly be able to take on more responsibility more quickly. The engineering organization was slated to double within a year. I was already very familiar with Airbnb’s tech stack, mostly Ruby on Rails, since it was what I’d been teaching at App Academy and developing on for the last year. It was also younger company. Unlike Google and its “lifers,” this was a place where I’d be more likely to meet people in an earlier stage in their lives—and meet potential co-founders.
Of course, it was also walking distance (the ol’ commute-less commute).
But, seemingly more affecting than all of those things—they needed me. At Google, I’d be a smart person sitting in a smart person chair. I’d be doing serious engineering work no doubt, but by the time I’d be done, I’d be walking away having changed little more than my own resume.
At Airbnb, they really needed my help. They believed I could make a difference. For the life of me I couldn’t figure out why, but they made it clear. They thought I was valuable, and they wanted someone with my experience.
God, I’m a sap.
I had less than a week to decide. I didn’t know how to make the decision. So I started trying to evaluate everything objectively. I tried estimating the value of different outcomes. I tried to ascribe weights and calculate the value of things like network, branding, growth, faster promotion, potential for meeting co-founders, likelihood of IPOing. But nothing was convincing. It felt like an impossible choice. Before long it was Thursday night and I had to make a decision before the end of day Friday. There was a lot of cursing.
Google was assuring me that they’d raise their number by Friday morning. That night I couldn’t sleep. I repeatedly got out of bed, pacing back and forth rehearsing conversations, frantically checking my e-mail and re-tweaking Excel models. What the fuck? Just a few weeks ago I could barely get anyone to look at my resume. My first offer barely cleared 120K. 220K? What on earth is Airbnb thinking??
That night and the following morning, I called up trusted friends and asked them what I should do. I was on the phone off and on for several hours through that morning. The consensus was overwhelming.
Everyone thought I should go with Airbnb.
That morning, worn thin with sleep deprivation, I got a call from Google. They were raising the offer to 211K. That’s 211K. Liquid. I’d receive all of that before a year’s end. I remember scratching my chin and just laughing. God fucking dammit. I thanked my recruiter, and let her know I’d get back to her before the end of the day.
I knew Google would have a strong final offer, maybe upwards of 200K, but 211K was stronger than I’d expected. Still, it shouldn’t sway my decision, right? Was this really a decision within a margin of 10K in EV? No one else seemed to think so. If Airbnb was the winner, it should still be the winner now.
I told myself: if I’m choosing Airbnb, just remember. 220K was their initial offer. That means there’s money on the table. If there’s one thing this job search had taught me, is that there’s always, always more money on the table.
As an instructor at App Academy I ceaselessly pushed my students to negotiate hard, without fear of being rejected, looking stupid, or being perceived as greedy. Employers negotiate even harder and with more power behind them, and so it’s up to candidates to tip the scales back in the direction of employees. As absurd as it seemed now, given an offer of 220K, I had to take my own advice and ask for more. I rehearsed it again and again in my head.
But if I’m going to ask for more, I shouldn’t just ask for 10K more. I should expect to be met somewhere in the middle, right? I’ve got to be aggressive. But I don’t have any stronger offers and they know that, so maybe it’s stupid.
I called my recruiter from Airbnb and, half expecting to get laughed at, announced: “If Airbnb can move up the RSUs by 30K to hit a total of 250K in all-in compensation, then I’ll sign.”
“250K? Do I have your word?” she said.
“Okay. Let me see what I can do. I’ll get back to you before evening.”
The rest of the afternoon was a blur of habitually checking my phone, email, anything for some word of what would happen. I was driving my car into Austin, bumper-to-bumper in traffic when I got the phone call. It was the Airbnb recruiter.
“Haseeb? This is Janice.”
“Janice! What’s the word??” I held my breath.
“I made the magic happen. 250K. 130K salary, 25K signing, 95K a year in RSUs. So you’re in?”
I almost swerved into the car next to me from punching the air so hard.
So that’s the story. I start on Monday.
On the whole, I’m really excited to be joining the Airbnb family. It’s definitely a different path than Google. Most significantly, there’ll be less that I can donate to charity in a year’s time. But not only is the total value of the assets greater, I’m also convinced that in the longer term, Airbnb will be the better move for my career.
Stock in a private company is of course still a valuable asset—I just won’t be able to donate a third of their value until a liquidation event (hopefully an IPO). But my pledge to donate 1/3rd of all of my income, including my salary, doesn’t change. Ultimately, this will be a better move in terms of EV, provided some discounting for the fact that I’ll have to donate later in the future.
That said, the brand of the company was obviously an explicit consideration for me. From that perspective, my choice to join Airbnb might seem a little strange to some. In many parts of the world, Google and Airbnb wouldn’t even be said in the same sentence. But within the SF ecosystem, Airbnb and Google are largely considered to be in the same tier of engineering organizations. I’d even argue that among certain crowds, Airbnb would be a stronger signal on one’s resume than Google would be.
So I think, on the whole, I really got lucky with a company that’s a perfect fit for what I’m looking for.
One other thing I want to add. I know some might think it’s weird to be sharing your compensation in a public venue like this. I take my inspiration from Jeff Kaufman (who ironically works for Google, albeit in Boston), who donates 50% of his income to EA charities and catalogues it publicly every year.
The norm of keeping compensation secret is a very American one. And I think on the whole, it stifles transparency and open dialogue about things like class and economic inequality. But more poignantly, it makes it harder to be transparent and galvanizing about earning-to-give, which is very much one of my goals.
I explicitly entered into tech a year ago because I believed it was a place where I’d be uniquely well-suited to create a lot of value. It’s an industry where smart, driven young people can quickly earn an outsized income. Seeing that opportunity, I decided to pivot into tech and make building a career here an active aim of my life. And I hope to, as long as I can, continue to speak openly about my compensation and give even more of it away.
So that’s enough of soapboxing. Here are some stats.
By the end of my process, I had received a total of 8 job offers (not including re-negotiation with App Academy). I had completed 12 onsites total, so my I had a total onsite-to-offer rate of 66%.
Considering only the onsites after receiving my first offer however, my onsite-to-offer rate was 87%.
Of my offers, 2 of them were through TripleByte (one from TripleByte itself, the other, Gusto, through their introduction). The remainder were through referrals. Two of the 6 referrals were non-engineering referrals.
There were 12 companies where I was referred but did not receive an offer. 25% of the companies I was referred to didn’t even talk to me. But that was a lot better than the base rate: overall, 53% of companies I applied to through any means rejected me without even talking to me.
In the end, I didn’t get a single offer through a raw application. Every single offer came through a referral of some kind. (This I did not expect, and strongly influences the advice I’d give to a job-seeker.)
The differential between my lowest (initial) offer and my highest (final) offer was, in total value, an increase of 104%. That is, my compensation literally more than doubled by not accepting my first job offer. (I expect this to be highly anomalous, since companies had a lot of discrepancies in where they leveled me on their engineering ladders.)
The largest percentage increase was also with my lowest initial offer, Yelp. They started at a total annualized value of 122.5K (105K salary + 17.5K stock), and their final offer was at a total value of 180K, an increase of $57.5K, or 47%. Again, I expect this to be anomalous, because I literally jumped in engineering levels (they initially offered me a junior role, then re-evaluated). The second largest increase was from Google, moving up $48.6K for an increase of 30%. This one is perhaps less anomalous. I’m not sure.
On all but two of my offers, I negotiated. The average delta for company offers at which I negotiated was +$30,671 for the final offer. So, negotiation pays, boys and girls. More on that later.
In total, I received offers from Airbnb, Youtube (Google subsidiary), Uber, Twitch (Amazon subsidiary), Yelp, Stripe, Gusto, and TripleByte. The average value of the final offers was approximately $193,600. The salaries were all approximately the same at $130K. (Only one company offered me a base salary of $125K.) I should also note that I negotiated more aggressively on RSUs and signing bonus. I’ll also talk more about that later.
There’s obviously a lot in this department, but this blog post is already long enough. I’m going to write one more post before I start at Airbnb this coming Monday: my key takeaways from this job search, and advice to current job seekers. I’ll also talk more about my thoughts on negotiation in that upcoming post.
Look forward to it!
This post has gotten a lot of unexpected attention, so I want to clarify a couple things.
First (and this should go without saying), everything mentioned in my story are my own thoughts and words, and though I am employed by Airbnb, I in no way speak on their behalf. (It’s legally important to say that, I guess.)
That said, I realize that pay transparency is a controversial subject, and I seem to have stirred up a hornet’s nest. So I want to make clear a few things.
Many people seem to think that publicly disclosing your compensation is a fireable offense, and that Airbnb will fire me now that they see I’ve posted this. Neither of those statements are true.
It’s explicitly illegal under the National Labor Relations Act to fire workers for discussing their compensations, and it has been illegal in American law since 1935. This kind of policy is known as “Pay Secrecy,” and such policies have been repeatedly struck down by courts.
And yet, pay secrecy is considered the norm in American culture.
There was a time in American history when income tax records were in the public domain. Even now, there are many cultures in which talking about your compensation is not at all considered wrong or disrespectful. Rather, it’s seen as an important part of creating a transparent society.
Pay secrecy is an easy fallback, because talking about social inequality and pay differentials is uncomfortable. It’s especially uncomfortable in American culture, where your salary often serves as a signal of your social status.
But pay secrecy carries with it a lot of costs. It can hide gender and racial discrimination, systemic exploitation, and nepotism. It’s easy to sweep these problems under the rug and not want to look at them. And for what it’s worth, I have a lot of respect to Airbnb for openly working toward solving these problems in the culture they’re building.
These are complicated problems. I don’t have all the answers. But because I am committed to effective altruism and publicly earning-to-give, I will continue to be open every year about how much I donate (and by association, how much I earn), insofar as it’s possible.
(For further reading, check out Your Coworkers Should Know Your Salary, published in the Harvard Business Review. Also, my response to a commenter on how disclosing my salary might be unwise or affect colleagues at Airbnb.)
The second thing I want to say is that for some reason, many people are drawing the conclusion that I primarily got a job at Airbnb by being really good at negotiating, or gaming the system, or something like that.
If you have ever done a software engineering interview, you would know that this is completely absurd. There is no way to negotiate or charm someone into passing a software engineering interview. Much less 8 of them.
If you don’t know the ins and outs of object-oriented programming, database design, asymptotic analysis, binary search trees, or how to improve the cache efficiency of an algorithm, then you’re not going to pass a computer science-heavy interview at a top company. You don’t even have a shot at it.
The moral of my story is not “get really good at negotiating and you’ll get a great job.” Negotiating is important, and I certainly encourage everyone to negotiate!
But first, get good at the thing you’re doing. Then worry about negotiating.
I moved to San Francisco from Austin, Texas about a year ago because I decided I was going to earn-to-give. Since then I’ve been relentlessly trying to build a new career for myself, so I could earn more and donate more to charity.
Entering into App Academy, barely knowing the basics of Ruby, I came into the office and grinded every day, spending 80+ hour weeks just coding and studying. I’d come in at 9AM in the morning and leave around midnight, 7 days a week, sleeping in a bunk bed in SOMA in a 200 square feet shared room.
It’s certainly true that I probably have a mind that’s well-suited for coding. But it’s also true that I outworked almost everyone who was in my cohort. And when I was hired by App Academy to help teach the course, I continued working as hard as I could to get good at this.
I still stayed late in the evenings, I still came into the office on weekends alongside the students just to continue coding and learning more. I started an algorithms study group in the evenings where I taught students new algorithms that I had read about, and wrote specs and instructions to guide them through the implementation. I took over our entire algorithms curriculum and taught well over 100 students the basics of data structures and algorithms.
And of course, I was scared that none of this would matter. That having been an English major, having a non-traditional background, being 26 and too old to transition into tech, competing against 20 year olds who’d been coding since they were 10, I thought I must have no chance.
Thankfully, I was wrong. And I’m very, very lucky that I was wrong, because I was almost right.
So if there’s one takeaway I want people to have, it’s not “here’s why it pays to be a master negotiator.” I’m going to talk a lot more about negotiation advice in my next blog post, but that’s almost a detail compared to the larger point.
The real takeaway should be: get so good that they can’t ignore you. Because once you are, they won’t.
I recently completed a job search for my first role as a software engineer. Despite having first learned how to code almost a year before, having a background as an English major and former professional poker player, I was able to land a total of 8 offers including Google, Uber, Yelp, and Airbnb (where I ultimately joined). In this three-part blog post I’m going to describe my advice to a...
A couple weeks ago I had my last day as Director of Product at App Academy. This coming Monday, I will be starting work as a software engineer at Airbnb. Here’s the story of why I left App Academy, the tribulations of my ensuing job search, and why I decided to join Airbnb. [video] Disclaimer: in this blog post and the next, I'll be speaking frankly about compensation packages I...