How we read this posting
FieldAs postedAs we read it
TitleInfrastructure engineerInfrastructure Engineer · Level not stated
  • Title: Infrastructure Engineer: "Infrastructure engineer"
  • Level: seniority not stated
LocationNew York City, NY; Seattle, WA; San Francisco, CA; United States · workplace field: Hybrid; isRemote: trueHybrid · New York
  • Workplace: not remote; the workplace field or location says hybrid
  • City: New York from the location; offices named: New York, Seattle, San Francisco (the first is kept)
Salary$155K – $240K • Offers Equity • Multiple Ranges155,000–240,000 USD a year
  • Salary: from the pay field (the description when the pay field had no usable pay)
Keywords22 keywords found in the posting
  • AWS (not in your profile)
  • Azure (not in your profile)
  • Containerization (not in your profile)
  • Feature engineering (not in your profile)
  • GCP (not in your profile)
  • Go (not in your profile)
  • Go-to-market (not in your profile)
  • Grafana (not in your profile)
  • Helm (not in your profile)
  • High availability (not in your profile)
  • Incident response (not in your profile)
  • Kubernetes (not in your profile)
  • Large language models (not in your profile)
  • Observability (not in your profile)
  • Prometheus (not in your profile)
  • Pulumi (not in your profile)
  • Python (not in your profile)
  • Roadmapping (not in your profile)
  • Scalability (not in your profile)
  • Site reliability engineering (not in your profile)
  • System design (not in your profile)
  • Terraform (not in your profile)
Duplicates1 postingNo other open posting with the same company and title.

Grouped by company and title: "writer|infrastructure engineer"

Posted
First seen
Last seen
Closed
Still listed