ABOUT ME

I like understandinghow systems fit together.

I'm a cybersecurity and software engineer with a background in full-stack development, application security, networking and infrastructure.

What interests me most is the space between those disciplines: how applications are built, how they communicate, how they are deployed, and how they can be secured.

BACKGROUND

From software development to cybersecurity.

01

Data Engineering

My software-engineering foundation came from studying data engineering and working with full-stack application development. My bachelor project involved developing a complete web application with a .NET backend, React frontend, MongoDB and enterprise identity integration.

02

Moving deeper into security

During my studies I became increasingly interested in what happens behind the application layer — networks, authentication, attack paths, monitoring and the decisions involved in protecting real systems.

That interest led me to continue into a master's degree in cybersecurity.

03

Cybersecurity

My master's work focused on application-embedded defense: building a working prototype that analysed structured business data before it reached a protected application and routed suspicious requests into different defensive response paths.

Explore the thesis →
04

Building my own infrastructure

A large part of how I learn is through my homelab. I run my own storage, containers, DNS, VPN, reverse proxy, cloud services and home-automation infrastructure.

It gives me an environment where I can experiment with networking, Linux, deployment and security using services I actually rely on.

Explore the homelab →

HOW I WORK

Build it. Understand it. Improve it.

01

Learn by building

I understand technologies best when I can deploy them, break them, troubleshoot them and see how they behave in a real environment.

02

Understand the whole path

I like following a system from the frontend through APIs, networks, infrastructure and security controls instead of treating each layer as completely separate.

03

Automate repeatable work

If something needs to be performed repeatedly, I prefer turning it into a reproducible process through scripts, containers or CI/CD.

04

Keep asking why

Knowing that something works is useful. Understanding why it works, where it can fail and what assumptions it depends on is much more valuable.

TOOLKIT

Technologies I work with.

Not an exhaustive list — just the technologies and areas that best represent the work shown throughout this portfolio.

Cybersecurity

Application SecurityIncident AnalysisNetwork SecurityThreat AnalysisSecurity Monitoring

Software Engineering

PythonC# / .NETReactTypeScriptFastAPIREST APIs

Infrastructure

DockerTrueNASLinuxNginxWireGuardDNS

DevOps & Tools

GitGitHub ActionsCI/CDMongoDBPrometheusGrafana

CURRENTLY INTERESTED IN

Security, infrastructure and the systems between them.

Application SecuritySecurity OperationsNetworkingDetection & ResponseSelf-HostingInfrastructure Automation

WANT TO SEE THE WORK?

The projects tell the rest of the story.

Explore my academic work, software projects and the infrastructure running this website.