2

Remote Platform Engineer Jobs in New York (NOW HIRING)

Platform engineers are software engineers who apply sound engineering principles, operational ... Collaborating across the global remote teams, often working asynchronously * Document everything so ...

Staff Platform Security Engineer

New York, NY · On-site +1

$168K - $240K/yr

Staff Platform Security Engineer The Platform Security team builds and delivers zero-trust ... Deep Terraform expertise including module development, CI/CD gates, policy testing, remote state ...

Senior Platform Security Engineer

New York, NY · On-site +1

$140K - $200K/yr

The Role: Senior Platform Security Engineer The Platform Security team secures Gemini ... Employees who do not live near one of our hubs are part of our remote workforce. All employees ...

We're a remote-first (with a NYC base) Series A startup of 20+ employees that believe in the power ... We're an engineer-led team that obsesses over the reliability and availability of our service, and ...

This role owns that expansion as the sole DRI for the Next Gen VDI platform: the remote-compute infrastructure powering hundreds of engineers, network operators, and support teams company-wide. You ...

Showing results 21-40

Remote Platform Engineer information

What are the key skills and qualifications needed to thrive as a remote platform engineer?

To thrive as a Remote Platform Engineer, you need strong expertise in software development, cloud infrastructure, automation, and a relevant degree or equivalent experience. Familiarity with tools such as AWS, Docker, Kubernetes, CI/CD pipelines, and infrastructure-as-code platforms like Terraform is typically required. Excellent problem-solving, self-motivation, and collaboration skills set standout candidates apart, especially in distributed teams. These skills ensure the reliability, scalability, and efficiency of platforms while enabling smooth teamwork in a remote work environment.

What is a remote platform engineer?

A Remote Platform Engineer is a technology professional who designs, builds, and maintains the foundational systems (platforms) that support software applications, all while working from a remote location. Their responsibilities often include developing cloud infrastructure, automating deployment processes, and ensuring system reliability and scalability. They collaborate with other engineers and teams via digital tools, leveraging their expertise in areas like DevOps, cloud computing, and system architecture. This role requires strong technical skills, problem-solving abilities, and effective communication for remote teamwork.

How does a remote platform engineer typically collaborate with cross-functional teams?

As a Remote Platform Engineer, you’ll frequently work with developers, DevOps, security, and product teams to ensure the platform’s stability, scalability, and security. Collaboration is often managed through daily stand-ups, code reviews, and project management tools like Jira or Trello. Clear communication and documentation are crucial, as most interactions happen via video calls, chat, and version control platforms. Successful remote platform engineers proactively seek feedback, clarify requirements, and keep stakeholders updated on progress.

What is the difference between Remote Platform Engineer vs Remote DevOps Engineer?

AspectRemote Platform EngineerRemote DevOps Engineer
CredentialsBachelor's in CS or related, certifications like AWS, AzureBachelor's in CS or related, certifications like AWS, Azure, Docker
Work EnvironmentDeveloping and maintaining platform infrastructure, cloud servicesAutomating deployment, CI/CD pipelines, infrastructure management
Industry UsageTech, SaaS, cloud providersTech, software development, cloud services

Both roles often require similar technical skills and certifications, focusing on cloud and infrastructure. The Remote Platform Engineer primarily builds and maintains platform infrastructure, while the Remote DevOps Engineer emphasizes automation, deployment pipelines, and continuous integration. They often collaborate but serve distinct functions within tech organizations.

What are the most commonly searched types of Platform Engineer jobs in New York? The most popular types of Platform Engineer jobs in New York are:
What job categories do people searching Remote Platform Engineer jobs in New York look for? The top searched job categories for Remote Platform Engineer jobs in New York are:
What cities in New York are hiring for Remote Platform Engineer jobs? Cities in New York with the most Remote Platform Engineer job openings:
Infographic showing various Remote Platform Engineer job openings in New York as of August 2026, with employment types broken down into 56% Full Time, 40% Part Time, 1% Temporary, and 3% Contract. Highlights an 77% Physical, 3% Hybrid, and 20% Remote job distribution.

Senior Azure Platform / DevOps Engineer

Makai Labs LLC

New York, NY • On-site, Remote

$142K - $182K/yr

Full-time

Re-posted 5 days ago


Job description

Senior Azure Platform / DevOps Engineer
About Makai
Makai uses best-in-class AI and data to solve real-world operational and strategic challenges at scale. We help businesses with enterprise automation, human-machine teaming, product design and development, and market intelligence. Until now, people have had to learn and adapt to software. Makai creates solutions that adapt to people because technology will never be 100% accurate. People are essential for all of our human-machine teaming solutions.
About the role
We build and run cloud platforms for our clients. A lot of the time that means standing up a reusable Terraform foundation and adapting it for each client and environment. You'd own these platforms: design them, build them from an empty subscription, keep them running, and act as the person who actually knows how the whole thing fits together.
This is a senior role with a lot of trust attached. The clients differ, the topologies differ, the pipelines differ. What stays constant is Azure and the expectation that you can size up an unfamiliar setup, make the right calls, and own the result.
The ideal candidate will be able to
  • Stand up new platforms from scratch: network, compute, data, and the pipeline to ship to them.
  • Make the architecture calls and live with them. That includes knowing when a Terraform change is a safe in-place update and when it's a destroy-and-replace you should never run blind against production.
  • Run migrations that carry real risk. Move a live platform onto a new foundation, read the plan correctly, write the runbook, and have a rollback ready before you start.
  • Keep platforms healthy over time: provider upgrades, drift, security, and not letting a shared foundation rot as more clients land on it.
  • Work directly with the client's own DevOps engineers. Often they're the ones running the apply and you're advising, so you need to explain a plan, unblock a failure quickly, and be someone the engineer holding the keys trusts.
Qualifications
Azure experience is the hard requirement. You've built and run production Azure yourself, not just used modules someone else wrote. Specifically:
  • Azure networking is where most of the work lives: VNets and subnets, private endpoints and private DNS zones, NSGs and UDRs, NAT, Application Gateway and WAF, load balancers, and hub-and-spoke / Virtual WAN.
  • Terraform on Azure, with state treated as something you respect: workspaces, migrations, imports, remote backends, and the discipline not to force an apply through a lifecycle guard.
  • The delivery path: Azure Container Registry, VM Scale Sets and cloud-init, and CI/CD with Azure DevOps or GitHub.
  • Azure data services: Postgres Flexible Server, managed Redis, Blob storage, and a real sense of their sizing, failover, and cutover risks.
  • Entra ID and RBAC: app registrations, service principals, role assignments scoped properly across subscriptions.
  • Clear writing and a level head on a live call. You can hand someone a runbook they can follow without you in the room.
Nice-to-haves
  • Azure certs (AZ-104, AZ-305).
  • Temporal or similar workflow runtimes, and scripting (Bash, Python) for the glue.
  • Past consulting or client-embedded work. You've been the outside expert before.
How we work
Small senior teams, real ownership. We'd rather have one engineer who understands a platform top to bottom than several who each own a slice.
Core values for Makai employees
  • Be a flexible, innovative and creative thinker
  • Be congenial and a team player
  • Be self-sufficient
  • Be self-driven with an ownership mentality
  • Have a strong work ethic