opes.
read in full·matched, not skimmed·rare ones surfaced
wealth · riches · abundanceōpēsnoun · latin

People here aren't
just a resource,
they are our wealth.

opes is the pipeline OMMAX hires through.

01

Reads to the end.

No keyword skim. Each CV gets the read your sharpest reviewer would give it.

02

Knows the difference.

A Java engineer is not a data engineer. opes reads the work, not the labels.

03

Surfaces the rare ones.

Too strong for an open role? Flagged, not dropped. The “we had no slot, but…” hires live here.

The workspace

Drop in the CVs.
Read what matters.

Each department defines its roles. opes scores every applicant against them, and routes the matches.

opes.ommax-intelligence.de

Pipeline

12 applicants awaiting review · last sync 2m ago
In review
12
+4 this week
Strong profiles
3
no role match yet
Below threshold
47
under 50% fit
JL
Julia Lehmann
Senior Data Engineer·Data · Engineering·6 yrs · Berlin · Zalando, Delivery Hero
92fit
PythonSparkAirflowdbtSnowflakeKafkaPostgreSQLTerraform+4 more
View extracted CV & match reasoning
Why opes scored 92
Strong on the role's core stack: production Python pipelines at scale, deep Airflow + dbt experience, and a recent move from Zalando's data platform to Delivery Hero's real-time analytics. Calls out Kafka and Snowflake in the work, not just the keywords. Slightly light on cloud ops vs. the role description, which weighs the score down from 95.
“Led the migration of Delivery Hero's order-events pipeline from a legacy Kafka → Spark batch system to a near-real-time dbt+Snowflake model serving 40+ downstream teams.”
All 12
Awaiting HR 4
Awaiting Expert 8
Strong profiles 3
Below threshold 47
Applicant
Matched role
Status
Fit
JL
Julia Lehmann
Senior Data Engineer · 6y
Senior Data Engineer
Data · Engineering
Awaiting Expert
92
MR
Marco Reuter
10y BCG · 4y McKinsey
no current match
Strong profile
AB
Aisha Bello
CI/CD · Kubernetes · AWS
Platform Engineering
Engineering
HR approved
87
TK
Tobias Kraus
Java backend · 6y
Software Engineer
Engineering
Below threshold
42
How it works

From inbox to shortlist.

— 01

Define the roles.

Each department keeps its own roles — title, description, and the keywords that hint at fit. Not a regex; inspiration for the model.

— 02

Drop in the CVs.

One at a time or a batch. opes reads each résumé, picks the role it best fits across all departments, and scores the fit honestly.

— 03

Review what matters.

HR sees what passed the bar. Department leads see what’s tagged for them. Strong profiles without a slot still surface — for the times you hire anyway.