I'm an AI infrastructure engineer. I build systems that take a signal and route it to the right backend — compute, agents, payments, quantum hardware.
Your XYZ role is the same problem in a different dialect. A prospect signal has to find the right play, the right person, and the right channel, fast, with almost no headcount. You don't need a marketer who learned AI. You need someone who already thinks in pipelines.
Every one of these is the same shape: a signal comes in on one side, gets classified and enriched, and goes out to the cheapest-viable destination. The category changes. The pattern doesn't.
The JD describes a pipeline: prospect intelligence → enrichment → outreach → CRM. That's a router. Pick a signal below and watch it move through the stack. Every stage is something I can stand up in a week with Claude, a handful of APIs, and a GitHub repo full of markdown.
I spent five years in risk management at State Farm — evaluating complex scenarios, managing claims portfolios, making data-driven calls at scale. Then I left to build AI infrastructure because I could see what was coming and wanted to build the rails, not just use them.
Since then I've shipped twelve tools, opened twenty-four repos, filed a patent on a quantum consensus protocol, and built the only Western bridge to Chinese quantum hardware.
What that profile actually says: I finish things. I am deeply comfortable with ambiguity, terminals, APIs, markdown repos, and systems that didn't exist yesterday. The JD calls for someone who "does two impossible things before noon because nobody told them it was hard." I have been that person, alone, for the last twelve months.
Every line in your “What You Will Do” is something I've already built an analogue of. Here's the translation table.