Glean
Software Engineer, Developer Productivity
About this role
Glean seeks a Software Engineer for Developer Productivity to optimize build systems, CI/CD pipelines, and developer tooling for a large multi-language codebase. You'll enhance engineering velocity by improving infrastructure efficiency, reducing build times, and integrating AI-powered productivity tools across the team.
What you'll do
- Develop and maintain Bazel monorepo infrastructure supporting multiple programming languages
- Improve build caching, reproducibility, and dependency management across the codebase
- Extend Bazel with custom rules, macros, and integrations to meet team needs
- Operate and optimize CI/CD pipelines on GitHub Actions, Kubernetes, and cloud infrastructure
- Reduce CI latency through remote execution, caching strategies, and parallelization
- Create telemetry and dashboards to measure pipeline speed, reliability, and cost
What they're looking for
- Bazel build system expertise
- CI/CD pipeline design and optimization
- GitHub Actions and cloud infrastructure knowledge
- Multi-language development experience
- Remote execution and caching technologies
- Kubernetes or container orchestration
- Performance instrumentation and monitoring
- Systems infrastructure design
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
- Tell us about your experience with Bazel or similar build systems. How have you optimized build times or improved caching in a monorepo?
- Describe a time you designed or improved a CI/CD pipeline. What metrics did you use to measure success, and what bottlenecks did you eliminate?