Opal Security - Software Engineer, Infrastructure

• →4+ years of experience as a software engineer building distributed systems [Required]

• Worked on platform/infrastructure teams as a software engineer, writing services and systems, not just managing or operating infrastructure [Must have]
• Built or scaled systems serving enterprise-grade traffic or multi-tenant SaaS [Required]
• Experience building internal developer platforms or tooling that product engineers depend on [Strongly preferred]

• Strong software engineering fundamentals; must pass a rigorous Leetcode-style coding screen (same bar as product engineers) [Must have]
• Systems design for large distributed systems (a dedicated interview round tests this) [Must have]
• Backend development in Golang or a comparable systems language [Required]
• Experience with cloud infrastructure (AWS or GCP): deployment, scaling, and monitoring at production scale [Required]
• Familiarity with infrastructure tooling (Kubernetes, Terraform, Kafka); deep expertise not required, baseline awareness expected [Required]

• Pure infra/SRE/DevOps background without software engineering depth (would not pass a standard coding screen)

• Salary | $160,000–$250,000 (up to ~$260,000 for exceptional candidates) |
• Equity | Competitive equity |
• On-site policy | Hybrid, 3 days in office (Mon, Tue, Thu); most of the team is in 4 to 5 days; flexibility for exceptional remote candidates |
• Visa sponsorship | Yes, case by case; open to transfers (OPT, H-1B) |
• Employment type | Full-time |
• Location | San Francisco, CA |

1. Can you be on-site (hybrid, 3 days/week in SF)? If not, are you willing to relocate?
2. What is your salary expectation?
3. How actively are you exploring new opportunities right now?

Updated Jul 15, 2026

Top-tier big tech (strong fundamentals, systems at scale) Google, Meta, Stripe, Dropbox, Airbnb, Lyft, Uber, Square, Coinbase (1 company hidden behind "Show all 10" and not captured in the paste)

Well-regarded mid-stage startups with strong engineering reputations DoorDash, Figma, Databricks, Notion, Ramp, Plaid, Scale AI, Retool, Linear (1 company hidden behind "Show all 10" and not captured in the paste)

Non-ideal: large retail/non-tech with big but less rigorous eng teams (avoid sourcing) Walmart, Target, Capital One, JPMorganChase, Bank of America, Accenture, Infosys, Wipro, TCS (1 company hidden behind "Show all 10" and not captured in the paste)

Non-ideal: mixed engineering reputations / overly large orgs (avoid sourcing) Amazon, Splunk, Yahoo, eBay, PayPal, Intuit, Adobe, Qualcomm

For reference only, do not source these specific profiles.

Zoe Kuebrich (LinkedIn) AWS Software Development Engineer II | UC Berkeley Computer Science | Seattle, United States

• Flagged by the hiring manager as an ideal profile (no detailed rationale in the brief).

Rafael Félix (LinkedIn) Software Engineer | San Francisco Bay Area

• Flagged by the hiring manager as an ideal profile (no detailed rationale in the brief).

• Focus on top-tier tech signals: only advance candidates from renowned companies (Meta, Google, DoorDash, Rubrik) and avoid those from Oracle, Apple, Salesforce, Visa, or similarly perceived second-tier firms.
• Emphasize coding depth: candidates must be true software engineers who build infrastructure and can pass the rigorous coding screen, not pure SRE/DevOps operational backgrounds.
• Look for consistent, startup-like ownership: prioritize clear end-to-end product and infrastructure ownership from VC-backed or early-stage environments; flag short stints or hoppy career moves.