1. What is a UX/UI Designer?

At EvenUp, the role of a UX/UI Designer (often titled Product Designer or Staff Product Designer) is far more than just visual execution. You are the architect of the interface between complex artificial intelligence and the pursuit of justice. We are a vertical SaaS company on a mission to close the justice gap, and your design decisions directly impact how personal injury lawyers secure better outcomes for victims.

In this position, you will own the end-to-end design process for critical product areas. You are not just designing screens; you are designing workflows for high-stakes environments where efficiency and accuracy are paramount. Whether you are leading our Design Systems to ensure scalability or crafting specific B2B workflows for power users, your work bridges the gap between sophisticated AI/ML technology and the attorneys who rely on it. You will collaborate deeply with engineers, data scientists, and product managers to turn ambiguous legal problems into intuitive, high-leverage tools.

2. Common Interview Questions

These questions are based on real interview experiences from candidates who interviewed at this company. You can practice answering them interactively on Dataford to better prepare for your interview.

3. Getting Ready for Your Interviews

Preparing for an interview at EvenUp requires a shift in mindset. We are a fast-growing startup dealing with dense data and complex user needs. Your preparation should focus not just on "clean UI," but on how you manage complexity and drive product strategy.

Design Craft & Systems Thinking – You must demonstrate deep expertise in Figma and an ability to build scalable solutions. For the Staff role specifically, we evaluate your ability to create and maintain design systems that other designers and engineers love to use. We look for precision, consistency, and a strong command of interaction design.

Complex Problem Solving – We build for specialized power users (attorneys) in a B2B environment. You need to show how you take massive amounts of information—medical records, police reports, legal precedents—and synthesize them into clear, actionable interfaces. We value designers who can simplify complexity without losing necessary detail.

Collaboration & Ambiguity – Startups move fast. We evaluate how you partner with cross-functional teams, especially AI researchers and engineers. You should be ready to discuss how you navigate ambiguous problem spaces, make trade-offs between speed and perfection, and advocate for design excellence in a technically sophisticated environment.

4. Interview Process Overview

The interview process at EvenUp is rigorous but designed to give you a clear view of our challenges and culture. Generally, the process moves quickly, reflecting our "execution mindset." You should expect a series of conversations that test both your hard skills (visual design, prototyping) and your soft skills (strategy, communication).

The process typically begins with a Recruiter Screen, followed by a Hiring Manager screen where you will discuss your background and interest in legal tech. If successful, you will move to a portfolio review or deep dive. This is the most critical step: you will present case studies that highlight your process, from research to final pixels. Expect deep questions about why you made specific decisions.

The final stage is an onsite loop (often virtual) comprising multiple sessions. These usually include a deeper portfolio presentation, a whiteboard or problem-solving challenge (often focused on a B2B or workflow scenario), and behavioral interviews with cross-functional partners like Engineering and Product Management. Throughout this process, we are looking for evidence of your ability to "ship high-quality features efficiently."

This timeline illustrates a standard flow. Note that for senior or Staff roles, the emphasis on the Portfolio Presentation and System Design discussions will be significantly higher. Use the gaps between stages to refine your case studies—specifically focusing on the business impact of your designs.

5. Deep Dive into Evaluation Areas

To succeed, you need to demonstrate mastery in several core areas. We tailor our evaluation to find designers who can thrive in a high-growth, AI-driven environment.

Product Thinking & Strategy

We evaluate whether you can define the problem before you start designing. You should be able to articulate how your design choices support business goals.

Be ready to go over:

• Problem definition – How you validate that you are solving the right problem.
• Success metrics – How you measure the impact of your designs (e.g., time on task, error reduction).
• Scoping – How you break down large, ambiguous initiatives into shippable versions.

Example questions or scenarios:

• "Tell me about a time you influenced the product roadmap based on user research."
• "How do you decide what features to cut when working against a tight deadline?"

Interaction Design & Complexity

Since our users are legal professionals handling sensitive cases, the interface must be efficient and trustworthy. We look for your ability to handle data density.

Be ready to go over:

• Information Architecture – Organizing complex legal data hierarchies.
• Workflow optimization – Designing for "power users" who need speed and keyboard shortcuts.
• Prototyping – Using high-fidelity prototypes to communicate interaction details to engineers.

Example questions or scenarios:

• "Walk me through a complex dashboard or data table you designed. How did you handle edge cases?"
• "How would you design an interface that requires a user to review hundreds of documents quickly?"

Design Systems & Craft (Critical for Staff Role)

For the Design Systems focus, this is the primary evaluation criteria. We need to see that you can build tools that scale.

Be ready to go over:

• Component architecture – Building flexible, reusable Figma components.
• Documentation – How you document patterns for engineering adoption.
• Governance – How you manage contributions to the system from other designers.

Example questions or scenarios:

• "How have you measured the adoption of a design system you built?"
• "Describe a time you had to refactor a legacy component. What was your process?"