Career-tech / In development / 2026
Atsly
Know your resume’s fit.
For the job and country.
I designed Atsly to check a resume against both the job description and what recruiters look for in the target country’s job market. Country-gap guidance, ATS feedback and reviewable AI rewrites help applicants prepare for opportunities abroad.
Applicants don’t know what to fix in their resume.
Applicants can spend hours tailoring a resume without knowing which change matters or whether a suggestion accurately represents their experience.
Applicants tailoring for different jobs and countries receive generic scores and suggestions without a clear order of priorities. They have to judge whether an AI edit changes the meaning of their experience and keep the right resume version linked to each application.
Solution
Connect every issue to a clear next step.
Atsly separates score dimensions, specific issues and market-fit guidance. The improvement flow keeps the selected resume and the applicant’s review visible before a new version is downloaded.
Atsly is in development. The interactive prototype shown here uses sample scores to demonstrate the interface; they are not employer ATS results, interview probabilities or measured hiring outcomes.
Format & readability
Role-relevant skills
Your experience, accurately
Review every proposed changeExplain the feedback
Name the dimensions and show the issues behind a score.
Keep the role in view
Make the selected resume and job description explicit.
Separate market context
Give target-market guidance a clear place in the review.
Protect applicant control
Make AI suggestions reviewable before they change a resume.
Business impact
In development / Before launch
Make the improvement workflow worth completing.
Atsly connects a resume, a target job and country-specific guidance to reviewable improvements. The business goal is to turn confusing feedback into a useful completed workflow that applicants have a reason to return to for their next application.
- Current evidence
- Atsly is in development. The delivered design system, screens and interactive prototype establish the experience for implementation; live conversion, retention and hiring outcomes are not yet measured.
- What to measure next
- Validate feedback comprehension, completed review-and-export journeys, wrong-version errors and repeat use across applications.
Target audience
Different applicants.
A clearer next step.
Atsly supports people preparing for a specific role, with particular attention to international applicants and people who are new to resume feedback tools.
Applicants tailoring across roles and markets.
Professionals applying beyond their current market need to review relevance and presentation without losing the facts of their experience. They need guidance they can question, with versions they can find later.
- A visible connection between a resume and a job description
- Specific issues with a reason to investigate each one
- Separate target-market guidance and ATS feedback
Understand the report before changing the resume.
New applicants need readable explanations and a manageable next action. The interface should help them use feedback without treating an AI score as an employer’s decision.
- Named score dimensions and plain-language issue labels
- Review controls that preserve ownership of the wording
- Helpful loading, error and empty-result states on mobile
Research & evaluation
Understand what applicants need to trust.
Competitor analysis, applicant questions and task-based evaluation focus on interpreting feedback, choosing inputs and reviewing changes.
Competitor analysis
Compare resume matching, feedback explanations and editing workflows.
Applicant interviews
Explore how people interpret feedback and tailor their experience.
Prototype evaluation
Test input selection, score understanding and rewrite review.
Content & trust review
Check that suggestions preserve facts and scores are not treated as hiring promises.
Competitor analysis
Compare how feedback becomes action.
Relevant products help applicants review content, match a role or organize their job search. The questions below focus on Atsly’s workflow rather than claiming a competitor lacks a feature.
| Product | Publicly described offering | Design question for Atsly |
|---|---|---|
| Jobscan | Compares a resume with a job description and provides a match rate plus feedback on keywords, formatting and relevance. | How can Atsly make the selected inputs and the reason for each recommendation easy to inspect? |
| Resume Worded | Resume scoring and detailed feedback on structure and wording, with suggestions for improving individual lines. | How can feedback lead to a focused, reviewable change rather than an unexplained new score? |
| Teal | A resume analyzer for structure and content, with job matching handled through its Job Matcher. | How should Atsly connect saved jobs, resume versions and the report for a particular pairing? |
Public sources reviewed on 19 October 2026. This is a workflow comparison, not a feature ranking or a market-share claim.
Interview guide / reconstructed
Ask about the application. Then the interface.
Use the same core questions across participants, then follow up on their experience level and application context. Each question is tied to a decision about the product.
Core questions for every applicant
Understand the reportThe sample ATS report shows 74 with five dimensions. Explain what you think the score represents and one thing it cannot tell you.
Design decision it informs: Determines whether the score needs a clearer explanation and whether people mistake it for a probability of getting an interview.
Choose a useful next stepFind the formatting and impact-language issues in this report. Which would you address first, and why?
Design decision it informs: Tests the issue hierarchy and whether explanations help applicants choose a change rather than chase a number.
Review an AI suggestionCompare the original text and the suggested rewrite. What would you change, accept or reject before putting it on your resume?
Design decision it informs: Sets requirements for review, editing and preserving factual accuracy when AI suggests stronger wording.
Follow-ups by applicant persona
Experienced professionalYou are tailoring your resume for a Canadian design role. Open the ATS report and market-fit report. Which issue would you check first, and what evidence would you need before changing it?
Design decision it informs: Tests whether role relevance and market context are distinguishable, and whether each recommendation has enough explanation.
Usability evaluation / reconstructed scenarios
Test the decisions behind the taps.
Use fictional resumes and sample job descriptions, so personal contact details and employment histories are not needed for the task. Observe what applicants understand before and after each action.
Choose the correct inputs
A person may analyze the wrong version or overlook the selected job description.
A preparation screen shows the resume and job description together before the check.
Give the participant a base resume and two jobs. Ask them to prepare a check for one role and explain the pairing.
Task completion, wrong-version selections, explanations of the score and changes accepted or rejected. Record the reason for a choice rather than treating a tap as proof of understanding.
Check comprehension
Can the applicant explain the selected resume, job and report without help?
Check control
Can they preview, question and revise a suggestion before it appears in an exported version?
Check recovery
Can they recover from an import failure, find a version after filtering and return to the library after a check?
Applicant personas
Illustrative profiles representing different application contexts. Names and needs explain the design approach; they are not participant identities or interview transcripts.
Priya Nair
Bengaluru / Applying internationally
NeedsUnderstand which changes matter for a target role and market without rewriting her whole career story.
Design responseSeparate ATS feedback, market-fit guidance and individual rewrite suggestions.
Marco Gutierrez
Mexico City / Remote roles
NeedsCompare resume versions against specific job descriptions and understand what each fix changes.
Design responseSaved job descriptions, a resume library and a preview before applying improvements.
Anjali Sharma
India / Graduate roles
NeedsKnow what the report means and identify a manageable next step without assuming recruitment expertise.
Design responseNamed score dimensions, clear issue labels and reviewable AI suggestions.
Design strategy
Turn feedback into a considered change.
The design makes the inputs, explanations and review steps visible, so applicants can decide what to change rather than follow a score blindly.
The frictionA single number does not tell an applicant what to improve or how the result was produced.
My design responseShow keywords, readability, format, skill match and impact language alongside specific issues. Keep the next step close to the explanation.
Working within the project constraints.
The product needed to make dense reports usable on a mobile screen and keep multiple resume versions understandable. AI suggestions needed a review step, and scoring needed to remain explainable. The interactive prototype demonstrates these interactions using sample content.
Information architecture & flow
From a base resume to a reviewed version.
Import the experience, select the target role, read the feedback and review the changes. The resume library connects each stage.
Sign in and import
Enter the sample sign-in and verification flow, then choose how to create a resume. The prototype demonstrates LinkedIn import; manual-entry layouts are in the screen library.
Information architecture
Product sitemap
The four main tabs and their supporting screens. The journey above shows the order of a typical review task.
Home & setup
- Sign in / OTP
- Home
- LinkedIn import
- Manual entry (screen designs)
- Resume ready
Jobs
- Saved job descriptions
- Add job description
- Select or edit jobs
- Choose a job for a check
Resume
- Resume library
- Status filters
- Choose a resume
- Tailor / check / download
ATS Check
- Resume & job selection
- Sample ATS report
- Preview fixes / re-score
- Market-fit report
- AI rewrite / download
Account
- Account & profile
- Plan & usage (screen design)
- Edit profile (screen design)
- Delete confirmation (screen design)
About the interactive prototype
The prototype demonstrates sign-in, sample import, saved jobs, resume selection, reports, rewrites and download states. It uses scripted content rather than real authentication, resume processing or an ATS scoring service. Manual entry, extended library filters and account-management states are also documented in the screen gallery.
The design system behind Atsly
A design system.
Ready to build.
Report dimensions, issue rows, resume cards and selection sheets share the same foundations. The system keeps dense feedback readable and makes product states consistent.
- Color, typography and spacing foundations
- Reusable reports, cards and review patterns
- States, usage guidance and developer handoff
Understand the score.
Guidance, not a hiring prediction
<ScoreBreakdown dimensions={data} />My working process
How I designed the product.
Research questions became a structured brief, wireframes, an interactive prototype and reusable components. I reviewed the wording, hierarchy and flow at each stage.
Define the problem and project scope
I started with the uncertainty around resume feedback and the extra context involved in applying across markets.
- Map the applicant’s tasks from importing a resume to preparing a version for a specific role.
- Separate ATS feedback, target-market guidance and rewriting into distinct decisions.
- Define the product scope without treating a resume score as a hiring prediction.
Output: A product brief centered on actionable feedback and applicant control.
Research users, competitors and tasks
The research approach focuses on how applicants interpret feedback, choose changes and manage multiple versions.
- Compare report explanations, job matching and resume editing in relevant products.
- Explore the needs of international applicants, technical job seekers and first-time applicants.
- Turn uncertainties into tasks for prototype evaluation rather than assuming every low score causes a rejection.
Output: Research questions tied to score comprehension, version selection and rewrite review.
Write a structured design brief
I used a structured brief to keep the screen requirements and AI-assisted design work consistent.
- Describe the audience, task sequence, information hierarchy and required states.
- Include importing, checking, applying improvements, failure and empty-result feedback.
- Review generated instructions before using them to build the design.
Output: A reviewed design brief with clear boundaries and screen requirements.
Create wireframes in Figma through MCP
I used Claude Code connected to Figma through MCP to develop the wireframes and organize the design work.
- Lay out import, saved jobs, resume selection and reports around the main application task.
- Connect fixes and rewrite review back to the selected resume.
- Review labels and transitions before adding visual detail.
Output: Wireframes for the import, review, improve and export journey.
Build a prototype, test and revise
I used a working prototype to inspect the flow and make the relationships between screens tangible.
- Prototype sign-in, import, job selection, reports, rewrite and download using sample content.
- Use task-based walkthroughs to test understanding of the score and control over changes.
- Record confusion about inputs, score meaning and saved versions, then revise the affected flow.
Output: An interactive prototype. Reconstructed evaluation examples are labeled in the research section.
Build the visual foundations
The product uses deep green, light surfaces and warm neutral feedback areas to support reading and decision-making on mobile.
- Define colors, typography, spacing and semantic feedback roles.
- Check long issue labels, bottom sheets and multi-line suggestions on a narrow screen.
- Keep selection, success, warnings and primary actions visually distinct.
Output: Reusable mobile foundations for readable reports and editing flows.
Build components and final screens
I built the component set around repeated report, library and selection patterns, then assembled the complete screen set.
- Create resume cards, score breakdowns, issue rows, selection sheets and review controls.
- Specify loading, success, error, empty and selected states.
- Review the sequence end to end, including how users return to the library after a check.
Output: A complete screen library with reusable components and interaction states.
Document the design handoff
I documented the component behavior and implementation references as part of the product’s handoff work.
- Specify variants, states, content behavior and usage guidance.
- Document the distinction between demonstration scores and validated scoring.
- Review the prototype against the designs and identify what would require backend validation.
Output: Design specifications and a developer-ready component reference for the product.
Accessibility / Design & developer handoff
A career journey without barriers.
WCAG 2.2 Level AA guides the design and implementation requirements. ATS and market-fit scores include numeric values and labels. Country choices include names alongside flags. Native handoff uses VoiceOver and TalkBack semantics, Dynamic Type and font scaling, with 44pt iOS and 48dp Android touch targets.
Readable, beyond color
Text contrast: at least 4.5:1, or 3:1 for large text. Essential control boundaries and state indicators: 3:1. Labels and symbols carry meaning alongside color.
1.4.1 · 1.4.3 · 1.4.11Keyboard & focus
Every action works by keyboard, with visible focus that stays in view. Dialogs contain focus, support Escape and return focus to the trigger. Web targets meet the 24 × 24 CSS px minimum or its spacing exception.
2.1.1 · 2.1.2 · 2.4.7 · 2.4.11 · 2.5.8Clear names & feedback
Controls expose their name, role and state. Inputs have persistent labels and linked error messages. Async results use status announcements without moving focus.
1.3.1 · 3.3.1 · 3.3.2 · 4.1.2 · 4.1.3Adaptable layouts
Support text resizing to 200% and reflow at 320 CSS px without losing controls or content. Respect reduced-motion preferences and provide text alternatives for meaningful graphics.
1.1.1 · 1.4.4 · 1.4.10 · Motion preferenceRelease checklist: test every state with keyboard and screen readers, zoom and narrow layouts; measure actual foreground/background pairs. Static product screens document visual intent and do not establish app conformance. View the WCAG 2.2 requirements ↗
The final experience
Explore the product screens.
Browse setup, saved jobs, resume versions, reports and product states. Choose a category, then open any screen to inspect it at full size.
Onboarding & import
9 screens / Click to enlarge
Delivery & reflection
In development.
Continuing to evolve.
Atsly is in development. The work connects visual foundations, a detailed mobile screen set and a reusable design system. The interactive prototype demonstrates selected flows using sample content.
What worked
Keeping the resume, target role and named feedback dimensions connected made the review task easier to explain. The same component patterns supported reports, improvements and saved versions.
What I’d improve
I would test score comprehension and wrong-version selection earlier, then evaluate longer resumes, low-confidence feedback and suggestions that accidentally change meaning.
What I learned
A higher score is not the only sign of a useful tool. Applicants need to understand the feedback, recognize its limits and stay responsible for the claims in their resume.
