Cloud Platform Engineer (Azure)

About the opportunity

Our client, an investment firm in Manhattan, is hiring (2) hands-on Azure engineers to help build out its cloud platform. This is building work, not maintenance. The team is early in its Azure journey and is moving from portal-driven changes to everything in code. You would help shape how that is done.

• Small team, real impact. You would own meaningful workstreams and take work directly off the architect's plate, not sit in a large ticket queue.
• The team is building the Azure foundation for new internal AI initiatives and getting small business-built applications into production.
• The role is contract-to-hire.

There are two openings with different focus areas, described below. We don't expect anyone to be an expert in everything. We are looking for strong engineers who work independently and can figure out problems they haven't seen before.

These are hands-on engineering roles, not people-management roles.

Role 1: DevOps & Platform Engineer

You will build the delivery platform: infrastructure as code, GitHub, Kubernetes, and the path that gets applications into production.

What you'll do

• Write and maintain Terraform for Azure infrastructure, including modules, state management, and imports of existing resources.
• Build GitHub Actions pipelines that take code from pull request to production, with testing, approvals, and secure deployment identities.
• Set up and administer GitHub Enterprise: organization settings, policies, rulesets, repository templates, and self-hosted runners.
• Build and operate AKS clusters, including node pools, networking, ingress, workload identity, upgrades, and troubleshooting.
• Onboard small internal applications into production, choosing the right hosting and putting secrets, monitoring, and support in place.
• Help migrate existing Bicep templates to Terraform.

Required

• Hands-on Azure experience: subscriptions, resource groups, landing zones, and building resources yourself.
• Terraform you have personally written and run in production.
• GitHub Actions pipelines you have built or substantially improved.
• Real GitHub Enterprise administration experience.
• AKS or Kubernetes clusters you have built and operated yourself, not only deployed into.
• Experience getting applications into production, including hosting, secrets, and monitoring.
• Working knowledge of Azure access: roles, permissions, and managed identities.

Preferred

• Bicep-to-Terraform migration experience.
• Azure networking: VNets, private endpoints, DNS.
• Scripting in PowerShell, Python, or Bash.
• Financial services or consulting background.

Role 2: Azure Infrastructure Engineer

You will build the Azure foundation: subscriptions, landing zone, networking, and the infrastructure code that defines them.

What you'll do

• Design and build Azure foundations, including subscriptions, management groups, Azure Policy, and landing zones.
• Build and maintain Azure networking: hub-and-spoke or Virtual WAN, firewalls, DNS, private endpoints, VPN, and ExpressRoute.
• Write and maintain Terraform for the environment.
• Support and extend Azure Virtual Desktop environments.
• Troubleshoot connectivity, name resolution, and access issues in production.

Required

• Hands-on Azure experience: subscriptions, resource groups, landing zones, and building resources yourself.
• Azure networking you have built and supported in production.
• Terraform you have personally written and run in production.
• Working knowledge of Azure access: roles, permissions, and managed identities.

Preferred

• Azure Virtual Desktop experience, on top of broad Azure infrastructure skills.
• GitHub Actions or GitHub Enterprise experience.
• AKS or Kubernetes exposure, or willingness to learn it.
• Bicep-to-Terraform migration experience.
• Scripting in PowerShell, Python, or Bash.
• Financial services or consulting background.

Who thrives here

Both roles need engineers who have personally built what they describe and can work without hand-holding. We care more about what you have built than how many years you have.

• You are comfortable joining an established team and delivering within its controls in your first month.
• You build with security, permissions, and change control in mind.
• You leave behind work others can run: clear code, runbooks, and monitoring.

If you are strong in one role's core skills but not every listed item, that's ok. Most candidates will fit one role clearly rather than both. Please specify which fit is better.