Hampus
Andersson

Fullstackdeveloper

Full-stack developer building clear, maintainable web products. Looking for LIA in Varberg and the wider Halland area from January 2027.

Languages

JavaScriptTypeScriptPythonC# / .NETHTMLCSS

Frontend

ReactNext.js

Backend

Node.jsExpressREST APIsPrisma

Database

MySQLPostgreSQL

Design & UX

Responsive designAccessibilityUser flowsPerformance

Tools & Workflow

GitGitHubViteCloudflareLighthouseAgile workflow

Projects

Parameter Management System

Preview illustration for the Parameter Management System case study

A full-stack internal tool focused on large data sets, clearer information architecture, and faster access to the right parameter data.

Rörmokaren Västerås

Preview illustration for the Rörmokaren Västerås case study

A service-business site rebuilt around trust, speed, and clearer calls to action for visitors ready to get in touch.

HA Webbyra

Preview illustration for the HA Webbyra case study

End-to-end client work across discovery, design, development, launch, and long-term iteration.

More About Me

Porträtt på Hampus Andersson

Hello!

I currently live in Köping during my studies, am originally from Varberg, and am looking for LIA in Varberg or the wider Halland area from January 4 to March 12, 2027.

I study the two-year Full-Stack Developer program at Medieinstitutet, a full-time distance education focused on frontend, backend, APIs, databases, and modern e-commerce flows. Alongside that, I build real solutions through my own agency work at HA Webbyrå.

I have previously done LIA and internship work at Volvo Powertrain. During that period, I worked in an international .NET team that developed and maintained an internal application used across the Volvo Group.

As my thesis project, I then built an internal system for parameter management. That experience gave me a clear understanding of how structure, APIs, and databases need to work together in larger environments.

I enjoy working close to real needs. To me, a good solution is not just visually polished or technically correct. It also needs to be clear to use, possible to build on, and understandable for the next developer.