Emil Fabel

Should you hire Emil Fabel?

I solve problems with code, machine learning, statistics and AI, mostly for financial services firms. In finance, every call gets a bull case and a bear case. Here are mine.

Email me
Role
AI and machine learning engineer
Right now
Founder and lead engineer at Pallisade Data
Studying
PGDip in data analytics and ML, done Feb 2027
Based in
Cape Town, South Africa
Emil Fabel in a navy suit and tie, arms crossed, in an office

The bull case

Why he’s worth hiring

  1. He solves the problem in front of him.

    A REIT fund manager’s team adjusted their target portfolio by hand every morning. He built the rebalancing pipeline now running beside that manual process, and is turning the routine into rules they approve line by line. For a debt-review firm keying creditor emails in by hand, he built a prototype that pulls out each figure with its source sentence and asks a person when it isn’t sure.

    Sources: Rebalancing engine, Debt-review prototype

  2. He tests ideas like a statistician.

    His research puts LLMs through a controlled experiment: 405 calls across three levels of context, 15 injected pipeline failures and three models, scored blind and analysed with two-way ANOVA, Tukey post-hoc tests and Holm correction. First result: more context makes every model’s fixes more specific.

    Source: Research project

  3. He knows the maths under the models.

    He wrote logistic regression from scratch in NumPy, with gradient descent and Newton-Raphson, for a class only 1.7% of the data belongs to: one in nine books it flags is a bestseller, against one in 59 by chance. His Bi-LSTM names the author of a 180-word passage with 0.685 macro-F1 across six authors.

    Sources: Logistic regression, Author attribution

  4. He builds for regulated finance by default.

    As his company’s POPIA Information Officer, he scopes what each AI system can access and where a human signs off. For a payments product, he mapped the SARB, PASA, FICA and FAIS requirements before any build began.

    Sources: Pallisade Data, Barrel

The bear case

What to weigh, with the bull’s reply

  1. He hasn’t worked inside a big engineering team yet.

    Bull’s reply: True, and it’s why he’s looking. He has shipped for paying clients on his own, and he grows fastest around senior engineers who push him.

    Source: About me

  2. His paid work leans on LLMs more than classical ML.

    Bull’s reply: True so far. His machine learning and statistics are real, just not yet paid for: the regression and classifiers he built from scratch, a designed experiment and a Kaggle imaging competition. It’s where he wants to go deeper.

    Sources: Logistic regression, RSNA competition

  3. He’s still studying until February 2027.

    Bull’s reply: Everything on this page was built alongside his studies, and his research answers a question from client work: does giving an LLM more context about a failing data pipeline actually produce better fixes?

    Source: Research project

Verdict: worth a conversation.

The evidence

What both sides argued from: my work, research and studies.

Work

Pallisade Data

Nov 2025 to present

Founder and lead engineer

AI and data solutions for financial services firms, Cape Town

  • Rebalancing engine, REIT fund manager. Multi-currency NAV and weights for each book, in a pipeline now running with the portfolio team alongside their manual process to validate outputs. Turning the manager’s morning routine (blend the books’ drift, round each line to the nearest 5 bps, let cash reconcile to 100%) into suggestions approved line by line. Scoped LSEG API ingestion for end-of-day pricing.
  • KYC automation, asset manager. A tool that automates client onboarding and KYC document checks.
  • Debt-review correspondence, prototype. For a firm whose creditor replies were keyed into the CRM by hand: reads each email, matches it to the right consumer account, extracts balances with the source sentence attached and holds them for a person to approve. When it isn’t sure, it names its candidates instead of guessing.
  • Research platform, asset manager. Built on a fork of the open-source TradingAgents framework and extended into a research platform whose answers cite their sources: a resolver that checks client documents first, then licensed data, then public sources, retrieval over vector embeddings and a job worker for long runs. Code on GitHub
  • Data reliability platform. Where Pallisade began: an AI copilot for data pipelines that answers questions about the warehouse, traces lineage across the stack and catches broken data before dashboards do. Built on Airflow and dbt. Code on GitHub
  • Operations system. The internal system I run Pallisade on: leads, outreach, follow-ups, projects and AI summaries. Code on GitHub
  • Peer review platform, engineering group. Building a web platform to manage and track peer reviews.
  • Delivery and governance. Map client processes before building, scope AI features with non-technical stakeholders, then build, deploy and hand over. Company POPIA Information Officer. Run public “AI in Finance” webinars.

GrowYourClinic

2025 to 2026

Co-founder and technical lead

Marketing automation agency for private medical clinics

  • Clinic automations. Workflow automations on GoHighLevel for lead capture, bookings and follow-ups, plus CRM automation and email deliverability.
  • Conversion tracking. Server-side Meta Conversions API tracking, so clinics could tie bookings back to the campaigns that drove them.
  • Client products. A dental practice platform, a veterinary communications tool and a fitness coaching app.

Research and projects

Do LLMs fix failing data pipelines better with more context?

2026

PGDip research project

A controlled experiment on LLM advice for broken dbt pipelines, building on Pallisade’s data reliability work. Fifteen failures injected into a dbt and DuckDB project, prompts at three levels of context, three models (two hosted, one local Llama 3) and three repetitions: 405 calls. Answers are scored blind and by two experts, with agreement measured by Cohen’s kappa, and checked automatically for hallucinated references. Analysis: two-way ANOVA per model with Tukey post-hoc tests and Holm correction, with Friedman tests as a rank-based check. First result: more context makes all three models’ fixes more specific.

Logistic regression from scratch

2026

PGDip coursework, NumPy and Spark

Predicting Amazon’s Best Seller badge across 133,102 Kindle books, where only 1.7% carry it. Logistic regression written in NumPy, with gradient descent and Newton-Raphson and verified with five checks. Features chosen with variance inflation factors and backward elimination on Wald p-values; models judged on PR-AUC, because accuracy rewards flagging nothing. Class weights were tested rather than assumed, and rejected because they hurt the ranking. With a threshold tuned on validation data, one in nine flagged books is a bestseller, against one in 59 by chance.

Author attribution with recurrent neural networks

2026

PGDip coursework, TensorFlow and Spark

Naming the author of a 180-word passage from style alone: 21,000 passages from 60 novels by six authors, split by book so no novel appears in both training and test. A TF-IDF baseline, then three LSTM versions, each change tied to a diagnosed weakness. Removing character names took away an easy shortcut, and a Bi-LSTM 74% smaller than the one before scored higher: 0.685 macro-F1, against 16.7% accuracy from always guessing one author.

RSNA Knee Abnormality Detection

Kaggle

Deep-learning medical-imaging competition, Efficiency Track

Balancing model accuracy against latency and compute cost.

Barrel

2026

Payments product design

A fuel-price-lock product: users prepay for litres at today’s price and redeem them with a card restricted to fuel merchant category codes. Issued under a sponsor-bank programme-manager model, with price risk hedged through an OTC swap. I mapped its regulatory requirements across SARB, PASA, FICA, FAIS and POPIA, and built the app prototype. Code on GitHub

sprint-recap

2026

Claude Code plugin

Ends each AI coding turn with a one-screen recap card, with the size of the change measured from git rather than reported by the model, and two questions that check you understood why the change works. Plain Node with no dependencies, covered by 96 tests. Code on GitHub

Pip & Us

Pre-launch

Consumer app

Couples share a virtual pet that keeps them accountable for training. Freemium subscription model; the waitlist is live and the audience is growing through TikTok.

Toolkit

Machine learning
Logistic regression from first principles, LSTMs and Bi-LSTMs, gradient boosting, feature selection, evaluation on imbalanced data (PR-AUC, threshold tuning); PyTorch, TensorFlow, scikit-learn, pandas, NumPy, SciPy, XGBoost, LightGBM
Statistics
Experimental design, linear and logistic regression, ANOVA with Tukey post-hoc tests and Holm correction, Friedman and Kruskal-Wallis tests, inter-rater agreement (Cohen’s kappa), effect sizes
AI and LLMs
LLM APIs and SDKs, multi-agent orchestration, tool calling and MCP integrations, RAG and retrieval design, embeddings and semantic search, prompt engineering, LLM evaluation
Data and cloud
Spark (PySpark), Airflow, dbt, DuckDB, BigQuery, Cloud Run (GCP), Microsoft Azure, Vercel, pipeline monitoring and data quality
Engineering
Python, SQL, TypeScript, Next.js and React, REST APIs and JSON, Git and GitHub, testing and code review, AI-assisted coding since 2022
Domain
Financial services, portfolio management, payments and fintech products, KYC and compliance workflows, POPIA and data protection, healthcare

Education

PGDip (Honours level), Data Analytics and Machine Learning

Feb 2026 to Feb 2027

IIE Varsity College

In progress: data science and machine learning

BCAD, Computer Science

Mar 2023 to Feb 2026

Varsity College

Graduated with distinction

Languages

English and Afrikaans

About me

I’d rather try something and learn from it than wonder about it. While studying, I’ve coached fitness clients, traded the markets, run online stores and built SaaS products. Not all of it worked, but every one taught me something about people, money and actually shipping. I love people: figuring out how they think, learning from them and helping wherever I can, which is a big reason I enjoy building for real users. Training keeps me disciplined, and I do my best work around people who push me. That’s exactly what I’m looking for in a team.