Web developers build and maintain websites and web applications. Depending on the job, they may work on how pages look, how they connect to data, or both, and they often deliver complete sites for clients or employers.
Where you start matters less than what you can show you have done. This is what the work is built from.
Core skills
Tools and settings
What the work tends to feel like from one day to the next.
You may be building several things in a week: a new page for one client, a fix for another, and an update to an older site. Time goes to meeting with clients or colleagues to clarify what is needed, then building, testing on different devices, and publishing. There is also maintenance: updates, backups, and the occasional emergency when a site goes down.
The day-to-day tasks behind the job title, in plain terms.
There is rarely one route to becoming a web developer. These are the two most common.
Many web developers come from non-traditional routes, and a strong portfolio carries real weight.
A first live site for someone else shows you can take a brief to delivery.
How people usually show they can do the work, and how employers tend to weigh each route.
Common and helpful, but many engineers are self-taught or retrained. Employers care most about what you can build and explain.
Short, practical certifications for a cloud provider, a security standard or a tool show current skills, and can open doors for career changers.
Public repositories, a deployed project, or write-ups of problems you solved often count for more than any certificate.
As you gain experience the work tends to fork. These are two directions it commonly takes.
Building sites that non-technical editors can maintain.
Interactive products with accounts and data.
A typical shape, not a rule: people move at different speeds, and some skip stages.
Many web developers come from non-traditional routes, and a strong portfolio carries real weight.
Get dependable at hTML, CSS and JavaScript, a content management system or framework and responsive and accessible design, and learn how your employer's tools and habits work. This is where trust is earned.
Building sites that non-technical editors can maintain. Web applications is the other common direction.
Short design notes and post-incident write-ups show how you think, and they are what senior people are asked to produce.
What usually separates people who progress from people who stay level.
Take a feature, a service or an incident from first idea to production, and be the person who can explain every step of it.
Short design notes and post-incident write-ups show how you think, and they are what senior people are asked to produce.
Learn the layer just below and just above the one you work in; most promotions go to people who can see the whole path of a request.
Every role has them. Knowing what they are is part of choosing it well.
Agree scope and change processes in writing, show work early, and price changes clearly.
Schedule maintenance, keep backups, and use trusted components.
Plan time per project, communicate delays early and keep tasks small.
No role suits everyone. These are the traits that help and the things people say they wish they had weighed first.
Local meetups, online forums and open-source project chats are where hiring managers and peers actually talk shop.
Answering questions and reviewing others' code builds a record people can check before they ever meet you.
A repository or two with a clear readme beats a long list of technologies on a resume.
Lead with the problems you have solved and the systems you have run, not only the languages you know.
The two most common routes are self-study, a bootcamp or a degree and small client or volunteer projects. Many web developers come from non-traditional routes, and a strong portfolio carries real weight. A first live site for someone else shows you can take a brief to delivery.
The essentials are hTML, CSS and JavaScript, a content management system or framework and responsive and accessible design. Employers also value understanding client needs, managing your own time and explaining technical limits plainly.
Typical tools and settings include a code editor, browser developer tools, version control and a hosting platform. The names change with employer and fashion, so understanding what each kind of tool is for matters more than any one product.
Websites and content management: building sites that non-technical editors can maintain. Web applications: interactive products with accounts and data. To move up in this kind of work, own something end to end: take a feature, a service or an incident from first idea to production, and be the person who can explain every step of it.
Every organisation needs a web presence, so demand is broad, though basic site-building tools mean employers value developers who offer more than the basics. It is worth weighing the pace of change, screens and sitting and on-call and deadlines before you decide.
Read the interview questions for the role, then practise answering out loud. HireMonkey lets you upload your resume and a job description and answer an AI interviewer that follows up, then scores each answer and tells you what to fix.
Upload your resume and the job description, and the AI interviewer builds its questions from both. Every answer is scored against the bar for the role, with notes on what to fix.