NorthMark Strategies is a leading investment firm, combining capital, innovation, and engineering to drive long-term value. From operating complex businesses to backing breakthrough technologies, our mission is to build enduring businesses. Our team combines intelligent risk-taking, operational excellence, exceptional talent, and world-class computing capacity to create shareholder value.
Our company offers a dynamic environment where individuals have the freedom to lead companies toward bold achievements by embracing innovation, leveraging technology, and fostering differentiated business strategies. Our values are Integrity, Ability, and Energy, and the company aims to hire individuals who possess those qualities.
At NorthMark Strategies, we believe the future isn’t something to hope for, it’s something to build. We don’t just invest, we create. Bringing together strategic insight and technical horsepower to deliver outcomes that endure.
The Position
We run governed infrastructure across Azure, AWS, and on-prem for multiple portfolio companies. We want a Senior Cloud Platform Engineer who works as a peer on the platform. You’ll work from design through production, troubleshoot hard problems without help, and raise our bar for automation, security, and documentation.
What you will build
Paved roads
Shared Terraform modules that teams use to get their environments: networking, storage, identity, compute, secrets, and monitoring, with secure defaults built in.
Versioned, tested, documented modules, so a team can move to a new version without asking us.
Policy as code (Azure Policy, conftest, SCPs and RCPs) that catches problems at plan time, not after apply.
Self-service: a team fills in a short tfvars file and gets a working, compliant environment.
Projects
Platform projects, from design to production, with the architect. A current example is a secure platform that shares petabyte-scale data with our portfolio companies across Azure, AWS, and on-prem.
Infrastructure for the teams we serve: GPU capacity for machine learning, remote workspaces, and hybrid connectivity to the datacenter.
Proofs of concept that settle a design question quickly, with real numbers. This includes judging which new cloud features are worth adopting.
The platform itself
Landing zones and guardrails: management groups and subscriptions in Azure; Organizations, OUs (organizational units), SCPs, RCPs, and account vending in AWS.
Networking: hub-and-spoke and Transit Gateway, firewalls, private endpoints and VPC endpoints, DNS, ExpressRoute, Direct Connect, and VPN.
Identity: Entra ID, managed identities, IAM Identity Center permission sets, cross-account roles, and workload identity federation (OIDC). No stored secrets or long-lived keys where federation is possible.
CI/CD for infrastructure: GitHub Actions with OIDC, self-hosted runners, and plan review in every pull request.
What you will also run
Builders run what they build. You take part in:
the on-call rotation for the platform, with the security team for incidents
escalations that cross identity, networking, and pipelines: find the root cause, fix it, and write it up so it doesn’t come back
findings from Defender for Cloud, Security Hub, GuardDuty, and Access Analyzer, turned into preventive controls rather than one-off fixes
monitoring and alerting for what you ship, so that every alert has an owner
cost tracking for your projects, with right-sizing when the numbers say so
runbooks, so someone else can operate what you built
We would rather you automate an operational task than do it twice.
Must have
5 or more years building cloud infrastructure in production. Deep experience in Azure or AWS, and solid working experience in the other.
You have built Terraform modules that other teams used. You can talk about how you versioned, tested, and released them, and what you would do differently. You are comfortable with imports, state moves, and refactors on live infrastructure.
Strong networking:…