Adopting customizable technology categories
A 3-step walkthrough: configure categories, verify them in the editor, then update and verify your template.
Written By Łukasz Myśliński
Last updated 17 days ago
This walks through rolling out custom technology categories end to end — from configuring them, to confirming they actually show up where you expect.
1. Configure your categories
Go to Settings → Organization and set up the Tech categories you want — add, rename, reorder, or delete to match how your team thinks about skills. Give each one a clear, specific description; it's also what our AI extraction uses to sort technologies into it. See Customizing technology categories for the full walkthrough.
2. Upload a sample profile and check the editor
Upload a CV that covers the kinds of skills you want categorized, and let it convert into a profile. Open the profile and expand the Technologies section in the editor — this is where you verify categorization, not the template.
Check the editor first, not the exported document. Templates don't automatically pick up new categories — that's step 3.
Confirm each technology landed in the bucket you expected. If something's miscategorized, it usually means the category's description could be more specific — tweak it in Settings and re-upload to test again, since categorization runs fresh on each conversion.
3. Update your template and verify in the template preview
Categorization in the editor and AI extraction happen automatically, but your exported CVs don't reflect new categories until your template is updated to reference them. Open your template for editing and add a reference to category_tech.<identifier> for each category you want rendered — see the Template variables reference for exact syntax.
Then use the template preview (Templates → open a template → Check your template) to confirm it actually works: the Technologies section shown there uses your organization's live categories, the same as the profile editor, so you can drag a technology straight into the category bucket you're testing and re-render. If your template references the category correctly, it'll show up in the rendered PDF preview on the right; if not, nothing will appear for that category — and the editor also flags this directly with a "Not in template" badge next to any category your currently selected template doesn't reference, right in the preview.
The template preview loads a fixed sample profile, not your real data — it won't have anything pre-filled under a newly added category. Manually add a technology to that bucket in the preview editor before rendering to actually test it.
Once the rendered PDF looks right, save the template.