SIMON M.

HOI, DEVEDIS.I GLOUBE, MIRPASSE GUET ZÄME.

OVERVIEW

But first, the essentials.

My background at a glance: what defines my work, training, and context.

ENGINEERING

3 years of experience

in professional software development

  • React
  • Next.js
  • TypeScript
  • PostgreSQL
  • Docker

EDUCATION

MSc in Engineering

Human-Computer Interaction

Design thinking meets software engineering.

  • German

    Native speaker

  • Bern, CH

    Based locally

  • B permit

    EU/EFTA

WHY DEVEDIS

What interests me about devedis goes beyond the technologies you use.

I found a lot of familiar thinking in how you approach products, ownership, and technical decisions.

01PRODUCT BEFORE FRAMEWORK

We start with the product, not the framework.

devedis · Tech stack

You start withThe product.So do I.

What drew me to devedis is the belief that good software starts with understanding the problem, not jumping straight to a solution. I try to understand the people, their workflows and what they actually need before deciding what to build and how to build it.

02END-TO-END OWNERSHIP

Take on responsibility and lead projects in large parts yourself.

devedis · Job ad

Ownershipbeyond the code.

I like taking problems from the first conversation to a working product. That means understanding the business needs, shaping the solution and seeing it through.

At Aproda, I proposed the architecture for a multi-shop platform, helped prepare the commercial offer and took responsibility for technical delivery, working directly with the client through regular releases and feedback.

That's what I'd bring to devedis: someone who doesn't just build what's asked, but helps figure out what's worth building and takes responsibility for delivering it.

End-to-end delivery

How I took a client project from architecture and estimation through implementation and release.

03THE VERSATILE TOOLBOX

We keep the architecture as simple as possible.

devedis · Tech stack

WHERE I PUT IT TO THE TEST

If all you haveis a hammer,everything lookslike a nail.

I enjoy exploring technologies beyond the ones I use every day. It helps me question familiar choices and recognise when something could work better. But adopting a tool also means owning its complexity, dependencies and maintenance. Sometimes the right decision is to try something new. Other times, it's to keep what already works.

JOURNEY

My path from design to engineering

A git-style timeline of the key chapters that shaped how I build products today.

$ git log --graph --oneline --decorate

NEXT CHAPTER

The next commit could be ours.

PULL REQUEST #001

Open

feat(team): bring a product-minded engineer to devedis

simon/next-chapterdevedis/team

Why this PR?

I bring a combination of product thinking, a UX/HCI background, and hands-on engineering, which lets me connect user needs, design, and technology to build thoughtful, high-impact products with the team at devedis.

What's included

  • Product thinking grounded in UX and HCI
  • Full-stack engineering with React and TypeScript
  • Experience shipping products for real users
  • Curiosity, ownership, and thoughtful collaboration

Review summary

  • Waiting for review
  • Checking conflicts
  • Status checks: running

candidate-fit.md

+4−1

  1. generic candidate
  2. Product thinking grounded in UX and HCI
  3. Full-stack engineering with React and TypeScript
  4. Experience shipping software for real users
  5. Curiosity, ownership, and collaboration
Start the conversation