Engineer
PreviewSoftware, product, AI, infrastructure, data, security, developer relations, and engineering leadership.
Use when stacks, shipped systems, projects, and quantified technical impact matter.
Agent guide
Let your agent write your resume.
Use this guide when you want an agent to interview you, draft a clean Tiny CV resume, validate it, publish the link, hand you an edit link, and export a PDF when asked.
Copy into an agent
Read the Tiny CV agent guide first: https://tiny.cv/agents Help me create a complete one-page Tiny CV resume. Follow the guide, ask for missing facts, do not invent anything, and only publish, pay, or export a PDF after I approve the final draft.
Canonical URL: https://tiny.cv/agents
Interview
Ask before drafting.
The best Tiny CV starts with verified facts. Ask for the missing pieces, then compress the story into one page.
01What role, company type, seniority, and industry is this resume targeting?
02Can you share a current resume, LinkedIn, portfolio, GitHub, personal site, job description, or notes?
03What name, headline, location, email, phone, and public links should appear?
04For each role, what were the company, title, location, exact dates, scope, and most important outcomes?
05Which metrics can you verify: revenue, users, latency, conversion, quota, hiring, fundraising, or time saved?
06Which projects, selected work, education, credentials, awards, or certifications should be included?
07What should stay private or be omitted?
08Do you want only markdown, a public Tiny CV link, an edit link for the markdown editor, or a PDF export too?
Templates
Choose for the next role.
Pick the template by the job the user wants next, not just the job they had last.
Designer
PreviewProduct design, brand design, design engineering, research, creative direction, and portfolio-forward roles.
Use when selected work, craft, systems, process, and portfolio links need room.
Sales
PreviewAccount executives, GTM founders, customer success, growth, partnerships, and revenue ops.
Use when pipeline, quota, ACV, segments, close rates, and customer outcomes are the proof.
Founder
PreviewFounders, operators, chiefs of staff, product leaders, and cross-functional company builders.
Use when the story crosses product, hiring, fundraising, GTM, leadership, and execution.
Coverage
Give each role enough proof.
Tiny CV reads better when agents keep only the roles that matter, and give each full entry enough substance to justify the space.
Default to only the most recent ~4 substantive roles as full entries.
Each standalone role should usually have at least 2 meaningful lines, and preferably 3-4 when the user can support them.
Older or thinner roles can collapse into Additional Experience, or be omitted if they do not help the current story.
Do not keep very old roles unless they materially strengthen the narrative for the target role.
Good
## Experience ### Founder | Meridian Labs *Remote | 2021 - Present* - Built the first product surface and shipped the company to revenue. - Closed the first enterprise customers and turned early demand into repeatable proof. ## Additional Experience - Analyst, Summit Partners (2016 - 2018) - Research Assistant, Civic Data Lab (2014 - 2016)
Bad
## Experience ### Founder | Meridian Labs *Remote | 2021 - Present* - Built the first product surface. ### Analyst | Summit Partners *Boston, MA | 2016 - 2018* - Worked on investments. ### Research Assistant | Civic Data Lab *2014 - 2016* - Helped with research.
Truth
Never invent.
A polished resume is only useful if it stays true. Missing facts are questions, not creative prompts.
Do not invent employers, dates, degrees, credentials, metrics, awards, links, titles, locations, funding, customers, or quotas. If a number would help but the user cannot verify it, use truthful scale language instead.
Structure
Copy the right shape.
Agents should imitate these entry patterns exactly. Experience needs left-side context and right-side dates. Education can use date-only metadata. Projects can skip metadata.
Experience
### Founder & Investor | Weekend Fund *Miami, FL | Apr 2017 - Present* - Built...
Education
### University of Oregon Lundquist College of Business *2005 - 2009* B.S., Entrepreneurship Concentration; Minor in Computer Information Technology
Projects
### Tiny CV Agent Finish | Next.js, TypeScript, PostgreSQL - Designed...
Quality gate
Make markdown publish-ready.
Tiny CV accepts draft markdown freely, but API publish and paid Agent Finish require a clean structure.
# candidate name
Headline under 80 characters
Contact line under the headline
## Summary with one concise paragraph
## Experience with ### entries
*Location, Remote, or website | Dates* for experience metadata
Separate - bullet lines
No inline • or · lists
Validate with quality_gate: "publish"
Workflow
Validate, publish, export.
Use Tiny CV to move from raw facts to a finished artifact without making the user learn the API.
01Read this guide, /api/v1/spec/markdown, and /openapi.json.
02Choose the template that fits the user's next target role.
03Draft Tiny CV markdown with the candidate name as #, sections as ##, and entries as ###.
04Validate with POST /api/v1/resumes/validate using quality_gate: "publish" before publishing or paying.
05Before publishing or paying, show the final markdown, selected template, unverified facts, and next action.
06Resolve validation errors before asking the user to approve publish/payment.
07Ask for approval unless the user already explicitly authorized autonomous publishing and payment.
08If the user only wants markdown, stop there and show the markdown.
09If the user wants a public link and the agent can pay, use POST /api/v1/paid/agent-finish with x402 or MPP.
10If the user has a bearer API key, create a draft, publish it, and request a PDF only when asked.
11If the user wants to keep editing, request and return an edit claim link.
12Return the public URL, edit claim URL when useful, and PDF job or PDF URL if requested.
Review gate
Ask before spending or publishing.
Publishing a public resume and spending x402/MPP funds are high-trust actions. Review the artifact first unless the user already opted into autonomous completion.
Before publishing or paying, show the user:
- Selected template and why it fits the target role.
- Final Tiny CV markdown.
- Missing or unverified facts.
- The next action: publish public link, charge Agent Finish, queue PDF, return edit link, or stop at markdown.
Handoff
Let the human keep editing.
When the user wants direct markdown control, return a Tiny CV edit claim link with the finished resume.
Bearer API
Set return_edit_claim_url: true on POST /api/v1/resumes for a draft edit link, or on POST /api/v1/resumes/{resume_id}/publish for a public link plus edit link.
Agent Finish
POST /api/v1/paid/agent-finish always returns claim.editor_claim_url and resume.editor_claim_url with the hosted resume and queued PDF job.
Human handoff
When the user opens the one-time claim link, Tiny CV attaches the resume to their browser workspace and opens the markdown editor. They can then sign up or sign in and claim the workspace into their account.
OpenAPI
Machine-readable schema and x402/MPP metadata.
Open
Agent Finish
No-account paid path for a hosted resume, claim link, queued PDF job, and receipt.
Open
LLM docs
Single-file context bundle for agents that prefer plain text.
Open