
The short answer
Junior developer job posts keep asking for the same core: Git, SQL and a relational database, one back-end framework (Laravel is very common in Kenya), a front-end library (usually React), APIs, and the ability to learn and work in a team. Listing these on a CV is easy, so it proves little. Proving them with small, finished projects is what gets interviews.

You do not need to know everything on a job post. Posts describe the ideal person. If you have most of the core and can show it, apply.
What the posts actually ask for
Read a few junior and intern listings on Kenyan job boards and the same words repeat. Here is what they usually mean in practice:
| Posts say | What it means day to day | Learn it with |
|---|---|---|
| Git, GitHub, version control | Commit small changes, work on branches, open pull requests | Your first commit, Branches without fear |
| MySQL, PostgreSQL, SQL | Write queries, design simple tables, understand relationships | SQL: SELECT and WHERE |
| PHP, Laravel | Build pages and APIs, validate input, use the database layer | Your first Laravel route |
| REST APIs, JSON | Build and call APIs, return the right status codes | Build a REST API |
| React, Next.js, JavaScript | Build interactive interfaces that call your API | A small front end for one of your projects |
| Linux, deployment | Use the terminal, put an app on a server | Linux files and permissions, Why your first deploy fails |
| Payments, integrations | Connect to services such as M-Pesa safely | Accept M-Pesa payments in Laravel |
| Testing | Write tests that prove your code works | Feature tests in your projects |
| "Team player", "willing to learn" | Ask good questions, accept code review, explain your work | Write clear READMEs and commit messages |
The skills that matter more every year
AI tools now write a lot of routine code, so the work given to juniors is shifting. Simple, repetitive pages and boilerplate are increasingly automated. What stays valuable:
- Reading and reviewing code, including code an AI wrote, and spotting what is wrong or unsafe.
- Understanding the system: how the web works, how data flows, where things break.
- Debugging calmly from error messages and logs.
- Security basics: hashing passwords, validating input, keeping secrets out of Git.
- Communication: explaining a problem and a decision clearly, in writing.
Our guide on learning to code with AI shows how to build these skills while still using AI.
Prove it: a portfolio that answers the job post
Three finished projects, each proving several skills, beat ten tutorials you followed.
| Project | Proves |
|---|---|
| Portfolio website, live | HTML, CSS, Git, deployment, attention to detail |
| Task tracker with sign-in | Laravel, SQL, authentication, authorisation, tests |
| M-Pesa checkout API | APIs, payments, security habits, careful state handling |
For each project, your GitHub repository should have:
- A README: what it does, a screenshot, how to run it, and what you would improve next.
- A clean history of small commits with clear messages.
- A
.env.exampleand no secrets anywhere. - Tests, even a few.
- A live link if possible.

Recruiters often give a GitHub profile only a quick look. Pin your three best projects and make each README's first screen say what it is and show it working.
Your CV in one page
- Top: your name, the role you want, links to GitHub and your portfolio.
- Projects before courses: what you built, the stack, and one result or lesson for each.
- Skills: only what you can discuss in an interview. Group them (back end, front end, databases, tools).
- Experience: any real work counts: freelance sites, volunteer projects, school systems. Say what you built, not just where.
The interview: what juniors are really tested on
Expect to explain a project, walk through some code, and solve a small problem. Interviewers watch how you think more than whether you are instantly right:
- Talk through your reasoning out loud.
- Ask questions when something is unclear.
- Say "I do not know, but here is how I would find out" when you do not know.
- Know your own projects deeply: why you chose each tool, and what you would change.
Ask your AI assistant
Act as an interviewer for a junior Laravel developer role. Ask me five questions about this project, one at a time, waiting for my answer each time: [paste your project README]. After each answer, tell me what was good and what a stronger answer would include.
Key takeaways
- The core of most junior posts: Git, SQL, a back-end framework, a front end, APIs.
- Reading, reviewing and debugging code matter more as AI writes more of it.
- Prove skills with three finished, well-documented projects.
- Put projects before courses on your CV.
- In interviews, show how you think.
Want a personal plan for the job you are targeting? Book a one-to-one session at a time that suits you.
Check your understanding

Every lesson stays free. Tap the thumbs up so we know what works, or say thanks with a soda or a coffee: it pays for hosting and new lessons.



