An interactive CV for roles where the CV itself is the demo
For a front-end developer, a motion designer or a creative technologist, a CV you can explore is a work sample in its own right. For almost everyone else, a recruiter wants a clean page they can read in a minute and a PDF that survives an applicant tracking system. Build the interactive version as an extra, never the only version, and keep the facts identical in both.
Who an interactive resume actually helps
| Role | Interactive CV | Why |
|---|---|---|
| Front-end or creative developer | Strong fit | It shows the craft the job asks for |
| Product, motion or interaction designer | Good fit | Interaction is the skill on show |
| Data analyst or visualisation specialist | Good fit, if it's a real chart of your work | A filterable view of projects demonstrates the job |
| Marketing, writing, operations | Optional | A clear resume page does more; an interactive extra can stand out for a small agency |
| Law, finance, medicine, public sector | Usually a distraction | Readers expect convention and speed |
Whichever row you're in, the people screening applications read quickly and often on a phone. If they can't find your last role and dates in a few seconds, the cleverness has cost you.
Ideas that earn the interaction
- Filter by skill. Tap "accessibility" or "data visualisation" and see only the roles and projects that used it. Good for people with varied careers.
- A timeline you can scrub. Drag along the years to see roles, projects and what you learned in each period.
- A project explorer. Cards for each project with the problem, your part, the result and a link, sortable by year or type.
- A terminal or game framing, for developers and game designers only, and only if the plain content is one click away.
- A printable view that turns the whole thing into a one-page CV, so nobody has to ask for a PDF.
Avoid interaction for its own sake: skill bars with percentages, autoplaying animations and puzzles that gate your contact details all annoy the people you're trying to impress.
Building it as a small app
In Anticode, this is an app build: the model writes the whole program as one HTML document with its own HTML, CSS and JavaScript, streamed as it goes. Describe it: "an explorable CV for a front-end developer, with a skills filter, a scrubbable timeline of roles from 2016, a project explorer and a print-friendly view; data for eight roles and twelve projects below", then paste your history. Upload a photo and project screenshots; the model sees photos. When the self-review service is available, a new app build is opened in a headless browser at phone and laptop widths, screenshotted and clicked through, and problems it finds are fixed.
Apps run in a strict sandbox with no network of any kind. For a CV that's mostly a benefit: nothing tracks the reader and nothing loads from elsewhere apart from Google Fonts. It does mean the app can't pull your live GitHub activity, posts or stats; anything like that has to be written into the data, and anything simulated is labelled "Demo data". Link out to your profiles instead.
Keep a plain version too
Applicant tracking systems read text from a PDF or a form, not from an app's interface, so an interactive CV does nothing at that stage. Keep a conventional resume PDF and a plain resume website page with the same facts, and link the interactive version from both as "Explore my work". When you change jobs, update all three on the same day; contradictions between versions look careless.
Limits
- No live data. The app can't fetch repositories, posts or analytics.
- Forms only through the form pipeline. A contact or enquiry form in the app reaches you through Anticode's form pipeline; anything else, such as booking a call in a scheduling tool, needs a link.
- No PDF generation. Print to PDF from the browser using the print view, or keep a PDF made elsewhere.
- No private version for one employer. Published apps are public at their address.
Questions people ask
Do recruiters read interactive CVs?
Some will, especially for creative and technical roles, but usually after a conventional CV has got you shortlisted. Lead with the plain version.
Can I update it myself?
Yes. Ask for a change in a sentence, such as adding a role, and the build updates. Keep your data in one list so changes are easy to describe.
Will it work on a phone?
It should; check it at phone width anyway, because filters and timelines are the parts most likely to feel cramped.