Ožbej Bohanec

Engineering profile

Engineering Stack and Contact

I work across software, automation, data, infrastructure, and operational systems. The levels below describe how I use each technology; links point to case studies where public evidence is available.

Working method

How I approach technical work

I trace the real workflow and constraints before changing the system, then verify the result against code, runtime behavior, and operational evidence.

1. Establish the system

I map ownership, data paths, current behavior, failure modes, and the boundary between public evidence and private operations.

2. Make controlled changes

I prefer small, reviewable improvements with explicit acceptance checks over broad rewrites that hide risk.

3. Verify delivery

I use tests, validators, runtime checks, documentation, and proof limits so completion is based on evidence rather than confidence.

Capability map

Technical stack by working depth

Regular use

Used in recurring engineering and operational work

Technologies I use for administration, integrations, diagnostics, and supporting systems.

  • PowerShell
  • Microsoft 365
  • Entra ID
  • SharePoint
  • Microsoft Defender
  • Proxmox
  • Portainer
  • Cloudflare Zero Trust
  • n8n
  • REST APIs
  • C# / .NET
  • SQLite
  • Linux
  • Git
Working knowledge

Applied in bounded projects, learning, or integration work

Useful capability without implying the same depth as the core stack.

  • Azure administration concepts
  • QRadar
  • SignalR
  • MQTT
  • OCR providers
  • Ubiquiti
  • C++
  • Three.js / React Three Fiber
  • Security telemetry formats

Contact

Discuss an engineering role or project

I am open to relevant software, automation, systems, and technical-operations discussions. LinkedIn is the public contact channel for this portfolio.

Contact me on LinkedIn Review selected work