Selected work

Meteory · May 2026 — Present

A multi-site network foundation for eighteen locations

Designing and implementing the first four locations of a phased company network roadmap spanning eighteen sites, alongside internal systems and infrastructure automation.

Role
Network Engineer
Organization
Meteory
Period
May 2026 — Present

Context

The environment

Meteory operates a distributed branch footprint. The infrastructure needs to support current operations while establishing a repeatable foundation for later phases.

Problem

What needed to change

Create a consistent, secure network model that connects locations, separates business functions, centralizes identity and policy, and remains manageable as the footprint expands.

Constraints

  • Phase one covers four locations within an eighteen-location roadmap.
  • The design must accommodate mixed network vendors and existing operational requirements.
  • Public documentation cannot expose internal addresses, hostnames, firewall rules, or credentials.

Contribution

My responsibility

  • Network architecture and phased rollout planning
  • VLAN segmentation and inter-site connectivity
  • FortiGate firewall policy and VPN design
  • Corporate Wi-Fi, monitoring, and Active Directory integration
  • Internal business systems and infrastructure automation

Approach

How I structured the work

Standardize the branch model

Define a repeatable site pattern for segmentation, edge security, wireless access, monitoring, and identity services so later locations can follow the same operating model.

Separate trust zones

Use VLANs and firewall policy boundaries to separate business functions and reduce unnecessary lateral access between network segments.

Centralize access and visibility

Connect locations through managed VPN paths, integrate directory-backed identity, and establish monitoring that supports consistent operations across sites.

Automate repeatable work

Build internal systems and automation around common infrastructure tasks to reduce manual effort and improve consistency during expansion.

Evidence

A safe view of the system

Repeatable site pattern for an 18-location roadmap. This diagram is intentionally abstract and contains no operational identifiers.

Outcome

What the work established

  • Established a repeatable architecture for the initial rollout and the wider eighteen-location roadmap.
  • Introduced clear segmentation, centralized policy, identity integration, and cross-site visibility.
  • Created a foundation for internal systems and infrastructure automation as the environment scales.