Understanding modules
A module is a single skill domain from a single job, written as a self-contained paragraph. It's the core unit of everything ModuleHire does.
Why modules instead of a full resume?
A traditional resume forces you to commit to one story. If you apply for a community-focused role and a product-focused role on the same day, you're either writing two resumes from scratch or sending the wrong one. Modules solve this by separating your experience into its parts — so the right combination can be assembled for any role in seconds.
Think of your module library as a content bank. Each module is a piece of writing about something you've actually done. When you apply to a job, the system selects the 6–10 pieces that best match the role and assembles them into a coherent document.
Anatomy of a module
Title
A short label for the skill domain — for example, Community Building & Engagement or Developer Onboarding Programs. This is used for display in your library and as a section heading in the output resume.
Content
The body of the module — a paragraph or two describing the work you did in this specific domain, at this specific company. Written in first-person past tense. The output resume uses this content almost verbatim, with light rewording to match the JD's language.
Metadata
Each module carries a source company, job title, date range, employment type, weight, type, and a set of tags. This metadata powers the matching engine — it's what lets the system know a module is relevant to a VP-level community role at a growth-stage company, for example.
Module weight
Weight determines how the matching engine treats a module:
Anchor — Always included in the stack regardless of match score. Use this for your most important, defining experience. Most resumes should have one or two anchors.
Strong — Included when its match score is 65 or higher. This covers the core competencies you want on most applications.
Supporting — Included only when its match score is 80 or higher. These are specialist modules that are highly relevant to some roles and irrelevant to others.
Your module library over time
The library grows as you upload more resumes or add modules manually. Older modules stay in the library indefinitely — they won't appear in generated resumes unless the matching engine selects them. As your career evolves, you can update content, adjust weights, or archive modules you no longer want included.