Glean
Software Engineer, APIs & Context Platform
About this role
Glean seeks a Software Engineer to build and evolve the APIs and context platform that powers enterprise AI experiences. You'll own REST API standards, design platform primitives, build the API gateway layer, and create developer tools that enable both internal teams and external partners to build on Glean's Work AI ecosystem.
What you'll do
- Own REST API standards including versioning, backward-compatibility, deprecation policy, and OpenAPI tooling
- Design and ship new API endpoints exposing search, knowledge graph, chat, and agent capabilities
- Build API gateway layer with routing, authentication, rate limiting, and usage metering
- Define reusable platform primitives for internal and external developers
- Develop SDKs, client libraries, and agent integrations
- Create infrastructure, documentation, and developer tools across multiple stack layers
What they're looking for
- REST API design and architecture
- Backend services development
- Authentication and security (OAuth2, API keys, OIDC)
- API gateway implementation
- SDK and client library development
- OpenAPI/specification tooling
- Full-stack development across backend and developer tools
- Documentation and developer experience
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Glean
Glean builds a Work AI platform that helps enterprises access and leverage their internal data intelligently. The company is hiring backend engineers, infrastructure specialists, fullstack engineers, and billing platform leads to develop scalable features, robust data infrastructure, consumption-based billing systems, and enterprise-grade storage and analytics capabilities.
- Website
- glean.com
Likely interview questions
- Walk us through your experience designing and maintaining REST API standards at scale. How have you handled versioning, backward compatibility, and deprecation policies?
- Describe a time you built or evolved an API gateway. What authentication mechanisms, rate limiting, or quota management strategies did you implement?