Software Engineer
I build backend systems for problems where correctness matters: engineering calculations, business rules and data that has to stay consistent. Now applying that to AI systems that need to be evaluated, observed and trusted.
Systems I built, with the problem, my role and what changed.
Technical configuration depended partly on spreadsheet calculators, technical tables and manual validation. The engineering rules needed one consistent, reusable implementation.
Engineering rules that lived partly in spreadsheets now run from one backend implementation.
APIs and services that encode business and engineering rules.
Relational models that keep data consistent as the rules change.
Where my work is heading: checking what AI systems produce against reference answers before trusting it.
Reproducible builds, tests and deployments that behave the same everywhere.
Why a system that computes from rules and then recommends from live data should keep those two steps apart, and how that changes persistence and testing.
Open to backend and software engineering roles, including work on applied AI systems. Remote.
sam.hernandezc103@