I'm Sorin, a Product Engineer and IT Consultant based in Germany. I started experimenting with code (Python) when I was 15, 19 years ago, and I've spent the last 13 working professionally shipping products end-to-end, from frontend and backend to infrastructure, and helping other companies do the same through consulting.
Outside of work I tinker with electronics and 3D printing.
Things I've built and still maintain. Products I took from an idea to something people actually use, doing the product, design, app, API and infrastructure myself.
The couples app that plans your week
A mobile app that turns good intentions into actual plans. Couples pick what they want to work on, quality time, communication, fun, adventure or romance, and Cuplido schedules one concrete plan a week inside the time they actually have. No lists to browse, no prompts to write. Shipped end-to-end: product, app, API and infrastructure.
A modern, open source Discord bot
A modular Discord bot built by the community, for the community. Everything is a plugin, so server owners enable only what they need: moderation and captcha verification, standup reminders and timezones, automatic threads, calendar events, quests, and AI summaries. Open source and self-hostable.
These are the technologies, tools, and services I rely on day-to-day for building and shipping applications. The stack evolves over time, so toggle to History to see what I've used in the past.
The core technologies I use across my projects, from language runtimes and frameworks to data stores and cloud infrastructure.
Thoughts on web development, software engineering, and things I've learned along the way. Here are the most recent ones.
The things people usually ask before we start working together.
I'm Sorin, en3sis online. Product engineer and IT consultant, based in Germany. I started poking at Python when I was 15 and have been paid to write software for 13 years. I'm comfortable anywhere in the stack, which mostly means I can follow a problem to wherever it actually lives instead of handing it off.
I help businesses ship products and keep them healthy while usage climbs. Much of my work is with companies whose product is heading toward hundreds of thousands of users and whose first architecture will not get them there. Sometimes that means writing something from scratch. More often it means joining a team that already has traffic and repairing the parts that have started to hurt.
Growth exposing decisions that were perfectly reasonable at the start. A query that was quick against ten thousand rows. A service that can only run as a single instance. A deploy everyone is slightly afraid of. No alerting, so customers notice incidents before the team does. Rarely does any of that need a rewrite. It needs someone to find the actual bottleneck and fix it without stopping the roadmap.
We talk first, and I will say so if I am not the right person. From there it tends to take one of three shapes: a short review with written findings, a few months embedded in your team, or full delivery when you have no engineers yet. Remote either way, written updates by default, calls when a call is genuinely faster. I stay in the code the whole time.
TypeScript for most things, React and Next.js on the front, Node, Bun or Nest behind it. Go when a service should be small and fast. Postgres and Redis for data. Docker everywhere, on AWS (ECS, ALB, RDS, ElastiCache) when it has to hold up, or Vercel and Hetzner when it is an MVP and moving quickly matters more. Grafana and Sentry so nothing fails quietly. None of that is dogma: I will work in whatever you already run.
Cuplido, a couples app that turns vague intentions into one concrete plan a week. I did all of it: the product, the mobile app, the API, the infrastructure. It is live on iOS and Android. Hans is an open source Discord bot I have maintained since 2022, built entirely out of plugins so server owners switch on only what they need. Both are in the Projects section above.
Germany, and yes. Most of my work has been with people in other time zones, so async is the default and nobody waits for a meeting to find out where things stand.
Write to me on X at @en3sis, or open a conversation on GitHub at github.com/en3sis. Tell me what you are building, roughly where it stands, and what worries you about the next six months. I will tell you fairly quickly whether I can help or whether you want someone else.