I've accepted a Junior Front End Developer job in London!

I’ve recently accepted an offer for a Junior Front End Developer position. A couple weeks on and I still can’t believe it and I can’t wait to start in a weeks time. I tweeted the news and received an amazing amount of support, the tech community is awesome :slight_smile:

Anyway, here is an account of my background, journey in coding, and advice I’d give to myself if I were to do it all over again (sorry about the length).

Recruitment Career
I graduated university and went straight into a Tech Recruitment Consultant position which involved finding Developers for various tech companies in and around London. I learnt a few things in this field that would help me later on, the key ones being:

  1. Companies tended to want Front End Developers with fundamental JavaScript skills as opposed to being reliant on a library like JQuery
  2. Good developers are in high demand and companies are falling over each other trying to attract the best (in terms of compensation, work environment, benefits, flexibility etc).
  3. Hiring managers will look at your Github and Portfolios

After a couple of years, I realised that Recruitment wasn’t challenging me intellectually and, having hired for a lot of different positions, I knew that I wanted to become a Developer.

Around this time, I took an internal Talent Acquisition role within a cool London FinTech company. It was this internal Recruitment position that has been very helpful for me on my journey to learn enough about Front End Development to land a job.

The FCC curriculum formed the basis for my Front End Development learning and I recommend it to any of my friends that are starting to learn to code. The challenges were great for learning the fundamentals. Even now, I’m using the FCC challenges to learn the basics of Redux so I can implement it into my projects and prepare for my new job.

However, I think the real value of FCC for me came from building the projects. There’s a big difference between doing a tiny challenge on FCC and having to build an app from scratch. It very much felt like being chucked in the deep end, having to break down a big project into smaller tasks. This experience meant I could see the impact of every bit of code I wrote, and therefore understand what it was actually doing.

I built the original 10 FreeCodeCamp projects in vanilla JavaScript, HTML and CSS and then, when I wanted to learn React, I rebuilt them all in React. I also decided to build them locally and push to Github rather than just having them on CodePen, as I also wanted to understand that process well.

I first heard of 100DoC on a podcast (I think CodeNewbie) and it has been an absolute game-changer for me. Instead of doing the 100 days consecutively, I did them as and when I could. I may have broken the rules, but I still gained a lot from the challenge, the main takeaway being that it’s better for me to learn little and often. Even late nights where I was tired, or didn’t have enough time, and so only sat down for 30 minutes - I still learnt something!

Another surprising benefit was the Twitter community. I’m not a social media guy but I decided to Tweet out for this challenge and I realised that there is a lot of value in simply seeing other people go through the same things you have. I now use Twitter very regularly and I’ve found cool articles, YT talks or even free Udemy courses on there.

Languages and Tools
I knew from my Recruitment career that fundamental programming skills were one of the most important aspects of being a good Developer. Therefore, when I came to learning to code, I avoided any frameworks or libraries for as long as I could.

Working in a tech company, Developers would tell me about cool new tools they were using and encourage me to look into them. I resisted the urge to learn about that tool right there and then and I had the attitude that I didn’t want to use a new tool until I felt the pain that that tool would alleviate.

This strategy only took me so far though as eventually I had to learn React and that really put me on my ass. I thought learning React would build upon my JavaScript knowledge but instead it felt like I was going back to square 1. After watching reading numerous articles, tutorials and watching videos, I began building a React application and that’s where the slow journey to understanding started.

Job Search Process
After about 8 months of pretty solid studying and coding I started to get signs that I may be ready to apply to Junior Front End Developer jobs. One big eye opener was when I saw the list of tech questions asked, and then what the expectations were for a Senior, Mid and Junior. A potential Junior developer just needed to know some basics around ES6 and React and demonstrate an ability and enthusiasm to learn!

I was fortunate that my current company had told me that in 6 months they would 100% transition me into a Junior Front End Developer. It would have been sooner, except they were going through massive growth and needed me to do my current role of Talent Acquisition. I was a bit frustrated with the time frame of it but in the grand scheme of a whole career, I guess 6 months isn’t too long…until one day I wanted to see if I could get a Dev job elsewhere off my own back (as opposed to moving horizontally internally).

I “applied” to 17 companies and I made sure to tailor each application to the company and role as much as possible. This involved writing unique cover letters and addressing my suitability of the requirements in the job spec.

  • 7 of those never came back to me
  • 7 of those rejected me at CV stage
  • 1 had a very informal coffee with me, then said they needed 3 Senior Dev hires before taking on a Junior
  • 1 recruiter friend gave me their company’s tech task for practice (but it would be marked by their devs)
  • 1 company took me through their process and eventually offered me a job

Recruitment is a lot about right time, right place and quite a bit of luck as well. When it comes to hiring Junior Developers, the company has to have a good amount of experienced Developers to mentor the Juniors. As a Tech Recruiter, it’s quite difficult finding good Senior (perm) Developers and so I understood when companies rejected me because they couldn’t take on a Junior at that time.

The application process I went through was an informal phone conversation followed by a technical task and then a 2-3 hour face-to-face. The tech task I probably spent about 12 hours on, if not more, before submitting. Then the face-to-face mainly consisted of soft skills questions around my motivations, how I problem solve, how I learn, my expectations of being a Junior Dev etc.

About one third of the interview was asking around my tech test and why I made certain choices with my code. To which I often replied, “That’s the only way I knew how to do it!”. I made sure to be honest about my knowledge but I also knew my code inside and out which helped a lot. I was also not afraid to simply say “I don’t know” on the one or two occasions where they asked me a question on a topic I’d never come across.

Overall, I came out of the interview thinking that I had demonstrated my abilities accurately and if that wasn’t what they were looking for then I’d keep on studying, coding and applying for jobs. Fortunately, they called me the next working day and offered me a job.

Lessons Learnt
If I had to do it all over again then I would do a few things differently. First of all, I would go to meetups. I wanted to go to meetups but chickened out of doing them as I didn’t want to be the “worst” developer there. This isn’t something I’m proud of and I wish I had gone to at least one to see what they were like.

Fortunately, I had some very good mentors at my day job who were instrumental in shaping my learning-to-code journey. However you go about it, I would highly recommend having some form of community around you of more experienced Devs that you can learn from.

When learning a new technology, start building as soon as you can. I got into a tutorial rut with SCSS, React, and, more recently, Redux. The sooner you start building and playing around with the tech, the sooner you fail and therefore learn. I wasted a lot of time sticking to reading articles and watching videos before I got started.

This has been a super long post, believe it or not, I cut it down a lot. I hope it added some value to someone that is on their coding journey. I started my journey on FCC and I found peoples stories into professional Development really interesting and helpful.

My plan now is to keep studying and building things in my own time, work really hard in my new job and give back to the learn-to-code community where I can. If you have any questions then feel free to ask and I’ll get to them as soon as I can.

Good luck :slight_smile:


Congratulations and thank you for sharing your journey and insights :slight_smile:.

Good luck!

1 Like


Thanks for your detailed post, there is a lot of good advice in here.

1 Like

Valuable knowledge. Always good to hear it :slight_smile:

1 Like

Great to hear, well done!

So did you use any other online resource / course other than FCC?

1 Like

Thanks! Yeh I used a lot of resources, you can actually check out every course/resource I used on my website. When I started I thought it would be a good idea to document everything in case it ever was useful.


Thats a cracking breakdown of everything, helpful pointers for what courses people should have a look at, nice job!

1 Like

congrats on the position, very inspirational.

1 Like

Well done and good luck. I hope it goes well for you.
What I like about your portfolio and social media links is you have used a quality photo of yourself on all platforms.
This was something I picked up on watching a course about promoting yourself. Many people I see here don’t bother with photos for some reason. It makes a difference.

1 Like

Congrats ! Thanks for all the details about your journey ! Well done.
Good luck in this new challenge :grin:

1 Like

Congratulations. Consistency in learning is the key. Thanks for documenting your process.

1 Like

“Learnt” is NOT a word. It’s “learned”.

Congratulations! Good luck!

1 Like

I am new in this journey. Congs bro

1 Like

Congrats on the job! Your perspective of being a former recruiter is really interesting.

May I ask you: Looking back, would you say that building everything in VanillaJS first was worth it? Or would you say that you should have learnt React earlier?

And another thing: A friend of mine who is a web developer for about 2 1/2 years now, recently told me that for front end, Photoshop is a very important skill. Actually he even said that it’s the most important skill! I was kind of surprised about that. So did they ask you for Photoshop skills?

1 Like

Congratulations on the job!

Thank you for taking the time to share your journey. There are some valuable insights that can help alot of us along the way.
One thing that stood out for me was don’t spend way too much time on tutorials etc instead keeping practicing code. Build-to-learn

Best of luck for the future!

1 Like

Thanks for the contribution…


This is a good question. I would definitely build everything in VanillaJS first if I was to do it all over again. I decided to do this in the first place because I heard from hiring managers, Developers and podcasts that having a good core understanding of a language is so important. Frameworks and libraries will come and go. Also, working in React involves a lot of core JS.

From my recruiter experience, Photoshop is not worth learning at all for a number of reasons:

  1. Typically Front End Devs will be working with Designers who’s job it is to create Designs (sometimes in Photoshop)
  2. Nowadays, a lot of good designers don’t even use Photoshop and use Sketch instead.

This will vary between companies so don’t take for gospel. For the record, I don’t know any Front End Devs that use Photoshop in their day job.

I think there is a saying in Fortnite that goes something like “just build lol”. Seems applicable here :slight_smile:

1 Like

congratulations! posts like these are gonna keep us having hope that one day we can get a job on the tech field too!

1 Like

That’s an awesome answer, thanks a lot! (well, not meaning Fortnite now lol … at least not too much :wink:)

What I also love about this VanillaJS idea is that I can begin coding right now. Because actually I’ve thought I first might have to learn React or Vue before I can start. Especially because jQuery, which I already know from the old FCC curriculum, is no longer in real demand concerning new projects.

I’m also a friend of learning the basics as good as possible. In a way, I also prefer to solve problems by myself instead of taking a framework for it :stuck_out_tongue:

Ok, then best wishes for your new job!

1 Like