Who are you?
I am Helmut Januschka, Head of Engineering at krone.at in Austria, where I work on engineering leadership, technical strategy, reliability, and systems that serve millions of users. I have been building software for more than 25 years, across everything from low-level C++ and browser engines to web platforms, infrastructure, Kubernetes, media systems, and developer tooling.
Outside my day job, I contribute to open source, including Chromium, PDFium, LLVM, and jxl-rs. In Chromium I have worked on web platform fixes, DevTools, media, Linux/Wayland, JPEG XL, and developer-facing features like the `–focus` command-line flag.
Your hobbies? Inside or outside of tech what are the things you like to do in your free time?
I spend a lot of my free time on open source, which probably counts as both hobby and obsession. I enjoy digging into browser bugs, reducing failing test cases, reading specs, and turning small user frustrations into concrete patches.
What did you want to be when you were a kid?
I did not have a perfectly planned career dream, but I was always drawn to technical systems and problem solving. In hindsight, software engineering was a natural fit because it combines creativity, logic, and endless opportunities to learn. It was just “something with computer” that i wanted todo.
What led you to a career in tech?
I was contributing to some open source forum software back in the day, mostly to get through the day, for fun. That somehow led to a job offer from my current employer, and that was 25 years ago.
Do you remember your first open source contribution?
I do not remember the exact first one, but I remember the feeling: sending a patch into a project used by people you have never met is both intimidating and exciting. Early contributions taught me that open source is not just about code. It is about communication, patience, review culture, and learning how to make a change maintainable for everyone else.
How did you get involved in Chromium?
My first Chromium CL was 4964180. It did not land but it opened a door for me.
I remember realizing that Chromium was not some unreachable black box. It was a living project where a real bug could be investigated, discussed, tested, and improved in the open. Even though that first attempt failed, it showed me the process: repro cases, tests, code review, maintainers, and the amount of care that goes into every change. That experience hooked me immediately. I became a little addicted, knowing that even a small change will be run by billions of devices.
What is your favorite thing/project/tech to work on?
Browser engines. They sit at the intersection of almost everything I enjoy: C++, web standards, rendering, networking, media, security, performance, developer tools, and huge-scale engineering.
I especially like bugs where the cause crosses layers: a web API behavior that depends on browser process state, a media issue that depends on GPU drivers, or a layout/accessibility issue that only shows up with a precise test case. Those problems are hard, but they are also very rewarding because the fix can improve the web for many users.
Tell us about the thing you’re most proud of and why?
Besides having two great kids, I would say I am proud of becoming a Chromium committer and OWNER, but even more of the path that led there: trying to improve myself year over year, chasing higher impact, and building deeper understanding.
A specific highlight is helping with the JPEG XL revival in Chromium. That work involved the Rust-based jxl-rs decoder, Chromium integration, tests, performance work, and many small details that have to line up before a feature can ship in a browser.
Chromium is such a large and complex project that it changed how I approach open source in general. After learning my way around Chromium, other repositories feel much less intimidating.
What is the best connection you’ve made through open source?
It is honestly hard to name just one, or even a few. The Chromium community has been incredibly welcoming and generous with knowledge, so the full list would be far too long.
What I value most is that these connections started from concrete technical work: a bug, a CL, a review comment, or a discussion about how to make something better. That is what makes open source special to me. And it was a pleasure that my recent BlinkOn visit made it possible to meet some of the community in person!
What is your #1 top tip for getting involved in the community?
Consistency is key. If it is open source and you have the code, then with enough time and persistence, you can understand it.
Start with something small: reproduce a bug, write a test, fix a typo, or investigate one failing case. You do not need to understand the whole project before you begin. Just start doing, keep showing up, and do not hesitate to ask for help.
What’s your favorite open source conference?
At this stage of my life I choose conferences carefully, because staying home and playing with my kids is priority number one.
Where can people find you?
Website: https://www.januschka.com
GitHub: https://github.com/hjanuschka
LinkedIn: https://www.linkedin.com/in/hjanuschka/
X/Twitter: https://x.com/hjanuschka
Email: helmut@januschka.com