Team · Lead, Database Integrity (CCS-DB)
Jordan Pearce
Data Engineer
“A larger database isn’t a better database. The same dish having ten conflicting entries is a worse signal than one accurate one.”
Who is Jordan Pearce?
Jordan runs the database benchmark — the unglamorous but load-bearing part of the protocol. He maintains the 200-item reference dish list (Western, Latin, East Asian, South Asian, Middle Eastern and African cuisines, weighted by the global recipe-traffic distribution), reconciles each app's database lookups against USDA FoodData Central and NCCDB, and runs the nutrient-completeness checks across the same item set. The infamous "the same dish has ten conflicting entries" finding is his. He also owns the quarterly re-pull of every reference dataset and is the gatekeeper for any change to the reference dish list.
What does Pearce specialise in?
- USDA / NCCDB benchmarking
- Database integrity testing
- Regional cuisine coverage
- Nutrient-completeness audits
Where did Pearce study?
- BSc, Software Engineering — University of Manchester (2017)
What did Pearce do before The Calorie Counter Standard?
- Data Engineer, food-supply analytics company (2020–2023)
- Backend Engineer, recipe platform (2017–2020)
What has Pearce published?
- Pearce J., Chen M. "Reproducible accuracy benchmarks for consumer health AI." Internal preprint, 2024.
Which CCS calorie counter protocols does Pearce own?
Jordan owns the following CCS scoring protocols. See the methodology page for what each measures.
CCS-DB
Reviews by Jordan
- Cronometer Review — 78.4/100
- MyFitnessPal Review — 71.6/100
How do you contact Pearce?
For database audit raw data, email research@calorie-counters.com.