How I work
Engagement Framework & Boundaries
To maintain maximum focus and deliver world-class technical results, I operate under a rigid, highly structured working model. I value structural clarity, rigorous logic, and absolute efficiency over corporate social rituals.
Preferred
What I take on
The situations where I do my best work, and where the return on your investment is most likely to be clear.
-
01
Highly Challenging Technical Problems
When your existing engineering team is stumped by statistical anomalies, model performance decay, or high-latency inference bottlenecks. I bring deep expertise and a fresh mathematical perspective.
-
02
Fully Remote, Async-First Work
Collaboration via Slack, email, GitHub issues, and comprehensive Markdown documentation. No daily standups, no video marathons — just structured written progress and robust code.
-
03
High Trust & Autonomy
You define the objective function and success criteria, then step back to let me engineer the solution. I deliver regular written updates and a complete technical artifact at the end.
-
04
Well-Defined Scope
Engagements focused on specific technical deliverables, statistical audits, or architecture refactoring. Clear beginning, middle, and end — typically 4 to 12 weeks.
Boundaries
Where I draw the line
Saying no clearly is the only way to say yes well. These are the lines I don't cross — for your benefit as much as mine.
Synchronous Meetings
I do not join daily stand-ups, brainstorming video-chats, or multi-hour status calls. Zero exceptions. My communication is written, structured, and archived.
Office Politics & Consensus-Building
I do not design models to satisfy executive optics, nor do I navigate internal political battles. I focus solely on what is technically and mathematically optimal.
On-Site Requirements
I operate 100% remotely. I will not visit your office under any circumstance. My setup is optimized for deep async work across time zones.
Ad-Hoc Fire Drills
I work on structured schedules with clear scope. Ad-hoc, high-adrenaline midnight requests are incompatible with my operational model. Planning prevents crisis.
Process
The shape of an engagement
-
01
Conversation
A 30-minute call or written exchange to see if the problem fits. No prep on your side required.
-
02
Proposal
Within a week, a written proposal: scope, approach, deliverables, and a fixed fee.
-
03
Kickoff
A structured working session to align on the question, the constraints, and the success criteria.
-
04
Work
Weekly written updates, a shared document, and a single standing call. No slide decks — just code, math, and clear thinking.
-
05
Handoff
A clear memo, a recorded walkthrough, and an invitation to reconnect in six months.
Ready?