About

Writing a CV in a word processor couples content with formatting. Every font change or margin tweak risks breaking layout consistency. Markdown separates structure from presentation: you write content in plain text, and the generator applies typographic rules uniformly. This tool parses raw Markdown syntax into a structured CV layout using a custom tokenizer that handles headings (h1 - h6), emphasis, lists, links, and blockquotes. The output targets A4 print dimensions at 96 DPI with proper margins. No data leaves your browser. Limitations: the parser covers standard Markdown; extended syntax like tables or footnotes is not supported.

Recruiters spend an average of 7.4 seconds on initial CV screening. A misaligned bullet point or inconsistent heading hierarchy signals carelessness. This tool enforces visual consistency programmatically. Choose from 3 professional templates, preview changes in real time, and export via the browser's native print dialog to PDF. Pro tip: keep your Markdown source file in version control alongside your code projects for a complete career changelog.

Formulas

The Markdown parser operates as a line-by-line tokenizer. Each input line L is tested against an ordered set of regular expression patterns P_i. The first matching pattern determines the output HTML element.

parse(L) =

{

<h_n> if L matches P_heading = /^(#{1,6})\s(.+)/<blockquote> if L matches P_quote = /^>\s?(.+)/<li> if L matches P_list = /^[-*]\s(.+)/ or /^\d+\.\s(.+)/<hr> if L matches P_rule = /^-{3,}$/<p> otherwise

Inline transformations apply sequentially within each line's content: P_bold = /\*\*(.+?)\*\*/g → <strong>, then P_italic = /\*(.+?)\*/g → <em>, then P_code = /`(.+?)`/g → <code>, then P_link = /\[(.+?)\]$(.+?)$/g → <a>. Order matters: bold must be matched before italic to prevent **text** from being consumed by the single-asterisk rule.

Where L = input line string, P_i = regex pattern for token type i, n = heading level (1 - 6), determined by count of # characters.

Reference Data

Markdown Syntax	Purpose	CV Usage	Example
`# Heading 1`	Top-level heading	Your full name	`# Jane Doe`
`## Heading 2`	Section heading	Section titles (Experience, Education)	`## Work Experience`
`### Heading 3`	Sub-section heading	Job title or degree	`### Senior Engineer`
`bold`	Strong emphasis	Company names, key skills	`Google Inc.`
`italic`	Emphasis	Dates, locations	`Jan 2020 - Present`
`- item`	Unordered list	Responsibilities, skills list	`- Led team of 8 engineers`
`1. item`	Ordered list	Ranked achievements	`1. Increased revenue by 40%`
`[text](url)`	Hyperlink	Portfolio, LinkedIn, GitHub	`[Portfolio](https://example.com)`
`> text`	Blockquote	Professional summary or quote	`> Results-driven engineer...`
`---`	Horizontal rule	Section separator	`---`
`code`	Inline code	Technical terms, tools	`Python`, `Docker`
`#### Heading 4`	Minor heading	Project names within a role	`#### Project Atlas`
Blank line	Paragraph break	Separate content blocks	(empty line between blocks)
`_combined_`	Bold + Italic	Critical highlights	`_cum laude_`
Plain text	Body paragraph	Descriptions, summaries	Any free-form text

Frequently Asked Questions

Click the "Export PDF" button, which triggers the browser's native print dialog. Select "Save as PDF" as the destination. The print stylesheet removes all editor UI elements and formats the CV for A4 paper with proper margins. This produces a vector PDF with selectable text, unlike screenshot-based approaches.

No. This parser implements standard Markdown covering headings (h1 - h6), bold, italic, inline code, links, unordered and ordered lists, blockquotes, and horizontal rules. Tables, images, and extended syntax (footnotes, task lists) are excluded by design. CVs rarely benefit from embedded images (which increase file size and can trigger ATS parsing failures), and tabular data is better expressed as structured lists.

Yes. The output uses semantic HTML rendered to PDF via the browser's print engine, producing text-selectable vector output. ATS systems can extract text from such PDFs reliably. Avoid the "Classic" template's two-column layout if targeting older ATS systems, as some struggle with multi-column documents. The "Clean" template uses a single-column flow optimized for machine parsing.

No data leaves your browser. All content is processed client-side using JavaScript string operations. Your Markdown source is persisted to localStorage for convenience across page reloads. Clear it using the "Clear" button or by clearing browser site data. No analytics, cookies, or network requests are made with your CV content.

Use h1 (single #) for your name only - one per document. Use h2 (##) for major sections: Summary, Experience, Education, Skills, etc. Use h3 (###) for individual positions or degrees within a section. Use h4 (####) for sub-projects within a role. This hierarchy maps to semantic HTML and helps both human readers and automated parsers understand document structure.

The three built-in templates (Clean, Modern, Classic) use carefully paired font stacks and color schemes optimized for print legibility and ATS compatibility. Custom styling is intentionally limited to prevent the formatting inconsistencies this tool aims to eliminate. For branding needs, export to PDF and post-process in a vector editor.