Sample shortlist · candidates written by us, real screener output
Web Designer
This is what the screening delivers: every candidate scored against the brief, with screening notes, their answers and a graded work sample. These sample candidates were written by us and run through the real screener — the scores and notes are its unedited output.
At a glance
Highest score first. Scores within 2 points are level: when we had the screener read the same two applications again, the gap between them moved by up to 2. A must-have in the brief (below the list) costs 5 points when the application does not show it and 2 when it only partly does.
- Lucía H.Goes on to the interviewAhead of Gerald R. mainly on the brief: Gerald R. only partly showed "hands off a file a developer can build without guessing".85/100
- Gerald R.Goes on to the interviewAhead of Palesa M. mainly on the work sample (82 vs 48).80/100
- Palesa M.Stops here49/100
2 of 3 clear 70, the score an applicant needs to go on to the written interview. A real shortlist only holds people who clear it and then the interview; the one below it is shown so you can see what the screener turns down.
The brief they were screened against
Role: Web Designer · Band: $900–1,600/mo
Must-haves: designs marketing pages in Figma mobile-first, explains hierarchy decisions, hands off a file a developer can build without guessing, pushes back on a reference-led brief with data
Nice to have: Webflow or WordPress builds, components and design systems, basic accessibility (contrast, tap targets)
Scored on 2026-09-23 by the AI screener that grades real applicants: the web-designer rubric, run on claude-sonnet-4-6. Nothing below was edited afterwards — including where it went against a candidate. The rubric and weights are published.
Lucía H. · 1 of 3
SCREEN 85/100How the 85 adds up · Top ~10%
A bar is as long as its part's weight; the filled share is the score out of 100.
- Graded work sample 35%84
Three decisions are specific, numbered, and evidenced — 40px/64px type scale, 44px tap targets, 8-point spacing variables — with a real outcome (0.9% to 1.6% mobile demo requests) and an honest self-critique about the tablet width and font weights.
- Scenario judgment 25%87
Leads with analytics decomposition (mobile share vs. mobile conversion rate vs. enquiry source) before responding, names specific tools (GA4, Clarity), and proposes a concrete 30-day post-launch comparison — not a generic 'I'd push back' answer.
- Experience specificity 20%83
Six years, 30 homepages, named tools with specific feature depth (Client-First, number variables, Dev Mode), and a quantified outcome tied to a named vertical — physiotherapy scheduling — with desktop as a control.
- Written & spoken English 15%82
Consistently precise register throughout — 'the change was the mobile page, not the traffic' shows controlled, client-ready prose with no errors.
- Salary-band fit 5%100
Asks $1,500 a month, inside the $900–1,600 band.
Must-haves in the brief: 4 of 4 shown
- designs marketing pages in Figma mobile-first — shown
I design the mobile frames first
- explains hierarchy decisions — shown
The eye goes to the headline first because it's the largest type by a clear step (40px on mobile, 64px on desktop, against 18px body), then to the one coloured shape
- hands off a file a developer can build without guessing — shown
hand off with components, variables and notes written for a developer who has never seen the project
- pushes back on a reference-led brief with data — shown
Before I reply, I look past the 68%. Three numbers matter more: what share of enquiries (GA4 key events) come from mobile, the mobile conversion rate against desktop
The parts, weighted as above, come to 85.
Screening notes
Strongest: Scenario answer — decomposes analytics before responding and proposes a measurable post-launch test, not just a process description.
Concern: Work sample is described, not shown; no link or screenshots are present, so the Figma file quality cannot be assessed here.
Worth asking: Can they share the Figma file or a read-only link before the next round, and walk through the tablet-width fix they identified?
Verdict: A well-evidenced, analytically grounded candidate whose ask sits near the top of the band and whose stated depth across Figma, Webflow, and data tools aligns closely with the brief.
Experience
6 years designing marketing sites, the last 4 at a Buenos Aires studio working for US software and subscription companies: about 30 homepages and landing pages, designed in Figma and built in Webflow, half of them by me. I design the mobile frames first and hand off with components, variables and notes written for a developer who has never seen the project. Best result: a homepage redesign for a US physiotherapy scheduling platform, after which mobile demo requests went from 0.9% to 1.6% of sessions over eight weeks while desktop stayed flat — so the change was the mobile page, not the traffic.
Tools
Figma (auto layout, components and variants, number variables with Mobile and Desktop modes for spacing, Dev Mode for handoff), Webflow (I build about half my own designs, with Client-First class naming), FigJam for kick-off workshops, GA4 and Microsoft Clarity for the data I design from, Stark for contrast checks, WordPress (I hand off to WordPress developers; I don't build in it myself)
Scenario answer
Asked: A client asks you to redesign their homepage. They send three competitor sites they like and ask you to make it look like these. You check their analytics: 68% of their traffic is mobile, but all three reference sites are clearly desktop-first. Walk through how you'd handle the brief — what you'd push back on, what questions you'd ask, and how your deliverable would differ from what they described.
I wouldn't start by saying no to the references. The client is telling me something real with them; my job is to work out what, and separate it from the layout that came along with it. Before I reply, I look past the 68%. Three numbers matter more: what share of enquiries (GA4 key events) come from mobile, the mobile conversion rate against desktop, and which pages mobile visitors land on. If mobile is 68% of visits but only 35% of enquiries, either the mobile page is losing people or they come back on a laptop to enquire — ten Microsoft Clarity recordings of mobile visitors usually show which in a few minutes. Then a 30-minute call with the three sites open. My questions: 1. What exactly do you like in each one? It's usually the confidence of the headline, the photography or the type — rarely the three-column grid. 2. What is the one thing a visitor should do on this homepage: book, buy, call? 3. Where does the mobile traffic come from? Someone arriving from an Instagram ad behaves differently from someone who searched your name. 4. Who builds it, and in what? That changes how I hand off. What I push back on: copying the layouts. Each reference was designed for a wide screen — a hero with the button in a side column, hover effects, a feature grid that becomes a very long scroll on a phone. I can give them the feel of those sites; I shouldn't give them the structure, because two-thirds of their visitors will never see it the way it was designed to be seen. What I deliver instead: - The mobile homepage first, at 375px, then the desktop version — both finished, neither stretched from the other. - A one-page 'reference translation': for each site, what I kept (say, the serif headlines from the first, the product photography from the second, the customer-logo strip from the third) and what I dropped and why — hover cards don't exist on a touchscreen, and an autoplay hero video costs load time on a phone. - A file a developer can build without asking: auto layout throughout, spacing and type as variables, every button state drawn, and a note on what changes between breakpoints. If they still want a copy of the first reference after all that, it's their site. I'd design it, show its mobile version next to mine, and ask that we compare mobile enquiries for 30 days after launch.
Work sample
Asked: Describe a page redesign or interface you've designed (link, screenshots, or describe it in detail). Walk through three specific decisions: one about visual hierarchy, one about the mobile layout, and one about spacing or density — and what you'd change doing it again.
WORK SAMPLE — homepage redesign for a US scheduling platform for physiotherapy clinics (live since last year; I can walk through the Figma file on a call) CONTEXT: 71% of visits on mobile, most from paid social. The old homepage was a desktop design squeezed down: a 4-slide carousel, two equal buttons ('Book a demo' and 'See pricing') and a 3-column feature grid. 1. HIERARCHY — ONE HEADLINE, ONE BUTTON, ONE COLOUR. I replaced the carousel with a single headline in the clinic owner's words — 'Fill cancelled appointments before they cost you' — and made 'Book a demo' the only filled button on the page, in the only saturated colour. 'See pricing' became a text link beneath it. The eye goes to the headline first because it's the largest type by a clear step (40px on mobile, 64px on desktop, against 18px body), then to the one coloured shape. Two equal buttons had asked visitors to choose before the page had told them anything. 2. MOBILE — THE RECOMMENDED PLAN FIRST. On desktop the three plans sit side by side. Stacked on a phone, comparing them meant about 2,400px of scrolling, and Clarity showed most visitors never reached the third. On mobile the plan most clinics buy comes first and fully open, the other two collapsed below it, and a sticky 'Book a demo' bar appears once the hero scrolls away. Every tap target is at least 44px high, and the sales number is a tap-to-call link, which the old site didn't have. 3. SPACING — A SEPARATE MOBILE SCALE. The old site used 120px between sections on every screen, so on a phone nearly a third of the scroll was empty. I set up an 8-point scale as Figma number variables with a Desktop mode (96px between sections) and a Mobile mode (48px), so the same components change spacing when the frame's mode changes, and the developer builds the scale once instead of guessing per section. RESULT: mobile demo requests went from 0.9% to 1.6% of sessions over the next eight weeks; desktop stayed at about 2.3%. WHAT I WOULD CHANGE: I designed the tablet width last, and it shows — at 768px the plan cards are awkwardly wide. I'd design it as its own frame instead of letting it fall between the other two. I'd also load two font weights instead of four; the extra two cost load time on phones for very little.
The screener grades what they write about this work: it cannot open a link or watch a video. In a real search the applicant's link opens the work itself, and you look at it before deciding anything. These sample candidates are written, so there is nothing behind a link to show.
Availability
Full-time on US Eastern hours from Buenos Aires: 11am–8pm ART in the US winter, 10am–7pm in summer. Two weeks' notice.
Gerald R. · 2 of 3
SCREEN 80/100How the 80 adds up · Top ~10%
A bar is as long as its part's weight; the filled share is the score out of 100.
- Graded work sample 35%82
Specific hierarchy, mobile, and density decisions with real numbers (90→140 calls, 240px hero, 56px targets, 375×667 test size) and an honest handoff failure acknowledged.
- Scenario judgment 25%84
Opens with data validation, uses phone screenshots as client-facing evidence, asks the right questions, and reframes the deliverable around mobile-first — all grounded in service-business specifics.
- Experience specificity 20%78
Five years, ~60 sites, named tools (CallRail, Stark, Elementor Pro, Dev Mode), a real outcome with an honest caveat about seasonal confounding.
- Written & spoken English 15%80
Consistently clear and direct; phrases like 'pushback is only as good as its numbers' show confident, professional register with no errors.
- Salary-band fit 5%100
Asks $1,150 a month, inside the $900–1,600 band.
Must-haves in the brief: 3 of 4 shown, 1 partly
- designs marketing pages in Figma mobile-first — shown
the mobile homepage is the main design, the desktop version comes second
- explains hierarchy decisions — shown
The eye lands on the headline because of its size and position, then on the only warm colour
- hands off a file a developer can build without guessing — partly shown (−2)
Now I annotate states and spacing in the file, set spacing as variables and use Dev Mode, so the file answers those questions without me
- pushes back on a reference-led brief with data — shown
pushback is only as good as its numbers
The parts, weighted as above, come to 82; must-haves not fully shown cost 2, so 80.
Screening notes
Strongest: Scenario answer — data-first pushback with a concrete client-facing move (phone screenshots) and service-business fluency throughout.
Concern: Handoff practice is described as a recent correction, not an established habit; must-have 3 is only partly demonstrated.
Worth asking: Can they share a current Figma file with annotations and Dev Mode specs so handoff quality can be assessed directly?
Verdict: A focused, commercially grounded web designer whose mobile-first instincts and scenario judgement are strong, with handoff rigour still maturing.
Experience
5 years designing websites for US home-service businesses — plumbers, HVAC and roofing companies — at a Cebu agency that builds on WordPress. About 60 sites, most of them redesigns, and on these sites the phone is the business: most leads are calls from someone whose AC or water heater just stopped. I design in Figma and usually build my own designs in Elementor. I measure through the client's call tracking: my best redesign took a Phoenix HVAC company from about 90 calls a month from the website to 140 within two months, though summer started in the same period, so not all of it is mine.
Tools
Figma (auto layout, components; Dev Mode — still learning to annotate properly for other developers), WordPress with Elementor Pro and some Gutenberg blocks, CallRail call-tracking reports, GA4, PageSpeed Insights, Microsoft Clarity, Photoshop for image prep, Stark for contrast
Scenario answer
Asked: A client asks you to redesign their homepage. They send three competitor sites they like and ask you to make it look like these. You check their analytics: 68% of their traffic is mobile, but all three reference sites are clearly desktop-first. Walk through how you'd handle the brief — what you'd push back on, what questions you'd ask, and how your deliverable would differ from what they described.
First I check the data behind the 68%, because pushback is only as good as its numbers. In GA4 I compare mobile and desktop on key events — form submissions and tap-to-call clicks, if those are tracked; on half the sites I inherit, they aren't — and I look at which pages mobile visitors land on. For a service business I also ask for the call-tracking report, because many mobile leads are phone calls that never touch a form. Then I do the thing that usually settles it: I open each reference site on my phone and take full-length screenshots. A desktop-first site on a phone looks like what it is — a small hero, a phone number hidden in the menu, a feature grid that becomes a long scroll. I put those next to the client's own mobile homepage and send them with one line: 'This is how 68% of your visitors would see the design you like.' Questions I'd ask: - What do you like in each site — the colours, the photos, the tone? Usually it's one or two things, and those I can keep. - What does a good lead look like: a call, a booked appointment, a form? - Is there anyone else whose opinion decides this? - Do you have real photos of your team and your trucks? Stock photos are the first thing I'd replace. What I push back on: copying their layouts. I keep what the client likes about the look and design the page for the phone first — the phone number and one clear headline in the first screen, a sticky bottom bar with 'Call now' and 'Book online', and the reviews moved up, because trust is what makes someone call. How the deliverable differs: the mobile homepage is the main design, the desktop version comes second, and I present it on a phone, not on a big monitor, because that's where most of their customers will see it. One honest note: I usually build my own designs in Elementor, so my Figma files have been written for me. If another developer builds this one, I'd put extra time into the handoff — layer names, spacing values, every button state — because I've learned that what's obvious to me isn't obvious to them.
Work sample
Asked: Describe a page redesign or interface you've designed (link, screenshots, or describe it in detail). Walk through three specific decisions: one about visual hierarchy, one about the mobile layout, and one about spacing or density — and what you'd change doing it again.
WORK SAMPLE — homepage redesign for a family-owned HVAC company in Phoenix (WordPress, built by me in Elementor) THE PROBLEM: 82% of visits were on mobile, and the old homepage opened with a stock photo of a family on a sofa and 'Welcome to our website'. The phone number was inside the hamburger menu. 1. HIERARCHY — THE PROMISE AND THE PHONE. The first screen now says 'Same-day AC repair in Phoenix' in the largest type on the page, with the Google rating (4.8 from 600+ reviews) right under it and one orange 'Call now' button — the only orange on the page. The eye lands on the headline because of its size and position, then on the only warm colour. The stock family moved out and the company's own technicians and trucks came in. 2. MOBILE — A STICKY CALL BAR. On phones a bar stays fixed at the bottom with 'Call now' (a tap-to-call link) and 'Book online', 56px tall so it's easy to hit with a thumb. The 3×3 grid of service icons became a list of tappable rows, each 56px high, because nine small icons on a phone are hard to read and harder to tap. 3. DENSITY — FIT THE FIRST SCREEN. The old hero image was 520px tall on mobile and pushed everything useful below the fold. I cut it to a 240px strip and tightened the spacing so the headline, the rating and the call button all fit on a 375×667 screen, the smallest one we still test on. RESULT: calls from the website went from about 90 a month to 140 in the first two months (CallRail), with the caveat that summer started in the same period. WHAT I WOULD CHANGE: because I built it myself, the Figma file was really a sketch of what I then built in Elementor. When the client later moved to another developer, that developer sent me more than 20 questions about hover states, breakpoints and spacing. Now I annotate states and spacing in the file, set spacing as variables and use Dev Mode, so the file answers those questions without me.
The screener grades what they write about this work: it cannot open a link or watch a video. In a real search the applicant's link opens the work itself, and you look at it before deciding anything. These sample candidates are written, so there is nothing behind a link to show.
Availability
Full-time, 9pm–6am PHT, which is 9am–6pm EDT; I start an hour later when the US is on winter time. Available in two weeks.
Palesa M. · 3 of 3
SCREEN 49/100How the 49 adds up · Thin
A bar is as long as its part's weight; the filled share is the score out of 100.
- Graded work sample 35%48
Describes standard decisions (hero headline, stacked columns, white space) with no specifics: no measurements, no rationale beyond aesthetics, no evidence of buildable handoff.
- Scenario judgment 25%52
Acknowledges mobile traffic and suggests inspiration over copying, but designs desktop first and never uses the analytics data as a pushback argument.
- Experience specificity 20%58
Four years, real client verticals, and Figma-to-WordPress handoff named, but no numbers, project outcomes, or decisions beyond tool names.
- Written & spoken English 15%72
Consistently clear and correct; phrase 'take inspiration from the reference sites rather than copying them' shows natural, professional register throughout.
- Salary-band fit 5%100
Asks $1,000 a month, inside the $900–1,600 band.
Must-haves in the brief: 0 of 4 shown, 4 partly
- designs marketing pages in Figma mobile-first — partly shown (−2)
I would design the desktop homepage in Figma based on the style of the references, and then create a mobile version that is fully responsive
- explains hierarchy decisions — partly shown (−2)
I used a large hero image of the team with a bold headline and a 'Contact us' button on top of it, so it is the first thing visitors see. I made the headline bigger than everything else so it stands out.
- hands off a file a developer can build without guessing — partly shown (−2)
I design the layouts in Figma and hand them over to our developers, who build them in WordPress
- pushes back on a reference-led brief with data — partly shown (−2)
I would let the client know that since 68% of their traffic comes from mobile, it is very important for the new design to work well on mobile devices
The parts, weighted as above, come to 57; must-haves not fully shown cost 8, so 49.
Screening notes
Strongest: Clean, professional English and four years of real agency experience handing Figma files to WordPress developers across recognisable client verticals.
Concern: Every answer stays at surface level — no measurements, no hierarchy rationale beyond size, no evidence the handoff file is actually buildable without guessing.
Worth asking: Can they share a Figma file or live URL? How do they document spacing, type styles, and component states for developers?
Verdict: A competent mid-level candidate whose experience is real but whose answers reveal generic thinking rather than the mobile-first, data-led rigour the brief requires.
Experience
4 years as a web designer at a Johannesburg digital agency, designing websites for small and medium businesses — accounting firms, a private school, restaurants and a car dealership. I design the layouts in Figma and hand them over to our developers, who build them in WordPress. I am passionate about clean, modern design and creating user-friendly websites that represent the client's brand well. I work well with clients and I am good at understanding what they want.
Tools
Figma, Adobe Photoshop, Adobe Illustrator, WordPress (Elementor), Canva, Google Analytics (basic)
Scenario answer
Asked: A client asks you to redesign their homepage. They send three competitor sites they like and ask you to make it look like these. You check their analytics: 68% of their traffic is mobile, but all three reference sites are clearly desktop-first. Walk through how you'd handle the brief — what you'd push back on, what questions you'd ask, and how your deliverable would differ from what they described.
When a client sends three competitor websites and asks me to make their homepage look like them, I would first study the reference sites carefully to understand what the client likes about them — the colours, the layout, the fonts and the overall style. I would let the client know that since 68% of their traffic comes from mobile, it is very important for the new design to work well on mobile devices. I would suggest that we take inspiration from the reference sites rather than copying them directly, so that the website is unique to their brand. Some questions I would ask: What do you like most about each reference site? What are your brand colours and fonts? What is the main goal of the homepage? Who is your target audience? For the deliverable, I would design the desktop homepage in Figma based on the style of the references, and then create a mobile version that is fully responsive, with the columns stacked and a hamburger menu. I would make sure the buttons are big enough to tap and the text is easy to read on a small screen. This way the client gets the look they want, and their mobile users still get a good experience.
Work sample
Asked: Describe a page redesign or interface you've designed (link, screenshots, or describe it in detail). Walk through three specific decisions: one about visual hierarchy, one about the mobile layout, and one about spacing or density — and what you'd change doing it again.
WORK SAMPLE — homepage redesign for an accounting firm in Johannesburg The client's old website looked outdated and was hard to navigate, so they wanted a fresh, modern design that would make the firm look more professional. 1. VISUAL HIERARCHY — I used a large hero image of the team with a bold headline and a 'Contact us' button on top of it, so it is the first thing visitors see. I made the headline bigger than everything else so it stands out. 2. MOBILE LAYOUT — On mobile I stacked the three service columns on top of each other and changed the navigation into a hamburger menu to save space. I also made sure the contact button is easy to tap. 3. SPACING — I used generous white space between the sections to make the design feel clean and modern and easier to read. WHAT I WOULD CHANGE — I would add some subtle animations to make the page more engaging, and I would spend more time testing the mobile version on different phones, because some of the spacing looked too big on smaller screens.
The screener grades what they write about this work: it cannot open a link or watch a video. In a real search the applicant's link opens the work itself, and you look at it before deciding anything. These sample candidates are written, so there is nothing behind a link to show.
Availability
Full-time, 11am–8pm SAST, which overlaps with US Eastern mornings (about 4 hours). Available in one month.
This is the artifact every search delivers
Post the role and the same screener runs on your real applicants — the questions arrive already written, and you read every finalist in full before any fee is due.
The same screener, other roles
- Customer Support VA
- Executive Assistant
- Bookkeeper
- Operations Manager
- Social Media Manager
- Data Entry Specialist
- Content Marketer
- Junior Developer
- Graphic Designer
- Sales Development Rep
- Real Estate VA
- E-commerce VA
- Bookkeeping Assistant
- Virtual Assistant
- Video Editor
- Copywriter
- SEO Specialist
- PPC Specialist
- WordPress Developer
- Shopify Developer
- Accountant
- Project Manager
- Lead Generation Specialist