Software Engineer · Software Evolution
I care about what happens when that software needs to change.
I’m a Software Engineer with fullstack experience and strong backend depth, focused on understanding complex systems, reducing uncertainty, and making software easier to maintain and evolve.
SYSTEM / 01
uncertainty safer change01 / Engineering approach
Complex systems rarely need more activity first. They need a clearer model of what is actually happening.
I investigate behavior, make assumptions explicit, weigh consequences, and match engineering effort to the context. The goal is not theoretical perfection. It is a system that remains understandable and capable of change.
02 / Selected evidence
Case studies about investigation, trade-offs, maintainability, and what happens after software begins to evolve.
Software engineering · Test automation architecture
Investigation of instability patterns, followed by clearer responsibilities, reusable components, resilience mechanisms, and structured execution evidence.
Key lesson: sound architecture also needs decision-relevant evidence and an adoption strategy.
Read case studyLegacy system · Root-cause investigation
Tracing runtime behavior exposed an obsolete module that overwrote correct restrictions on the in-memory user entity.
Key lesson: follow state changes and revise the hypothesis when runtime evidence contradicts it.
Read case studySystems thinking · Externalizing complexity
How investigation and a connection map turned implicit knowledge into something others could use.
Read case studyReliability · Consequence-aware decisions
An anonymized engineering story about a known cable condition, a deferred intervention and more than 16 hours of operational recovery.
Key lesson: working is not the same as healthy.
Read case study03 / Technical expertise
A
Strong depth in Java and Spring, with attention to boundaries, behavior, maintainability, and system evolution.
B
Fullstack experience with a current focus on React and secondary experience with Angular.
C
Systems thinking, explicit trade-offs, contextual judgment, and structures that make change easier to reason about.
D
Evidence-driven engineering, automated testing, investigation of instability, and quality under real constraints.
04 / About
My path into software was shaped by the same question that guided earlier technical work: how does this system really work?
That curiosity became a practical engineering method — investigate uncertainty, build a useful model, test assumptions, and act with an understanding of risk, cost, and consequence.
Today, I bring fullstack experience and strong backend depth to software that needs not only to work, but to remain understandable and capable of change.