Not Applicable
Posted April 17, 2026
Job link
Thinking about this job
Responsibilities
Commitments
Responsibilities
- Internal Collaboration: The contractor will work closely with our internal Engineering team, who own our RTU and field-device configurations.
- Phase 1 — Network Documentation & MSP Transition Support
- Document our existing segmented network architecture and static routing configuration.
- Inventory and document our current VPN footprint, including VPNs hosted on internal servers via virtual machines as well as those terminated directly on our existing consumer-grade hardware.
- Identify gaps, undocumented configurations, and technical debt that should be addressed or flagged before handoff.
- Support the transition to our incoming managed services provider, including knowledge transfer and runbook development.
- The new network will use FortiGate hardware.
- Phase 2 — AWS Network Architecture
- Design a scalable architecture for connecting remote field servers (Client-owned and customer-owned) to our AWS environment and through to our data center.
- Target solution would replace or supplement our current cellular-based connectivity with a VPN-based approach.
- Key design goals: scalability across a growing fleet, predictable per-asset cost, resilience, and clean separation between Client and customer network domains.
- Deliverables include architecture diagrams, an implementation plan, Infrastructure-as-Code collateral (Terraform preferred) to support repeatable deployment, and a pilot deployment for a representative site.
Commitments
Engagement Type: Contract / fractional, ability to be onsite in Boston.
Estimated duration 6 months with the possibility of extension depending on Phase 2 scope.
Target solution would replace or supplement our current cellular-based connectivity with a VPN-based approach.
Not Met Priorities
What still needs stronger evidence
Requirements
- Deliverables include architecture diagrams, an implementation plan, Infrastructure-as-Code collateral (Terraform preferred) to support repeatable deployment, and a pilot deployment for a representative site.
- Strong hands-on experience with AWS networking (Transit Gateway, VPN, Direct Connect, VPC design, Route 53).
- Proficiency with Terraform and Infrastructure-as-Code practices for network deployments.
- Solid fundamentals in enterprise networking (routing, firewalls, VLANs, identity-aware access).
- Experience supporting or transitioning to MSP-managed environments.
- Experience with FortiGate hardware and associated FortiManager software.
- Comfortable producing clear written documentation and architecture artifacts — this role is as much about what gets written down as what gets built.
- Able to work independently against defined deliverables while collaborating with a small engineering team.
Preferred Skills
- Strong hands-on experience with AWS networking (Transit Gateway, VPN, Direct Connect, VPC design, Route 53).
- Proficiency with Terraform and Infrastructure-as-Code practices for network deployments.
- Solid fundamentals in enterprise networking (routing, firewalls, VLANs, identity-aware access).
- Experience supporting or transitioning to MSP-managed environments.
- Experience with FortiGate hardware and associated FortiManager software.
- Comfortable producing clear written documentation and architecture artifacts — this role is as much about what gets written down as what gets built.
- Exposure to industrial / OT networking or SCADA-adjacent environments is a plus but not required.
- Able to work independently against defined deliverables while collaborating with a small engineering team.
Engagement Type: Contract / fractional, ability to be onsite in Boston. Estimated duration 6 months with the possibility of extension depending on Phase 2 scope.
Internal Collaboration: The contractor will work closely with our internal Engineering team, who own our RTU and field-device configurations. We are looking for someone who partners well with existing technical staff rather than operating in isolation.
Scope of Work
Phase 1 — Network Documentation & MSP Transition Support
Document our existing segmented network architecture and static routing configuration.
Inventory and document our current VPN footprint, including VPNs hosted on internal servers via virtual machines as well as those terminated directly on our existing consumer-grade hardware.
Identify gaps, undocumented configurations, and technical debt that should be addressed or flagged before handoff.
Support the transition to our incoming managed services provider, including knowledge transfer and runbook development. The new network will use FortiGate hardware.
Phase 2 — AWS Network Architecture
Design a scalable architecture for connecting remote field servers (Client-owned and customer-owned) to our AWS environment and through to our data center.
Target solution would replace or supplement our current cellular-based connectivity with a VPN-based approach. Key design goals: scalability across a growing fleet, predictable per-asset cost, resilience, and clean separation between Client and customer network domains.
Deliverables include architecture diagrams, an implementation plan, Infrastructure-as-Code collateral (Terraform preferred) to support repeatable deployment, and a pilot deployment for a representative site.
Desired Attributes
Strong hands-on experience with AWS networking (Transit Gateway, VPN, Direct Connect, VPC design, Route 53).
Proficiency with Terraform and Infrastructure-as-Code practices for network deployments.
Solid fundamentals in enterprise networking (routing, firewalls, VLANs, identity-aware access).
Experience supporting or transitioning to MSP-managed environments.
Experience with FortiGate hardware and associated FortiManager software.
Comfortable producing clear written documentation and architecture artifacts — this role is as much about what gets written down as what gets built.
Exposure to industrial / OT networking or SCADA-adjacent environments is a plus but not required.
Able to work independently against defined deliverables while collaborating with a small engineering team.
Internal Collaboration: The contractor will work closely with our internal Engineering team, who own our RTU and field-device configurations. We are looking for someone who partners well with existing technical staff rather than operating in isolation.
Scope of Work
Phase 1 — Network Documentation & MSP Transition Support
Document our existing segmented network architecture and static routing configuration.
Inventory and document our current VPN footprint, including VPNs hosted on internal servers via virtual machines as well as those terminated directly on our existing consumer-grade hardware.
Identify gaps, undocumented configurations, and technical debt that should be addressed or flagged before handoff.
Support the transition to our incoming managed services provider, including knowledge transfer and runbook development. The new network will use FortiGate hardware.
Phase 2 — AWS Network Architecture
Design a scalable architecture for connecting remote field servers (Client-owned and customer-owned) to our AWS environment and through to our data center.
Target solution would replace or supplement our current cellular-based connectivity with a VPN-based approach. Key design goals: scalability across a growing fleet, predictable per-asset cost, resilience, and clean separation between Client and customer network domains.
Deliverables include architecture diagrams, an implementation plan, Infrastructure-as-Code collateral (Terraform preferred) to support repeatable deployment, and a pilot deployment for a representative site.
Desired Attributes
Strong hands-on experience with AWS networking (Transit Gateway, VPN, Direct Connect, VPC design, Route 53).
Proficiency with Terraform and Infrastructure-as-Code practices for network deployments.
Solid fundamentals in enterprise networking (routing, firewalls, VLANs, identity-aware access).
Experience supporting or transitioning to MSP-managed environments.
Experience with FortiGate hardware and associated FortiManager software.
Comfortable producing clear written documentation and architecture artifacts — this role is as much about what gets written down as what gets built.
Exposure to industrial / OT networking or SCADA-adjacent environments is a plus but not required.
Able to work independently against defined deliverables while collaborating with a small engineering team.