I'm Andreas, a frontend developer working at the overlap between design and engineering.

I'm Andreas, a frontend developer who enjoys the overlap between design and engineering: building interfaces that feel calm, clear, and intentional.I'm Andreas, a frontend developer who enjoys the overlap between design and engineering: building interfaces that feel calm, clear, and intentional.I'm Andreas, a frontend developer who enjoys the overlap between design and engineering: building interfaces that feel calm, clear, and intentional.I'm Andreas, a frontend developer who enjoys the overlap between design and engineering: building interfaces that feel calm, clear, and intentional.

I'm especially interested in product work where the UI is driven by real data: integrations, dashboards, and the kind of features where how information is shaped matters just as much as how it's presented.I'm especially interested in product work where the UI is driven by real data: integrations, dashboards, and the kind of features where how information is shaped matters just as much as how it's presented.I'm especially interested in product work where the UI is driven by real data: integrations, dashboards, and the kind of features where how information is shaped matters just as much as how it's presented.I'm especially interested in product work where the UI is driven by real data: integrations, dashboards, and the kind of features where how information is shaped matters just as much as how it's presented.

When I'm not coding, I'm at the gym or cooking. Both are basically the same hobby: small improvements, done consistently.When I'm not coding, I'm at the gym or cooking. Both are basically the same hobby: small improvements, done consistently.When I'm not coding, I'm at the gym or cooking. Both are basically the same hobby: small improvements, done consistently.When I'm not coding, I'm at the gym or cooking. Both are basically the same hobby: small improvements, done consistently.

I'd rather understand a problem well than move fast and fix it later. That usually means asking more questions upfront, and iterating until both the data and the interface feel clear.I'd rather understand a problem well than move fast and fix it later. That usually means asking more questions upfront, and iterating until both the data and the interface feel clear.I'd rather understand a problem well than move fast and fix it later. That usually means asking more questions upfront, and iterating until both the data and the interface feel clear.I'd rather understand a problem well than move fast and fix it later. That usually means asking more questions upfront, and iterating until both the data and the interface feel clear.

I find it easier to start from what a product needs to do for the person using it, and work backwards to how it should be built.I find it easier to start from what a product needs to do for the person using it, and work backwards to how it should be built.I find it easier to start from what a product needs to do for the person using it, and work backwards to how it should be built.I find it easier to start from what a product needs to do for the person using it, and work backwards to how it should be built.

I'm looking for a frontend internship where that approach matters — somewhere close to the product, where the focus is on how well something is built, not just that it's done.I'm looking for a frontend internship where that approach matters — somewhere close to the product, where the focus is on how well something is built, not just that it's done.I'm looking for a frontend internship where that approach matters — somewhere close to the product, where the focus is on how well something is built, not just that it's done.I'm looking for a frontend internship where that approach matters — somewhere close to the product, where the focus is on how well something is built, not just that it's done.