posted an update —

While waiting for judging, I’ve been building out the core infrastructure to address a systemic inefficiency: the "resume tax."

Every platform uses a proprietary schema, forcing us to re-format the same data hundreds of times. This redundancy costs millions of person-hours and unnecessary server cycles. I believe a shared, structured interchange format could drastically cut that waste.

To turn this concept into a practical tool, I’ve spent this time developing:

resumejson (Dart/Flutter package): By building this in Dart, I’m leveraging the work of the Google Dart and Flutter teams to ensure this logic runs literally anywhere: Web, Mobile (iOS/Android), Desktop (Windows/macOS/Linux), Server, and even CLI.

The Open Schema: A normalized data model that treats professional history as portable data rather than a static document.

The goal is a vendor-neutral alternative that lets you write once and render anywhere. We should be spending our energy on our careers, not on reconciling semantically identical data.