Weird problem → working system
I am a systems/problem-solving software engineer with C#/.NET as my strongest home base. The useful part is not a single stack: it is the pattern of understanding an unfamiliar system, crossing whichever layers matter, and owning the result through deployment and operation.
I prefer hands-on engineering. I am comfortable carrying architecture or technical-lead responsibility, but I do not want management to replace making things. The best work usually includes direct communication, room to investigate, and a problem strange enough to teach me something.
Games are not decorative flavor here. Building worlds, preserving an MMO, leading a volunteer studio and shipping small experiments shaped how I think about feedback loops, performance, systems and scope.