Sycamore is building the trusted agent operating system for the enterprise. Our platform helps companies build, deploy, and orchestrate agentic apps that take on real operational work, with the security and control large organizations need.

We are a small, engineering-led team working directly with Fortune 500 enterprises. The surface spans user-facing applications, APIs, agent runtimes, tools and connectors, identity and authorization, untrusted code execution, multi-tenant data, cloud infrastructure, and the software-delivery system itself.

You will write production code, build security controls and paved paths, review designs and code, model threats, test systems from an attacker's perspective, investigate incidents, and work with engineers until durable fixes reach production.

Agent systems introduce unusual security problems. A model may consume hostile instructions from a document, invoke tools on a user's behalf, generate executable code or browser content, retain information in memory, and operate across long-running workflows. Securing that system requires more than a conventional web checklist: identity must remain attributable, authority must narrow at every boundary, untrusted content must stay contained, credentials must remain outside model context, and high-impact actions must be observable and governable.

You will work across Product, Core AI, and Infrastructure. Security helps them identify risks early, provides reusable controls, validates important boundaries, and steps in directly when a problem needs deep security engineering.

Lead threat modeling and security architecture for agent products, APIs, connectors, execution environments, customer applications, and platform services.

Build production security controls for authentication, authorization, delegated agent identity, workload identity, credential brokering, tenant isolation, encryption, policy enforcement, and auditability.

Design isolation boundaries for untrusted code and generated content, including sandboxing, network and resource controls, browser containment, and safe communication with trusted services.

Identify and remediate vulnerabilities through design review, code review, targeted security assessment, hands-on exploitation, and adversarial testing.

Develop reusable libraries, services, policies, test harnesses, and developer tooling that eliminate vulnerability classes rather than documenting the same mistake repeatedly.

Secure the software-development lifecycle through dependency verification, secret detection, code and infrastructure scanning, build isolation, artifact integrity, and risk-based release gates.

Build security telemetry,



detections, investigation tools, containment paths, and response automation across application, identity, agent, and infrastructure events.

Participate in incident response from triage and containment through root-cause analysis, remediation, evidence preservation, and control improvement.

Partner with Product and Core AI on risks specific to agentic systems, including prompt injection, confused deputies, excessive agency, unsafe tool calls, memory poisoning, sensitive-data leakage, and model-generated executable content.

Partner with Infrastructure on cloud and cluster security, network boundaries, workload identity, secrets, data protection, deployment safety, and customer-controlled environments.

Translate enterprise security requirements into defensible engineering controls and evidence without allowing questionnaire-driven work to replace actual risk reduction.

Raise the security capability of the engineering organization through clear design patterns, direct coaching, useful reviews, incident learning, and tools engineers want to use.

Sycamore operates a cloud-native, multi-tenant platform spanning browser applications, typed backend services, agent runtimes, durable workflows, relational and vector data, containerized execution, customer-authorized integrations, infrastructure as code, and automated delivery.

It must protect customer data and credentials while allowing agents to call tools, generate applications, execute code, retain scoped memory, and act under human-delegated authority.

Our current security controls include identity and authorization boundaries, tenant-scoped data access, workload isolation, encrypted secrets, secure delivery gates, dependency and vulnerability checks, audit trails, production telemetry, staged rollouts, and incident-response procedures. others are active engineering problems you will help define.

We do not require experience with every language, framework, cloud provider, scanner, or security product in our setting. We care about transferable security and software-engineering judgment and your ability to understand an unfamiliar system deeply.

5-12 years of software or security engineering experience.



Strong software-engineering fundamentals and evidence that you have built, shipped, and operated security-relevant production systems—not only assessed them.

- Depth in at least two of product security, application security, identity and authorization, cloud or infrastructure security, platform security, software supply chain, offensive security, or detection and response.
- Experience threat-modeling complex systems, finding realistic failure paths, and translating them into proportionate controls and executable tests.
- Strong understanding of trust boundaries, least privilege, identity, authorization, secrets, cryptography, isolation, secure software design, and common web and distributed-systems vulnerabilities.
- Practical risk judgment. You distinguish plausible impact from theoretical concern, prioritize the highest-leverage work, and avoid both security theater and reckless shortcuts.
- A collaborative approach that raises engineering velocity and ownership rather than turning Security into a late-stage approval queue.
- You can explain a subtle exploit to an engineer, a control gap to leadership, and an evidence-backed posture to a customer's security team.
- AI-native. You use modern AI systems and coding agents to expand your coverage while independently validating findings, exploitability, and remediation.
- Comfort with startup ambiguity, broad ownership, and occasional customer travel.

Experience securing AI or agent systems is valuable but not required. Engineers from strong product-security, platform-security, identity, cloud-security, developer-security, offensive-security, or security-focused software-engineering backgrounds can succeed here if they are excited to learn the agent-specific threat model.

Two 60-minute technical interviews, one focused on security systems design and threat modeling and one on coding and practical problem solving.

A take-home assignment where you analyze or build a real system and present the risks, tradeoffs, implementation, and verification using the tools you would use on the job.

Work on identity, authorization, isolation, tools, connectors, generated code, multi-tenant data, supply chain, and incident response as one connected system.

Build security foundations and paved paths rather than operating a policy or review function from the sidelines.

Help define the security model for a category whose most important attack paths are still emerging.

Join early enough to shape Sycamore's security architecture, engineering culture, and India team.

Receive competitive cash compensation and meaningful equity in the company you are helping build.

📌 Security Engineering (Engineering) (Bengaluru)
🏢 Sycamore
📍 Bengaluru