JOIN AGGRIVER

Bring your
way of thinking.

We welcome talent from every STEM discipline.

Science, technology, engineering, and mathematics offer different ways to understand a difficult problem. There is room for all of them here.

Apply to Aggriver

YOUR BACKGROUND

Every STEM major.
No prescribed path.

We recruit across all STEM majors, with no restriction to a particular field of study.

You might have studied physics, chemistry, biology, mathematics, statistics, computer science, or an engineering discipline. These are examples, not a checklist. Interdisciplinary backgrounds belong here too.

Tell us how you approach a problem, what you have built or investigated, and what you learned along the way. A research project, a piece of software, or an experiment can be a useful place to start.

OUR TEAM

Different backgrounds.
Distinct contributions.

Aggriver began with mathematicians and computer scientists from Berkeley. Today, our team includes people from a range of disciplines.

Each person's unique background and academic experience brings an irreplaceable contribution to the team.

ROLES AT AGGRIVER

Three ways to contribute.

We are looking for researchers, infrastructure engineers, and people who keep our internal applications running well. Every role is open to all STEM disciplines. Prior financial knowledge is not required.

RESEARCH

Researcher

Develop and test ideas about markets with the care you would bring to a scientific problem.

Apply for this role

What you will work on

Formulate testable hypotheses and design experiments that can distinguish a useful result from noise.
Build and examine datasets; investigate measurement errors, selection effects, and information leakage.
Develop statistical or computational models and evaluate them with reproducible, out-of-sample tests.
Work with engineering colleagues to turn research into implementations and understand the gap between a simulation and observed behavior.

What you bring

Evidence of academic and research ability, sound quantitative reasoning, and the ability to explain your methods and their limitations. You should be comfortable using code to investigate a problem; Python or comparable scientific computing experience is useful.

What to share

A thesis, paper, research project, or reproducible experiment. Describe your own contribution, the evidence behind your conclusions, and what did not work. Research in any STEM field is relevant.

SYSTEMS & RELIABILITY

Infrastructure Operations Engineer

Keep the computing, networking, and storage foundations dependable for research and company operations.

Apply for this role

What you will work on

Operate Linux hosts, networks, storage, and compute environments; diagnose failures across those layers.
Automate provisioning, configuration, patching, and deployment with changes that can be reviewed and rolled back.
Improve monitoring and alert quality; investigate performance and capacity constraints using measurements.
Test recovery procedures, document incidents, and turn repeated problems into lasting fixes.

What you bring

A practical understanding of Linux processes, filesystems, permissions, and networking, plus scripting ability and a systematic approach to troubleshooting. Experience with containers, orchestration, infrastructure as code, or observability is useful. Clear incident communication matters.

What to share

A system you operated, an automation you built, or a difficult failure you diagnosed. Explain how you identified the cause, verified the fix, and planned for recovery. Academic and lab projects are welcome evidence.

INTERNAL SYSTEMS

Application Operations Engineer

Keep internal applications and their integrations reliable, usable, and consistent with approved access policies.

Apply for this role

What you will work on

Maintain internal business applications, background jobs, and integrations; trace issues through logs, APIs, and databases.
Support account lifecycle and access workflows through the existing identity and approval systems.
Plan application upgrades, test data migrations and restores, and verify workflows after changes.
Automate recurring support tasks and maintain clear operating procedures with the people who use the systems.

What you bring

A methodical approach to application troubleshooting, comfort with SQL and scripts, and an understanding of HTTP, APIs, and authentication. Take care with permissions and data changes, and communicate clearly with both technical colleagues and application users.

What to share

An application you supported, an integration you built, or a workflow you improved. Explain the checks, recovery steps, and evidence you used to confirm that the system worked for its users.

COMMON QUESTIONS

A few things
you may be wondering.

Do I need a background in finance?

No. We do not require applicants to have financial knowledge. We ask only that you demonstrate your academic and research abilities.

Do I need a particular STEM major?

No. We welcome applicants from every STEM discipline. The fields listed on this page are examples, not eligibility restrictions.

Does an interdisciplinary degree count?

Yes. Work across subjects can bring a useful perspective. Tell us about the questions you explored and your own contribution.

What kind of work should I talk about?

Choose something you understand well: a thesis, a research project, software you built, or an experiment. Explain the problem, your approach, the result, and its limitations. Share only material you are permitted to disclose.

YOUR APPLICATION

Bring yourway of thinking.

Every STEM major.No prescribed path.

Different backgrounds.Distinct contributions.

Three ways to contribute.

Researcher

What you will work on

What you bring

What to share

A few thingsyou may be wondering.

Tell us about yourself.

Bring your
way of thinking.

Every STEM major.
No prescribed path.

Different backgrounds.
Distinct contributions.

A few things
you may be wondering.