Software · Systems integration · Applied AI · Solution architecture
I build technical systems around real operational problems.
I work from messy user problems through architecture, prototyping, integration, implementation, and validation. My background combines full-stack software development, data and AI systems, military operations, and the judgment to choose the simplest useful thing to build next.
Christopher Reece · Software Engineer | Solutions & Applied AI
Find the real problem
Start with users, decisions, constraints, and the workflow—not a predetermined technology.
Design the system
Make boundaries, trade-offs, interfaces, data flows, and failure modes explicit enough to test.
Build and prove it
Write the code, integrate the platforms, test the hypothesis, and keep the implementation close to users.
Selected work
Evidence over titles.
Building an Ontology-Backed Reporting Workflow
Built a working Foundry/Vantage reporting workflow used or tested by roughly 10 people, replacing a fragmented email-and-copy-paste process with structured creation, review, selection, and onward reporting.
Read case study → Distributed systems and systems integrationBuilding a Neutral Integration Bridge with Zenoh and ISA
Took a teammate's integration concept and built a working Java proof of concept that moves normalized records through Eclipse Zenoh, translates them into ISA constructs, and packages the path with repeatable validation and diagnostics.
Read case study → Applied AI researchKnowledge-Augmented Visual Question Answering
Built and evaluated a reproducible knowledge-augmented VQA pipeline across 5,046 validation examples. The KG branch did not improve baseline accuracy, but controlled experiments showed how gating reduced harm from unreliable external knowledge.
Read case study →Where I fit best
Hands-on roles between the user and the system.
I am most interested in forward-deployed engineering, solutions engineering and architecture, applied AI, integration, and product-minded software engineering—roles where technical judgment still ends in something being built.
My career began in U.S. Army military intelligence and evolved into software development, data platforms, technical discovery, and applied AI. That operational background is useful because I am comfortable working where requirements are incomplete, users disagree, systems have hard constraints, and the first technical request is rarely the actual problem.
Career journeyHave a problem that needs to become a working system?
I am preparing for a 2027 transition to the UK and am interested in engineering and architecture roles where I can stay close to the build.