Reactive Resume: The Best Open-Source CV Builder?

You have your CV data neatly stored in a resume.json, as described in our guide to flexible CV theming. The separation of content and design works. But now you want to tweak the layout, adjust colors, rearrange sections, and instead of writing CSS, you would rather have a visual interface. That is exactly what Reactive Resume is for.

Reactive Resume (rxresu for short) is an open-source CV editor that works like a CMS for your resume. Drag-and-drop instead of Handlebars templates. Live preview instead of compile cycles. And because the project is fully open source on GitHub, you can self-host it if data control matters to you.

Sounds promising. In practice, however, we ran into a few stumbling blocks. This guide gives you an honest assessment: what works well, where it falls short, and how to use Reactive Resume so that your CV meets the requirements of the German tech market.

What Reactive Resume Can Do🔗

The Editor at a Glance🔗

Reactive Resume offers a split-screen interface. On the left, you edit content in structured forms: personal details, work experience, education, skills, projects, languages, certifications. On the right, you see a real-time preview of the finished PDF.

The concept behind it is the same as JSON Resume: content and design are separated. But instead of switching between themes on the command line, you click through visual options. You can reorder sections via drag-and-drop, change colors with a color picker, switch fonts, and adjust spacing with sliders.

For developers who do not want to dive into a CSS file for every small layout change, this is a real win.

Import Options🔗

Reactive Resume supports several import formats. The most relevant for this guide’s audience:

JSON Resume Import: You can upload your existing resume.json directly. The tool maps the fields to its internal structure. In theory, this saves you from entering all data manually.

LinkedIn Import: You can export your LinkedIn data and import it into Reactive Resume. LinkedIn offers a GDPR-compliant data export (in Germany known as DSGVO) that delivers your profile data as structured files.

PDF Import: You can also import an existing PDF, though parsing quality naturally varies more here than with structured formats.

Manual: Of course, you can also enter everything by hand. The forms are clearly structured and guide you through each section.

Templates and Customization🔗

Reactive Resume comes with several pre-built templates. After selecting a base template, you can customize almost every visual aspect:

Page layout (single or two-column), color scheme (primary and accent colors), typography (font, font size, line height), spacing between sections, visibility of individual sections (show/hide), and section order via drag-and-drop.

For advanced users, there is also the option to inject custom CSS. This is a nice safety net: if the visual options are not enough, you still have full control.

Sharing and Exporting🔗

One feature that sets Reactive Resume apart from most offline tools is the ability to share your CV via a link. Instead of sending a new PDF after every change, you share a URL. Changes to the CV are immediately visible to anyone who has the link.

This is especially handy for feedback rounds. Share the link with a colleague or send it to us for a CV review, and the feedback always refers to the latest version.

The PDF export works directly from the editor. You get a print-ready document that you can attach to job applications.

Honest Hands-On Review: What Works, What Doesn’t🔗

Import Issues🔗

This is where things get bumpy. When importing our JSON Resume file, several fields showed “undefined” in the work experience timeline. Skill expertise levels were not carried over correctly. The mapping of keywords to positions was partially lost.

The LinkedIn import did not work at all for us. The exported LinkedIn data was accepted, but the resulting output was unusable: fields in the wrong places, missing date ranges, merged entries.

What this means in practice: plan time for manual cleanup. The import is a starting point, not a finished result. For a resume.json with 15 positions and detailed bullet points, expect 30 to 60 minutes of correction work.

Missing Variant Support🔗

In our guide to CV design, we emphasize why you need multiple CV variants for different roles. A “Senior Frontend Engineer” version alongside a “Tech Lead” version, with overlapping data but different focal points.

Reactive Resume only supports this through a workaround: you duplicate the entire resume and edit the copy. This works but quickly becomes unwieldy. When you update your current position, you have to do it separately in each variant. With three or four variants, this is error-prone.

With JSON Resume and Git, this can be solved more elegantly, because you can synchronize changes to shared data via diffs. With Reactive Resume, it remains manual work.

Performance🔗

The interface looks good but responds noticeably slowly. With longer CVs (three or more positions with four to five bullet points each), re-rendering the live preview takes a noticeable amount of time. This is not a showstopper, but it does not feel like a modern web editor.

If you self-host the tool, you may be able to mitigate performance issues with better infrastructure. The hosted version on rxresu.me runs on limited resources.

What Works Well🔗

Despite the criticism, the visual editor itself is well thought out. The drag-and-drop functionality for sections works reliably. Color and typography adjustments take effect on the preview immediately. And the ability to show and hide sections is practical for quick adjustments across different applications.

The PDF export delivers clean results. Typography is consistent, page breaks are set correctly, and the resulting PDF is text-based (not rendered as an image), which is relevant for ATS compatibility.

Reactive Resume and the German Tech Market🔗

Profile Photo and German CV Conventions🔗

The German tech market has expectations for resumes that differ from US or UK standards. A profile photo is still common. The format is chronological, not functional. Arbeitszeugnisse (formal employer references, a document unique to the German market) and education carry more weight than in English-speaking markets.

Reactive Resume supports profile photos. You can upload an image that is displayed in the CV header. Placement depends on the chosen template, some show the photo in the upper right (the German standard), others centered or on the left. After selecting a template, check whether the photo placement matches conventions.

ATS Compatibility🔗

Before a human sees your resume, an Applicant Tracking System (ATS) parses the file at most companies. Complex layouts with columns, icons, and embedded graphics cause parsers to fail.

Reactive Resume generates text-based PDFs by default, which lays the foundation for ATS compatibility. However, the result depends heavily on the chosen template. Two-column layouts can cause problems because ATS parsers misinterpret the reading direction. Single-column templates are the safer choice.

The simplest test: open your exported PDF, select all text, and copy it into a text editor. If the order is correct and all information is readable, the foundation is solid. If columns are jumbled or text is missing, switch the template.

[1] Two-column layouts work with some ATS systems but not others. If you do not know which system the target company uses, choose single-column.

Language and Localization🔗

The Reactive Resume interface is in English. You enter your CV content in your own language, of course. For the German market, this means you type German text into English form fields. This works without issues but can be confusing when it comes to section naming. Make sure the section headings in the exported PDF appear in German (e.g., “Berufserfahrung” instead of “Work Experience”), and adjust them manually if needed.

Reactive Resume vs. JSON Resume: Which Tool for Which Purpose?🔗

The question “Reactive Resume or JSON Resume?” cannot be answered with a blanket recommendation. Both tools solve the same fundamental problem (separating content from design), but in different ways.

[1] Both tools support JSON Resume import/export, so you can switch between them.

Our take: if you regularly maintain multiple CV variants and want version control, JSON Resume with Git is the more robust approach. If you want to quickly build a visually appealing CV without touching the command line, Reactive Resume is the better choice. The two tools are not mutually exclusive. You can maintain your data in JSON Resume and import it into Reactive Resume for visual fine-tuning.

Tips for an Optimal Setup🔗

Workflow Recommendation🔗

A setup that combines the strengths of both tools:

1. Data Source: Maintain your CV data in a resume.json in a Git repository. This is your single source of truth. Every change is traceable, and variants can be managed cleanly.

2. Visual Design: Import your resume.json into Reactive Resume when you want to work on the layout. Use the visual editor for colors, spacing, and section order. Export the result as a PDF.

3. Regular Updates: Keep your data source current. New projects, updated skills, changed responsibilities. Those who maintain their CV continuously, instead of catching up on everything before the next round of applications, save themselves stress and forget less.

4. ATS Check: Before every application round: export the PDF, run the text copy-paste test, and verify that all information is extracted in the correct order.

Open Source and Data Control🔗

Reactive Resume is fully open source under the MIT license. This means you can inspect the code, self-host the tool, and be confident that your data is not being sold to third parties. For developers who value data control, self-hosting is a serious option.

The Docker-based installation is documented in the README. You need Docker, a PostgreSQL database, and S3-compatible storage for uploads. If you already run a VPS or homelab, you can have it set up in half an hour.

If self-hosting is too much effort, the hosted version on rxresu.me works fine for getting started. Keep in mind, though, that you are entrusting your career data to a third party. Export your data regularly as a JSON backup.

Avoiding Common Mistakes🔗

Too much design, too little content. A CV with perfect colors and an elegant layout, but generic bullet points like “Development and maintenance of microservices,” will not convince any recruiter. Content matters more than design. Read our guide to Builder vs. Papiertiger if you want to learn how to turn task descriptions into real impact statements.

Two-column layout for ATS applications. Two-column CVs look modern, but many ATS systems read them incorrectly. If you are applying through an online portal, use a single-column template.

Forgetting CV variants. A single CV for all applications is a compromise that costs you interviews. Create at least two variants: one for your primary target role, one for the broader search.

Forgetting the profile photo. For the German market, a professional profile photo is still standard. Reactive Resume supports photos. Use the option.

When a Tool Is Not Enough: Professional CV Review🔗

Reactive Resume and JSON Resume solve the technical problem: how do I get my CV into a clean format? The harder question is about content. Which projects belong prominently at the top? Which phrasing survives the 6-second recruiter scan? Which structure works for the German market, where Arbeitszeugnisse (formal employer references) carry a different weight than in the US market?

Tools do not give you feedback on whether your CV is convincing in terms of content. They format what you give them. If what you give them consists of generic task descriptions, you get a beautifully formatted but substantively weak resume.

CodingCareer’s CV optimization picks up exactly where tools leave off. In a structured session, a coach who works as a developer in the German tech market reviews your resume line by line. Task descriptions are rewritten as impact statements. The structure is adjusted so that your strongest projects are visible within the first six seconds. The result is a concrete, revised document, not vague advice.

CV optimization is part of all coaching packages: Junior Kickstart for career starters, Germany Market Entry for international developers entering the German market, The Salary Jump for the next salary leap, and High-Pay Tech Strategy for experienced developers applying for senior or staff positions. All packages offer a pay-on-success model: you pay a reduced amount upfront and the rest only when you land the job.

Book your free 15-minute diagnostic call and find out if your CV is optimized for the German tech market.