ZipRecruiter

Log In

2

Entry Level High Performance Computing Engineer Jobs in Berkeley, CA

AMAX

Junior System Engineer

Fremont, CA

$80K - $95K/yr

... of high-performance computing systems and server platforms. The ideal candidate has strong ... Collaborate with engineering teams to define system specifications and evaluate the interface ...

AMAX

Industrial Engineer

Fremont, CA · On-site

$76K - $103K/yr

Requirements * BS, MS, or equivalent in Industrial, Mechanical, or Electronic Engineering ... Catering to industries such as AI, cloud computing, autonomous vehicles, and high-performance ...

AMAX

Industrial Engineer

Fremont, CA · On-site

$76K - $103K/yr

Requirements * BS, MS, or equivalent in Industrial, Mechanical, or Electronic Engineering ... Catering to industries such as AI, cloud computing, autonomous vehicles, and high-performance ...

AMAX

Industrial Engineer

Fremont, CA · On-site

$76K - $103K/yr

Requirements * BS, MS, or equivalent in Industrial, Mechanical, or Electronic Engineering ... Catering to industries such as AI, cloud computing, autonomous vehicles, and high-performance ...

next page

Showing results 1-20

All JobsHigh Performance Computing Engineer JobsEntry Level High Performance Computing Engineer JobsEntry Level High Performance Computing Engineer Jobs in Berkeley, CA

Entry Level High Performance Computing Engineer information

See Berkeley, CA salary details

$36.7K

$84.9K

$144.5K

How much do entry level high performance computing engineer jobs pay per year?

As of Aug 1, 2026, the average yearly pay for entry level high performance computing engineer in Berkeley, CA is $84,930.00, according to ZipRecruiter salary data. Most workers in this role earn between $63,100.00 and $96,100.00 per year, depending on experience, location, and employer.

What is an Entry Level High Performance Computing Engineer?

An Entry Level High Performance Computing (HPC) Engineer is a professional who assists in designing, building, and maintaining high-speed computing systems used for complex computations and large-scale data analysis. They typically work with supercomputers or computer clusters in fields like scientific research, finance, or engineering. Responsibilities often include configuring hardware, optimizing software, and troubleshooting system issues, usually under the guidance of more experienced engineers. Entry-level engineers may also help monitor system performance and support users in running high-performance applications.

What are some common challenges faced by entry level High Performance Computing (HPC) engineers, and how can new hires successfully navigate them?

Entry level HPC engineers often encounter challenges such as working with complex parallel computing architectures, optimizing code for performance, and troubleshooting across large-scale, distributed systems. New hires may also need to quickly learn job-specific tools and adapt to rapidly evolving hardware and software environments. To navigate these challenges, it’s important to proactively seek mentorship, participate in team code reviews, and continuously build your skills through hands-on experience and training opportunities. Open communication and collaboration with experienced team members also play a key role in overcoming technical hurdles and growing within the HPC field.

What is the difference between Entry Level High Performance Computing Engineer vs Entry Level Data Scientist?

AspectEntry Level High Performance Computing EngineerEntry Level Data Scientist
Required CredentialsBachelor's in Computer Science, Engineering, or related field; knowledge of parallel computingBachelor's in Data Science, Statistics, or related; programming skills in Python/R
Work EnvironmentResearch labs, tech companies, supercomputing centersBusiness, tech firms, research institutions
Industry UsageHigh-performance computing, scientific research, simulationsData analysis, machine learning, predictive modeling

Entry Level High Performance Computing Engineers focus on developing and optimizing computational systems for scientific and technical applications, while Entry Level Data Scientists analyze data to extract insights. Both roles require programming skills and a strong technical background, but they serve different industry needs and environments.

What are the key skills and qualifications needed to thrive as an Entry Level High Performance Computing (HPC) Engineer, and why are they important?

To thrive as an Entry Level High Performance Computing Engineer, you typically need a solid background in computer science or engineering, familiarity with parallel computing concepts, and proficiency in programming languages like C/C++ or Python. Experience with Linux environments, HPC cluster management tools, and knowledge of batch schedulers or MPI/OpenMP are often required. Strong problem-solving abilities, teamwork, and effective communication help you excel in collaborating with researchers and technical teams. These skills ensure efficient support and optimization of complex computing systems critical for scientific and technical advancements.
What job categories do people searching Entry Level High Performance Computing Engineer jobs in Berkeley, CA look for? The top searched job categories for Entry Level High Performance Computing Engineer jobs in Berkeley, CA are:
Entry Level High Performance Computing Engineer jobs near you
Infographic showing various Entry Level High Performance Computing Engineer job openings in Berkeley, CA as of July 2026, with employment types broken down into 3% Locum Tenens, 79% Full Time, 16% Part Time, and 2% Contract. Highlights an 79% Physical, 3% Hybrid, and 18% Remote job distribution, with an average salary of $84,930 per year, or $40.8 per hour.

Software Engineer, High Performance Computing

Eventual Computing

San Francisco, CA • On-site

$150K - $250K/yr

Full-time

Medical, Dental, Vision, Retirement, PTO

Re-posted yesterday

Job description

About Eventual
Every breakthrough Physical AI system - humanoid robots, autonomous vehicles, video generation models - is trained on petabytes of video, lidar, radar, and sensor data. But today's data platforms (Databricks, Snowflake) were built for spreadsheet-like analytics, not the multimodal corpora that power AI. Robotics and video-AI teams now lose 20-40% of their training time to dataloading alone. GPU bandwidth has grown 2-3× per generation. Storage and pipelines haven't. The gap widens every year.
Eventual was founded in 2022 to close it. Our open-source engine, Daft, is the distributed data engine purpose-built for multimodal AI - already running 2 PB/day at Amazon, 60-100 PB at another FAANG company, and in production at Mobileye, TogetherAI, and CloudKitchens. We are building a video-native index on top of our engine for Physical AI that streams curated datasets to GPUs at line rate. Saturates B200s today. Aimed at NVL72 and Vera Rubin tomorrow.
We're building this in partnership with the top PhysicalAI labs and public AI infrastructure companies today. We have raised $30M from Felicis, CRV, Microsoft M12, Citi, Essence, Y Combinator, Caffeinated Capital, Array.vc, and angels from the co-founders of Databricks and Perplexity. We've assembled a world-class team from AWS, Render, Pinecone and Tesla. We have spent our careers powering the last generation of PhysicalAI in self-driving, and are excited to now do this for the next.
Join our small (but powerful!) team working together 4 days/week in our SF Mission district office.
Your Role
As a Systems Engineer on the Dataloading team, you'll build the layer that turns multi-petabyte video corpora into dict[str, Tensor] already on the GPU at line rate. We work with the top labs training Physical AI on the newest generation hardware - H100, B200, GB200, NVL72, with Vera Rubin on the horizon - on billions of dollars worth of compute, in collaboration with partners that are the largest public AI companies on Earth. Our job is to keep those GPUs fed: rank-aware sampling, NVMe caching, video and sensor co-loading, random access into clips, decode pipelining. Streaming alone can already saturate a B200; the hard part is enabling the complex sampling patterns researchers actually need without giving up a single percentage point of MFU.
This is a systems engineering role for someone who feels physical pain when a system is slow. You won't need GPU experience on day one - we'll uplevel you on NVL72, CUDA, and SLURM. We will need you to bring real expertise on what happens between NVMe, network, memory, and CPU, and a deep instinct for where bytes go.
Key Responsibilities
  • Design and build the video-native dataloader: rank-aware, NVMe-cached, random-access into clips, returns tensors directly to the GPU.
  • Profile and optimize the full data path from object store → NVMe → page cache → host RAM → device RAM. Eliminate every avoidable copy and stall.
  • Saturate the latest hardware (B200, GB200, NVL72) on real customer training jobs. Push toward Vera Rubin bandwidth requirements.
  • Own performance benchmarks against customer baselines (custom DataLoaders, DALI, decord, LeRobot) and against our own historical numbers - regressions get caught at PR time.
  • Partner with researchers at our partner labs to land the loader in their training stack and measure MFU end-to-end.
  • Work cross-team with Storage Infrastructure on the index/format boundary and with Visual Understanding on the model-output ingestion path.

What we look for
  • Obsession with systems-level performance. You can recite Jeff Dean's "numbers every programmer should know" in your sleep. You eat flamegraphs for breakfast.
  • Strong opinions on io_uring - love it or hate it, you've earned the opinion.
  • Live and breathe Rust, C++, or C. You reach for them when it matters and you know why.
  • Strong familiarity with operating systems - page cache, scheduling, syscalls, NUMA, memory hierarchies.
  • A sense for where bytes actually go: NVMe vs. memory vs. network vs. PCIe vs. NVLink, and the throughput and latency budgets of each.

Nice to have
  • Experience working with GPUs is a plus, but you don't need it on day one.
  • Experience working with SLURM, Kubernetes for GPU workloads, or other HPC schedulers.
  • Hands-on CUDA experience.
  • Deep expertise on memory and caching subsystems - page cache tuning, hugepages, NUMA pinning, GPU-Direct Storage.
  • Worked on video decode pipelines (PyAV, decord, NVDEC) or PyTorch DataLoader internals.
  • Contributed to open-source systems projects in Rust/C++.

Perks & Benefits
  • In-person, tight-knit team - 4 days/week in our SF Mission office.
  • Competitive comp and meaningful startup equity.
  • Catered lunches and dinners for SF employees.
  • Commuter benefit.
  • Team-building events and poker nights.
  • Health, vision, and dental coverage.
  • Flexible PTO.
  • Latest Apple equipment.
  • 401(k) plan with match.

If slow systems evoke emotional pain for you and you want to spend the next few years making the most expensive GPU clusters on the planet earn their keep, we'd love to talk.

Apply