Ilich Briceño — Senior Data Platform Engineer · PT / EN / ES

Your data migration stalled. I'm the senior engineer who finishes it — based in Brazil, working your hours.

Not a staffing pool. Not a headcount request. When a Databricks or Microsoft Fabric migration is stuck, over budget, or nobody trusts the dashboards anymore, I step in as the accountable senior engineer — timezone-friendly overlap with US/EU teams, direct communication, no account-management layer between you and the work.

Book an initial diagnostic See case studies

Sound familiar?

If this sounds familiar, we should talk

No end date in sight

A Databricks-to-Fabric (or Fabric-to-Databricks) migration has been "in progress" for months with no real completion date.

Capacity costs outpacing adoption

Capacity costs (F64 or equivalent) have grown faster than platform adoption.

Nobody can explain the current state

A previous vendor or internal team delivered something, but nobody can confidently explain the current state.

The business side stopped trusting the data

The business side has quietly stopped trusting the dashboards.

If two or more of these are true, the gap isn't technical knowledge on your team's side — it's a lack of one person who owns the problem end-to-end and has done this exact rescue before.

Why nearshore, why me

Nearshore staffing solves availability. I solve trust.

Nearshore staffing solves an availability problem — you get a person or a team, on your timezone, at a lower cost than local hire. That's real, but it doesn't solve a trust problem. A stalled or broken migration isn't a capacity gap you fill with more hands; it's a judgment gap that needs one senior person accountable for the outcome.

Nearshore staffing platforms

Staff augmentation

A vetted engineer or team, billed by hour/headcount
Best for ongoing capacity, greenfield build with clear spec
Accountability distributed across a bench of engineers

Loucoud

Diagnosis-first, scoped rescue

One senior engineer who owns the outcome directly
Best for stalled migrations, cost overruns, "nobody trusts this data" situations
One accountable person, backed by a registered Brazilian company

How engagements start

Initial diagnostic

I review pipelines, capacity cost, semantic modeling, and governance, and return a clear-eyed written assessment: what's salvageable, what needs rebuilding, and a realistic estimate.

Delivery: written diagnostic · 1–2 weeks

Prioritized rescue plan

Not everything needs a rebuild. I sequence the work by what most affects cost and business trust first.

Execution with visibility

Regular checkpoints, living documentation, no black box.

Handoff or ongoing partnership

Your team ends up able to run the platform independently, or we continue working together — your call.

Case studies

Two enterprise rescues, under real pressure

Full write-ups are currently published in Portuguese only — English versions are on the roadmap. Reach out and I'll walk you through either case directly.

See case studies (Portuguese)

Based in Brazil

Built for how you already work

Timezone overlap with US East/West and EU business hours, fluent English, available for live meetings. I work as a registered Brazilian company — you're contracting a real business, not an individual freelancer with no legal backing, while still working directly with the person who does the work.

Contact

Start with a diagnostic, not a sales call

Before any proposal, I need to understand the actual state of your platform. The first conversation is diagnostic, not a pitch.

Schedule a diagnostic Send an email