Cloud Compute & Infrastructure Engineer (C++)
Orange County, California
What "good" looks like: 4+ years at their current or most recent role, or a clear pattern of long stays (3-5+ years per stop). One short stint is explainable — two or three is a pattern, and client will pass immediately.
Primary Skills - azure, linux, c++, python, kubernetes, ci/cd, distributed systems, networking, aws, cloud infrastructure, cloud platform, gcp
Secondary Skills - google cloud, cloud migration, provisioning, scripting languages, cloud environment
Work Experience (Years) - 4-20
Remote Status - No Remote
Relocation Paid - No
Job Description
A well-capitalized, technology-driven investment firm in Southern California is looking for an engineer who can own the full platform layer between raw cloud resources and the people who need them. The firm is in the middle of a major infrastructure shift — moving from a fully on-premises environment to public cloud (GCP specifically) — and this hire will be central to making that transition work.
Your day-to-day will live at the intersection of platform tooling and compute delivery. Some weeks you'll be designing how internal teams request, provision, and access compute resources — building the CLIs, dashboards, and APIs that make self-service possible. Other weeks you'll be deep in IaC pipelines, wiring up orchestration for batch workloads, or figuring out how to make a hybrid on-prem/cloud environment feel seamless to end users. You'll also shape the tooling around the full software development and operations lifecycle — everything from build pipelines to deployment workflows.
This isn't a "maintain the Jenkins server" job. It's a build-from-scratch opportunity where you'll shape how an entire firm interacts with its compute layer during a pivotal transition. You'll work closely with researchers, traders, and other engineers in a flat, collaborative environment where your ideas carry real weight.
The team is small and growing. The culture values kindness and intellectual curiosity as much as technical chops. Private offices, premium workspace, and a group of colleagues who genuinely enjoy solving hard problems together.
Qualifications
What matters most: you've built infrastructure that other engineers actually want to use. You're a true generalist who can move between cloud orchestration, web interfaces, and CLI tooling without missing a beat.
You should bring broad systems knowledge — networking, storage, compute, containers — and have real experience with Infrastructure-as-Code (Terraform, Pulumi, or similar). Strong background in C++ plus comfort in scripting languages like Python, Go, Rust, or Ruby. Cloud platform depth required (GCP preferred, AWS or Azure transferable). Experience building and supporting production-critical applications.
Building developer-facing tools (CLIs, internal portals, APIs) is a big plus. CS degree or equivalent depth from hands-on experience. 5+ years building and shipping production infrastructure.
You're the kind of engineer who sees a manual process and immediately starts thinking about how to automate it. You take ownership, communicate clearly, and thrive in a small, flat organization where you're trusted to figure things out independently and proactively.
IDEAL CANDIDATE PROFILE: True generalist with strong C++ plus scripting languages (Python, Go, Rust, Ruby). Cloud infrastructure experience required — GCP preferred but AWS/Azure transfers. Should have IaC experience and comfort building tools other developers use (CLIs, web UIs, APIs). The example candidate profile: someone at a major tech company (Facebook, Amazon, Google level) with 5–10+ years shipping infrastructure, CS degree from a strong school (e.g., Waterloo, top-100 US), who wants to move into a smaller, high-impact environment.