Forward Deployed Engineer

We’re looking for a Forward Deployed Engineer who is, first and foremost, a software engineer; someone who writes code, reasons about systems, and understands how distributed applications behave in real-world environments. But you’re also the kind of person who enjoys rolling up your sleeves and helping customers succeed directly: embedding with their teams, understanding their constraints, and making complex cloud‑native systems actually work in the places they need to run.

You’ll work across cloud and on‑prem environments; including secure and classified networks; deploying, adapting, and occasionally adapting our platform to environments that don’t always behave as expected. This is not a traditional Dev Ops or IT role. You will ship code, build tooling, write automation, debug real distributed‑systems failures, and help customers adopt best practices in Kubernetes, Git Ops, networking, and infrastructure‑as‑code.

We value engineers who are curious, adaptable, empathetic, and calm under ambiguity. You’re the kind of person who can pick up a new tool in a day, learn a customer’s entire system architecture in a week, and become their most trusted technical partner in a month. You have strong opinions (and the experience to back them up) but no ego. You prefer shipping things over polishing them endlessly.

And you enjoy the blend of deep technical work, human collaboration, and the occasional “how on earth is this network even working?” puzzle.

• 5+ years professional experience as a software engineer (backend or platform‑focused).
• Proficiency in at least one modern backend language (Type Script, Java, Go, Python).
• Hands‑on experience deploying and operating Kubernetes workloads in production environments.
• Practical experience with Git Ops tooling (ArgoCD preferred; Flux acceptable).
• Experience building and maintaining infrastructure‑as‑code using Terraform, Helm, and/or Kustomize.
• Ability to troubleshoot distributed systems, including:
• container runtime issues
• API failures
• microservices communication
• misconfigured networking or CNI behavior
• Familiarity with CNI plugins such as Calico, Cilium, or Multus.
• Strong understanding of networking fundamentals (DNS, TCP/IP, firewalls, proxies, service networking).
• Experience with cloud platforms (AWS preferred; Gov Cloud is a plus but not required).
• Ability to write automation and tooling in scripting languages (Bash, Shell, Python).

• Experience working directly with customer engineering or IT/Sec Ops teams.
• Ability to gather requirements, interpret constraints, and adjust implementation plans accordingly.
• Strong verbal and written communication skills, including technical explanations for non‑experts.
• Experience performing technical troubleshooting in unfamiliar or partially‑documented environments.
• Comfortable working in secure, regulated, or on‑prem environments with limited visibility or access.

• Active DoD Secret clearance or higher (TS/SCI strongly preferred, but Secret is minimum).
• Ability to work within DoD, IC, or government security frameworks and deployment requirements.

• Highly self‑directed—able to navigate ambiguity, set your own plan of attack, and move work forward without relying on rigid processes, prescriptive task lists, or constant guidance.
• Pragmatic problem solver who prefers shipping working solutions to debating theory.
• Capable of working through ambiguity without needing fully defined requirements.
• Low‑ego collaborator who can discuss architecture tradeoffs and accept feedback.
• Comfortable balancing “ideal engineering” with “what is practical in this customer environment.”

• Experience delivering software to air‑gapped, disconnected, or highly regulated customer environments.
• Hands‑on experience with AWS EKS, IAM, VPC/networking, or Gov Cloud.
• Familiarity with DoD accreditation processes (RMF, NIST 800‑53, STIGs).
• Knowledge of service mesh (Istio, Linkerd) or eBPF‑based networking.
• Prior experience in a forward‑deployed, field engineering, or customer‑embedded role.
• Experience with monitoring/observability stacks…