Faster personalization from profile context
Resume/profile routes are part of the shipped dashboard flow and can support onboarding copy.
Why profile context helps
Cold-starting personalization is tedious: you forget half the libraries you touch weekly, and new hires may not yet know how your team spells “preferred stack.”
Resume and profile inputs give EraCode a plausible first guess at technologies, seniority, and focus areas so your first sessions feel relevant instead of generic.
What we use—and what we do not
We treat uploads as configuration signals for practice, not as an automated rating of how “good” an engineer you are.
You can always edit the derived technology list, remove inputs, or skip resume upload entirely and build the list by hand.
How it connects to the rest of the product
Better bootstrap means faster time-to-value for stack-aware challenges and, on paid tiers, smarter context when you connect GitHub for repo-backed work.
Use the Technologies dashboard when you want explicit control; use profile and resume when you want a faster first pass.
Good to know
Uploading a resume is optional; we use it to bootstrap technology suggestions, not as a hiring score.