<ul><li>Get through to real people. If you’re applying through the front door, make sure you’re getting to human beings.</li><li>Start small and work your way up. Plan to tackle easier interviews early on and more difficult ones later on.</li><li>Study like your future job depends on it (because it does). There’s no such thing as too much preparation.</li><li>Put your best foot forward. Don’t sell yourself short! And remember, it’s a mutual exploration.</li><li>Prepare for the long game and make sure you take care of yourself.</li></ul>

Lessons learned from applying to jobs after a coding bootcamp

<img alt="Felix Feng" src="https://miro.medium.com/max/500/1*FEyyK-nuOQai3OV9iHB69g" width="48" height="48">A less-talked about part of the bootcamper’s journey is what happens after you graduate — when you’re searching for that six-figure developer position.<figure><img alt="" src="https://miro.medium.com/max/500/1*JjdbhfedcVR3i9XezIlCJA.png" width="680" height="324"><figcaption dir="auto">&lt; 3% of applications became offers</figcaption></figure>I completed Hack Reactor in July 2016 and took almost 3 months before accepting an offer with Radius Intelligence. I applied to 291 companies, did 32 phone screens, 16 technical screens, 13 coding challenges, 11 on-sites, and received 8 offers. The offers ranged from $60-125k in salary from companies all over the US, and for both front end and full stack roles. In total, 2.8% of applications became offers.Here are 5 things I wish I’d known before I began my job search.<h1 data-selectable-paragraph="">Insight #1: Get through to real people</h1>At first, I applied for companies using the shotgun approach. I applied through Indeed.com, AngelList, LinkedIn, StackOverflow, Hacker News, company websites, and even Craigslist.I’d submit a resume for any role that wanted React, Node, or JavaScript experience. In the first week, I applied to 15–20 companies a day.<BLOCKQUOTE>Pro-Tip: Find companies using this <a href="https://github.com/j-delaney/easy-application" rel="noopener" dir="ltr">easy-application repo</a>.</BLOCKQUOTE>My yield was low. Less than five percent of companies responded to me. I was throwing applications into a black hole.Everything changed when one of my cohort-mates, a former recruiter, shared a guide to the job search. He told us to send emails directly to real people with each application. It could be anybody. As long as someone read it.From then on, whenever I submitted an application, I searched for the company on LinkedIn and emailed someone on their engineering or hiring team.For most small companies or C-level executives, the email format is usually firstName@dreamCompany.com. For larger companies, it may be firstName.lastName@dreamCompany.com.To verify emails, I used <a href="https://rapportive.com/" rel="noopener" dir="ltr">Rapportive</a> to cross-check emails with social media accounts.The results were amazing. With 150+ emails sent, my response rate was a whopping 22%.It also felt great to hear from real people. Surprisingly, CEOs and CTOs responded to me. Sometimes they even interviewed me themselves.<BLOCKQUOTE>Takeaway: If you’re applying through the front door, make sure you’re getting to human beings.</BLOCKQUOTE><h1 data-selectable-paragraph="">Insight #2: Start small and work your way up</h1>You will face Level 1 interviews (a non-tech company that needs any dev), where interviewers ask you nothing more than JavaScript trivia.You will face Level 9 interviews (Google/Facebook level), where interviewers ask difficult data structure and algorithm questions.I strategically set up my process so that I had lower-level interviews earlier, and higher-level interviews later on.Early on, I gained experience, built confidence, and secured offers from companies that had less intensive interviews.As I got more experience, I effectively “leveled up.” I became capable of completing interviews at companies with higher hiring bars. This is illustrated below as a linear correlation between the number of weeks I was into the process and the base salary I was offered.<figure><img alt="" src="https://miro.medium.com/max/500/1*408EHuqaKEnSRTFPfd9AOg.png" width="680" height="489"><figcaption dir="auto">There’s a direct correlation between time spent interviewing and offer salary.</figcaption></figure>I unlocked tougher questions. I unlocked higher salaries. And eventually, I unlocked the job I took.<BLOCKQUOTE>Takeaway: Plan to tackle easier interviews early on and more difficult ones later on.</BLOCKQUOTE><h1 data-selectable-paragraph="">Insight #3: Study like your future job depends on it (because it does)</h1>I hate to break it to you, but the most important thing you could be doing at any point is studying and preparing.Why? Because you won’t get the offer if you don’t have good answers to the questions they ask you.People won’t refer you if they don’t think you’re prepared for their interviews.Coming out of Hack Reactor, my weaknesses were data structures and algorithms. <a href="http://blog.triplebyte.com/bootcamps-vs-college" rel="noopener" dir="ltr">A study by Triplebyte</a> has found that bootcamp grads are weaker in these areas than computer science grads.So I learned and practiced. Every day.I devoted entire days to learning sorting algorithms. Other days, I focused on understanding how the internet worked.If I didn’t fully understand a concept, I’d spend the day watching YouTube videos or searching StackOverflow until I did.I found the following study materials useful:<UL><LI><a href="https://www.interviewcake.com/" rel="noopener" dir="ltr">InterviewCake</a>: My favorite resource for data structures and algorithms. It breaks down solutions into step-by-step chunks — a great alternative to Cracking the Code Interview (CTCI). My only gripe is that they don’t have more problems!</LI><LI><a href="https://www.hiredintech.com/classrooms/system-design/lesson/60" rel="noopener" dir="ltr">HiredInTech’s System Design Section</a>: A great guide for system design interview questions.</LI><LI><a href="https://www.educative.io/collection/5642554087309312/5679846214598656" rel="noopener" dir="ltr">Coderust</a>: If you’re avoiding CTCI like the plague, Coderust 2.0 may be perfect for you. For $49, you get solutions in almost any programming language, with interactive diagrams.</LI><LI><a href="https://www.reddit.com/r/cscareerquestions/comments/1jov24/heres_how_to_prepare_for_tech_interviews/" rel="noopener" dir="ltr">Reddit’s How to Prepare for Tech Interviews</a>: I constantly used this as a benchmark for how prepared I was.</LI><LI><a href="https://github.com/h5bp/Front-end-Developer-Interview-Questions" rel="noopener" dir="ltr">Front End Interview Questions</a>: An exhaustive list of front-end questions.</LI><LI><a href="https://leetcode.com/" rel="noopener" dir="ltr">Leetcode</a>: The go-to resource for algorithm and data structure questions. You can filter by company, so for example, you could get all the questions that Uber or Google typically ask.</LI></UL><BLOCKQUOTE>Takeaway: There’s no such thing as too much preparation.</BLOCKQUOTE><h1 data-selectable-paragraph="">Insight #4: Put your best foot forward</h1>Breaking into the industry is hard. You have to perform well, even when you’re not fully prepared. In order to succeed, you have to be your own advocate.<h2 data-selectable-paragraph="">Sell Yourself</h2>At Hack Reactor, we’re trained to mask our inexperience. In our personal narratives, we purposely omit our bootcamp education.Why? Otherwise, companies automatically categorize us into junior developer roles or tag us as “not enough experience.”In one interview with a startup, the interview immediately went south once they realized I’d done a bootcamp. One company used it against me and made me a $60k offer, benchmarking against junior developers.Ultimately, you need to convince companies that you can do the job.At the same time, you need to convince yourself that you can do the job.You can. Focus on your love for programming. Focus on what you’ve built with React and Node. Focus on demonstrating your deep knowledge in JavaScript and any other languages you’ve learned.Only then can they justify giving you the job.<h2 data-selectable-paragraph="">It’s a Two-way Conversation</h2>Interviewing is a mutual exploration of fit between an employee and an employer. While it’s your job to convince employers to hire you, it’s also their job to win you over.Don’t be ashamed of using the interview as an opportunity to evaluate the job opportunity.I talked to any company, even if I had only the slightest interest.I did on-sites all over the country with any company that invited me out. I asked questions, and sucked up knowledge on engineering team organization, technologies and tools used, company challenges, and system architecture.<BLOCKQUOTE>Pro-Tip: During interviews, ask the following questions:What are some technical challenges you’ve recently faced?What do you enjoy about working at X company?How are teams structured and how are tasks usually divided?</BLOCKQUOTE>I treated every interaction as a learning opportunity. Each interaction helped me improve my presentation, interview, and technical skills. Each failure helped me find my blind spots.<BLOCKQUOTE>Takeaway: Don’t sell yourself short! And remember, it’s a mutual exploration.</BLOCKQUOTE><h1 data-selectable-paragraph="">Insight #5: It’s a marathon, not a sprint</h1>The journey is by no means easy. For 3 months, I grinded 6 days a week. But I tried to take care of myself.<figure><img alt="" src="https://miro.medium.com/max/500/1*k4R-k2YbaTd3lqphpEB9Cw.png" width="680" height="561"><figcaption dir="auto">What a typical day could look like in JavaScript</figcaption></figure>Some days, I’d study with friends. Other days, I’d go find a cafe and study alone, or hang out at Hack Reactor’s alumni lounge. And every week I’d check in with our career counselor to talk about my progress.It’s easy to burn out during the process. Eat well, sleep, and exercise.It can get lonely. Spend time with friends who are going through the same experience.<BLOCKQUOTE>Takeaway: Prepare for the long game and make sure you take care of yourself.</BLOCKQUOTE><h1 data-selectable-paragraph="">In summary, the key takeaways are:</h1><OL><LI>Get through to real people</LI><LI>Start small and work your way up</LI><LI>Study like your future job depends on it</LI><LI>Put your best foot forward</LI><LI>It’s a marathon, not a sprint</LI></OL>The process may seem endless, but you’re going to make it. Keep putting in the hours. Keep sending in the applications. Keep taking caring of yourself. All of it pays off in the end.A special thanks to , , , Stephanie Liu, and many others.Please share this with friends going through the job search. If you like what you read, hit that ❤ button below.

A less-talked about part of the bootcamper’s journey is what happens after you graduate — when you’re searching for that six-figure developer position. I completed Hack Reactor in July 2016 and took…

computerscience

Computer Science

artificialintelligence

Artificial Intelligence

A less-talked about part of the bootcamper’s journey is what happens after you graduate — when you’re searching for that six-figure developer position.

I completed Hack Reactor in July 2016 and took almost 3 months before accepting an offer with Radius Intelligence. I applied to 291 companies, did 32 phone screens, 16 technical screens, 13 coding challenges, 11 on-sites, and received 8 offers. The offers ranged from $60-125k in salary from companies all over the US, and for both front end and full stack roles. In total, 2.8% of applications became offers.

Here are 5 things I wish I’d known before I began my job search.

At first, I applied for companies using the shotgun approach. I applied through Indeed.com, AngelList, LinkedIn, StackOverflow, Hacker News, company websites, and even Craigslist.

I’d submit a resume for any role that wanted React, Node, or JavaScript experience. In the first week, I applied to 15–20 companies a day.

Pro-Tip: Find companies using this <a href="https://github.com/j-delaney/easy-application">easy-application repo </a>.

My yield was low. Less than five percent of companies responded to me. I was throwing applications into a black hole.

Everything changed when one of my cohort-mates, a former recruiter, shared a guide to the job search. He told us to send emails directly to real people with each application. It could be anybody. As long as someone read it.

From then on, whenever I submitted an application, I searched for the company on LinkedIn and emailed someone on their engineering or hiring team.

For most small companies or C-level executives, the email format is usually firstName@dreamCompany.com. For larger companies, it may be firstName.lastName@dreamCompany.com.

To verify emails, I used <a href="https://rapportive.com/">Rapportive </a>to cross-check emails with social media accounts.

The results were amazing. With 150+ emails sent, my response rate was a whopping 22%.

It also felt great to hear from real people. Surprisingly, CEOs and CTOs responded to me. Sometimes they even interviewed me themselves.

Takeaway: If you’re applying through the front door, make sure you’re getting to human beings.

Insight #2: Start small and work your way up

You will face Level 1 interviews (a non-tech company that needs any dev), where interviewers ask you nothing more than JavaScript trivia.

You will face Level 9 interviews (Google/Facebook level), where interviewers ask difficult data structure and algorithm questions.

I strategically set up my process so that I had lower-level interviews earlier, and higher-level interviews later on.

Early on, I gained experience, built confidence, and secured offers from companies that had less intensive interviews.

As I got more experience, I effectively “leveled up.” I became capable of completing interviews at companies with higher hiring bars. This is illustrated below as a linear correlation between the number of weeks I was into the process and the base salary I was offered.

I unlocked tougher questions. I unlocked higher salaries. And eventually, I unlocked the job I took.

Takeaway: Plan to tackle easier interviews early on and more difficult ones later on.

Insight #3: Study like your future job depends on it (because it does)

I hate to break it to you, but the most important thing you could be doing at any point is studying and preparing.

Why? Because you won’t get the offer if you don’t have good answers to the questions they ask you.

People won’t refer you if they don’t think you’re prepared for their interviews.

Coming out of Hack Reactor, my weaknesses were data structures and algorithms. <a href="http://blog.triplebyte.com/bootcamps-vs-college">A study by Triplebyte </a>has found that bootcamp grads are weaker in these areas than computer science grads.

So I learned and practiced. Every day.

I devoted entire days to learning sorting algorithms. Other days, I focused on understanding how the internet worked.

If I didn’t fully understand a concept, I’d spend the day watching YouTube videos or searching StackOverflow until I did.

I found the following study materials useful:

<ul><li><a href="https://www.interviewcake.com/">InterviewCake </a>: My favorite resource for data structures and algorithms. It breaks down solutions into step-by-step chunks — a great alternative to Cracking the Code Interview (CTCI). My only gripe is that they don’t have more problems! </li><li><a href="https://www.hiredintech.com/classrooms/system-design/lesson/60">HiredInTech’s System Design Section </a>: A great guide for system design interview questions. </li><li><a href="https://www.educative.io/collection/5642554087309312/5679846214598656">Coderust </a>: If you’re avoiding CTCI like the plague, Coderust 2.0 may be perfect for you. For $49, you get solutions in almost any programming language, with interactive diagrams. </li><li><a href="https://www.reddit.com/r/cscareerquestions/comments/1jov24/heres_how_to_prepare_for_tech_interviews/">Reddit’s How to Prepare for Tech Interviews </a>: I constantly used this as a benchmark for how prepared I was. </li><li><a href="https://github.com/h5bp/Front-end-Developer-Interview-Questions">Front End Interview Questions </a>: An exhaustive list of front-end questions. </li><li><a href="https://leetcode.com/">Leetcode </a>: The go-to resource for algorithm and data structure questions. You can filter by company, so for example, you could get all the questions that Uber or Google typically ask. </li> </ul>

Takeaway: There’s no such thing as too much preparation.

Breaking into the industry is hard. You have to perform well, even when you’re not fully prepared. In order to succeed, you have to be your own advocate.

At Hack Reactor, we’re trained to mask our inexperience. In our personal narratives, we purposely omit our bootcamp education.

Why? Otherwise, companies automatically categorize us into junior developer roles or tag us as “not enough experience.”

In one interview with a startup, the interview immediately went south once they realized I’d done a bootcamp. One company used it against me and made me a $60k offer, benchmarking against junior developers.

Ultimately, you need to convince companies that you can do the job.

At the same time, you need to convince yourself that you can do the job.

You can. Focus on your love for programming. Focus on what you’ve built with React and Node. Focus on demonstrating your deep knowledge in JavaScript and any other languages you’ve learned.

Only then can they justify giving you the job.

Interviewing is a mutual exploration of fit between an employee and an employer. While it’s your job to convince employers to hire you, it’s also their job to win you over.

Don’t be ashamed of using the interview as an opportunity to evaluate the job opportunity.

I talked to any company, even if I had only the slightest interest.

I did on-sites all over the country with any company that invited me out. I asked questions, and sucked up knowledge on engineering team organization, technologies and tools used, company challenges, and system architecture.

Pro-Tip: During interviews, ask the following questions:

What are some technical challenges you’ve recently faced?

What do you enjoy about working at X company?

How are teams structured and how are tasks usually divided?

I treated every interaction as a learning opportunity. Each interaction helped me improve my presentation, interview, and technical skills. Each failure helped me find my blind spots.

Takeaway: Don’t sell yourself short! And remember, it’s a mutual exploration.

Insight #5: It’s a marathon, not a sprint

The journey is by no means easy. For 3 months, I grinded 6 days a week. But I tried to take care of myself.

Some days, I’d study with friends. Other days, I’d go find a cafe and study alone, or hang out at Hack Reactor’s alumni lounge. And every week I’d check in with our career counselor to talk about my progress.

It’s easy to burn out during the process. Eat well, sleep, and exercise.

It can get lonely. Spend time with friends who are going through the same experience.

Takeaway: Prepare for the long game and make sure you take care of yourself.

<ol><li>Get through to real people </li><li>Start small and work your way up </li><li>Study like your future job depends on it </li><li>Put your best foot forward </li><li>It’s a marathon, not a sprint </li> </ol>

The process may seem endless, but you’re going to make it. Keep putting in the hours. Keep sending in the applications. Keep taking caring of yourself. All of it pays off in the end.

, Stephanie Liu, and many others.

Please share this with friends going through the job search. If you like what you read, hit that ❤ button below.

I spent 3 months applying to jobs after a coding bootcamp. Here’s what I learned.

Lessons learned from applying to jobs after a coding bootcamp

Related collections

Other curated ideas on this topic: