I love to teach. I post about #dataengineering and #mentalhealth daily. 

Many years of data engineering experience doing growth analytics at Facebook, security infrastructure at Netflix, and pricing and availability infrastructure at Airbnb. 

You can find me by looking up EcZachly on all social networks 

Join my Data Learning Platform https://www.dataexpert.io

Zach Wilson

Databricks is going to win “data” the same way that Meta won “social media” 

They are uniquely positioned because of the convergence of a few trends:

- the death of the data analyst
We are moving away from analytical architectures and towards action-oriented architectures. Instead of “the data engineer does ETL so analysts can look at it” it will be “the data engineer creates context for AI agents to do something” Actions will reduce timelines and speed up business velocity. Humans will no longer be the analytical bottleneck. 

- the crushing of data siloes 
Open table formats like delta and iceberg will make business able to do things that were previously though impossible! We’ll finally have all the context for our AI in one place. Entire business context + Agents = a waterfall of business value! 


I’m launching a paid Databricks boot camp on February 9th. Send me a DM with the word Databricks and I’ll get you the details!

Founder @ DataExpert.io | ADHD | 500k+ followers | Angel Investor

No alternative text description for this image

My perception of tech that nobody asked for:

- Postgres: extremely positive 
- SQL Server: you’re a boomer and slow 
- Spark: extremely positive 
- MongoDB: painfully neutral 
- NextJS: positive but only for solopreneurs 
- Microsoft Fabric: very negative, quality concerns
- Databricks: extremely positive after a war 
- Snowflake: surprisingly neutral after struggle 
- Trino: extremely positive 
- Presto: angry at Facebook for the divorce 
- Airflow: very positive, need Maxime’s autograph 
- Prefect: positive, Dr Pepper vibes 
- Iceberg: the most positive vibes
- Delta: Databricks PR approved positive vibes 
- Hudi: extremely fast and speedy vibes
- OpenAI: evil vibes 
- Anthropic: friendly vibes 
- Gemini: boomer AI vibes 

What tech would you add?

The first speaker lineup for the analytics engineering boot camp is going to be so amazing! 

These sessions are what truly separates my boot camp from “just another data course”

Data modeling is far from dead! It’s actually more relevant than ever. 

There’s been an interesting shift in the seas with AI. Some people saying we don’t need to do facts and dimensions anymore. This is a wild take because product analytics don’t suddenly disappear because LLM has arrived.

It seems like to me that multi-modal LLM is bringing together the three types of data:

- structured

- semi-structured

- unstructured

Dimensional modeling is still very relevant but will need to be augmented to include semi-structured outputs from the parsing of text and image data.

The necessity for complex types like VARIANT and STRUCT seems to be rising. Which is increasing the need for data modeling not decreasing it.

It feels like some company leaders now believe you can just point an LLM at a Kafka queue and have a perfect data warehouse which is still SO far from the actual reality of where data engineering sits today

Am I missing something or is the hype train just really loud right now?

Partitions no longer being immutable in formats like Iceberg and Delta is a good thing. This new power invites a lot of bad practices:

	•	Duplicates creeping in from sloppy upserts
	•	Non-deterministic reprocessing that silently rewrites history
	•	“Fix it in place” mentalities instead of fixing upstream contracts
	•	Broken idempotency assumptions across pipelines
	•	Hidden backfills that invalidate downstream aggregates
	•	Debugging nightmares when yesterday’s data isn’t actually yesterday’s data
	•	Teams treating tables like mutable OLTP systems instead of analytical logs

This is exactly why functional data engineering still matters.

Pipelines should behave like pure functions:
	•	same inputs → same outputs
	•	explicit side effects
	•	time and state modeled, not implied

Mutable partitions don’t remove the need for discipline. They raise the bar for it.

Iceberg and Delta give you scalpels.
Functional thinking is what keeps you from using them like chainsaws

DataExpert.io got on the banned list for Outlook and Hotmail a few months ago. 

Microsoft has a "Delisting service" that you submit your IP through to get unbanned. 

They email you a link to "confirm" 

Google says "this link looks dangerous"

IT IS FROM MICROSOFT (see the no-reply at microsoft)

Email in 2026 is a cursed protocol that I will never understand

I'm doing a live with Karan Dwivedi to talk about a cybersecurity boot camp that is launching on January 9th! 

This boot camp has an amazing capstone project where you do all of these on a company server!
- threat modeling
- detection engineering
- preventative controls 

Don't miss this webinar tomorrow!

January 9th Cybersecurity Boot Camp Webinar

My ex in 2018 broke up with me because “video games are for losers” 

Video games are consistently ranked as the least attractive hobby from a woman perspective.  

This reality of the world sits so weirdly with my lived reality.  

In 2017, I was 15th in the world in Halo 5. 15th out of 10 million players or the top 0.000015% of that video game. 

In 2026, my LinkedIn account sits at about the same percentile standing as my Halo 5 account did and makes me millions per year. 

My strategy to achieve both of these results was exactly the same. Relentless obsession every single day for 3-4 years. 

I want to be the very best at whatever I put my mind to. Video games are an amazing training ground for competition.

Using video games as a tool to build your competitive or creative drive is a powerful thing. 

Using video games as an escape from reality can be damaging over the long term and this is what women are picking up on 

Becoming a winner in a low stakes environment makes it easier to become one in a high stakes environment

The number one thing holding people back is thinking they need to "be ready" to start. Great post Mike Pinckney!

A simple truth most people avoid:

Results follow belief, not the other way around.

A few reminders worth sitting with:
• Belief precedes action
• Doubt often wears the mask of logic
• You already have power to move
• Responsibility can’t be outsourced
• Information without belief doesn’t execute

You don’t need certainty to start.
You need enough belief to take the next step.

I help entry-level, non-technical professionals get their first data analyst role | Data Analyst @RBC | Data Career Coach

I help immigrants and career-switchers land analyst roles—without burning out on certificates.

By day I build decision-grade analytics (currently at Autodesk). By night I run Data Career Compass, where we treat your job search like a product launch:
Market → Positioning → Portfolio → Distribution → Interviews.

My POV:
Most candidates try to add more tools. Winners learn to package their value. Your portfolio isn’t a gallery; it’s a sales page for your judgment.

Receipts:

→ Professionals land interviews by aligning projects to business outcomes (not toy datasets).

→ My frameworks have been used across finance, tech, and education to translate experience into results.

→ Built data products and controls in regulated environments (RBC Capital Markets) that leaders rely on daily.


What you’ll get here:

→ Weekly breakdowns of real projects (SQL, Python, dbt, DuckDB, Looker/Tableau/Power BI).

→ Storytelling patterns that turn insights into action.

→ Templates that remove friction: portfolio briefs, stakeholder one-pagers, interview scorecards.

Coming February:

I’m launching a coaching program designed for mid-level and senior professionals ready to transition into analytics.

This isn’t an entry-level bootcamp—it’s a career accelerator that helps you reposition your existing experience, communicate business value, and step confidently into data-driven roles.

Work with me:

↳ Cohorts + 1:1 coaching → DM “HIRED”

↳ January program for mid/senior professionals → DM “JANUARY” for early access

↳ Guest workshops for teams and communities → DM “WORKSHOP”


I build analysts who think like product managers and communicate like consultants.

Peter Ndiforchu

Most candidates think they’re being evaluated on what they built.

They’re not.

When you explain a project, hiring managers are quietly assessing something much deeper.

Here’s what’s actually happening behind the scenes 👇

1️⃣ Can you think in business outcomes—or just tasks?
If your story starts with “I used SQL to…” and ends there, that’s a red flag.
They’re listening for why the project existed and what changed because of it.

2️⃣ Do you understand the problem—or just the solution?
Strong candidates explain the constraint, the tradeoff, and the decision.
Weak ones jump straight to the dashboard.

3️⃣ Can you simplify complexity?
If you can’t explain your project to a non-technical stakeholder in 60 seconds,
they assume you’ll struggle in real meetings.

4️⃣ Did you drive the work—or were you just assigned it?
Ownership shows up in language:

“I noticed…”

“I proposed…”

“I pushed back when…”


That’s leadership without the title.

5️⃣ Do you sound like someone they can put in front of executives?
Clarity. Structure. Calm confidence.
That’s what earns trust.

Here’s the uncomfortable truth:

Two candidates can build the same project.
Only one gets the offer—because they frame it differently.

Your projects don’t get you hired.
Your interpretation of them does.

If this resonated, next time you explain a project, ask yourself:
“Am I telling a story—or reciting a task list?”

Helping Non-Technical Professionals Build Data-Driven Careers That Travel Globally | Data Career Strategist | Senior Data Analyst @ Autodesk

What Data Hiring Managers Really Evaluate on Interviews

Most candidates know the STAR method.
Very few use it in a way that actually signals seniority in data roles.

Here’s how hiring managers experience it 👇

The STAR method for data roles (with a real example)

S — Situation
❌ Weak: “We didn’t have good dashboards.”
✅ Strong: “Sales leaders were making weekly decisions using spreadsheets pulled manually from three systems.”

Why this matters:
You’re showing business context, not just a messy data problem.

T — Task
❌ Weak: “I was asked to build a dashboard.”
✅ Strong: “I was responsible for creating a single source of truth that leadership could trust for forecasting.”

Why this matters:
This reframes you from executor to owner.

A — Action
❌ Weak: “I used SQL and Tableau.”
✅ Strong:
“I audited existing tables, wrote validation queries to reconcile numbers across sources, aligned definitions with Sales Ops, and designed a dashboard focused on decision-making—not vanity metrics.”

Why this matters:
Tools are expected. Judgment is not.

R — Result
❌ Weak: “They liked the dashboard.”
✅ Strong:
“Forecast variance dropped by 18%, manual reporting time was reduced by 6 hours per week, and the dashboard became the default reference in leadership meetings.”

Why this matters:
Impact beats effort. Every time.

The real mistake candidates make:
They treat STAR like a storytelling template.
Hiring managers hear it as a decision-making framework.

In data roles, STAR isn’t about what you built.
It’s about:

How you understood the business

How you made trade-offs

How your work changed behavior


If your STAR answers don’t reveal those signals,
you’re underselling yourself—no matter how strong your skills are.

📌 Save this before your next interview.

How I went from Cameroon → Canada → a US data role (without ‘local experience’).

When I moved, I assumed the biggest hurdle would be visas, credentials, or “local experience.”

It wasn’t.

The real question global recruiters were silently asking was:
“Who can vouch for this person when we can’t observe them directly?”

Here’s what made the difference on my journey 👇

1/ Relationships reduce hiring risk
Recruiters outside your country can’t see your work day-to-day. They rely on people they trust to validate your judgment and impact.
I focused on building genuine connections with:

Hiring managers

Senior data practitioners

People in the ecosystem who could confidently say,

 “I’ve worked with him. He delivers. I’d hire him again.”

2/ Visibility beats invisibility
I didn’t just rely on a resume. I made my work and thinking visible by:

Sharing real projects publicly

Discussing trade-offs and decisions

Engaging with communities in LinkedIn, Slack, and Discord

This gave recruiters context before even meeting me.

3/ Skills matter, but signals win
SQL, Python, Excel—all necessary. But what got me hired was showing:

Structured thinking

Clear communication of impact

Ability to navigate ambiguity

Coupled with endorsements from people who could vouch for me, geography became irrelevant.

Global hiring isn’t about ‘local experience’—it’s about trusted signals.

Ask yourself: “Who in this market can confidently vouch for my work?”

That’s the real game.

Cameroon → Canada → a US data role

The first time I realized hiring expectations weren’t universal…
I thought I had done everything right.

Strong technical skills.
Solid projects.
Clear results.

Then I walked into an interview outside my home market and something felt off.

They weren’t impressed by what tools I knew.
They kept probing how I worked.

Questions like:

“How did you influence stakeholders who didn’t agree with you?”

“What trade-offs did you make under pressure?”

“Who trusted your judgment and why?”


That’s when it clicked.

In some markets, hiring is about capability.
In others, it’s about credibility.
And in global roles, it’s about signal alignment.

Same resume.
Same experience.
Very different evaluation lens.

I stopped optimizing for: 
❌ tool checklists
❌ keyword stuffing
❌ “local experience” myths

And started optimizing for: 
✔ decision-making stories
✔ business judgment
✔ proof that someone would trust me in the room

That shift changed everything.

Global hiring isn’t harder.
It’s just calibrated differently.

If you’re preparing for roles beyond your home country, ask yourself: Are you proving skills…
or earning confidence?

Because globally, confidence hires before competence.

Here’s the uncomfortable truth most candidates don’t hear early enough:

Most data portfolios aren’t evaluated as “work.”
They’re evaluated as signals.

And most of them send the wrong ones.

I’ve reviewed a good number of portfolios as part of the hiring team.
The pattern is consistent:

What candidates show:
• Dashboards with no business question
• Kaggle-style analyses disconnected from real decisions
• Tools-heavy walkthroughs (“I used SQL, Python, Tableau…”)
• Perfect charts that solve imaginary problems

What hiring managers are actually scanning for:
• Can this person frame a messy business problem?
• Do they understand tradeoffs, not just techniques?
• Can they explain why something mattered — not just how they built it?
• Would I trust them to influence a decision with imperfect data?

Here’s the part most people miss:

A portfolio isn’t proof of skill.
It’s evidence of judgment.


That’s why two candidates can use the same dataset —
and only one gets a callback.

The one who: 
• Anchors the project to a real stakeholder decision
• Explains assumptions and constraints
• Shows what they didn’t do and why
• Communicates impact in plain business language

Strategic shift to make today:

Stop asking, “How do I show more tools?”
Start asking, “What decision does this help someone make?”

That question alone will put your portfolio ahead of 90% of applicants.

If you’re building a portfolio right now, build it like you already have the job — not like you’re trying to pass a course.

taplio

The Battle

Zach Wilson

Peter Ndiforchu

Followers

Posts

Engagements

Likes

Performance ScoreZach Wilson's LinkedIn Performance

Performance ScorePeter Ndiforchu's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Zach Wilson

Peter Ndiforchu

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Zach Wilson's LinkedIn Performance

Performance ScorePeter Ndiforchu's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreZach Wilson's LinkedIn Performance