Application / UI/UX Designer

Tell us how you build.

Short, specific answers beat long ones. Your draft is kept in this browser until you submit.

01 About you

Full name

Location and timezone

Hours per week you can give

GitHub or portfolio

LinkedIn optional

This is a paid role, but the budget is still being negotiated, so we cannot give you a number yet. Does that work for you?

Yes, I can start before the budget is set I need the number before I start Contact me once the budget is set

02 Your experience

What is your stack?

Design tools, prototyping, research methods, design systems, handoff, any code you write. Mark what you have used in shipped work.

How much do you work in code?

Describe one product or feature you designed that shipped.

What problem did it solve, how did you test it with users, and what did you change after launch?

03 How you would work here

Reviewers say our pull-request comments are "too long, I just scroll past". 70% of comments are never expanded. What do you do in the first week, and what would you change?

How do you research it with few users and little time?

An analysis ends in one of three states: findings, no findings, or incomplete, because some values are only known after apply. In early tests, users read "incomplete" as "safe". How do you design the three states so nobody makes that mistake?

What is the strongest way to show severity in a list of findings?

Color only, from red to yellow A text label and an icon, with color as a secondary cue Icons only, to save space Sort by severity and hide the label

04 Design problem

One change opens a security group to the internet, widens an IAM policy, and marks a database for replacement. Each finding has a severity from the analyzer, a grounded explanation and the plan diff.

It must work as a GitHub comment (Markdown only, no scripts, no custom styles) and later as a dashboard page. You may link sketches or a Figma file in your answer.

How would you design the review experience?

Cover these points. If you think the brief is wrong in part, say so and explain why.

Who reads it, and what they must decide
What they see in the first five seconds
Structure of the comment within the limits of Markdown
States: no findings, incomplete analysis, explanation withheld
How the dashboard extends the comment instead of repeating it
Accessibility
How you would test it in the first two weeks

0 words. Most good answers run 300 to 800.

Your answers are used only to review this application.

Tell us how you build.

Thank you.