Job Overview
Join the Future of Security at Netskope Netskope (NASDAQ: NTSK) is a leader in modern security and networking for the cloud and AI era. We secure and accelerate cloud, data, and AI in real time, everywhere. Thousands of customers, including more than 30 of the Fortune 100, trust the Netskope One platform, its Zero Trust Engine, and the powerful NewEdge network to gain full visibility and control without performance trade-offs.
At Netskope, our technology is driven by our greatest strength: our people. We believe that belonging powers innovation, and success is both personal and organizational. We embrace differences in gender, ethnicity, beliefs, ability, and identity, creating an environment where every voice is heard and respected. We empower our employees to bring their authentic selves to work, grow their careers through continuous education and mentorship, and lead with transparency and curiosity. Join a team where you belong, where you are encouraged to be an entrepreneur, and where together, we continue to redefine the landscape of security.
Visit Careers at Netskope to learn more. Follow us on LinkedIn and Instagram .
Every agent on this platform runs inside its own isolated environment, and someone has to make sure that environment actually behaves the way it's supposed to under real load, not just in a clean test run. As a Senior Agent Runtime Engineer , you'll own the health of the systems agents run on: keeping sessions isolated from each other, catching the failure modes that only show up under real concurrency, and making sure a slow or expensive agent gets caught before it becomes everyone's problem. You'll work closely with the engineers building the agents themselves, since you're often the first call when something behaves strangely in a real environment but not in a test one. If you like being the person who understands a system well enough to know exactly why it's misbehaving, this is that job.
Skills and competencies
- Own the health of the agent execution environment day to day — session isolation, resource limits, and catching the failure modes that only appear once real concurrency and real traffic patterns show up, not just in a clean test run.
- Investigate and resolve cases where an agent behaves differently in production than it did in testing, working directly with the Agent Engineer or Quality Engineer who built it to figure out whether the problem is the agent's design or the environment it's running in.
- Tune cold-start and concurrency settings for the platform's critical-path functions, and review them on a regular cadence as usage patterns shift rather than setting them once and forgetting them.
- Understand the platform's session isolation model well enough to reason about its limits — where isolation is guaranteed by the underlying compute layer, and where the platform has to add its own controls because that guarantee doesn't fully hold.
- Build and maintain the observabili