How to show what you can do and find the direction after training
The training regulations for web developers have an entire subject dedicated to job seeking and industry knowledge: based on a company analysis, the student must be able to write a job application, prepare a CV with professional and personal competences, and explain the structure and importance of an up-to-date portfolio. It is no coincidence — in a practical trade like web development, the proof of what you can do is at least as important as the description of it.
A CV tells what you have learned; a portfolio shows it. Collect a small selection of projects you have actually built — preferably with a short description of what problem the project solves which technologies you used and what you contributed. A link to the code and where possible a running version of the solution carries weight: it lets an employer see quality for themselves instead of taking your word for it.
A professional CV for web development should show concrete technologies and tools you master, preferably linked to projects where you have used them, not just as a loose list of names. Supplement with the personal competences the trade actually requires: working together in a team, communicating with a client, and being able to document and explain your own work — all things the training regulations themselves emphasise as part of the education's goals.
An application that could have been sent to anyone is rarely read to the end. Take some time to understand the company — what technologies do they use, what kind of customers or products do they work with, and what does the job advert specifically ask for? Then write your application so it clearly links your specific experience to exactly what the company needs, rather than a generic description of yourself.
Web development is a trade in constant motion. The education therefore also focuses on professional renewal — the ability to acquire knowledge about current professional and technological development trends and use it in your own practice. Follow professionals and official documentation, try out new tools in smaller projects, and keep it a habit for the rest of your career, not just while you are an apprentice.
| Direction | What you typically work with |
|---|---|
| Frontend developer | User interfaces, accessibility, responsive design, browser performance |
| Backend-/serverside-udvikler | Business logic databases APIs and security |
| Full stack developer | Both frontend and backend, often in small teams or companies |
| Other paths | UX/design, quality assurance and testing, operations and DevOps |
“A portfolio is not a facade — it is the most honest job application you can send because it lets the work speak for itself.”
— Rule of thumb from the industry