Networks / Change / Handover

Infrastructure is a team sport.

Good network engineering makes the operating model easier to explain: clearer paths, cleaner policies, and fewer surprises at handover.

Work

The useful parts of network engineering, brought closer together.

Clear topology, realistic change paths, readable policies, and diagrams that are still useful when the project is over.

01

Enterprise routing and switching

Campus and WAN design, redesigns, migrations, and incident-driven troubleshooting for environments that cannot afford mystery.

02

Firewalls and segmentation

Security policy, zone design, migration planning, and rule hygiene with a bias toward things operators can actually understand later.

03

Cisco SSE and secure access

Secure access patterns for distributed users and hybrid environments, shaped around access needs instead of tool theater.

Profile

Calm infrastructure work for complicated environments.

I work with enterprise infrastructure and secure access at Telia Cygate in Stockholm. My default is to remove uncertainty: fewer moving parts, clearer boundaries, and documentation that survives handover.

Kevin Malmgren
Design

Keep the topology explainable and avoid complexity without a clear payoff.

Migration

Plan changes around dependencies, rollback paths, and operational visibility.

Troubleshooting

Turn symptoms into a clean path through routing, policy, and access layers.

Handover

Leave diagrams, decisions, and notes that make the next change easier.

Contact

Email is the easiest way to reach me.