> Markdown version of [/jobs/ext/4669951-software-engineer-runtime-infrastructure](https://www.wearedevelopers.com/jobs/ext/4669951-software-engineer-runtime-infrastructure). 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). --- # Software Engineer, Runtime Infrastructure - **Company:** Nominal Inc - **Location:** Austin, TX, United States - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Audit Trail, Code Generation, Profiling, Computer Engineering, Software Debugging, Distributed Systems, Fault Tolerance, Load Testing, Prometheus, Software Engineering, Test Data, TypeScript, Web Applications, Datadog, ReactJS, Grafana, Caching, Backend, Rate Limiting, Data Management, Front End Software Development, Api Design, Software Coding, Dynatrace - **Published:** November 11, 2026 - **Apply:** https://www.careerbuilder.com/job-details/software-engineer-runtime-infrastructure-austin-tx--aec0777d-e279-4eaa-b700-79ef2cb37d3e ## About the Role Software Engineering, Robotics, Computer Engineering, Testing, Artificial Intelligence (AI), Software Engineering, System Operations, Manufacturing, United States Air Force (USAF), Aerospace and Defense, * 3+ years of experience as a backend or full stack engineer, building and running production systems where performance, reliability, and operational simplicity matter. * Strong experience in at least one of Rust, Java, or TypeScript, with an emphasis on correctness, clarity, and long-lived systems. You dont need all three, but you should be excited to work across them. * Experience designing libraries, frameworks, or APIs that other engineers build on: hiding complexity behind simple interfaces, sensible defaults, and changing things without breaking the people who depend on you. * Hands-on experience with observability tools such as OpenTelemetry, Prometheus, or Datadog, including metrics, traces, and alerts that engineers actually rely on. * A solid understanding of concurrency, async runtimes, networking, and how distributed systems behave under load and failure. * A systems mindset. You like working out how a system should behave, and how it will fail, before you build it. * Excellent communication skills, and the ability to explain technical tradeoffs clearly to the engineers who depend on your work. * A bias toward ownership: you design it, build it, ship it, and run it. Skills that supercharge us Security & Compliance Experience building audit logging, access controls, data-handling safeguards, or other systems that help a company meet security and compliance requirements. API Design Experience with schema-driven APIs and RPC frameworks, code generation, and keeping APIs compatible as many teams build on them. Distributed Tracing Experience instrumenting services and following a request across process, network, and browser boundaries. Performance Engineering Experience profiling CPU and memory, load testing, and turning measurements into concrete improvements. Resilience Patterns Experience with backpressure, bulkheads, rate limiting, retries, and graceful degradation in production systems. Developer Experience A track record of building tools, libraries, or platforms that made other engineers more productive. Async Rust Experience with Tokio or similar, and a feel for what the runtime is doing under the hood. Frontend Architecture Experience designing how large TypeScript/React applications are structured: data fetching, caching, state management, and the API boundaries they depend on. ## Description Nominal runs mission-critical software wherever our customers need it: in our cloud, in theirs, and on disconnected networks for defense programs. An engineer might be watching a vehicle in real time or working through terabytes of post-test data. Either way, every layer between the hardware and the chart on their screen has to be fast and correct. Our customers expect a lot from us on reliability, security, and compliance. Runtime Infrastructure builds the libraries, services, and standards that let every Nominal team meet that bar by default. As a Software Engineer on Runtime Infrastructure, youll build the foundation the rest of engineering builds on. That covers how our services and applications are observed, how they record who did what, how they talk to each other, and how they behave under load and failure. Your main users are other Nominal engineers. If you do this well, they ship faster, catch problems sooner, and meet our customers standards without having to think about it. Through them, your work reaches the aerospace, defense, and autonomy teams who use Nominal for mission-critical testing. Were hiring both backend and full stack engineers for this team. Youll build services, libraries, and APIs that have to be correct, fast, and long-lived. Youll care about architecture across the whole stack: how our web applications are structured, how they talk to the backend, and how they behave in production. Youll have a lot of autonomy and work closely with product, frontend, platform, and deployment engineers. Youll help shape the requirements yourself, with input from fellow engineers and our customers, and make the tradeoffs that decide how our systems are built. Youll also be able to contribute to the open source projects we depend on. About the role Build the foundation other engineers stand on Build the service frameworks and shared libraries that every Nominal service starts from: configuration, health checks, graceful shutdown, resource limits, resilience, secure defaults, and the conventions for how services define their APIs and talk to each other. The goal is that a new service is reliable, observable, and compliant from its first commit. Youll measure success by how quickly other engineers can ship, debug, and operate their own services. Find where the time and memory go Investigate concurrency, memory, and latency problems across our services. Youll build runtime metrics, profiling, and load testing, then turn what you find into fixes, and into tools other engineers can use on their own. Success in this role comes from treating other engineers as your customers. Youll spend as much time understanding how teams build, run, and debug software as you will writing code.