\n\n\n\n.toolbar {\n display: flex;\n flex-wrap: wrap; / lets the row break instead of shrinking the buttons when they grow /\n gap: 4px;\n width: 300px;\n margin: 16px;\n padding: 0;\n}\n.toolbar button {\n box-sizing: border-box;\n width: 28px;\n height: 28px;\n padding: 0;\n border: 1px solid #667;\n border-radius: 4px;\n background: #eef0f6;\n}\n\n/ Primary input is a finger: same markup, bigger boxes. /\n@media (pointer: coarse) {\n .toolbar button {\n width: 44px;\n height: 44px;\n }\n}\n\nThe desktop rules are untouched: 28px buttons with a 4px gap.\nThe coarse block raises width and height to 44px. Because the buttons are real boxes of that size, the whole 44px square is the target and no extra hit-area trick is needed.\nThe toolbar is 300px wide. At 44px with 4px gaps, 6 x 44 + 5 x 4 = 284px fits and 7 x 44 + 6 x 4 = 332px does not, so the eight buttons break into rows of 6 and 2. On a fine pointer, 8 x 28 + 7 x 4 = 252px fits in one row.\nWhere wrapping would make the toolbar too tall (a 14-button toolbar at 44px wraps to three rows of 6, 6 and 2, as the last line of the output shows), the alternatives are horizontal scrolling or moving the least-used actions into an overflow menu. Those change the markup and behaviour, which is the point at which \"no redesign\" stops being possible.\n\nVerifying it\n\nThe test runs in Chromium, Firefox and WebKit, the three browser engines (the rendering cores that lay out the page), driven by Playwright 1.48.2, a library that scripts real browsers; its WebKit build is Playwright's, not Safari, and it runs headless, meaning without a visible window, so it can measure layout and simulate a tap but cannot tell how a real thumb feels on a real phone. A fine pointer is the default context. A touch context is created with hasTouch: true, in which matchMedia('(pointer: coarse)') is true in all three engines. It asserts the sizes, the row counts, that nothing pokes out of the toolbar, and that a real touch tap 40px right and 20px down from the first button's corner (inside a 44px box, outside a 28px one) activates it. Deleting the coarse rule or the flex-wrap declaration makes the assertions fail; both mutants fail the 44px size assertion, the second because a non-wrapping flex row shrinks its items to fit instead of letting them overflow.\n\n// check.mjs\nimport { chromium, firefox, webkit } from 'playwright';\nimport { readFileSync } from 'node:fs';\n\nconst css = readFileSync('toolbar.css', 'utf8');\nconst html = readFileSync('index.html', 'utf8');\nconst variants = {\n shipped: css,\n noCoarseRule: css.replace(/@media \\(pointer: coarse\\) \\{[\\s\\S]*\\n\\}\\n/, ''),\n noWrap: css.replace('flex-wrap: wrap;', 'flex-wrap: nowrap;'),\n};\nconst ok = (c, m) => { if (!c) throw new Error('ASSERT FAILED: ' + m); };\n\nasync function open(browser, variant, touch) {\n const ctx = await browser.newContext({ viewport: { width: 400, height: 400 }, hasTouch: touch });\n const p = await ctx.newPage();\n await p.route('**/toolbar.css', r => r.fulfill({ contentType: 'text/css', body: variants[variant] }));\n await p.route('**/index.html', r => r.fulfill({ contentType: 'text/html', body: html }));\n await p.goto('http://x.test/index.html');\n return p;\n}\nconst layout = p => p.evaluate(() => {\n const bar = document.querySelector('.toolbar');\n const r = [...bar.querySelectorAll('button')].map(b => b.getBoundingClientRect());\n const rows = {};\n r.forEach(b => { rows[Math.round(b.top)] = (rows[Math.round(b.top)] || 0) + 1; });\n return {\n coarse: matchMedia('(pointer: coarse)').matches,\n size: [r[0].width, r[0].height],\n perRow: Object.values(rows),\n overflowsBar: r.some(b => b.right > bar.getBoundingClientRect().right + 0.5),\n minSide: Math.min(...r.map(b => Math.min(b.width, b.height))),\n };\n});\n\nasync function fineTest(b) {\n const p = await open(b, 'shipped', false);\n const m = await layout(p);\n ok(!m.coarse && m.size.join() === '28,28' && m.perRow.join() === '8', 'fine pointer keeps the dense 28px single row');\n return m;\n}\nasync function coarseTest(b, variant) {\n const p = await open(b, variant, true);\n const m = await layout(p);\n ok(m.coarse, 'touch context reports pointer: coarse');\n ok(m.minSide >= 44, 'every button is at least 44 by 44');\n ok(!m.overflowsBar, 'no button pokes out of the toolbar');\n ok(m.perRow.join() === '6,2', 'wraps to rows of 6 and 2');\n // a tap 40px right and 20px down from a button's top-left lands inside its 44px box but outside a 28px one\n const first = await p.evaluate(() => { const r = document.querySelector('.toolbar button').getBoundingClientRect(); return { x: r.x, y: r.y }; });\n await p.touchscreen.tap(first.x + 40, first.y + 20);\n ok((await p.evaluate(() => window.clicks)).join() === 'Bold', 'tap near the edge of the 44px button activates it');\n return m;\n}\n\nfor (const [name, type] of [['chromium', chromium], ['firefox', firefox], ['webkit', webkit]]) {\n const b = await type.launch();\n const f = await fineTest(b);\n const c = await coarseTest(b, 'shipped');\n console.log(name, 'fine:', JSON.stringify({ size: f.size, perRow: f.perRow }), 'coarse:', JSON.stringify({ size: c.size, perRow: c.perRow }));\n const res = {};\n for (const v of ['noCoarseRule', 'noWrap']) { try { await coarseTest(b, v); res[v] = 'STILL PASSES'; } catch (e) { res[v] = 'fails: ' + e.message; } }\n console.log(' without the rule:', JSON.stringify(res));\n // 14 buttons: clone the first button until there are 14, then count buttons per row at 44px\n const p14 = await open(b, 'shipped', true);\n await p14.evaluate(() => { const bar = document.querySelector('.toolbar'); while (bar.children.length < 14) bar.append(bar.firstElementChild.cloneNode(true)); });\n const m14 = await layout(p14);\n ok(m14.perRow.join() === '6,6,2', '14 buttons wrap to rows of 6, 6 and 2');\n console.log(' 14 buttons, coarse pointer, buttons per row:', JSON.stringify(m14.perRow));\n await b.close();\n}\n\nRun in the Playwright 1.48.2 container, it prints the same values for all three engines (repeated runs print the same thing):\n\nchromium fine: {\"size\":[28,28],\"perRow\":[8]} coarse: {\"size\":[44,44],\"perRow\":[6,2]}\n without the rule: {\"noCoarseRule\":\"fails: ASSERT FAILED: every button is at least 44 by 44\",\"noWrap\":\"fails: ASSERT FAILED: every button is at least 44 by 44\"}\n 14 buttons, coarse pointer, buttons per row: [6,6,2]\nfirefox fine: {\"size\":[28,28],\"perRow\":[8]} coarse: {\"size\":[44,44],\"perRow\":[6,2]}\n without the rule: {\"noCoarseRule\":\"fails: ASSERT FAILED: every button is at least 44 by 44\",\"noWrap\":\"fails: ASSERT FAILED: every button is at least 44 by 44\"}\n 14 buttons, coarse pointer, buttons per row: [6,6,2]\nwebkit fine: {\"size\":[28,28],\"perRow\":[8]} coarse: {\"size\":[44,44],\"perRow\":[6,2]}\n without the rule: {\"noCoarseRule\":\"fails: ASSERT FAILED: every button is at least 44 by 44\",\"noWrap\":\"fails: ASSERT FAILED: every button is at least 44 by 44\"}\n 14 buttons, coarse pointer, buttons per row: [6,6,2]\n\nHow to read it: size is the first button's width and height in CSS pixels; perRow lists how many buttons sit on each row, found by grouping the buttons by the rounded top coordinate of their boxes (getBoundingClientRect() returns a box's position and size), so [6,2] means a row of six and a row of two. In layout(), overflowsBar is true if any button's right edge passes the toolbar's right edge and minSide is the smallest side of any button. fineTest opens a normal (mouse-like) page and expects the dense single row; coarseTest opens a touch page and expects the 44px, two-row result plus the tap. without the rule reruns the touch checks against a stylesheet with the coarse block deleted or with flex-wrap switched off, and fails: followed by the assertion message means the checks caught the missing rule (both mutants trip the 44px size assertion first). The last line adds six more buttons (14 in all) and counts rows again.\n\nComplexity and edge cases\n\nThe layout is a single flex pass over eight items. Edge cases to handle:\n\nHybrid devices (laptops or tablets that have both a touchscreen and a mouse or trackpad): pointer reports only the primary input (see the MDN definition above), so a touch laptop whose primary input is the trackpad keeps the dense toolbar; any-pointer is true if any attached input matches, so switch to it if that matters.\nLabels: the buttons carry aria-label so the accessible name does not depend on the glyph; resizing them does not change it.\nPage height: wrapping makes the toolbar taller on touch, which pushes content below it down; account for that in the surrounding layout.\nZoom and user font size: the sizes are in CSS pixels, so they track browser zoom. If the buttons are sized in rem instead, they also track the user's default font size.\n\nRunning the code\n\nmkdir demo && cd demo\necho '{\"type\":\"module\"}' > package.json\nnpm i playwright@1.48.2 && npx playwright install chromium firefox webkit\nsave the three listings above as index.html, toolbar.css and check.mjs, then:\nnode check.mjs"}},{"@type":"Question","name":"You have a strict launch deadline but discover the current implementation violates key accessibility standards. Full remediation would delay launch. Describe the immediate steps you would take to manage this trade-off: how you would triage accessibility issues by severity, propose interim mitigations, communicate with PM/engineering/legal, and ensure accountability for full remediation post-launch.","acceptedAnswer":{"@type":"Answer","text":"The framework: severity triage, then match mitigation to severity, then make the deferred work impossible to forget.\n\nStart by triaging every accessibility violation against a concrete severity scale, not a vague \"bad/worse\" sense. A workable three-tier scale:\nBlocking: a user with a disability cannot complete a core task at all (for example, a checkout button with no accessible name, so a screen reader announces nothing actionable, or a modal that traps keyboard focus with no way out).\nDegrading: the task is completable but meaningfully harder or slower (for example, a form with low-contrast error text that a low-vision user can complete only with extra effort).\nCosmetic: a real WCAG (Web Content Accessibility Guidelines) violation that does not block or meaningfully degrade any task (for example, a decorative icon missing an aria-label when it carries no information).\n\nConcrete example: launching a checkout flow. Triage finds one Blocking issue (the \"place order\" button has no accessible label, so it's literally invisible to screen reader users), two Degrading issues (contrast ratio of 3.8:1 on form validation text, below the 4.5:1 WCAG AA minimum), and four Cosmetic issues (missing alt text on non-essential marketing images).\n\nInterim mitigations, sized to the severity. For the Blocking issue, you do not launch it as-is: either fix it (adding an aria-label is usually a same-day fix, far cheaper than full remediation) or, if genuinely un-fixable before launch, stand up a documented fallback path (a phone or chat order line specifically flagged for accessibility support) so no user is fully locked out. For Degrading issues, ship with the known gap but add a lightweight mitigation where cheap (bump the specific contrast value even if the broader design system audit waits). Cosmetic issues simply get logged, no mitigation needed pre-launch.\n\nCommunication, tailored per audience. To engineering: a ticket per issue, tagged with severity, effort estimate, and target sprint, so remediation is plannable work, not an open-ended promise. To the PM: frame it as a trade-off in product terms, \"the Blocking issue is fixed before launch; the two Degrading issues ship with an interim contrast bump and are fully remediated within two sprints; four Cosmetic issues are tracked for the next design-system pass.\" To legal: this is the audience most people forget, and it matters most, since unremediated violations carry real exposure: WCAG 2.1 AA is the de facto standard referenced in disputes under ADA Title III (the part of the US disability-rights law covering private businesses) and Section 508 (the federal law requiring US government websites to be accessible). Legal needs to know exactly what's shipping unfixed, why (the mitigation, not just \"we ran out of time\"), and needs to sign off on the residual risk in writing, since a documented good-faith remediation plan is meaningfully different, legally, from silence.\n\nAccountability for the post-launch fix. The trap here is \"we'll fix it after launch\" with no forcing function, which in practice means it never gets fixed once the team moves to the next deadline. Make it concrete: every deferred issue gets a ticket, an owner, and a target release, and the Blocking-tier bar for the next release is \"zero known Blocking issues,\" gating that release the same way you'd gate a security vulnerability. Put a specific date on the calendar (not \"next quarter\") to revisit the full list with the PM and confirm what actually shipped.\n\nThe mediocre answer here is a vague promise: \"we'll note the issues and revisit later.\" Without severity tiers, without owners, and without a legal sign-off on the specific residual risk, \"later\" is functionally \"never,\" and the team has neither reduced harm now nor guaranteed remediation later.\n\nThis same shape applies outside of web engineering. A data team publishing a public-facing report with inaccessible tables (no header structure a screen reader can navigate) faces the identical decision: triage which tables are load-bearing for a blind user's actual task versus decorative, ship a plain-text summary as an interim mitigation for the load-bearing ones, and put a ticket and a date on the real fix rather than letting \"we'll clean it up later\" quietly become permanent."}},{"@type":"Question","name":"You're interviewing at a company that evaluates candidates against a published list of leadership principles or core values. Walk through how you would prepare: how you would build an inventory of your own stories, decide which principle each story best fits, and adjust your language so it sounds authentic rather than like you memorized the company's website. Give one concrete example of a wording change you would make to an existing story so it lands as a genuine match for a specific principle instead of a name-drop.","acceptedAnswer":{"@type":"Answer","text":"Direct answer\nDifferent companies score behavioral interviews against an explicit, published list of values or principles (Amazon's Leadership Principles, Google's culture questions, Netflix's Freedom and Responsibility framing, and many others). The preparation move is building a small inventory of six to ten real stories from your own work, tagging each with the one or two principles it most naturally demonstrates, then rehearsing them so they sound like your own voice, not the company's marketing language.\n\nStructured elaboration\n1. Research the company's actual, current published list. Read the real wording rather than a paraphrase from a prep article, since the specific phrasing often matters to how an interviewer will probe.\n2. Build a story inventory before the interview: six to ten stories spanning different situations (a technical trade-off, a conflict, a mistake, a moment you led without formal authority, a customer-facing choice).\n3. For each story, identify which one or two principles it most naturally supports. Resist forcing a story to fit a principle it doesn't genuinely show; a shallow fit is easy for an experienced interviewer to spot.\n4. Rehearse the story itself, not a script that names the principle repeatedly. A good answer demonstrates the principle through the actions and choices described, and lets the interviewer recognize it.\n5. Prepare to reframe the same story around a different principle if asked. Candidates who over-fit one story to one principle tend to struggle when a panel probes for a different angle.\n\nWorked example\nA candidate has a story about shipping a feature despite pushback. A first-draft framing centers on: \"I pushed hard to get the feature out on time.\" A more principle-authentic framing, for a company whose stated principle is customer focus, instead leads with the evidence: \"Support tickets showed users were repeatedly confused by the old flow, so I made the case that shipping on time mattered less than shipping the right fix, and I only pushed for speed once we had confirmed the new version actually addressed what customers were reporting.\" The underlying facts are identical; the second version leads with the customer evidence, which is what makes it read as authentic to the principle rather than a generic assertion of hard work.\n\nTrade-offs and pitfalls\nOver-rehearsed language that repeats the principle's name throughout a story tends to sound recited, and interviewers who run these loops regularly notice it quickly. Forcing one story into every principle bucket produces a worse answer than admitting a different story fits better and asking, where the format allows it, to use that one instead. Researching an outdated version of a company's list, then referencing a principle name that has since changed, undermines credibility even when the underlying story is strong."}},{"@type":"Question","name":"Power users want fine-grained control and everyday users want a simple, safe default. How do you decide what to build so both are served without overcomplicating the product?","acceptedAnswer":{"@type":"Answer","text":"Direct answer\n\nI serve both with a safe default for everyday users and progressive disclosure for power users: the common path is simple and works out of the box, and fine-grained control lives one step deeper (an \"Advanced\" area, a rule editor), with guardrails. I decide per control, using who needs it, how often, and how safely it can be hidden.\n\nDecision test for each requested control\n\n1. Is a real job blocked without it? Ask power users what they are trying to achieve, not which control they want.\n2. Can the default path stay unchanged? If adding it clutters the main screen, it goes behind a deeper layer.\n3. Is it safe to misconfigure? If a wrong setting can cause harm, add a preview, a confirmation, and an undo.\n4. How many people need it? Check usage evidence and who the power users are (revenue, influence, advocacy), but do not let the loudest segment set the default.\n5. Can a preset do the job? Presets cover most of the need without exposing every knob.\n\nWorked example (illustrative): alert rules in a monitoring product\n\nEveryday users get three presets: \"Recommended\", \"Quiet\" and \"Everything\". Power users get a rule editor behind \"Advanced\" with a preview of how many alerts the rule would have sent last week and an undo for edits.\n\nRequested control | Decision\n\nCustom thresholds per metric | Advanced editor\nQuiet hours | Main settings (many need it)\nPer-channel routing | Advanced editor\nRaw query syntax | Advanced editor, with preview\nTurn alerts off completely | Not offered; use \"Quiet\" with a confirmation\n\nFive requests: one on the main screen, three behind Advanced, one declined in favour of a safer route. Measure the share of everyday users who keep the default and whether power users complete their jobs without support.\n\nFor an AI-based product\n\nExpose a few outcome-level choices (for example a \"creative\" versus \"precise\" mode) as the default, and keep model-level settings in an advanced layer.\n\nPitfalls\n\nSettings sprawl: every extra control is a decision for every user.\nHiding power features so deeply that experts leave.\nTreating the loudest segment as the whole user base.\nNo safety net on advanced controls."}}]}

Amazon UI Designer (Junior Level) - Comprehensive Interview Preparation Guide

UI Designer
Amazon
Junior
5 rounds
Updated 6/14/2026

Amazon's UI Designer interview process for junior-level candidates typically follows a structured evaluation approach that assesses both creative design capabilities and technical execution. The process begins with recruiter screening to validate background and role fit, followed by phone screening to evaluate design fundamentals and communication. Onsite rounds assess hands-on design skills through portfolio review, design exercises, systems thinking, and cultural alignment through behavioral discussions. At the junior level, the focus is on demonstrating solid foundational design skills, the ability to work independently on smaller features with guidance, and strong collaboration potential with UX teams and engineering.

Interview Rounds

1

Recruiter Screening

2

Design Exercise Phone Screen

3

Portfolio Review and Design System Knowledge

4

Behavioral Interview - Amazon Leadership Principles

5

Technical Execution and Prototyping Round

Frequently Asked UI Designer Interview Questions

Design Tools and AI-Assisted WorkflowsEasyTechnical
37 practiced

How do resizing constraints (for example, 'fill container', 'hug contents', or fixed size) in Figma or Sketch help adapt components across screen sizes? Describe a header component example that must keep the logo left and action icons right while the center area adapts between breakpoints, and explain the constraint choices you'd make.

Design Thinking and the End-to-End Design ProcessMediumTechnical
60 practiced

Product wants to add a feature, but the underlying user motivation for it isn't clear yet. How would you scope a short discovery effort, a few weeks, to actually define the problem before anyone starts designing solutions?

Coachability, Feedback, and HumilityMediumBehavioral
72 practiced

Describe a time when feedback led you to change the scope or timeline of a feature. Explain how you quantified impact, communicated the change to stakeholders, updated the sprint plan, and any retrospective or process changes you introduced to reduce future scope surprises.

Design Systems and Component LibrariesEasyTechnical
46 practiced

What is a design system, and how does it differ from a component library and from a lighter-weight style guide or pattern library? Describe the core building blocks a design system is typically made of, who benefits from having one, and give an example of when a lightweight pattern library is enough versus when a full design system is warranted.

Design Handoff and Developer CollaborationEasyTechnical
57 practiced

How do you keep design and engineering aligned during sprints? Describe specific rituals (daily syncs, pairing sessions, design reviews), artifacts (tickets with acceptance criteria, annotated prototypes), and signals that indicate alignment or drift. Provide an example of a mid-sprint process adjustment you made to restore alignment.

Visual Design Fundamentals: Typography, Color, and BrandHardTechnical
71 practiced

Your company has several related products, each with its own icon set that's drifted apart in style over time. How would you bring them back into a shared visual language without forcing every product to look identical, and where would you draw the line on what stays unique to each product versus what should be shared?

Frontend Fundamentals: HTML, CSS, and Responsive StylingEasyTechnical
116 practiced

What size should touch targets be on mobile, and why? How would you keep a dense desktop toolbar usable on touch screens without redesigning it?

Navigating Ambiguity and Adaptive PlanningMediumTechnical
112 practiced

You have a strict launch deadline but discover the current implementation violates key accessibility standards. Full remediation would delay launch. Describe the immediate steps you would take to manage this trade-off: how you would triage accessibility issues by severity, propose interim mitigations, communicate with PM/engineering/legal, and ensure accountability for full remediation post-launch.

Values-Based and Leadership-Principle InterviewsEasyBehavioral
29 practiced

You're interviewing at a company that evaluates candidates against a published list of leadership principles or core values. Walk through how you would prepare: how you would build an inventory of your own stories, decide which principle each story best fits, and adjust your language so it sounds authentic rather than like you memorized the company's website. Give one concrete example of a wording change you would make to an existing story so it lands as a genuine match for a specific principle instead of a name-drop.

Customer and User ObsessionMediumTechnical
84 practiced

Power users want fine-grained control and everyday users want a simple, safe default. How do you decide what to build so both are served without overcomplicating the product?

Want to create your own tailored preparation guide using our deep research?

Get Started for Free

Interview-Ready Courses

Visual-first, interactive, structured learning paths

Browse UI Designer jobs

AI-enriched listings across hundreds of company career pages

Explore Jobs