Systems engineering · automation · internal software

Ožbej Bohanec — Systems Engineer

I design and improve reliable digital systems, automation workflows, and data-driven tools that make complex work clearer, safer, and easier to maintain.

My work connects software delivery with operational reality. I build internal applications, infrastructure-aware services, reporting workflows, and evidence-driven technical documentation for environments where maintainability and precise execution matter.

I am Ožbej Bohanec, a systems engineer from Slovenia

Verifiable signals

Proof before positioning

I separate public evidence from private operational context. These entry points show source code, a constrained live product, a verified credential, and bounded case studies without exposing restricted systems.

Public product evidence

I publish TraceHawk source, a guided demo, reproducible verification gates, screenshots, and explicit production limits.

Review the TraceHawk evidence →

Verified technical learning

I document my Microsoft Azure Fundamentals credential separately from broader Microsoft community and learning work.

Review the AZ-900 evidence →

Bounded case studies

I maintain nine project case studies that state my role, constraints, outcome type, public evidence, and proof limits.

Compare the case studies →

Experience

Software, infrastructure, and operational delivery

Microsoft and infrastructure operations

I support Microsoft environment analysis, reporting, security posture review, technical troubleshooting, and infrastructure-aware workflows. I convert findings into explicit remediation steps and maintainable operational documentation.

CNS platforms and internal software

I maintain, improve, and automate internal platforms that connect application behavior with real operational constraints. Public case studies describe the engineering method while restricted infrastructure details remain private.

Research and learning

Evidence-led learning without inflated claims

I keep verified credentials, active research, and community learning separate. A credential proves a defined milestone; a working paper remains active research until a stable artifact exists; community participation is not presented as an official title without direct confirmation.

Contact

Discuss a systems or automation problem

I am based in Slovenia. For professional discussions about internal software, automation, infrastructure workflows, and systems engineering, I use LinkedIn as my primary public contact channel.