🤟 Kamil Kiełbasa — CTO
I’ve been working in IT for over a decade, long enough to see technologies come and go, and long enough to focus less on trends and more on what actually works in production. I started as a developer, but over time moved toward architecture and technical leadership. Not as a planned career path, but as a result of consistently asking the same questions: Why is this system hard to change? Why does delivery slow down over time? Why do seemingly small decisions create long-term risk? Today I work at the intersection of software architecture, engineering leadership, and organizational design. I help teams and companies build systems that are not only scalable, but also adaptable to change — because in practice, the ability to evolve matters more than the ability to scale. My experience spans designing distributed systems, working with Domain-Driven Design, and building cloud-based platforms (.NET, AWS, Docker). But more importantly, it includes shaping how teams make decisions, define boundaries, and collaborate across roles. I’ve led technical initiatives, supported teams in making architectural trade-offs, and facilitated workshops that align engineering with business goals before those decisions are locked into code. I care deeply about: - reducing delivery risk as systems grow - improving clarity in complex domains - building shared understanding between engineering, product, and business - creating environments where teams can make better decisions, not just write better code Beyond hands-on work, I regularly run architecture workshops, trainings, and modeling sessions. I also write and speak about software architecture — not to promote silver bullets, but to share practical lessons from real systems and real constraints. Topics I keep coming back to include evolutionary architecture, domain modeling, escaping legacy traps, and keeping systems maintainable as organizations scale. I’m naturally curious, skeptical of hype, and focused on outcomes. I believe good software is the result of technical decisions made in the right context, by teams that understand both the system and the business behind it. If you're working on complex systems, scaling teams, or trying to make better engineering decisions under real-world constraints — let’s connect.
Stackforce AI infers this person is a SaaS architect with a strong focus on scalable and maintainable systems.
Location: Warsaw, Mazowieckie, Poland
Experience: 9 yrs 5 mos
Skills
- Web Applications
- Amazon Web Services (aws)
- Domain-driven Design (ddd)
- .net
- Cloud Computing
- Project Management
- Artificial Intelligence (ai)
- Data Engineering
Career Highlights
- Expert in Domain-Driven Design and scalable architectures.
- Led teams to deliver complex software solutions.
- Passionate about aligning engineering with business goals.
Work Experience
Jit Team
Technical Lead (9 mos)
Meniga
Team Lead (1 yr 2 mos)
Valkir Academy
Technical Trainer (2 yrs 6 mos)
Interact Software
Technical Lead (9 mos)
exeno.com
Head of Software Engineering (1 yr 2 mos)
Technical Lead (7 mos)
Sages
Technical Trainer (7 yrs 2 mos)
7N
Consultant Dotnet (2 yrs 7 mos)
bd90
Chief Blogging Officer (9 yrs 2 mos)
Polskie Radio S.A.
Lead Software Developer (2 yrs)
Linecode
Owner / CTO (9 yrs 10 mos)
CYFROWY POLSAT
Software Developer (2 yrs 3 mos)
Samsung Electronics
Junior Software Engineer (1 yr 1 mo)
NetKata
Web Developer (1 yr 7 mos)
Education
Informatyka at Wyższa Szkoła Technologii Informatycznych w Warszawie
Informatyka at Uniwersytet Marii Curie-Skłodowskiej w Lublinie
