Apache Spark · Databricks · Delta Lake

Make your Spark workloads faster, steadier, and cheaper to run.

Probatum helps data teams find the real bottleneck in slow, failing, or expensive Spark and Databricks pipelines — and fix it with changes your engineers understand and can maintain.

Discuss your workload Explore services

Independent practice based in São Paulo · English and Portuguese

Where an assessment starts

Stage timeline and task skewSpark UI
Shuffle volume per stageSpark UI
Join strategy in the physical planEXPLAIN
Spill, GC, and memory pressurelogs
File sizes and table layoutDelta
Compute sizing vs. actual useconfig

Evidence first. Recommendations second.

I. Problems we solve

If one of these sounds familiar, we should talk.

cost

Compute spend keeps climbing

…and nobody can say with confidence which jobs drive it, or why.

deadline

A critical pipeline misses its window

Downstream reports and teams wait while a job runs past its completion deadline.

scale

Data grew. The pipeline didn’t keep up.

Jobs that used to finish comfortably now run for hours.

reliability

Failures that come and go

Out-of-memory errors, lost executors, SQL timeouts — often “fixed” by a retry, until the next time.

migration

Migrated to Databricks, still slow

The move is done, but runtimes and costs aren’t where the team expected.

bottleneck

One stage the team can’t crack

Your engineers are capable — they need a second specialist on a hard problem.

II. Services

Start with a diagnosis. Then fix what matters.

Most engagements begin with a focused assessment, so changes are based on evidence instead of guesses.

Start here

Spark Performance Assessment

A focused review of the workloads that hurt most. Execution plans, Spark UI evidence, logs, configuration, and data layout — read to find what is actually slowing them down.

You receive

— Bottleneck analysis per workload

— Prioritized recommendations

— Likely impact and tradeoffs of each

— A practical implementation plan

Workload Optimization Sprint

Implement and validate the agreed improvements on a defined set of pipelines, measured against a baseline set together.

Typical areas

— Join strategies and broadcast joins

— Shuffle, partitioning, and skew

— Memory pressure and spill

— File sizes and Delta table layout

— Right-sized compute configuration

Troubleshooting & Technical Guidance

For a slow, failing, or unpredictable workload your team is stuck on. We find the cause together, and you keep a repeatable diagnostic process for the next one.

Good fit for

— Recurring or intermittent failures

— Hard-to-explain slowdowns

— A second opinion on a fix in progress

Scheduled engagement — not on-call or 24/7 incident support.

Also available Databricks & Delta Lake review — pipeline patterns, table layout, SQL performance, platform configuration. Team enablement — workshops or pairing so your team can maintain the improvements.

III. Experience

Five years building Spark pipelines — and now debugging them in production.

That combination is the point: reading what a job does at execution time, and turning it into a change an engineering team can actually ship.

Today

Production diagnosis at scale

Investigating and improving mission-critical Spark and Databricks workloads — including jobs that read petabyte-scale tables. Long-running jobs, shuffle and partition sizing, join strategy, UDF memory issues, SQL timeouts, JDBC, Unity Catalog access, and Delta Lake layout.

2021 — 2025

Data engineering in financial services

Building and migrating pipelines for large banking platforms: batch frameworks across DB2, Oracle, and Delta Lake; Medallion and Data Vault models for risk and regulatory reporting; Delta Live Tables; and the migration of legacy Cloudera pipelines to Azure Databricks.

Selected results from in-house roles

100+critical banking pipelines migrated from on-prem Cloudera to Azure Databricks
~30%lower cost after that migration
~55%faster processing after that migration
~40%fewer production incidents after an automated testing framework (~90% coverage)

Outcomes of team initiatives from earlier in-house roles in banking, as measured internally. They describe past work, not consulting results, and are not a forecast for any client. No customer or employer confidential information is shared.

IV. How I work

Measured against your baseline, not a promise.

  1. 1

    Understand

    The workload, who depends on it, and what the problem costs the business.

  2. 2

    Scope & evidence

    Agree on scope and the success metric, and collect the technical evidence.

  3. 3

    Diagnose

    Find the bottlenecks and rank changes by impact, effort, and risk.

  4. 4

    Improve

    Implement the agreed changes, or guide your team through them.

  5. 5

    Compare & hand off

    Measure against the baseline and document everything for your team.

What we measure depends on the problem: runtime compute cost per run failure frequency throughput on-time completion

No number is quoted before the workload has been reviewed. After the assessment, you’ll know what’s realistic and why.

V. About

A specialist, not an agency.

Probatum is Latin for “tested, proven” — the standard every recommendation here has to meet.

Probatum is a one-person practice. I’m a data engineer in São Paulo who has spent his career on Spark pipelines — first building and migrating them for one of Brazil’s largest banks, now helping teams investigate and fix them in production. I like problems where the answer is in the execution plan, not in a bigger cluster.

You work directly with the person doing the analysis, in English or Portuguese.

Current certifications

Databricks Certified Associate Developer for Apache Spark

Databricks Certified Data Engineer Associate

Databricks Certified Data Analyst Associate

Microsoft Azure Data Fundamentals · Azure Fundamentals

Credential verification available on request.

Education

B.Sc. Computer Engineering

MBA, Data Engineering

Probatum is independent. It is not affiliated with, endorsed by, or a partner of Databricks, and engagements do not include vendor support, privileged access, or any employer or customer confidential information.

VI. FAQ

Common questions

Which platforms do you work with?

Apache Spark (PySpark and Spark SQL) and Databricks, including Delta Lake and Databricks SQL. Most platform experience is on Azure. If you run Spark elsewhere, describe your setup and you’ll get an honest answer on fit.

Can you work alongside our existing team?

Yes — that’s the default. I work with your engineers, explain the reasoning behind each change, and leave documentation so the team owns the result.

What do you need to get started?

A short description of the workload, what’s going wrong, and why it matters. Useful evidence includes Spark UI or event logs, query plans, job and cluster configuration, and table sizes. Exactly what is shared, and how, is agreed during scoping.

How are improvements measured?

Against a baseline agreed before anything changes — runtime, compute cost per run, failure frequency, throughput, or completion within your processing window, depending on the problem.

Do you implement, or only recommend?

Both. An assessment ends with prioritized recommendations and a plan; an optimization sprint implements and validates them. Choose either, or both in sequence.

VII. Contact

Tell me about the workload.

Send a short note: what the pipeline does, what’s going wrong, and what it’s costing you. You’ll get a reply on whether Probatum can help and a suggested first step.

Emailprobatumdata@gmail.com