> Markdown version of [/jobs/ext/2791829-senior-ai-engineer](https://www.wearedevelopers.com/jobs/ext/2791829-senior-ai-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior AI Engineer - **Company:** MAULT INC - **Location:** United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Java (Programming Language), JavaScript (Programming Language), Microsoft Windows, Application Programming Interfaces (APIs), Artificial Intelligence, Apple Mac Systems, Audit Trail, Microsoft Azure, Static Program Analysis, Continuous Integration, Linux, Programming Tools, File Systems, Github, Python (Programming Language), Node.Js, Role-Based Access Control, TypeScript, Management of Software Versions, SSL Certificate Management, GitHub Copilot, ReactJS, Git, U-Boot, Api Design - **Published:** September 8, 2026 - **Apply:** https://arc.dev/remote-jobs/j/redirect/pigm2i3ddd ## About the Role * Security engineering fundamentals. Least privilege, access control, audit logging, cryptographic hashing and signing. * Cross-platform work on macOS, Windows, and Linux, including the differences that matter * Enterprise deployment reality. MDM, endpoint detection coexistence, and installs into environments with no internet. Languages and frameworks * Strong in TypeScript and JavaScript, including Node * Strong in Java * Solid Python * React, and comfort in the front end when the work calls for it * Able to pick up a language you have not shipped in and reason about it well enough to govern it Seniority and track record * Ten or more years building production software, with several of those years at a senior, staff, principal, or founding engineer level * Extensive experience building harnesses, scaffolding, or control layers around coding agents. Not using agents. Building the thing that constrains them. * You know from practice where agents are strong and where they fail, and you can say specifically which failure modes you have had to design around * You build end to end yourself. Architecture through delivery through what happens when it breaks at 2am. There is nobody to hand the hard part to. * Zero to one. You have taken something from nothing to shipped and in customers hands. * You have set technical direction others followed, and you can defend a decision without needing a title behind it. * You write specifications before you write code, and you can hand your work to someone else Pace and environment * You are fast. Not careless, but you ship in days rather than quarters and you do not need a long ramp before you are useful. * You have worked at seed stage or earlier, or you know exactly what you are walking into. Small team, no scaffolding around you, priorities that move, and you own the outcome. * You are comfortable deciding without complete information and correcting later Preferred * Kernel-level or OS-level programming * Endpoint security frameworks on macOS or Windows * Code signing, certificate management, and driver distribution * Hardware-backed attestation and secure boot * Compiler, language server, or developer tooling work * Compliance frameworks such as SOC 2, ISO 27001, or FedRAMP * Working alongside patent counsel on technical documentation, Remote, with real autonomy. We care what ships, not what hours you keep.d written communication skills ## Description This is a senior hire, and the most senior engineer we will bring on. You will own the SDK and take it to market, working directly with leadership and without anyone above you on the technical side. We are not looking for someone who needs a spec handed to them. In the first ninety days: * Own the SDK architecture and ship the first release * Get the enforcement layer running cleanly across multiple coding agents at enterprise scale * Stand up the deployment path for Azure and GitHub environments, including Azure DevOps and GitHub Actions * Get enterprise pilots off the ground, fitting the deployment to each client's stack, languages, and pipeline Required Systems and enforcement * Built or operated guardrails, policy engines, or enforcement systems in production. Systems that block, not systems that warn. * Deterministic systems design. You know why nondeterminism is a defect here and you build for idempotency and repeatability by default. * Process and file system interception. Hooks, plugin architectures, extension points, and the failure modes of each. * Performance discipline in a hot path. Enforcement runs on every write and cannot be the reason a developer's editor feels slow. Coding agents * Production experience with Claude Code, GitHub Copilot, and Codex. You should know their hook and extension surfaces well enough to argue about them. * Understanding of how agentic tools actually read a codebase, make tool calls, and mutate state. SDK and API design * Shipped an SDK or public API that outside teams built against * Versioning, backwards compatibility, deprecation, and the discipline of not breaking your consumers * Documentation and developer experience treated as part of the product, not an afterthought Platform and pipeline * Azure and Azure DevOps * GitHub at enterprise scale, including Actions, org administration, branch protection, and merge policy * Git internals. Hooks, refs, merge and rebase mechanics, and what actually happens at the merge gate. * CI/CD pipeline engineering end to end Code analysis * Static analysis and AST-level parsing across more than one language * Dependency and import graph analysis * Comfortable adding support for a new language without a rewrite ## Related Videos - [Docker network without Docker](https://www.wearedevelopers.com/videos/1418-docker-network-without-docker) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [Craftsmanship in the Age of Agents](https://www.wearedevelopers.com/videos/100106-craftsmanship-in-the-age-of-agents) - [Docker exec without Docker](https://www.wearedevelopers.com/videos/1094-docker-exec-without-docker) - [Git for Code Reviews](https://www.wearedevelopers.com/videos/429-git-for-code-reviews) - [The AI-Native Engineering Org: What’s Real, What’s Hype, What’s Next](https://www.wearedevelopers.com/videos/100004-the-ai-native-engineering-org-what-s-real-what-s-hype-what-s-next) ## Related Articles - [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this)