hireme
SYSTEM NOTE 01 · ARCHITECTURE & AUTONOMOUS AGENT WORKFLOWActive Development

Precision resume engineering, built to be executed by agents.

Most job-application automation fails at the same boundary: agents are asked to tailor a resume on the fly while filling forms, producing hallucinated skills, broken line wraps, and accidental two-page overflows. hireme separates editorial calibration from mechanical submission so autonomous browser agents receive locked, single-page vector artifacts ready for upload.

01 · Pipeline Architecture

Four decoupled workspaces, from master source to agent queue

Instead of mutating one shared document, HireMe routes every target job posting through four strictly typed stages. Each stage writes into isolated collections in Firebase Realtime Database backed by immediate localStorage hydration:

  • 01/experience stores your canonical MasterResume, imported via the Universal LaTeX Parser or structured inline while maintaining domain context tags and numeric metrics.
  • 02/operations ingests a job description, classifies target keywords across four defensibility tiers, and solves an O(n³) Hungarian bipartite assignment so each bullet accepts at most one clean edit.
  • 03/preview clones the master resume into per-application PreviewQueueItem slots. Fine edits made in Customize Resume stay isolated to that job while rendering a live vector PDF side-by-side.
  • 04/agents freezes approved tailored snapshots into AgentResumeEntry rows engineered specifically for reliable browser-agent consumption.
Figure 01 · End-to-End Pipeline & Data Isolation SchematicHuman Editorial Loop → Autonomous Execution
CALIBRATION & APPROVAL WORKSPACE (HUMAN-IN-THE-LOOP)EXECUTION HANDOFF01 ExperienceMasterResume02 OperationsHungarian Match03 PreviewSlot Isolation04 /agentsLocked PDFsBrowser AgentPortal Submit + SwitchOFFLINE-FIRST REALTIME DATABASE LAYERmasterResumes/{uid} · previewQueues/{uid} · agentsQueues/{uid} · appliedJobs/{pushId}
02 · Typographic Calibration

Measuring Helvetica glyphs before a single line wraps

Blind word-count limits fail because three uppercase acronyms occupy far more horizontal ink than three lowercase prepositions. Both the calibration bar in /experience and the rewrite verifier read per-character Adobe Font Metrics (AFM) widths scaled to 108.0 units per printable line (DEFAULT_CALIBRATION).

If reframing a 1-line achievement pushes it across 108 units without reaching at least 65% fill on the second line, validateRewrite rejects the proposal as an orphan spillover. What renders cleanly in Preview stays locked onto one crisp vector page via pdf-lib.

Chart 01 · Helvetica AFM Glyph-Width Calibration ZonesDEFAULT_CALIBRATION: oneLineMax = 108 · twoLineMax = 216
0 units88 (1L min)108 (1L max)170 (2L min)216 (2L max)240+
1-Line Tight Green Zone88 – 108 AFM units (82%–100% of 1L)
Accepted

“Built idempotent PostgreSQL billing webhooks cutting duplicate invoice retries by 64% across 18M calls.”

102 / 108 units · 1L exact
2-Line Orphan Danger Zone109 – 158 AFM units (< 65% of Line 2)
Rejected (line_growth)

“Built idempotent PostgreSQL billing webhooks cutting duplicate invoice retries by 64% across 18M annual API requests.”

118 units · 2-word orphan spillover
2-Line Balanced Green Zone170 – 216 AFM units (65%–100% of 2L)
Accepted

“Built idempotent PostgreSQL and Redis billing webhooks with distributed locking, eliminating duplicate invoice retries by 64% across 18M high-throughput monthly partner requests.”

184 / 216 units · 2L balanced
Page-Break Overflow> 216 AFM units (3+ lines)
Rejected (overflow)

“Spills onto a third line, compounding vertically to push the final footer onto an unintended Page 2.”

> 216 units · Hard guardrail block
03 · Defensibility & Matching

Four-tier guardrails and Hungarian bipartite optimization

Keyword alignment only works if you can defend every phrase in a technical interview. Before proposing changes, HireMe partitions extracted JD requirements into four strict tiers. Unfamiliar hard systems technologies are locked out completely (Tier 2), while adjacent tools stay confined to the Skills block (Tier 1.5).

Eligible workflow terms compete in a global bipartite matrix rather than greedy first-match loops. Every bullet edit is hard-capped at <= 7 changed words and must preserve 100% of original numbers and latency/scale metrics. When an optional role-specific point is needed, collapsible 1-line malleable cards let you swap between domain phrasings in one click before all 6 automated invariants execute.

Chart 02 · Coverage Lift (Illustrative Run) & 4-Tier Defensibility Gates6/6 Verification Invariants
Unweighted JD Term Match+42% lift
Master Resume Baseline44%
After Hungarian Alignment86%
Section-Weighted ATS Score+48% lift
Master Resume Baseline41%
After Hungarian Alignment89%
TierClassificationDefensibility GateAllowed Placement
Tier 0Present in InventoryAlready verified in resume bullets or skills.No mutation
Tier 1Workflow & FramingPlausibly grounded in existing engineering context.<= 7 word bullet edit + Skills
Tier 1.5Skills-Table OnlyAdjacent framework candidate never fabricated inside bullets.Skills section strictly
Tier 2Hard-BannedLow-level/specialized tools absent from resume (e.g. CUDA, C++).Blocked across all outputs
Check 1 · Guardrail Re-Validation on All Edits
Check 2 · Zero Tier-2 Banned Tech Leakage
Check 3 · Zero Tier-1.5 Skills-Only Tech in Bullets
Check 4 · Calibrated Line-Fit & Zero Overflow
Check 5 · Zero Duplicate Bullets
Check 6 · JD Keyword Coverage Progression
04 · Autonomous Agent Workflow

How HireMe is designed to be handed off to an agent

In the browser-agent paradigm, you curate and approve resumes in /operations and /preview, then batch-push the finished roles to /agents. Once queued, an autonomous agent (Antigravity Browser Subagent, Computer Use, or Playwright) only needs access to that single page to drive submissions end-to-end.

Every row in /agents exposes predictable semantic hooks: a deterministic filename download button, the external posting anchor, an ARIA role="switch" button that records submissions directly to appliedJobs, and an Archive button that remains disabled until the application is confirmed sent.

Figure 02 · Annotated /agents Queue Contract & State MachineDOM-Deterministic Primitives
Active Queue Row Anatomy (/agents)
Stripe — Backend Infrastructure EngineerNot Sent
[01]Candidate_Stripe_Backend_Infra.pdf[02]https://stripe.com/jobs/...
[03]Sent to Company[04]Archive
01Click filename button

Triggers on-demand vector PDF compilation from the frozen entry.tailoredResume snapshot.

02Follow target roleUrl

Opens the company ATS portal. The agent uploads the deterministic PDF and completes portal fields.

03Flip Sent to Company

Toggles the ARIA role="switch" state, persisting sentAt locally and logging the job to RTDB appliedJobs.

04Click Archive gate

Unlocked exclusively when sentToCompany === true, preventing accidental dismissal of unsubmitted roles.

Active · Not Sentarchived: falsePDF Compiledvector BlobPortal Submittedexternal ATSSent to Companylogs appliedJobsArchivedgate unlocked

Drop-in prompt for your browser agent

Point an authenticated browser agent at /agents with the runbook below:

Agent Execution Runbook Prompt
You are operating the HireMe Agents Queue (/agents) to submit job applications deterministically.

For each entry inside the "Active Queue" section that shows status "Not Sent":
1. Download the locked PDF by clicking the monospace filename button (e.g., First_Last_Role.pdf). Wait for the download to finish.
2. Open the adjacent external job posting URL in a new tab.
3. Complete the application form faithfully using the candidate data inside that downloaded PDF:
   - Upload the downloaded PDF directly (do NOT edit or reformat it).
   - Fill work authorization, education, links, and required questions truthfully.
   - If the portal pauses for manual review, captcha, or login, ask the user before proceeding.
4. Once the confirmation screen renders, return to /agents and toggle the "Sent to Company" switch (role="switch") on that exact row.
5. Click the now-enabled "Archive" button to move the completed entry into Archive and proceed to the next queued role.
05 · Offline-First Persistence

Resilient local queuing with automatic Firebase synchronization

Every edit across /experience, /preview, and /agents renders optimistically from in-memory and localStorage stores. When network connectivity drops, pending writes buffer inside hireme_offline_sync_queue and automatically flush to Firebase Realtime Database the moment online or focus fires.

Ready to calibrate your master resume?

Start in Experience, run alignment in Operations, verify layout in Preview, and queue for Agents.