About me
Software Testing Engineer, six+ years in quality assurance
I test software for a living because shipping something broken is expensive and shipping something solid is a craft. I work across manual and automated testing, and I care most about the part people skip: making tests that a team still trusts a year later.
Curriculum vitae
My CV is available in English and Swedish. Both are up to date as of this month.
I'm currently exploring new QA and test automation roles. Send me a message if you'd like to talk.
Experience
Five years in software testing, split between hands-on manual testing and building automation. I've covered web applications, mobile apps and API layers, usually as the person responsible for deciding what gets automated and what stays exploratory.
Most of my automation work is in Playwright and Pytest, with a long stretch of Selenium before that. I've set up test suites in CI from scratch, cleaned up flaky ones I inherited, and spent a lot of time on the unglamorous parts: test data, environments, and reporting that non-testers actually read.
What I'm good at
Turning vague requirements into concrete test cases. Writing bug reports that get fixed on the first pass. Keeping a suite fast enough that developers don't start ignoring it. And saying out loud when a feature isn't ready, which is less popular but more useful.
Why I write
This blog is where I keep what I've learned: the approaches that worked, the ones that quietly wasted a month, and the tooling decisions I'd make differently now. Testing gets talked about in abstractions far more often than in specifics, so I try to write the specifics.
Outside work
When I'm not breaking or fixing software, I'm at the gym or hiking with my wife.