
What you will do
- Build and run the MCP fleet — ship, secure, and patch self-hosted and managed MCP servers for business apps and databases, and manage the MCP registry.
- Own the agent platform other teams build on — the deploy pattern, guardrails, observability, and hosting substrate that let other teams ship agents without you in the loop.
- Co-own the Bedrock runtime and gateway — model access, cost attribution, content-filtering guardrails, model pinning, and quota management behind an AWS/Okta-SSO'd gateway.
- Make AI spend and usage visible — build the Bedrock-to-Snowflake pipeline, identity-matched, with usage tracking and threshold alerting.
- Make the secure path the easy path — own MDM config, desktop client setup, credentials, and auth flows for non-technical employees; build AI automations across Claude desktop, Slack, and Google Workspace.
- Build governance into the platform — route workflows by data sensitivity, enforce least privilege and auditability, and keep unproven models sandboxed away from production data as configuration, not a rewrite.
What you will bring with you
- 6+ years in software engineering, platform engineering, or DevOps, including ownership of something in production that others depended on.
- Hands-on AWS — IAM, ECS or Lambda, CloudWatch, and working VPC knowledge. Required, not a bonus.
- Full-stack range — backend services, APIs, CI/CD, containerized deployments.
- Builder, not just integrator — you can write an MCP server or API integration from scratch, not just wire up a managed connector.
- Hands-on with LLMs — comfortable with LLM APIs, prompt engineering, and agent development; you've shipped something with them.
- Self-direction — you can take an underspecified task and figure out the parts nobody wrote down.
What we look for
- Bias to ship — and to automate whatever you just did by hand.
- Ownership of the boring parts — upgrades, credentials, quotas, on-call.
- Candor — you raise problems and disagreements early, even about platform choices.
- Judgment on buy vs. build — you'd rather run a small, coherent stack than a sprawling "perfect" one.
When you join Sysdig, you can expect
You will be redirected to the company website to complete your application.








