Software Engineer, Context Platform

Glean Glean · Enterprise · Mountain View, CA · Engineering

Software Engineer to build and evolve Glean's horizontal AI platform, focusing on SDKs, client libraries, agent tooling, custom context services (Code Search, Code Writer, Memory), and public REST APIs. The role involves designing platform primitives and collaborating on developer authentication and authorization flows, aiming to enable external frameworks and agents to integrate with Glean.

What you'd actually do

  1. Design, build, and evolve SDKs and client libraries that developers use to integrate with Glean from their own applications and agent frameworks.
  2. Own and advance agent‑focused tooling and SDKs (including MCP and related integrations) so external frameworks, IDEs, and agents can easily and reliably call into Glean.
  3. Build custom platform context services and actions such as Code Search, Code Writer, and Memory that power rich experiences across apps.
  4. Define and maintain standards and conventions for Glean’s public REST APIs (resource design, versioning, errors, deprecations) and provide the OpenAPI schemas, tools, and CI checks that other teams use when building and evolving endpoints.
  5. Collaborate with Security to design and operate authentication and authorization flows for developer scenarios (e.g., OAuth2/OIDC, dynamic client registration, service‑to‑service auth).

Skills

Required

  • BA/BS in computer science or a related field, or equivalent practical experience
  • 1+ years of industry software engineering experience
  • Experience building and shipping backend and/or platform systems that are used in production
  • Proficiency in at least one modern backend language (ideally Golang, or strong interest in learning it)
  • Thrive in a customer‑focused, tight‑knit, cross‑functional environment
  • A proactive and positive attitude to lead, learn, troubleshoot, and take ownership of both small tasks and large features

Nice to have

  • TypeScript
  • Python
  • Java
  • Familiarity with cloud‑native development practices in GCP/AWS/Azure

What the JD emphasized

  • build systems used daily across Microsoft Teams, Zoom, ServiceNow, Zendesk, GitHub, and many more
  • ship agentic capabilities on an open, extensible stack
  • craft and care required for enterprise trust
  • build this context platform and deliver rich, trustworthy experiences across all of those apps
  • platform experience end‑to‑end
  • standards and tooling for REST APIs, SDKs and client libraries, agent SDKs and integrations, MCP servers, custom context such as code and memory, and the infrastructure and docs that make it easy to build on Glean
  • working across multiple layers of the stack – backend services, developer tools, SDKs, and docs
  • developers use to integrate with Glean from their own applications and agent frameworks
  • external frameworks, IDEs, and agents can easily and reliably call into Glean
  • power rich experiences across apps
  • Glean’s public REST APIs
  • other teams use when building and evolving endpoints
  • authentication and authorization flows for developer scenarios
  • reusable platform primitives
  • reused by internal teams and partners
  • customer‑focused, tight‑knit, cross‑functional environment
  • team player and willing to take on whatever is most impactful for the company is a must

Other signals

  • AI agents
  • Work AI platform
  • LLM choice
  • Enterprise Graph
  • Personal Knowledge Graph
  • agentic capabilities
  • horizontal AI platform
  • agent SDKs
  • custom context services
  • public REST APIs
  • developer scenarios
  • reusable platform primitives