2

Remote Container Ship Jobs (NOW HIRING)

Software Engineer III/Senior, Agent

San Francisco, CA ยท Remote

$144K - $190K/yr

Ship software that runs everywhere : The Agent runs on developer laptops, servers, CI systems ... Engineers develop by using remote development tools and/or ssh to connect to remote EC2 ...

Manage IAM, secrets, and container security; automate deployment pipelines via CI/CD and ... Proven ability to ship and operate production ML systems with SLOs. * Strong Python skills and ...

... and ship production services written in Python and Go. This is a product engineering role with a ... Cloud experience (AWS or GCP), containers, and orchestration (Docker, ECS/EKS/GKE) * Robust testing ...

Senior Infrastructure Engineer

New York, NY ยท On-site +1

$200K - $260K/yr

... remote and have an office in New York City. First 30 days: Learn the infrastructure, ship ... CI/CD: GitHub Actions, container registries, automated testing and deployment pipelines * Data:

Senior Platform Engineer

Los Altos, CA ยท On-site +1

$123K - $169K/yr

We offer a flexible, remote working environment. You can expect a warm welcome from a friendly and ... Own and evolve the infrastructure layer - CI/CD pipelines, container orchestration, deployment ...

Senior Platform Engineer

Los Altos, CA ยท On-site +1

$123K - $169K/yr

We offer a flexible, remote working environment. You can expect a warm welcome from a friendly and ... Own and evolve the infrastructure layer - CI/CD pipelines, container orchestration, deployment ...

Seattle, WA - Remote Openings: 1 Type: Full Time Hire The Client is searching for an experienced ... Work with modern CI/CD tool and methodologies to ship product on a daily basis. * Work in an agile ...

Senior Platform Engineer

Los Altos, CA ยท Remote

$107K - $146K/yr

We offer a flexible, remote working environment. You can expect a warm welcome from a friendly and ... Own and evolve the infrastructure layer -- CI/CD pipelines, container orchestration, deployment ...

We ship in months, not years, and the people using what we build are operators, analysts, and ... Flat structure, real autonomy, direct access to leadership. * We're remote-first. Work from where ...

DevOps Engineer

$54 - $74/hr

Job Title: DevOps Engineer Position Type: Full-Time, Remote Working Hours: U.S. Client Business ... This role requires deep expertise in cloud platforms, automation, CI/CD, container orchestration ...

... for hosted and remote managed customers. * Contribute to customer success through a close ... Experience with containers, container-based applications, and/or container orchestration tools.

We ship in months, not years, and the people using what we build are operators, analysts, and ... Flat structure, real autonomy, direct access to leadership. * We're remote-first. Work from where ...

Senior Platform engineer

OR ยท Remote

$104K - $143K/yr

Herndon, VA (Remote) Type: Full-time Who You Are We're looking for a Platform Engineer to help ... to ship software reliably at scale. This is a role for someone who is equally comfortable diving ...

New

Ship product SRE work directly in the product codebase: load balancing, load shedding, instrumentation, scalability, efficiency * Build and extend common tooling so product teams can self-service ...

Senior Platform Engineer

Saint Petersburg, FL ยท Remote

$98K - $135K/yr

... ship, document, and bring others along. Bonus points for experience with * Container platform ... Remote-first: work from wherever you do your best work * Small team, big impact: your work directly ...

... remote. For location-specific details, please connect with our recruiting team. What you will do ... Ship polished, user -facing experiences across multiple surfaces (Slack, dashboard, CLI) without ...

next page

Showing results 1-20

Remote Container Ship information

What are the key skills and qualifications needed to thrive as a Remote Container Ship Operator, and why are they important?

To thrive as a Remote Container Ship Operator, you need expertise in maritime operations, navigation, and logistics, typically supported by relevant maritime certifications and experience. Familiarity with remote vessel control systems, maritime communication technologies, and fleet management software is essential. Strong problem-solving skills, attention to detail, and effective communication are crucial soft skills for this role. These abilities ensure safe, efficient, and compliant remote vessel operations in a highly technical and dynamic environment.

What is the difference between Remote Container Ship vs Remote Cargo Coordinator?

AspectRemote Container ShipRemote Cargo Coordinator
Required CredentialsMaritime certifications, shipping licensesLogistics certifications, supply chain training
Work EnvironmentShipboard, port operations, remote planningOffice, home-based, logistics centers
Industry UsageShipping, maritime transportFreight, logistics, supply chain management
Common Search/ComparisonYesYes

The Remote Container Ship primarily involves maritime operations, navigation, and ship management, often requiring maritime certifications. In contrast, the Remote Cargo Coordinator focuses on coordinating shipments, managing logistics, and ensuring cargo delivery efficiency, typically needing logistics or supply chain credentials. Both roles are integral to the shipping industry but differ in work environment and specific responsibilities.

What are some common challenges faced by crew members working on a remote container ship, and how are they typically addressed?

Crew members on remote container ships often face challenges such as extended periods away from home, adapting to confined living quarters, and managing communication with family and shore-based teams. These challenges are typically addressed through robust onboard support systems, scheduled shore leave, and access to reliable internet for staying connected. Additionally, regular drills, safety trainings, and strong camaraderie among the crew help to maintain morale and ensure a safe, effective working environment.

What is a Remote Container Ship?

A Remote Container Ship is a type of cargo vessel designed to be operated with minimal or no onboard crew, instead being monitored and controlled remotely using advanced automation, sensors, and communication technologies. These ships are part of the growing trend toward autonomous shipping, aiming to improve efficiency, safety, and reduce operational costs. Remote container ships use sophisticated navigation systems and are often overseen by operators from shore-based control centers. This innovation is transforming maritime logistics and is expected to play a significant role in the future of global trade.
More about Remote Container Ship jobs
What cities are hiring for Remote Container Ship jobs? Cities with the most Remote Container Ship job openings:
What are the most commonly searched types of Container Ship jobs? The most popular types of Container Ship jobs are:
What states have the most Remote Container Ship jobs? States with the most job openings for Remote Container Ship jobs include:
Infographic showing various Remote Container Ship job openings in the United States as of May 2026, with employment types broken down into 1% Locum Tenens, 95% Full Time, 2% Part Time, 1% Temporary, and 1% Contract. Highlights an 90% Physical, 4% Hybrid, and 6% Remote job distribution.
Software Engineer III/Senior, Agent

Software Engineer III/Senior, Agent

ngrok

San Francisco, CA โ€ข Remote

$144K - $190K/yr

Full-time

This job post hasย expired 1 day ago.ย Applications are no longer accepted.


Job description

Software Engineer III/Senior, Agent

United States

About Ngrok Inc.

Ngrok is an all-in-one cloud networking platform that secures, transforms, and routes traffic to services running anywhere. Instead of cobbling together nginx, NLBs, VPNs, model routers, and oodles of other tools, developers solve every networking problem with one gateway. Doesn't matter if they're sharing localhost or running AI workloads in production.

We're trusted by more than 9 million developers at companies like GitHub, Okta, HashiCorp, and Twilio. What started as a way to put your local app on a public URL has grown into a universal gateway for API delivery, AI inference, device fleets, and site-to-site connectivity. It's the same ngrok that millions of developers have loved and leaned on every day for years, now with the power to run production traffic at scale.

A few things you should know:

  • We are obsessed with our pets, Viper sunglasses and Bufo (yes, the toad)
  • We have a designated Chief Emoji Officer - they are vital to our success!
  • We like software that's serious and culture that's not

Still reading? Good. There's more below worth your time.

About the Agent Team

Our Agent team builds the software that sits at the edge of every ngrok connection. The Agent is what developers install, run, embed, and trust to expose their systems securely to the internet.

It's the first thing customers touch and the last thing we want to debug at 3am.

The Agent must be fast, correct, and predictable under hostile conditions: flaky networks, broken configs, expired certs, overloaded laptops, CI environments held together by duct tape, and production traffic that does not care about your feelings.

When it works, nobody thinks about it.

When it doesn't, it's immediately obvious โ€” and very public.

What You'll Actually Do

  • Build and evolve the ngrok Agent itself : You'll work on the core agent that handles connection management, tunneling, authentication, and secure traffic forwarding. This is a high-performance networking system that must behave correctly across a wide range of environments and failure modes.
  • Own reliability at the edge : You'll design for latency, throughput, and correctness under real-world chaosโ€”network partitions, transient failures, misconfiguration, and resource-constrained machines. When something goes wrong, the Agent should fail clearly, safely, and explainably.
  • Develop SDKs and embeddable integrations : You'll build and maintain SDKs and embedded agent components that other systems and products depend on. These need to be easy to integrate, hard to misuse, and stable over time.
  • Make the system observable : You'll improve diagnostics, logging, and metrics so we can understand what the Agent is doing in the wild. When customers ask "what happened?", you'll help make sure we can answer with facts instead of guesses.
  • Ship software that runs everywhere : The Agent runs on developer laptops, servers, CI systems, containers, and occasionally very questionable hardware. You'll ensure it behaves consistently across platforms and environments.
  • Work with people who care about correctness : You'll collaborate closely with product, platform, and support teams. When something breaks, you'll help explain why. When something is confusing, you'll help make it boring.

You Might Be a Great Fit If...

  • You've built systems-level software that had to work under pressure
  • You're comfortable in Go, Rust, C/C++, or Java (bonus points for Go)
  • You enjoy debugging things that "shouldn't be possible"
  • You think deeply about reliability, security, and performance
  • You can reason about tradeoffs and explain them like a normal human
  • You care about developer experience โ€” not just correctness

Extra credit if you've worked on:

  • Networking, proxies, or agents
  • SDKs or embeddable runtimes
  • Observability tooling
  • Open-source systems people actually use

Tech Stack

Ngrok runs entirely on AWS. Engineers develop by using remote development tools and/or ssh to connect to remote EC2 environments that run a full Kubernetes cluster of the ngrok stack, closely mirroring production. The codebase is primarily Go and TypeScript. We use Postgres for persistence, Kafka for streaming, Protobuf for service boundaries, and Kubernetes, Terraform, Helm, and Buildkite to operate and ship reliably. React is used for user interfaces, and GitHub supports our development workflows and remembers everything.

Location

This is a remote position for candidates outside of the Bay Area and a hybrid role for candidates within commuting distance to San Francisco. Our Bay Area employees commute to the office on Tuesdays and Wednesdays.

Sponsorship

All candidates must be US-based, and legally authorized to work in the United States.

At this time, ngrok is unable to provide visa sponsorship for this position. Applicants must be authorized to work in the United States on a permanent, ongoing basis without the need for current or future sponsorship.

Compensation

About the Admin Team

Our Admin Engineering team builds the systems that decide who can access ngrok, what they can do, and how everything is configured.

We own identity, access control, and configuration at scaleโ€”users, certificates, service accounts, domains, policies. If it answers "who can do what?", it's our problem. When things work, nobody notices. When they don't, people get locked out or something gets exposed that really shouldn't be.

A lot of this work lives in the tension between power and safety. Customers want full control and APIs for everything. They also want guardrails and sane defaults. You'll build systems that manage bothโ€”without making either side miserable.

What You'll Actually Do

Build the control plane

Design and operate the services and APIs behind admin workflowsโ€”the layer that defines how ngrok behaves in production.

Own identity and access

Develop and evolve IAM/RBAC systems across users, certificates, and service accounts. If something can authenticate or authorize, you'll touch it.

Make configuration scale

Build global configuration systems for domains, policies, and traffic behaviorโ€”flexible enough for automation, safe enough for humans.

Make debugging possible

Improve observability across admin workflows so we can answer "what changed?" without guessing or digging through logs for an hour.

Ship systems people rely on

Work with product and platform teams to deliver features that are stable, understandable, and actually usable in production.

Keep things from breaking (or worse)

Ensure admin systems stay scalable, reliable, and hard to misuseโ€”because mistakes here tend to be very visible.

You Might Be a Great Fit If...

  • You've built backend systems that needed to be correct and hard to misuse
  • You're comfortable in Go, Rust, Java, or C/C++
  • You understand APIs, distributed systems, and why auth is never "just add auth"
  • You take ownership, especially when things get weird

Extra credit if you've worked on:

  • Admin platforms, IAM, or enterprise SaaS
  • Certificates, identity systems, or observability
  • Systems where flexibility vs. safety is a constant fight

Tech Stack

Ngrok runs entirely on AWS. Engineers develop by using remote development tools and/or ssh to connect to remote EC2 environments that run a full Kubernetes cluster of the ngrok stack, closely mirroring production. The codebase