Job Preparation Guide

When Are You Ready to Apply?

Most people wait too long. You are ready to apply when:

• You have 3+ portfolio projects that work and are live
• You can explain your code in an interview
• You have a basic understanding of HTML, CSS, and JavaScript
• You know Git and have a populated GitHub profile

You do NOT need to know React, TypeScript, or advanced algorithms before your first application. Many junior roles will train you on the specific tech stack. Apply while you are still learning.

Where to Find Jobs

Job boards

• LinkedIn Jobs — largest professional network, easy "Easy Apply" for many roles
• Indeed — high volume, works well for broad searches
• Glassdoor — includes company reviews and salary data
• Stack Overflow Jobs — developer-focused, good quality listings
• Remote.co / We Work Remotely — for remote roles
• Angel.co (Wellfound) — startup jobs, often more flexible on requirements

Less obvious but effective

• Company career pages directly — many companies post here first or only here
• Networking — attend local tech meetups, join developer Discord servers
• Twitter/X and LinkedIn — developers often post open positions for their teams
• Recruiters — specialist tech recruiters have direct relationships with companies. Find them on LinkedIn.

The Application Process

Volume and targeting

Apply broadly but with quality over spam. Tailor your resume and cover letter for each application — especially for companies you really want to work at. For lower-priority applications, a lightly tailored resume is fine.

Aim for 5–10 quality applications per week consistently. Track every application in a spreadsheet: company, role, date applied, status.

Cover letters

Many roles don't require them. When they do, keep it short (3–4 paragraphs, under 300 words):

1. Why you are applying to this specific company (not just any company)
2. What you bring (2–3 relevant skills with brief evidence)
3. A link to your portfolio or best project
4. Enthusiasm and brief close

Never use a cover letter template that starts with "I am writing to express my interest in..." — it is immediately obvious and signals low effort.

The Interview Process

A typical junior frontend interview has 3–4 stages:

1. Recruiter / HR screen (20–30 min)

Phone or video call. Covers: background, salary expectations, start date, why you want the role. Be honest and enthusiastic. Research the company beforehand.

2. Technical screen / take-home task (1–3 hours)

Common for junior roles. You build something in your own time — often "build this component" or "fix this bug in our starter code". Tips:

• Read the brief very carefully — do exactly what is asked
• Write clean, commented code
• Add a README explaining your approach and any decisions made
• Submit before the deadline — late submissions are disqualifying
• Test in multiple browsers

3. Technical interview (45–60 min)

Live coding or whiteboard. You will be asked to solve problems or walk through your take-home task. Think aloud — explain your reasoning as you code. It is fine to ask clarifying questions. It is fine to say "I would normally Google this" — that shows self-awareness.

4. Final / cultural interview

Meets the team. Behavioural questions (STAR method). Also your opportunity to ask questions. Always prepare 2–3 good questions about the team, the tech stack, and what success looks like in the role.

Questions to Ask the Interviewer

Asking thoughtful questions signals genuine interest and helps you evaluate whether the role is right for you.

• "What does the tech stack look like, and what is the team currently working on?"
• "How does the team approach code review and knowledge sharing?"
• "What would success look like in this role after 6 months?"
• "What opportunities are there for learning and growth?"
• "What is the biggest challenge the frontend team is currently facing?"

Avoid asking about salary/benefits in early rounds unless the recruiter brings it up. Save that for after you have an offer.

Negotiating Your Salary

Many people accept the first number offered. This is a mistake — most offers have room to negotiate, and companies expect it.

Research first

Use Glassdoor, LinkedIn Salary, and levels.fyi to understand the market rate for your role and location. Know your number before you get an offer.

How to negotiate

When you receive an offer: thank them, say you are very excited, and ask for 24–48 hours to consider. Then come back with: "I am very excited about the role. Based on my research into similar roles in this market, I was hoping for [X]. Is there flexibility there?"

The worst they can say is no. Many will come back with a higher number.

Beyond salary

If the salary is fixed, negotiate other benefits: remote work flexibility, learning budget, more holiday, earlier performance review, or a specific signing bonus.

Handling Rejection

Rejection is a normal, expected part of the job search — not evidence that you are not good enough. The hiring process is imperfect and often has nothing to do with your ability: they hired internally, the budget was cut, another candidate had a very specific skill.

What to do after rejection

• Ask for feedback (most companies won't give it, but some will)
• Reflect on what you could improve in your next interview
• Keep applying — do not stop because of one or ten rejections
• Continue learning and building projects while you search

The developers who get jobs are not necessarily the most talented — they are the ones who kept applying.

Your First 90 Days

You got the job. Now what?

• Listen more than you talk. Understand the codebase, culture, and processes before suggesting changes.
• Ask questions freely. Junior developers are expected to ask questions. Pretending you understand when you do not creates problems later.
• Write things down. Take notes on everything — how the build works, team conventions, common patterns.
• Be reliable. Deliver what you say you will deliver on time. Communication first: if you are blocked, say so early.
• Volunteer for things. Show initiative. Take on tasks that stretch you slightly beyond your comfort zone.
• Build relationships. Your colleagues are your biggest resource. The developer next to you knows more about the codebase than any documentation.

Final Words

You started this roadmap at the beginning. You now know HTML, CSS, JavaScript, Git, and have a portfolio of real projects. That is more than many people who have been trying to learn to code for years.

The path forward is not complicated. Build things. Apply for jobs. Keep learning. Talk to people. Be consistent.

The developer community is largely welcoming and supportive. Share what you learn. Ask for help when you are stuck. Help others when you can. That is how careers are built.

Good luck — you have everything you need.