Role fit · Availability
The roles where I do my best work.
Open to full-time roles · Remote or hybrid Denver · US citizen, no sponsorship required · Available on standard notice
I do my best work where AI has to ship into systems with money, regulators, or auditors behind them. The signals below let you check your role in a minute. If it is close, send it anyway.
Fit signals
These weigh the outcome you are hiring for and your must-haves. Keyword overlap counts for very little.
Strong-fit signals
- You need somebody to found or lead an AI engineering group in a regulated or traditional firm.
- The work is governance, human-in-the-loop architecture, observability, and shipping.
- You want adoption measured, and you will act on the number when it comes back low.
- The domain is fintech, lending, crypto, healthcare-adjacent, or otherwise audit-heavy.
- You want production agentic engineering that survives change control.
Weak-fit signals
- The role centers consumer, mobile, or growth product experience.
- You need a research ML engineer who trains and fine-tunes models.
- You are hiring a prompt engineer, narrowly defined.
- The core requirement is something with no evidence here, and you need certainty now.
What you will hear back
Send a role and you get one of four answers, usually in a short paragraph.
Strong evidence of fit
Multiple relevant artifacts, no critical known gap. The case studies map directly to your must-haves.
Plausible fit worth discussing
Adjacent evidence, with specific questions to resolve before either side spends real time.
Insufficient evidence
The documented work cannot support a reliable conclusion. That is a distinct answer from "no."
Likely poor fit
A central requirement conflicts with documented experience or a published gap. I will tell you not to spend the hour.