I'm Jeb Seibel. I architect and build AI and data systems, usually as the only engineer on the project.
I've been writing software for twenty-five years. Most of that was spent on systems where being wrong was expensive — reporting infrastructure at Cisco processing billions of events a day, NLP and automation work on the Amelia AI platform, enterprise systems at Dell, Disney, and Tokyo Electron. Since 2024 I've done that work independently, through Seibel Consulting.
What I take on now tends to be AI applied to something that has to hold up: a verification platform whose findings get audited, an extraction pipeline whose output someone will dispute, a system that runs unattended and has to handle its own failures. The interesting engineering in those projects is rarely the model. It's everything around it.
How I work
One engineer, end to end. But don't get me wrong, I know other amazing engineers so if we need one I know how to find what you need. I am often a one person shop, but don't have to be. I do the architecture, the backend, the data layer, usually the frontend, and the deployment. You're not handed from a salesperson to a delivery team, and the person who scoped the work is the person who builds it.
Traceability by construction. If your output gets scrutinized, "the model read it off the PDF" isn't an answer. I design so every derived value can be traced back to the document it came from — that's a decision made at the start or not at all.
No vendor lock-in, mine or theirs. All code and infrastructure lives in your repositories and your accounts. I also build AI integrations to be provider-portable, so a price change or a deprecated model is a config change rather than a rewrite.
Straight answers. Including when an estimate was wrong, when a feature isn't worth building, or when your project doesn't need me.
Background
- Twenty-five years building production software; Java and AI specialization
- Mission-critical systems for Cisco, Amelia AI, Dell, Disney, and Tokyo Electron
- Architect, development manager, technical lead, and individual contributor
- B.A. in Computer Science and Communications, Trinity University
- Based in Colorado but looking to move. I'm working with clients anywhere
Before software took over, I wrote screenplays — three produced. It's less of a non sequitur than it sounds: most of this job is figuring out what a system is actually supposed to do, and then explaining it to people who don't share your assumptions.
There's a bit more about me, away from the work, on the Meet Me page.