The JSON-as-source-of-truth call is the interesting part here. Most resume builders lock the data inside a WYSIWYG editor, so tailoring for a second role turns into copy-paste drift between versions. Question: is the schema documented and exportable, i.e. could someone keep the JSON in their own repo and use CoreCV purely for rendering plus the ATS check?
Welcome to StartupBase
Join a community of founders sharing their products and discovering what others
are building.
Email sign-in is for existing accounts. New here? Use Google, LinkedIn, or X above
— your account is created automatically.
Continue with email
Enter the email address on your existing account and we'll send you a one-time
sign-in code. This does not create an account — to sign up, go back and
continue with Google, LinkedIn, or X.
Enter the verification code we sent to your email address.
Continue with Google
Continue with LinkedIn
Continue with X
The JSON-as-source-of-truth call is the interesting part here. Most resume builders lock the data inside a WYSIWYG editor, so tailoring for a second role turns into copy-paste drift between versions. Question: is the schema documented and exportable, i.e. could someone keep the JSON in their own repo and use CoreCV purely for rendering plus the ATS check?