Skip to main content

Glean

Software Engineer, Cloud Infrastructure

San Francisco, CA$200k–$270kmidAdded 1 month ago

About this role

Glean is looking for a Software Engineer to join their Platform Infrastructure team, focusing on automating customer setup and deployment in cloud environments. The role emphasizes solving complex deployment challenges while enhancing the user experience for enterprise customers.

What you'll do

  • Automate customer setup and deployment processes.
  • Develop infrastructure as code templates.
  • Address complex deployment scenarios.
  • Handle cloud account bootstrapping and authentication.
  • Collaborate with various teams for streamlined deployments.

What they're looking for

  • Cloud infrastructure
  • Networking
  • Infrastructure as code
  • Deployment workflows
  • Authentication mechanisms
  • Collaboration with cross-functional teams
  • Problem-solving
  • Enterprise software experience

Benefits

  • Innovative work environment
  • Opportunity to shape enterprise AI culture
  • Involvement in cutting-edge technology
  • Collaboration with global teams
  • [unknown]
  • [unknown]
Apply with Autofill

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
View all jobs at Glean

Likely interview questions

  • Describe your experience with infrastructure as code tools like Terraform or CloudFormation. How have you used them to manage complex cloud deployments?
  • Tell us about a time you had to support a challenging deployment scenario (e.g., airgapped environments, custom networking, or customer-managed security). How did you approach it?