Case I — Atsly · ATS Resume Copilot
Atsly
Most resumes are rejected by software before a human ever reads them. Atsly shows the score — and closes the gap — before you hit apply.
- Industry
- Career-tech · Consumer mobile
- Role
- Founding Product Designer · 0→1
- Duration
- 8 weeks
- Year
- 2026
§ The pitch
By widely cited estimates, around three in four resumes never reach a human. Atsly is the pre-flight check — an explainable ATS score, a country-specific fit report, and an AI rewrite you stay in charge of.
Format
Mobile-first · iOS
Scope
0→1 · brand to prototype
System
Tokenized design system
Artifact
50+ hi-fi screens, 9 flows
§ Why this exists
The rejection nobody sends.
Atsly started from a lived problem: applying for design roles abroad while based in India. You tailor a resume for days, submit it, and hear nothing — not a rejection, just silence. The reason is usually mundane: an applicant tracking system parsed a two-column layout into word salad, found too few of the right keywords, and filed the application where no recruiter would ever look.
For international job seekers there is a second, quieter filter: the market itself. A resume that works in Bengaluru fails in Toronto for reasons no ATS will tell you — photo on the resume, two pages instead of one, no measurable outcomes, no accessibility vocabulary. Every market has unwritten conventions, and applicants discover them only through months of silence.
I designed Atsly to make both filters visible before the apply button — so the feedback loop takes thirty seconds, not three months.
§ The problem
Three compounding failures.
The invisible filter
Most mid-to-large employers screen with ATS software before a recruiter reads anything. Formatting alone — sidebars, tables, graphics — can sink a strong candidate. Applicants are graded by a machine they can't see, against criteria they're never shown.
The silent feedback loop
Rejection arrives as silence. With no signal about what failed — keywords? format? seniority? — applicants change everything or nothing, and repeat. The cost of each iteration is weeks, and the lesson learned is usually wrong.
Country blindness
Existing tools assume a US resume going to a US company. Cross-border applicants — the fastest-growing segment of job seekers — get keyword advice when their real gap is convention: page count, photos, CV style, the vocabulary a market expects. No mainstream tool scores this.
§ The solution
A copilot for the whole journey, not a keyword counter.
Atsly compresses the entire pre-application loop into one mobile flow. Import your LinkedIn profile or upload an existing resume, save the job descriptions you're chasing, and run a check: the app returns an ATS score with a full breakdown — keywords, readability, format, skill match, impact language — where every weak dimension is a tappable, explained fix.
Then comes the layer no competitor ships: Market Fit. The same resume is benchmarked against successful resumes in the target country — Canada in the demo — and gaps are named in plain language: accessibility experience missing, only one quantified bullet, no enterprise scope. Each gap carries a severity and a suggested next step.
Finally, the AI rewrite works bullet by bullet. For each suggestion the user sees their original line, the proposed rewrite, and — critically — the reason it scores higher. Accept, edit, or skip. The session ends with a re-scored resume (74 → 91 in the scripted journey) and a cleanly named PDF.
§ USP
Four bets that make it different.
- I.
Every point is accounted for.
No black-box grades. 74 becomes 91 because single-column formatting adds 12, stronger verbs add 9, two metrics add 6. If the user can audit the math, they trust the tool — the same design conviction I bring to every AI product.
- II.
The market is the second ATS.
Country-specific market fit is the moat. Target-market selection is the first thing on the home screen — 'Canada · 1 page · No photo · CV-style' — and every score, gap, and rewrite is computed against that market, not a generic US default.
- III.
AI proposes. The human disposes.
The rewrite never bulk-replaces a resume. One bullet at a time, original beside rewrite, reasons attached, with accept / edit / skip on every card. Your resume stays yours — Atsly just shows you what the machine reading it will see.
- IV.
Built for the moment of need.
Job hunting happens on the phone — on commutes, between shifts, the night before a deadline. Atsly is mobile-first end to end: bottom sheets for decisions, one thumb-reach CTA per screen, a check that completes in under a minute.
§ Market gap
The unowned corner of a crowded market.
Resume tooling is a busy category, but it clusters in one corner. Jobscan and Resume Worded are desktop-web, keyword-centric, and subscription-gated before the first useful insight. Teal is a tracker first, an optimizer second. LinkedIn Premium tells you how you compare to other applicants — not how an ATS parses you. ChatGPT will rewrite a resume wholesale, with no score, no audit trail, and no idea what Canadian recruiters expect.
Plot the market on two axes — explainability of the score and awareness of the target market— and the top-right quadrant is empty. That corner is Atsly's position: mobile-first, point-by-point explainable, and the only tool treating country conventions as a first-class scoring dimension rather than a blog post.
Where it stands: designed end-to-end as a 0→1 concept — brand, tokenized design system, 50+ hi-fi screens across 9 flows, and the working prototype below. The wedge audience is cross-border applicants (India → Canada first, mirroring Express Entry demand), with per-check pricing instead of subscriptions — because job seekers buy outcomes, not memberships.
§ Design workflow
From global research to 50+ tokenized screens, in eight weeks.
Sole product designer, end-to-end. Working alone meant every decision was both freedom and risk — so I built the process to keep me honest.
Discover
Talked to seekers, not just recruiters.
Eight in-depth conversations with international applicants — India, Philippines, LATAM. Mapped where their resumes leak: format, keywords, market mismatch.
- 8× user interviews
- Competitive teardown
- Problem framing
Define
Explainability is the feature.
Wrote the principles: name every dimension, show every fix as a delta, never auto-apply without consent. Translated them into design specs.
- Design principles
- Decision filters
- Success metrics
System
Mobile-first token set.
Built the design system from primitives up — type, color, spacing, motion. Atomic library so 50+ screens stayed consistent through three iterations.
- Token set
- Atomic library
- Mobile + tablet specs
Prototype
50+ screens, clickable.
Hi-fi mockups for the full hero journey — onboarding, score breakdown, AI rewrite, export. Wired the prototype end-to-end in Figma.
- 50+ hi-fi screens
- End-to-end prototype
- Microcopy pass
Validate
Five testers, two pivots.
Tested with real job-seekers. Two material rewrites came from it: the score breakdown got named dimensions, and rewrite became point-deltas with diff view.
- 5× user tests
- Two design pivots
- Handoff specs
§ Stack
Tools that earned their place.
- FigmaDesign
- FigJamMapping
- NotionDocs
- LottieMotion
- AnthropicRewrite engine
- LinearTracking
§ AI pipeline
AI in the loop.
Human at the wheel.
One pipeline. Eight stages. Each one hands off cleanly to the next — Notion bookends the doc trail, ChatGPT shapes the prompt, Claude executes through the Figma MCP, and every artifact lands in a place a teammate could pick up cold.
- Notion
Business doc & design brief
Goals, constraints, success criteria, and the brand voice land in a single Notion canvas. Nothing moves until this reads cleanly.
- ChatGPT
Prompt engineering for Claude
Use ChatGPT to shape the brief into a tight, system-grade prompt — persona, context, constraints, success bar — that Claude will execute against.
- ClaudeFigma MCP
Wireframes — generated in Figma
Claude pairs with the Figma MCP and writes the low-fi structure directly into the file. Real frames, real components, real positions — not a screenshot.
- FigmaNotion
Iteration on wireframes
Hands-on edits in Figma; reasoning + decisions captured back in Notion. Loop until the structure earns its place against the brief.
- ClaudeFigma
Building components with Claude
Atoms → molecules → organisms. Tokens, variables, naming conventions. Claude does the heavy lift; I keep the judgment calls.
- Figma
Mid-fi screens· Optional
Only if the project needs a stakeholder gate before hi-fi. Greyscale layouts that prove the IA without committing the visual.
- Figma
Hi-fi screens
Pixel-perfect frames with real copy, real data, real states. Light and dark, edge cases handled, motion noted in-frame.
- Notion
Storyboard documentation
The final handoff lives in Notion: decisions, scope cuts, telemetry plan, what shipped, what didn't, what's next.
The same loop runs at any scale — a 12-week shipped product or a 3-day design sprint. What changes is the depth at each stage, not the order of the moves.
§ Sitemap
Mobile-first, six top-level sections.
The IA is shaped around the job-seeker's actual sequence: upload, understand, fix, apply. Settings and account meta sit at the edges. Click any node to inspect.
§ Screens
62 hi-fi screens — six user flows + a states bucket.
Every screen from the Career-IQ design file. Six flows reading left-to-right as the user journey actually unfolds, plus a cross-cutting bucket for loading, success, error, and empty states. Tap a flow to filter; click any screen to enlarge.
62 screens · 7 sections · iPhone 13/14 · 390×844
§ User flow
Upload → score → fix → re-score → apply.
The scripted hero journey: every step is a decision point. Hit play to watch the whole flow auto-advance, or step through manually.
Currently inspecting
Upload resume
User drops a PDF or DOCX into the empty state. Parsed locally on first launch.
Next: tap upload
§ Outcomes
- 50+ screens
- Hi-fi, tokenized, and componentized in Figma — sections for onboarding, JDs, resume library, ATS check, analysis, and account.
- 74 → 91
- The scripted hero journey: three explained fixes, a market-gap pass, and a bullet-level rewrite — every point of the delta accounted for.
- 2 filters, visible
- The ATS and the market — both scored, both explained, both fixable before the user ever hits apply.
§ What I learned
Explainability is the feature.
The first version of the score screen showed a single number and a “Fix everything” button. It tested as magic — and magic reads as suspicious when the stakes are someone's livelihood. Decomposing the score into named dimensions, and the fix into named point deltas, changed how testers talked about the product: from “does this actually work?” to “which fix should I take first?”
The same lesson as every AI product I've designed: trust isn't a claim, it's a receipt.Show the math, keep the human's hand on every change, and the model becomes a colleague instead of an oracle.
Next case study
All work →Currently viewing: Atsly