About

I design systems that turn raw signals into operations that can run without constant supervision.

My work sits between strategy, automation, and production engineering. The value is not more tooling. It is building the operating layer that makes a business respond faster, follow through consistently, and stop leaking demand.

Operating philosophy

“Interesting systems are easy. Reliable systems that support real business decisions are harder, and that is the work I care about.”

What I optimize for

Response speed, workflow clarity, and systems that keep running after launch.

What I usually walk into

Good tools, weak handoffs, manual follow-up, and no reliable operating logic.

What I actually build

Revenue systems, automation infrastructure, and implementation that matches the business.

Background

Data scientist turned systems engineer. I got into AI infrastructure because I kept seeing the same problem: valuable data and operational signals with no usable system behind them.

Before building automation and AI systems, I worked across data science, data engineering, and machine learning engineering: production pipelines, model deployment, orchestration, and the infrastructure that makes data actually useful at scale.

The throughline is the same whether the surface problem is lead response, reviews, missed follow-up, or broken handoffs: useful signals exist, but the business does not have an operating layer that knows what should happen next.

Currently

Focus

Revenue systems and sales/marketing operations

Building

Workflow architecture, automation infrastructure, and agent-supported systems

Status

Available for projects

Approach

Systems-first, implementation-minded

The gap between an interesting technical prototype and a system that can run every day without constant babysitting is where I spend most of my time.

Roles

A systems view built from multiple technical disciplines.

The work is stronger because it is not coming from a single narrow automation lens.

01

Data Scientist

Statistical modeling, experiment design, insight extraction from complex datasets

02

Data Engineer

Production pipelines, ETL architecture, data infrastructure at scale

03

ML Engineer

Model training, deployment, embeddings, clustering, and NLP systems

04

AI Systems Engineer

End-to-end autonomous systems — from ingestion to insight to action

LanguagesPython · TypeScript · SQL
Data & MLpandas · scikit-learn · HDBSCAN · semantic embeddings · vector search · topic modeling
DatabasesPostgreSQL · pgvector · Redis · Supabase
InfrastructureDocker · DigitalOcean · AWS
OrchestrationCelery · Prefect · OpenClaw · asyncio
FrontendNext.js · React · Tailwind CSS

Who I work with

Businesses and operators who are serious about building systems, not just buying more tools. If you want production-grade workflow logic and infrastructure behind the customer journey, we should talk.

see how I work →