Start from the resume you have been sending

Upload your PDF or DOCX and instantly turn it into an editable resume. Your roles, dates, experience, and skills are organized for you, so you can improve your existing resume instead of starting from scratch.

The reason people keep editing a resume in Word for six years is that starting over costs an afternoon. Import removes that cost: upload the file, and it is parsed into the same structured sections the editor uses, ready to edit, score and re-template.

There is a second benefit that surprises people. A parse is a reasonable approximation of what an applicant tracking system will do to your file, so a bad import is diagnostic. If your dates landed in the wrong fields or a whole role vanished, that is information about the document you have been sending.

In short

  • PDF and DOCX supported
  • Every extracted field shown before saving
  • Uncertain fields flagged, not guessed
  • A bad parse tells you what the ATS saw
Priya Raghunathan
Senior Backend Engineer, distributed systems and payments
priya.r@hey.com · +1 (415) 555-0142 · Oakland, CA · linkedin.com/in/priyaraghunathan · github.com/priyar · priyar.dev
Summary

Backend engineer with eight years on high-throughput payment infrastructure. Took a ledger service from 400 to 9,000 writes per second without a consistency regression, and led the migration that moved 42 million accounts off a single Postgres primary. Comfortable owning a system end to end: schema design, rollout, the pager.

Experience
Senior Backend Engineer, Northwind Payments · Remote (Oakland, CA)Mar 2022 – Present
Rebuilt the double-entry ledger on an append-only event store, lifting sustained throughput from 400 to 9,200 writes per second while keeping balance reconciliation exact.
Led the shard migration of 42M accounts off a single Postgres primary across six weeks with zero customer-visible downtime and no rollback.
Cut p99 settlement latency 71% (2.4s to 690ms) by replacing synchronous fan-out with a batched outbox consumer.
Mentored four engineers; two were promoted to senior within eighteen months.
Backend Engineer, Cartogram · San Francisco, CAJun 2019 – Feb 2022
Designed the tenancy model behind the enterprise tier, which closed $3.1M in ARR that had been blocked on data isolation.
Reduced infrastructure spend 34% ($780K annualised) by moving cold tiles to object storage behind a signed-URL cache.
Wrote the incident review process still used company-wide; mean time to resolution fell from 4.1 hours to 52 minutes.
Software Engineer, Helix Robotics · Berkeley, CAAug 2017 – May 2019
Built the telemetry pipeline ingesting 1.2TB per day from 3,400 field units, replacing a batch job that ran twelve hours behind.
Shipped the fleet-diagnostics API consumed by every downstream team and by two customer integrations.
Skills
Languages: Go, TypeScript, Python, SQL
Infrastructure: Kubernetes, Kafka, Postgres, Terraform, AWS
Practices: Distributed systems, Event sourcing, Observability, Incident command
Education
B.S. Electrical Engineering & Computer Science, University of California, Berkeley · Berkeley, CAAug 2013 – May 2017
Grade: 3.8/4.0

How it works

  1. 01

    Upload the file

    PDF or DOCX, up to a few megabytes. The original is kept so you can compare against it.

  2. 02

    Review what came out

    Every extracted field is shown before anything is saved. Heavily designed files parse worst, which is worth knowing, and you can correct any field inline.

  3. 03

    Score it and see the damage

    The moment it is structured, the full report runs. Most people find three or four things that have been costing them interviews for years.

What parses badly, and why that is useful

Multi-column layouts with text boxes, tables used for alignment, icons standing in for words, headings that are images, and dates written as "Spring '19" all degrade a parse. If the import mangles your file, a tracking system very likely mangled it too, and no recruiter ever told you.

Where extraction is uncertain, the field is flagged rather than guessed at. A confident wrong answer is worse than a visible gap.

Your file, your data

Uploads are stored so you can re-import or compare, and can be deleted at any point. Documents are not used to train models, not published, and not shared. Deleting your account deletes the files with it, immediately rather than on a queue.

Questions

Resume import questions

Will it get everything right?

No parser does. Simple one-column documents come out close to perfect; heavily designed ones need correcting. You see the result before it is saved, which is the point.

Can I import from LinkedIn?

Export your profile to PDF from LinkedIn and import that. It parses well because the layout is plain.

What happens to the uploaded file?

It is stored so you can re-import or compare against the original, and you can delete it whenever you like. It is never used for training.