I like the unglamorous parts.

I am a software engineer working across backend, AI, and distributed systems. I care about the details that keep software correct when no one is watching.

Most of what makes software good happens where no one is looking: the retry that is actually safe, the query that does not lock the table, the log line that turns a 2am page into a five-minute fix.

I gravitate toward that work. Since July 2024 I have been a software engineer at Infineon Technologies, building developer tooling for the people who design microcontrollers. I work alongside hardware engineers, translate their domain into code, and ship services in C#, ASP.NET Core, and Blazor that remove manual steps between a chip specification and a working device. Shorter feedback loops there mean silicon reaches the market sooner.

The thread through all of it is a preference for systems that are honest about their limits and legible to the next engineer. Outside that mandate I am deliberately going deeper on backend architecture, AI engineering, and distributed systems: retrieval and inference that stay cheap under load, queues and caches chosen on purpose, and consistency tradeoffs written down rather than discovered in an incident.

I also write. Explaining a concept is how I make sure I actually understand it, so I turn the things I learn into posts that the next person can read instead of relearning the hard way.

What I work on.

Backend Engineering

APIs and services that stay correct under real traffic. Clean data models, sane transactions, and error paths that fail loudly instead of silently.

ASP.NET Core

Python

PostgreSQL

AI Engineering

Retrieval, embeddings, and inference wired into products that ship. Keeping models useful, observable, and affordable in production.

PyTorch

RAG

Vector search

System Design

Distributed systems that degrade gracefully. Queues, caches, and consistency choices made on purpose, with the tradeoffs written down.

Kafka

Redis

Docker

Kubernetes

Where I have worked.