Platform Engineer (Agent Release)

About Netskope Today, there's more data and users outside the enterprise than inside, causing the network perimeter as we know it to dissolve. We realized a new perimeter was needed, one that is built in the cloud and follows and protects data wherever it goes, so we started Netskope to redefine Cloud, Network and Data Security.

Since 2012, we have built the market-leading cloud security company and an award-winning culture powered by hundreds of employees spread across offices in Santa Clara, St. Louis, Bangalore, London, Paris, Melbourne, Taipei, and Tokyo. Our core values are openness, honesty, and transparency, and we purposely developed our open desk layouts and large meeting spaces to support and promote partnerships, collaboration, and teamwork. From catered lunches and office celebrations to employee recognition events and social professional groups such as the Awesome Women of Netskope (AWON), we strive to keep work fun, supportive and interactive. Visit us at Netskope Careers. Please follow us on LinkedIn and Twitter @Netskope .

An agent doesn't go from a developer's laptop to production in one step here — it moves through a staged pipeline with real gates at every stage, then spends its first two weeks in production under close review before anyone trusts it to act on its own. As a Senior Agent Release Engineer, you'll own that entire path: the CI/CD pipeline every agent and every model change moves through, the automated checks that decide whether a release is safe to promote, and the rollback plan for when something isn't. You'll also own model tiering — making sure each agent is running on the model tier that actually fits its task, since that's one of the biggest cost levers on a platform running well over a hundred agents at once. If you like turning "we hope this works" into "here's the automated gate that proves it," this is that role.

Own and continuously improve the CI/CD pipeline every agent and every model or prompt change moves through, from initial commit through sandbox, development, and staging, before anything reaches production. Design and maintain the automated gates that decide whether a release is safe to promote — evaluation score thresholds, security scan results, guardrail test results — so a human isn't manually eyeballing test output before every promotion. Own progressive rollout for model and agent changes: canary a change to a small slice of traffic or sessions first, watch the quality and cost metrics live, and only promote to full traffic once those metrics hold. Build and maintain the rollback path for every stage of the pipeline,