Principal Solutions Architect — discovery to working prototype to production integration.
I have been building software for more than 25 years, across product companies, banks, healthcare systems, and high-volume consumer events. The constant is the same seat: sit with the customer, make the technical risk visible, ship a proof, then stay through go-live.
LinkedIn · GitHub · Minneapolis, MN
- Lead technical discovery with executives and with the engineers who have to implement the design
- Build prototypes and proof-of-concepts that a buyer can run, not just slides they can watch
- Design integrations across mobile, server, and edge stacks, then support the live event or launch
- Turn field work into reusable demo environments, playbooks, and product feedback
- Mentor solutions engineers and architects; write the enablement material I wish I had on day one
Pre-sales and post-sales are the same job when the prototype has to survive production.
Discovery → scoped workflow → working prototype → integration → launch → playbook back to product
Comfortable in a C-suite review and equally comfortable pairing on a failing integration. I would rather show a small running system than argue an architecture from a whiteboard alone.
| Layer | Tools |
|---|---|
| Languages | Python, JavaScript / TypeScript, C# / .NET, SQL |
| Platforms | AWS, Azure, Docker, Kubernetes |
| Delivery | APIs, CI/CD, demo environments, integration adapters |
| Motion | Technical discovery, POC development, live-event support, customer enablement |
- AWS Certified Machine Learning Engineer – Associate
- AWS Certified Solutions Architect – Associate
- AWS Certified AI Practitioner
Public reference repositories are being published here on purpose: small, documented systems that show how I think about workflow, rules, and integration — not tutorial dumps.
Customer implementation work stays private.