Infrastructure Engineer

Greptile; San Francisco (CA); On-site; USD 120,000 - 190,000; Full time

Job summary

Greptile is seeking an Infrastructure Engineer to design and implement scalable infrastructure to support rapid growth and enterprise deployments. You will work closely with customers to ensure smooth integration and successful operation within their environments.

The role emphasizes hands-on work with containers, VMs, and compute clusters, with a bias toward in-person collaboration and on-site office presence in San Francisco.

Qualifications

• Bachelor's degree in Computer Science or equivalent required.
• 1+ year of software, infrastructure or cloud engineering experience.
• Solid background in computer networking and Linux system administration.
• Experience with container runtimes and cloud providers (Docker, Kubernetes, AWS) desirable.

Responsibilities

• Design and implement robust infrastructure to support growing usage.
• Collaborate with enterprise customers to deploy Greptile in their environments.
• Operationalize on-premise deployment processes to serve smaller customers efficiently.

Skills

Networking

Cloud engineering

Customer interaction

Linux administration

Education

B.S. Computer Science

Equivalent degree

Tools

Docker

Kubernetes

Terraform

Linux VMs

Hypervisors

AWS

Job description

Infrastructure Engineer

Greptile is an AI code reviewer that catches bugs and anti-patterns in pull requests with complete context of the codebase. Hundreds of top software companies, from YC startups to big tech, and teams in finance, healthcare, and defense, use Greptile to merge PRs faster and catch more bugs.

Greptile reviews 5B lines of code every month for 22,000+ customers. A new repo starts using Greptile every 2 minutes. We also uniquely offer self-hosted, air-gapped deployments for enterprises across defense, financial services, and healthcare.

Problems we’re excited about

• Coding standards can be idiosyncratic and are often poorly documented; can we build agents that learn them through osmosis like a new hire might?
• Can we identify for each customer what types of PR feedback they do and don’t care about, perhaps using some sample efficient RL, in order to increase signal-to-noise ratio?
• Some bugs are best caught by running the code, potentially against discerning AI-generated E2E tests. Can we autonomously deploy feature branches and use agents to parallel try to break the application to detect bugs?

Trajectory

1. 22,000+ customers
2. 5B lines of code reviewed every month

Scaled from $0 to eight figures in ARR

Raised $30M from Benchmark, Y Combinator, Paul Graham, and Initialized

Team

• We have assembled a small, talent dense team who have scaled critical functions at companies like Stripe, Google, Figma, etc.

Responsibilities (in order of how much time you'll likely spend on each)

• Design and implement robust infrastructure to help Greptile keep up with growing usage
• Work with our largest enterprise customers to help deploy Greptile into their environments
• Operationalize the on-premise deployment process so we can serve smaller customers without needing much hands-on work.

Qualifications

• B.S. Computer Science or equivalent degree, undergraduate or higher
• 1+ years of software, infrastructure or cloud engineering
• Strong background in computer networking
• Experience with container runtimes, linux VMs, hypervisors, docker, kubernetes (k8), terraform, and cloud providers like AWS
• Experience building sandboxed or isolated execution environments
• Ability to work closely with customers (patience, friendliness)

You will like this role if

• You want to work on a product that thousands of developers rely on
• The chaos of high growth and things breaking is exciting to you
• You like being in an office every day around other smart people who are excited about what you're building
• You like tinkering with Docker Containers, Virtual Machines, Compute Clusters.
• You enjoy playing with Linux systems and reading blogs like this one: https://www.brendangregg.com/linuxperf.html
• You specifically prefer working in-person over working remote