Skip to content
aitrainer.work - AI Training Jobs Platform
Engineering Full-Time
Vendra (YC S24)

Cloud Infrastructure Engineer (US)

Vendra (YC S24) • San Francisco, CA

Company

Vendra (YC S24)

Annual salary

$155k – $180k/yr

Location

San Francisco, CA

Listed

23d ago

Experience:
2 to 4 years
Workplace:
On-site 5 days a week at Vendra's new office in San Francisco, which is easy to commute to. Open to supporting relocation
Equity:
0.05%-0.1% (worth ~$100k - $200k, but please be discrete about this in outreach)

On-site in San Francisco, CA.

Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.

Apply for a referral →

The recruiter emails you before anything happens and may suggest other jobs that suit you better.

What you'll do

  • Own all of Vendra's build and deployment pipelines (CI/CD), and refactor them where needed. They cover our customer platform, supplier portal, internal ERP, and AI/ML workflows, across both commercial AWS and AWS GovCloud.
  • Own cloud architecture and security: least-privilege IAM, network isolation, encryption, secrets management, audit logging, and automated vulnerability detection and patching.
  • Work directly with the CTO and a lean 3-person product engineering team. You'll give them repeatable, observable, easy-to-roll-back deployments so they don't need manual infrastructure help for every change.
  • Build and manage infrastructure as code (GitHub Actions today; Pulumi, CDK, or CloudFormation). You'll also set up useful monitoring, alerting, backups, and incident-response runbooks across dev, staging, and production.
  • Run the networking and access setup for Vendra's new in-house GPU training rigs from start to finish, so the technical team can reserve compute and test their own models.
  • Improve system performance, availability, and cloud cost efficiency. Support customer security reviews and compliance work with documented controls and evidence. Who this is for: This is a hands-on individual contributor (IC) role, not a team lead role. Senior candidates are welcome, but they must still be doing the work themselves. Cloud should be the main focus of their experience, not a side task next to backend or full-stack work. We'd rather see someone who built the build pipelines than someone who used systems running on the cloud. AWS is a must. Terraform-heavy, process-heavy profiles are less of a fit than scrappy builders who move fast.

What you need

  • We need someone with 2-5 years of hands-on experience in cloud infrastructure, DevOps, platform engineering, or SRE who has designed, built, and owned AWS build and deployment pipelines in production. Ideally they built them from scratch at an early-stage startup or on a small team. You should be comfortable working as the only infrastructure engineer on a small, fast team. Expect to own the work end to end and have engineers relying on you every day. You should have a track record of cutting manual deployments and incidents, securing cloud architecture, and helping engineers ship faster. Bonus points if you like breaking systems: hacking side projects, pen testing, or fixing vulnerabilities. Experience with AWS GovCloud or with aerospace and defense customers is also a plus.

Common questions

How do I apply for the Cloud Infrastructure Engineer (US) role at Vendra (YC S24)? +

Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.

What does this Vendra (YC S24) role pay? +

The listing gives $155k – $180k/yr.

Is this role remote? +

The listing gives the location as San Francisco, CA. On-site 5 days a week at Vendra's new office in San Francisco, which is easy to commute to. Open to supporting relocation.

Cloud Engineer interview prep

Questions Cloud Engineer interviewers often ask. They aren't taken from this listing.

How do you decide between a managed service and a self-managed equivalent when designing cloud infrastructure?

I weigh the operational overhead of self-managing against the specific control or cost benefit it provides, since managed services usually cost more directly but remove maintenance burden that's easy to underestimate. I lean toward self-managing only when there's a concrete requirement a managed option can't meet.

What's your approach to structuring infrastructure as code so it stays maintainable as the environment grows?

I modularize configuration around logical units, like a network layer and an application layer, rather than one large monolithic definition, so changes to one part don't require reviewing the entire configuration. I also keep environment-specific values separate from the shared structure so the same modules can be reused across environments.

How do you approach container resource limits to avoid both resource starvation and wasted capacity?

I set limits based on actual observed usage under realistic load rather than a default or guessed value, and I revisit them periodically as the application's resource profile changes. Setting limits too low causes throttling or crashes, while setting them too high wastes capacity across the cluster.

What's your process for managing secrets and credentials in a cloud environment without hardcoding them into infrastructure code?

I use a dedicated secrets manager that infrastructure code references rather than storing values directly, and I make sure access to secrets is scoped tightly to what each service actually needs. Committing a secret into version control, even briefly, requires rotating it, not just removing it from the file.

See all 10 Cloud Engineer interview questions →

Related roles

Vendra (YC S24)

Browse all referral roles

Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.

See all referral roles →