Skip to main content
Version: Next

Reactive Resume

What it is​

Reactive Resume provides the structured base resume that JobOps uses for PDF generation.

JobOps uses a selected RxResume base resume as the source of truth, applies job-specific tailoring (summary, headline, skills, project visibility), then renders the final PDF using the renderer selected in Settings.

Why it exists​

Most users need a repeatable resume pipeline:

  • one canonical resume source
  • controlled project inclusion rules
  • per-job tailored output without manual copy/paste

Reactive Resume integration provides the editable, structured resume source that makes that workflow reliable.

Why JobOps uses RxResume (instead of building a new editor)​

RxResume is a mature, established resume product with a strong editing experience and a JSON-native data model.

Key reasons:

  • The editor UX is strong and supports extensive user customization.
  • It supports many themes out of the box.
  • It has a JSON-native model (import/export), which is critical for JobOps automation.

Because RxResume uses structured JSON, JobOps can safely apply LLM-driven updates to specific sections before rendering PDFs locally.

Core concepts​

Base resume​

Your base resume is selected in Settings and used for:

  • profile extraction
  • project catalog extraction
  • PDF generation

If no base resume is selected, profile-dependent features and PDF generation cannot run.

Project catalog​

JobOps reads projects from sections.projects.items in the selected RxResume resume.

Each project is identified by:

  • id
  • name
  • description
  • date
  • visible (visible in base resume)

Project selection controls​

The Settings UI supports 3 controls:

  • Must Include: always include these projects.
  • AI Selectable: pool of projects AI can pick from.
  • Max Projects: final cap for included projects.

At generation time:

  1. Must-include projects are added first.
  2. AI picks up to remaining slots from AI-selectable projects.
  3. Final visible projects are applied to the generated resume.

Setup and configuration​

Account requirements (important)​

Before connecting Reactive Resume to JobOps:

  1. Choose a mode in Settings → Reactive Resume:
    • v5 (API key)
    • v4 (email/password)
  2. For v5 (recommended for self-hosted/latest), generate an API key and configure rxresumeApiKey or RXRESUME_API_KEY.
  3. For v4, create a native email/password account at v4.rxresu.me/auth/register and configure rxresumeEmail + rxresumePassword.

Important:

  • Explicit v4 and v5 modes do not silently fall back.
  • OAuth-only logins are not supported for the v4 email/password integration.

1) Configure Reactive Resume access​

Configure in Settings → Reactive Resume:

  • rxresumeMode (v5 or v4)
  • rxresumeUrl (optional shared URL for cloud or self-hosted deployments)
  • rxresumeApiKey (for v5)
  • rxresumeEmail + rxresumePassword (for v4)

Or via environment variables:

  • RXRESUME_MODE (v5 or v4)
  • RXRESUME_API_KEY (for v5)
  • RXRESUME_EMAIL
  • RXRESUME_PASSWORD
  • optional RXRESUME_URL (works for both modes; v5 OpenAPI path is added automatically)

If you leave the URL blank in the dashboard, JobOps uses RXRESUME_URL when it is set; if not set, it falls back to the public cloud default for the selected mode.

Save-time validation​

When you save Reactive Resume credentials or the shared URL in Settings:

  1. JobOps validates only the credential-bearing Reactive Resume fields for the selected mode.
  2. Invalid credentials or other 4xx configuration failures block the save and show a persistent inline error.
  3. Temporary network failures, timeouts, or upstream 5xx errors show a persistent inline warning, but the save still succeeds.

2) Select base resume​

In Settings → Reactive Resume:

  1. Click refresh to fetch resumes.
  2. Select the template/base resume.
  3. Save settings.

3) Configure project behavior​

In the same section:

  1. Set Max projects.
  2. Mark projects as Must Include where needed.
  3. Mark remaining projects as AI selectable.
  4. Save settings.

Runtime behavior​

During PDF generation​

High-level flow:

  1. Load selected base resume from RxResume.
  2. Apply tailored summary/headline/skills.
  3. Compute final visible projects from your selection rules.
  4. Optionally rewrite outbound links to tracer links (per-job toggle).
  5. Normalize the tailored resume data into JobOps' renderer document model.
  6. Render the PDF with the configured renderer:
    • RxResume export
    • Local LaTeX with tectonic

Resume-data caching​

JobOps caches successful Reactive Resume resume fetches in memory for 5 minutes.

This reduces repeated API calls from settings loads, profile checks, project lookups, and PDF generation while still refreshing often enough for normal editing workflows.

Before generating a PDF, each job can enable/disable tracer links.

  • Disabled: original RxResume links remain unchanged.
  • Enabled: eligible outbound links are rewritten to https://<your-host>/cv/<company>-xx (readable slug + 2-letter suffix).

For background pipeline generation, configure:

  • JOBOPS_PUBLIC_BASE_URL=https://your-host

Important:

  • tracer enablement is gated by readiness checks
  • if public host verification fails, enable is blocked until host health is restored
  • toggle changes apply on next PDF generation only

What JobOps changes with AI​

Current AI-driven edits are intentionally scoped:

  • summary
  • headline/title
  • skills and keywords
  • project visibility (enable/disable per project)

Local renderer dependency​

JobOps can generate the final PDF in 2 ways:

  • rxresume: use the upstream RxResume print/export endpoint
  • latex: render locally with the Jake Gutierrez-based LaTeX template

Notes:

  • RxResume still supplies the structured base resume and project data in both modes.
  • In Docker deployments, tectonic is bundled into the image for the LaTeX option.
  • In non-Docker local environments, install tectonic and optionally set TECTONIC_BIN if needed when using the LaTeX option.

API reference​

# Get effective settings (includes resolved resumeProjects and base resume id)
curl "http://localhost:3001/api/settings"
# Save base resume and project controls
curl -X PATCH "http://localhost:3001/api/settings" \
  -H "content-type: application/json" \
  -d '{
    "rxresumeBaseResumeId": "resume_id_here",
    "resumeProjects": {
      "maxProjects": 4,
      "lockedProjectIds": ["proj_a"],
      "aiSelectableProjectIds": ["proj_b","proj_c","proj_d"]
    }
  }'
# List available Reactive Resume resumes
curl "http://localhost:3001/api/settings/rx-resumes"
# Fetch projects from one RxResume resume
curl "http://localhost:3001/api/settings/rx-resumes/<resumeId>/projects"
# Regenerate PDF for a job after changing settings or resume data
curl -X POST "http://localhost:3001/api/jobs/<jobId>/generate-pdf"

Troubleshooting and FAQ​

RxResume controls are disabled​

  • Ensure the selected mode has credentials configured.
  • v5: set a valid API key.
  • v4: set email + password.
  • Invalid credentials block save and remain visible as an inline error until you edit the selected mode's credentials or URL.
  • Temporary Reactive Resume downtime shows an inline warning, but other settings can still be saved.
  • Save settings, then refresh resumes in the Reactive Resume section.

No resumes appear in dropdown​

  • Confirm the selected mode matches your Reactive Resume deployment.
  • For v5, confirm RXRESUME_API_KEY / rxresumeApiKey is valid for your self-hosted instance.
  • For v4, confirm credentials are valid for v4.rxresu.me (or your configured v4 URL) and are not OAuth-only.
  • Confirm the selected Reactive Resume account actually has resumes.

Project list is empty in settings​

  • Root cause is usually the source resume on rxresu.me having an empty Projects section.
  • Add projects directly in RxResume first.
  • Re-select/refresh the base resume in JobOps and regenerate the PDF.

Project checkboxes look wrong after changing base resume​

  • Save after selecting the new base resume.
  • Re-open Reactive Resume section and verify project IDs from that resume.
  • Re-run PDF generation to apply the new project map.

Changes did not affect an already generated PDF​

  • Settings changes apply to new generation runs.
  • Regenerate PDFs for already-ready jobs.

PDF generation fails because the renderer is unavailable​

  • Ensure tectonic is installed on the machine running JobOps.
  • If the binary is installed outside your normal shell PATH, set TECTONIC_BIN to the executable path.
  • Re-run PDF generation after fixing the local renderer dependency.

Best practices​

  • Keep base resume projects complete and up to date in RxResume.
  • Use Must Include sparingly for cornerstone projects.
  • Keep AI-selectable pool broad enough for job-specific relevance.
  • After major resume edits, regenerate PDFs for active high-priority jobs.

Add “context projects” even if they are usually hidden​

The LLM only knows what exists in your resume data.

That means there is real value in adding additional projects in RxResume, even if you keep them hidden by default:

  • They increase the AI’s context about your skills and range.
  • They can be toggled on only when relevant to a role.

Example:

  • If your main background is not Android, but you have one credible Android side project, include it in RxResume, but keep it hidden by default.
  • For a mobile role, the AI can enable that project automatically based on the job description.