DOCUMENT: CV  ·  SOFTWARE ARCHITECT — .NET

A career as a system:
versioned and documented.

Over a decade in the .NET ecosystem — from code, through architecture, to leading teams and my own company. An online version below; a PDF is available for recruiters.

Revision
2026.06
Status
CURRENT
Location
BIELSKO-BIAŁA / PL
Work mode
B2B / REMOTE
SEC-01

Experience.

2018 — PRESENT

Founder & Software Architect

Digital Templars — Bielsko-Biała

Full technical ownership of a B2B software studio: system architecture, delivery, CI/CD and production maintenance for clients in railway, banking, insurance and agriculture.

C# / .NETASP.NET CoreSQL ServerAzure DevOpsArchitecture
2022 — PRESENT

Internship program mentor

Digital Templars — program for pupils and students

A custom internship program based on real projects: working in a repository, code review of every change, weekly mentoring. Four graduating cohorts.

MentoringCode reviewGit / PR flow
2014 — 2018

Senior .NET Developer / Tech Lead

Transport systems

Design and development of railway transport management systems: integrations with external systems, electronic order modules, performance optimisation.

.NETT-SQLIntegrations
2010 — 2014

.NET Developer

Banking sector

Development of backend banking systems: transaction data processing, reporting, work under high-availability constraints.

C#SQL ServerWCF / services
SEC-02 / STACK

Technology matrix.

Backend
C# / .NET 10ASP.NET Core MVCMinimal APIEF CoreSignalRBlazor
Data
SQL ServerPostgreSQLT-SQL / optimisationBackup & DR
Frontend
ReactRazorAstroTailwind
Infra / DevOps
Azure DevOpsGitHub ActionsDockerIIS / Windows ServerLinux
AI / Automation
Agents / orchestrationOllaman8nClaude Code
SEC-03 / PRINCIPLES

Working principles.

01

Production is the judge

Architecture that has not survived contact with real load and real data is a hypothesis — not a solution.

02

Simplicity scales better than cleverness

The most expensive code is the kind only its author understands. I pick boring, predictable, maintainable solutions.

03

Decisions get documented too

Code says "how", decision records say "why". Years later the latter turns out to be more valuable.

Download PDF