Nod CareersAuto-apply free

Full-Stack Platform Engineer

openteams · United States - Hybrid · Austin, Texas, United States
Auto-apply to this job with Nod →
<div class="content-intro"><h3><strong>Who We Are</strong></h3> <p>Every organization runs on intelligence: years of accumulated knowledge, decisions, and context. As AI takes on more of that work, companies face a choice: rent that intelligence from vendors who keep the data, the context, and the results, or own it.<br><br>OpenTeams exists to make ownership possible.<br><br>Founded by Travis Oliphant, creator of NumPy and SciPy, and built by people with deep roots across the open-source ecosystem, including NumPy, SciPy, PyTorch, and Jupyter, we help enterprises and governments build AI they control, govern, and evolve themselves.<br><br>If that sounds like your kind of work, we'd like to meet you.</p></div><h3><strong>Full-Stack Platform Engineer</strong></h3> <p><strong>Location:</strong> U.S Hybrid - Washington, DC, Denver, CO or Colorado Springs, CO. </p> <p><strong>Work Authorization:</strong> U.S. citizenship required</p> <p><strong>Clearance Requirement:</strong> An active TS/SCI clearance is preferred. Candidates may also be considered if they previously held a TS/SCI with CI polygraph or currently hold an active TS or Secret clearance.  Candidates that are not eligible or willing to obtain a security clearance will not be considered.</p> <p><strong>Salary Range:</strong> $145,000–$250,000 USD, dependent on experience level and location</p> <p><strong>Travel Requirement:</strong> Up to 15% travel is required.</p> <h3><strong>About the Role</strong></h3> <p>We're looking for a <strong>Full-Stack Platform Engineer</strong> to build both sides of an AI platform — the API surface other teams build on, and the interfaces analysts use directly.</p> <p>The API comes first here, and that's a real constraint rather than a slogan: platform capabilities are consumed through documented interfaces by analysts, internal teams, and partner organizations using their own tools. If those interfaces are unstable or hard to reason about, adoption stalls regardless of what the platform can do underneath.</p> <p>On the backend, you build API-first services for workflow orchestration, data ingestion, evaluation execution, and results management, and you implement identity federation and access controls that hold up across deployment environments. On the frontend, you build the analyst-facing tooling — modern web consoles and utilities where someone actually kicks off a workflow, inspects a result, or figures out why a run failed. You should be comfortable in a component-based web stack, though the emphasis is on clear, functional interfaces over visual polish. Doing both sides means you feel your own API design decisions from the consuming side, which is the fastest way to find the ones that were wrong.</p> <p>You also produce what external teams need to build on the platform: documentation, reference implementations, and client examples that work when someone follows them.</p> <h3><strong>Key Responsibilities</strong></h3> <ul> <li>Design, implement, document, and maintain APIs for workflow orchestration, data ingestion, evaluation execution, and results management</li> <li>Define clear, stable, and versioned interface specifications for use by external integrators</li> <li>Implement brokered single sign-on and identity federation using protocols such as OpenID Connect, SAML, and PKI/X.509 certificate-based authentication</li> <li>Enforce approved authentication, authorization, and access-control requirements across platform services</li> <li>Design relational data models that support platform APIs and workflow requirements</li> <li>Build the analyst-facing web interfaces for the platform — consoles for launching workflows, inspecting results, and diagnosing failed runs</li> <li>Develop UI for AI-specific interaction patterns: streaming model output, long-running and multi-step agentic runs, prompt and configuration management, and side-by-side comparison of model or workflow results</li> <li>Ensure analyst-facing interfaces are built strictly on the same public APIs external integrators use, keeping the platform genuinely headless rather than headless in name</li> <li>Produce and maintain API documentation, integration guides, SDK examples, reference implementations, and example workflows</li> <li>Develop notebooks and other enablement resources for data science and analyst audiences</li> <li>Support partner organizations and Government teams integrating with published platform interfaces</li> <li>Write automated tests and maintain CI pipelines across backend and frontend code</li> <li>Ensure application dependencies are compatible with target deployment environments</li> <li>Collaborate with platform, security, infrastructure, and ML engineers to deliver reliable, secure, and interoperable platform services</li> </ul> <h3><strong>Required Skills & Experience</strong></h3> <ul> <li>U.S. citizenship and eligibility to obtain and maintain a U.S. security clearance</li> <li>5+ years of full-stack or backend engineering experience, with an emphasis on API-first services</li> <li>Proficiency in Python, TypeScript, Go, or a comparable programming language</li> <li>Experience designing, documenting, versioning, and maintaining REST or GraphQL APIs used by external teams or integrators</li> <li>Working proficiency with a modern component-based frontend framework such as React, Vue, or Svelte, and the abil

Let Nod apply for you →

More jobs at openteams

Solutions Architect — openteamsSenior AI/ML Test and Evaluation Engineer — openteamsOpenTeams - General Application — openteamsPlatform Engineer, AI/ML Infrastructure — openteamsTechnical Project Manager - Project Success — openteams