Role fit · Availability
The roles where I do my best work.
Open to full-time roles · Engineering Manager or Principal Engineer · Remote or hybrid Denver · US citizen, no sponsorship required · Available on standard notice
I do my best work leading a hands-on team that ships AI and modernized platforms on .NET, on Azure or AWS, in whatever industry you are in. 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 a hands-on Engineering Manager or Principal Engineer for an AI, platform, or developer-platform team.
- The stack is C# and .NET on Azure or AWS, and you are adopting agents or modernizing a platform.
- You want a leader who stays in the code: design, reviews, and delivery alongside a team of 5 to 10.
- You want adoption and delivery measured, and you will act on the number when it comes back low.
- Agents will touch production systems, so guardrails, evaluation, and observability matter. Any industry.
Weak-fit signals
- The role centers consumer, mobile, or growth product experience.
- You need a research ML engineer who trains and fine-tunes models.
- The role is Python-first AI engineering.
- 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.