Technology means deciding, supporting, and standing behind what gets delivered.
I'm head of a projects department. I don't set the direction for a single platform: we work across different applications, services, and products, with different needs and different teams. My role combines technical direction, architecture, analysis, presales, and support for the people who make it all possible.
The journey
Head of Technology and Tech Lead
I lead a projects department and coordinate resources across multiple initiatives. I define or validate architectures, support the moments of highest technical risk, and keep the connection between the need, the proposal, and what ultimately reaches production.
AI-driven transformation
I design the internal adoption of AI applied to development and training programs for other teams. The work includes course content, hands-on sessions, shadowing when it adds context, follow-up, and building MCP servers, agents, skills, and tailored tools.
Head of the projects department
Leadership of the department, API and mobile, desktop, and web application architecture, functional consulting, estimation, planning, and support throughout the delivery cycle.
Tech Lead, Team Lead, and mobile/desktop specialist
Architecture and development of .NET backend and applications for iOS, Android, and Windows with Xamarin, MAUI, WPF, UWP, and WinUI, plus team leadership and deployments on Azure.
From junior to senior developer
Analysis and development of management applications with C#, VB.NET, Windows Forms, WPF, WCF, ASP.NET, and SQL Server. During this stage I built the technical foundation I still use to review architecture and support other developers.
Presales as part of the job
Since 2015 I've taken part in project presales: I analyze the initial need, help define the solution, and draft and estimate the proposal. That continuity keeps the commercial proposal and the technical reality from becoming two different stories.
How I manage
A team works well when each person knows what they can decide on their own, what needs checking, and what's expected from the delivery. I try to put that framework in writing, review the outcome, and give context rather than just handing out tasks. When something breaks in production, the question isn't who touched it last, but what part of the system allowed it to get that far.
How I decide
I distinguish between reversible decisions and decisions that create lasting dependencies. The first kind gets tried out quickly and corrected; the second kind gets documented with a date, the alternatives considered, and the conditions for revisiting it. An architecture, a data model, or a public contract deserves more attention than a choice we could change tomorrow.
My background, in a browsable and downloadable format.
The CV page brings together experience, skills, education, and featured projects in a single linear order. It's also available as a two-page PDF, prepared for both human reading and ATS systems.
If this approach fits what you're building
We can pick up the conversation right where you already are.