DontApply.Club
Login Register

Senior Full-Stack Engineer - Agent Runtime & Platform

Ninjatech Ai — Australia · Posted ~3 hours ago

Senior Full-time Hybrid

Skills

Backend engineering Platform engineering AWS Container orchestration Distributed systems Infrastructure Observability Production systems AWS CDK Containers

🔓 Log in to save this job, tailor your resume & track your apply process — 7 days free, no card needed.

Log in to add to target list

Summary ✨ AI‑Generated

A senior full-stack/platform engineering role owning the runtime and infrastructure layer behind an AI-agent platform. You will build sandboxed execution environments, platform services for identity, secrets, storage and workflows, and an end-to-end observability stack while hardening systems for reliability and scale.

Highlights

High-ownership platform role focused on large-scale infrastructure, runtime reliability, observability, security, and performance, with broad technical scope across core platform services.

Description

Sydney Full-time On-site/hybrid Every agent task runs somewhere: a sandboxed container with a filesystem, a browser, tools and a time limit. This role owns that runtime and the platform services around it — the layer everything else in the product depends on. What You'll Do Own the agent sandbox runtime: provisioning, isolation, scheduling, lifecycle and cost per task at scale. Build and own platform services — identity plumbing, secrets, metering, object storage, workflow orchestration, and the tool/connector abstraction layer. Drive the observability stack from instrumentation through ingestion to the dashboard people actually open during an incident. Harden infrastructure against the failure modes that surface to users as “the agent got stuck”, and keep the platform from becoming a bottleneck to growth. What We're Looking For 5+ years building and operating production backend systems and platforms. Deep AWS (we are CDK-first) and container orchestration understanding below the level of configuration — schedulers, runtimes and isolation boundaries. Python strength, plus enough front end to build the internal tooling your platform needs rather than waiting for someone else. A bias for simplicity and pragmatism over architecture for its own sake.