My Interview Questions – bikshudesigner.com

Tell me about your self

I’m a Senior Product Designer with over 7 years of experience working on web and mobile platforms. I’ve designed for different domains like e-commerce, fintech, healthcare, and SaaS, which helped me become adaptable and quick at understanding user needs.

I also have strong experience in user research, design systems, and product strategy.

Now, I’m looking for a role where I can use both my versatility and product-focused skills to create impactful, scalable user experiences.

You already completed Leapfrog UI/UX certification, why again IxDF? What’s the difference?

Why again? I believe learning is continuous. Even though I completed Leapfrog certification earlier, I wanted to deepen my knowledge, learn advanced research and design frameworks, and gain exposure to international standards. IxDF gives me that global perspective.

Difference:

Leapfrog Certification was more practical and project-based, giving me strong hands-on skills.
IxDF Certification is more research-oriented, theory-driven, and globally recognized, focusing on principles, case studies, and advanced methodologies.

You worked in service company there u have worked multiple creative projects but in our product company we have big process and u might get bored, And u didn’t have experience for working on product company, how do you handle this?

Yes, I agree that service companies and product companies work differently. In a service company, I got exposure to multiple industries and projects in shorter timelines.

I don’t see working on one product as boring I see it as an opportunity to go deeper, solve complex user problems, and refine the experience over time. In fact, I’m excited about the chance to continuously improve a product, measure impact, and see how design decisions create real value for users.

What do your colleagues say about You?

1. Teamwork-focused
My colleagues often say I’m very approachable and supportive. Whenever someone is stuck, I’m the first to offer help, which makes teamwork smoother and keeps projects moving.

2. Problem-solving & reliability
My colleagues would describe me as dependable and detail-oriented. They know they can trust me to deliver on deadlines and double-check work for accuracy.

3. Leadership & positivity
My colleagues say I bring positive energy to the team. Even during stressful projects, I keep the mood encouraging, which helps everyone stay motivated and focused.

Questions to Ask:

If I’m selected, will I be joining for a specific client project? Is it a short-term or long-term engagement?
If the client engagement ends, how does the internal redeployment process work? How long does it typically take to be staffed on a new project?
In cases where there’s no immediate client assignment, what’s the usual next step bench, internal initiatives, or learning/upskilling programs?
How is the design team structured here? Do we collaborate closely with product and engineering or is it more service-driven?
Is there a Head or Lead of Design? How are design decisions made across projects?
Are there any internal initiatives where designers contribute to innovation, frameworks, or thought leadership?
What does a typical growth path look like for a designer here over 1–2 years?
How do performance reviews work—especially for designers working across different client contexts?

Why should we hire you?

You should hire me because I bring strong end-to-end product design experience and a very practical approach. I understand business goals, work closely with stakeholders, and turn ideas into clear, user-friendly solutions. I’m confident in handling complex problems, communicating with cross-functional teams, and delivering designs that are easy for developers to build. I’m reliable, collaborative, and I take ownership from discovery to final handoff — ensuring the product meets user needs and business outcomes.

Why do you want to change your company?

I’m looking for a change because I want to grow and work on more challenging, impactful projects. My current company has been a good experience, but I feel it’s the right time for me to move into a place where I can learn more, contribute more, and work with a team that pushes me to the next level. I’m looking for better opportunities to expand my skills and take on responsibilities that match my experience.

What is your biggest challenge, how did you solve it?

Challenge 1 – GearLaunch (Accessibility & Stakeholder Alignment):
The marketing team wanted to use their brand logo color as the primary UI color. However, it failed WCAG accessibility standards. To solve this, I adjusted the shade slightly to meet accessibility while keeping brand consistency. I also conducted usability tests and presented real data showing how accessible colors improved readability. With this evidence, stakeholders agreed to the change.

Challenge 2 – SureChain (Reducing Drop-offs in B2B Registration):
The stakeholder’s goal was to increase registrations, but the KYB process was long and complex. To solve this, I redesigned the flow by asking only minimal information upfront for quick signup. Once users registered and started engaging with the product, we gradually collected additional KYB data step by step. This reduced drop-offs significantly while still capturing all necessary information over time.

What & Why do we use Sketches?

Quick, hand-drawn ideas of screens or interfaces.
Helps to explore multiple design directions before going digital.
Useful for brainstorming and early-stage discussions.

What is your process for deciding which features to add to your product?

I evaluate user needs, business goals, and technical feasibility, then prioritize features using frameworks like MoSCoW or RICE.

What kind of UX research methods and processes do you use when starting a new project?

I usually start with stakeholder interviews, and research like user interviews, surveys, and competitive analysis, followed by synthesizing findings into personas and journey maps.

How do you validate or conduct usability testing on a design?

By running moderated/unmoderated tests with target users, tracking task success, time on task, and observing pain points.

Are you a team player? Give us some examples.

Absolutely. In one project, I collaborated closely with developers and PMs to redesign a checkout flow. By holding joint design–dev workshops, we cut development time and launched a more user-friendly product faster.

How do you handle negative feedback?

I see feedback as data. I listen, clarify, and use it to iterate. If I disagree, I present user evidence to support my design choices.

Have you ever received professional criticism that you felt was unfair?

Yes. In one case, I was told my design was “too simple.” Instead of reacting defensively, I asked for clarification and presented usability data showing why simplicity was valuable. It turned into a constructive conversation.

What strengths do you bring when you join the team?

When I join a team, I bring a user-centered design mindset and the ability to translate complex business requirements into simple, intuitive experiences. I also add value by collaborating closely with product managers, developers, and stakeholders to ensure designs are practical and aligned with business goals. My colleagues often say I help bridge the gap between design and development, which accelerates the product delivery while keeping the user experience strong. Additionally, I enjoy mentoring junior designers and sharing best practices, which helps strengthen the overall design culture of the team.

1. How do you ensure your design decisions align with long-term product strategy?

I stay close to the product roadmap, involve myself in planning sessions, and validate designs against both short-term goals and future scalability.

2. Share an example of how you measured the impact of your design work.

I measure design success through:

Usability Metrics: task success rate, error rate, time on task.
Engagement Metrics: user retention, conversion rate, and drop-off points.
Accessibility Compliance: ensuring designs meet WCAG guidelines.
Stakeholder & User Feedback: satisfaction scores (like SUS, NPS).

3. Have you ever created a design system or scaled design across multiple products?

I once led the creation of a design system because multiple apps were inconsistent. I worked with designers and developers to build shared components, typography, and patterns. This not only made the products look consistent but also reduced development time significantly.

4. Balancing business goals and user needs.

In one case, the business wanted to collect more data during signup, but users wanted a faster process. I proposed progressive profiling—asking for just the essentials up front, and gathering more details later. This balanced both needs, resulting in higher signups without losing valuable business data.

5. A project that didn’t go as planned what did you learn?

I worked on a redesign that got delayed because we spent too much time iterating internally without validating ideas early. The project taught me the importance of testing quickly with users, which I now apply to avoid wasted effort and speed up decision-making.

6. Tight deadline project how did you prioritize?

On one project, the launch date was suddenly moved up. To meet the deadline, I focused on designing the critical flows first, used wireframes instead of high-fidelity designs for secondary screens, and leaned heavily on our design system for consistency. This approach allowed us to deliver on time without sacrificing usability.

7. Have you ever had a design that didn’t perform as expected?

Yes, in one onboarding flow, completion rates were lower than expected. Instead of assuming why, I analyzed analytics data and ran usability tests. We identified where users were dropping off and iterated on the flow, which improved completion by 25%.

8. Tell me about a time you had limited data.

In a project where we didn’t have much user data, I relied on heuristic evaluations, competitor research, and quick guerilla testing with a small group of users. These lightweight methods gave enough direction to move forward, and later testing confirmed the design was effective.

9. Describe a time when a stakeholder gave conflicting feedback.

In one project, two stakeholders had different opinions about the homepage hero design. To resolve it, I mapped both options against business goals and user research insights, then presented the trade-offs. This transparent approach helped them agree on a unified direction that worked for both business and users.

10. How do you handle stakeholders prioritizing opinions over user needs?

When this happens, I acknowledge their perspective but share user research to show the impact of different decisions. For example, in one project, a stakeholder wanted to add extra fields to signup, but data showed long forms caused drop-offs. I suggested progressive profiling as a middle ground, which increased signups while still collecting business data.

11. Have you mentored a junior designer?

Yes, I’ve mentored junior designers by reviewing their work, giving constructive feedback, and coaching them on how to present designs to stakeholders. Over time, I noticed their confidence grow, and eventually, they were able to handle projects independently and present their own work effectively.

12. Describe a time you collaborated with cross-functional teams.

For a major product launch, I worked closely with PMs, engineers, and marketing. To keep everyone aligned, I set up a shared Figma workspace and weekly sync meetings. This transparency reduced misunderstandings and helped us launch smoothly without last-minute surprises.

13. How do you handle disagreements within your design team?

When designers on my team have conflicting ideas, I encourage open discussion where each person explains their reasoning. If the debate continues, I suggest running quick usability tests so we can let real user behavior guide the decision. This creates a fair process and avoids personal conflicts.

14. Tell me about a conflict with a developer.

Once, a developer wanted to use default components instead of the custom ones I designed. I explained the user benefits of my approach, but I also listened to their concerns about development effort. We agreed on a middle ground that required slight design adjustments but still maintained usability. It built trust between us and kept the project moving.

15. If a developer says “we can’t do that,” what would you do?

I always ask to understand the technical limitation—whether it’s a matter of time, cost, or technology. Then, I work with the developer to find a feasible alternative that still gives users a good experience. This way, it feels like collaboration rather than a compromise, and we usually find a workable solution together.

16. What do you do when a stakeholder disagrees with UX research results?

I remind them that research is about user behavior, not opinions. I walk them through how we conducted the research, who we tested with, and what the findings mean. If there’s still disagreement, I suggest running a quick A/B test so data can guide the decision. This usually helps shift the conversation from personal opinions to evidence.

17. Have you ever faced a situation in which your recommendation was not taken?

Yes, in a checkout flow project, I recommended simplifying the process, but the client wanted to keep extra steps. Instead of pushing back, I respected their decision but later built a prototype of my version and tested it with users. When the results showed higher completion rates, the client agreed to implement it in the next release.

18. Tell me about a time when a project went off track. How did you fix it?

A redesign project I worked on was slipping behind schedule because the requirements weren’t clear. I stepped in to realign the team by organizing a quick workshop with stakeholders to clarify goals and re-prioritize features. We agreed to focus on must-have items first, which helped us catch up and deliver on time while still meeting business needs.

19. A UX client has a problem. Walk me through your response.

I listen carefully, reframe the problem, gather context, propose research or prototyping to explore solutions, and share iterations until alignment is achieved.

20. How do you make a product accessible to users with disabilities?

By following WCAG standards, ensuring keyboard navigation, alt-text for images, color contrast, captions for media, and testing with accessibility tools.

21. What analytical tools, data and KPIs have you used to evaluate your previous designs?

Google Analytics, Mixpanel, Hotjar. KPIs include task success rate, conversion rate, bounce rate, Net Promoter Score (NPS), and time on task.

22. Take us through a UX design example from your project portfolio where you set out to solve a business problem.

In a project called fabletics, the business goal was to reduce cart abandonment. I conducted usability testing, identified checkout friction, redesigned the flow, and improved conversions by 18%.

23. When you validate a design, what kind of data do you use?

A mix of qualitative (user interviews, usability tests, feedback) and quantitative (analytics, heatmaps, A/B testing) data.

Have you ever been asked to provide feedback on other projects? Take us through your approach.

Yes. I focus on being constructive—highlighting strengths first, then suggesting improvements backed by reasoning or user insights. I always aim to support, not criticize.

When you and another stakeholder disagree on one of your designs, how do you bring the other person to your side?

I first listen to understand their perspective, then present my reasoning backed by user research, usability data, or design principles. If needed, I suggest A/B testing to let data guide the decision.

What makes a great UX Designer?

Empathy, curiosity, and the ability to balance user needs with business impact while collaborating across teams.

Do you prefer written or verbal communication?

Both, depending on context. Written for documentation and clarity; verbal for quick alignment and discussions. I often follow up verbal talks with short written recaps.

Tell us about a successful presentation you gave and why you think it did well.

I presented a redesign proposal to executives. It worked well because I told a clear story—problem, user insights, solution, and business impact—while keeping visuals simple and engaging.

What would you do when you encounter communication breakdowns at work?

I step back, clarify misunderstandings, and establish a single source of truth (like documentation or a shared board). Regular check-ins also help realign the team.

What excites you about this position?

The chance to solve meaningful problems for [company’s users/customers], contribute to high-impact projects, and grow within a strong design culture.

How would you define design thinking?

(Eempathize, Define, Ideate, Prototype, Test.)

My design process starts with understanding the problem deeply.
I begin with discovery sessions with stakeholders to align on business goals, user needs, and project constraints. Then, I move into the research phase, where I conduct user interviews, analyze data, and identify key insights.

Based on those insights, I define personas, user journeys, and problem statements to ensure clarity. Next, I start the ideation and design exploration — creating wireframes, user flows, and then move to high-fidelity UI designs with a consistent design system.

Once the design is validated through feedback and usability testing, I prepare a detailed handover for developers, including documentation, specs, and design assets. I also stay involved during the development phase to ensure design quality and alignment with the intended vision. Finally, I review the product after launch and collect feedback for continuous improvement.

What is Your Design (Thinking) Process?

When it is:

a) Initial stage (new project):
I begin with understanding the problem, business goals, and user needs. I run stakeholder interviews, user research, and competitive analysis. Then, I create personas, user journeys, and define requirements.

b) Middle of the project:
I move into ideation and design. I sketch wireframes, create flows, and build prototypes. I also run usability testing and get feedback to refine designs. Collaboration with PMs and developers is high at this stage.

c) End of the project:
I finalize high-fidelity designs, ensure design system consistency, and prepare handoff documentation. I support developers during implementation and run post-launch testing to check if the design meets goals.

What is Usability Testing? What are the steps?

Usability Testing is a method to evaluate a product by testing it with real users to identify problems, measure ease of use, and gather feedback.

Steps:

Define objectives (what do you want to test?)
Prepare test scenarios and tasks
Recruit participants (target users)
Conduct the sessions (observe and record how users perform tasks)
Collect feedback (both qualitative & quantitative)
Analyze results (find pain points, measure success rate, task completion time, etc.)
Provide recommendations and iterate on design.

How do you measure the success of your designs?

I measure design success through:

Usability Metrics: task success rate, error rate, time on task.
Engagement Metrics: user retention, conversion rate, and drop-off points.
Accessibility Compliance: ensuring designs meet WCAG guidelines.
Stakeholder & User Feedback: satisfaction scores (like SUS, NPS).
Business Impact: alignment with product goals such as higher registrations, reduced churn, or increased sales.

What is Difference between Usability & Accessibility?

Usability = How easy and efficient it is for users to use a product.
Accessibility = Making sure everyone, including people with disabilities (visual, auditory, motor), can use the product.

👉 Usability is about ease. Accessibility is about inclusiveness.

What is Information Architecture? and what is the difference between Information Architecture vs Sitemap?

Information Architecture (IA) is the process of structuring and organizing content so that users can easily find and understand it. It’s like creating a blueprint for a product.

IA = The logical structure of content, navigation, hierarchy, and relationships.
Sitemap = A visual diagram (like a tree) showing the pages/screens and how they connect.

👉 IA is the strategy and thinking. Sitemap is the outcome or representation of that strategy.

What is Design System, why do we use it?

A Design System is a collection of reusable components (buttons, forms, colors, typography) with guidelines on how to use them.

We use it to:

Maintain consistency across products.
Save time by reusing components.
Improve collaboration between designers and developers.

Scale design for future needs.

What is User Persona? and Why do we use it ?

A user persona is a semi-fictional story that represents a product’s target user, based on real research and data. It includes details like demographics, behaviors, goals, needs, pain points, and motivations. Personas help the design team understand who we are designing for.

We use personas to guide design decisions, ensuring the product meets the needs of real users. They help keep the team user-focused, prioritize features, and create more meaningful, intuitive experiences. Instead of guessing, we design with a clear understanding of the target audience.

What is Heuristic Evaluation

It’s a usability inspection method where experts evaluate a product against a set of usability principles (heuristics) such as consistency, error prevention, visibility of system status, etc.

Why do we use Guerrilla Testing?

We use it to quickly validate design ideas, identify usability issues, and get real user insights without spending much time or resources. It’s especially useful in the early stages of design to test concepts before investing in full-scale usability studies.”

Example: If I’m testing a new app flow, I might ask people in a coworking space to try it on my phone and observe their interactions, noting where they get confused or stuck.

What is Qualitative and Quantitative Analysis?

Qualitative = Insights from small groups using interviews, usability testing, or observations. It explains why users behave in a certain way.
Quantitative = Data-driven research like analytics, surveys, A/B tests. It shows what users are doing in numbers.

Difference Between User Flow vs User Journey

User Flow: A step-by-step path a user takes to complete a specific task within a product (e.g., sign-up flow, checkout flow). Focuses on actions and screens.
User Journey: A holistic map of the user’s experience across different touchpoints with the product, including emotions, pain points, and motivations. Goes beyond just the flow—it’s about the experience before, during, and after.

2. What is a Storyboards

A sequence of illustrations that show how a user interacts with a product step by step.
Focuses on the context (user environment, actions, emotions).
Good for communicating the overall experience, not just screens.

3. What is User Flows

A diagram showing the path a user takes to complete a task within a product.
Includes decision points, screens, and interactions.
Helps identify the smoothness or friction in a journey.

4. What is a User Journey?

A user journey is the path a user takes to accomplish a goal within a product or service. It captures each step of their interaction, from the starting point to completing a task. I use it to understand user behavior, emotions, and challenges along the way.

5. What is Journey Mapping?

Journey mapping is the process of visually representing the user journey. It shows what the user is doing, thinking, and feeling at each stage of interaction. I use journey maps to identify pain points, highlight opportunities, and align the team around user needs.

6. What is Affinity Mapping?

Affinity Mapping is a collaborative method of organizing research findings, ideas, or feedback into groups based on patterns and themes. It helps in making sense of large data sets, prioritizing issues, and finding insights for design decisions.

Can you join immediately ?

As per company policy, my notice period is 45 days. However, I’m currently in a supporting role assisting developers, and not in a critical project. Because of that, my company can relieve me immediately once I receive an offer.

What is your Salary Expectations ?

My expected CTC will depend on the exact roles and responsibilities. Once I understand the scope, I can share a fair range aligned with my experience and market standards.

Why do you want to change your company?

Why should we hire you?

Salary Negotiation!

After reviewing the offer and reflecting on the role’s scope and the impact I hope to bring—especially in service design, platform UX, and scaling design maturity—I would like to discuss the possibility of revising the compensation slightly.

While my previous CTC at EnterPi was ₹9 LPA, that was reflective of a different stage in my career where I prioritized growth and skill-building over compensation. Now, with 8+ years of experience and a strong track record of delivering high-impact solutions across complex systems, I believe a revised figure in the ₹22–24 LPA range would be more aligned with both the market benchmark and the level of responsibility expected in this role.

Of course, I remain flexible and open to discussing the complete structure—including performance incentives, learning opportunities, and title alignment—so that we find a win–win outcome.

Thanks again for the offer—I’m genuinely excited about the opportunity, especially the kind of digital transformation work and platform innovation you’re driving. I’ve reviewed the offer, and I’d love to discuss the compensation a bit, if that’s okay.

1. Nike Equipment Builder

Nike wanted a tool where athletes and teams could customize equipment like shoes and jerseys. The existing process was cluttered — too many options on one page, causing users to drop off.

My role was to redesign the flow. I studied competitor tools and mapped the journey. Instead of a single long page, I designed a step-by-step wizard with live previews so users could see changes instantly.

This progressive flow reduced confusion and gave users a smoother experience. After usability testing, task completion went up, and Nike decided to expand the workflow to more product categories.

It was a great project because it balanced brand expression with usability.

2. Corporate Travel Management Application

This was a corporate travel management application designed for enterprises. The challenge was that employees found booking very complex, and finance teams didn’t have visibility into expenses.

My role was to lead the end-to-end design. I started with interviews and journey maps to identify pain points. Then I designed booking flows, an approval system, and dashboards for finance managers.

One key decision was to create a mobile-first booking experience with one-tap approvals, and a dashboard where finance teams could instantly see expenses.

In usability testing, we reduced booking time by about 30%, and finance teams finally had real-time reports, which improved adoption across clients. It was a great example of how design simplified both the employee and finance side.

3. Inventory Management System

This was a SaaS platform to help small and medium businesses track and forecast inventory. Many of them relied on spreadsheets, which caused errors and poor visibility.

I designed the end-to-end experience: research, personas, information architecture, and dashboards. The focus was on clarity and efficiency.

One important decision was prioritizing data visualization — charts and KPIs on the dashboard so managers could make decisions quickly. I also added powerful filters and a modular grid so the system could grow with future needs.

The result was a tool that gave real-time visibility. Clients reported reduced stock issues and greater efficiency in managing inventory.

4. Design System

This was about creating a design system to unify Etta’s products across iOS, Android, and web. The main issue was inconsistency — different teams were designing differently, which slowed down development.

I led the system creation: auditing components, building a Figma library, defining tokens, and documenting guidelines. Accessibility was a big focus — ensuring proper contrast and scalable typography.

We introduced semantic tokens for colors and created reusable components with do’s and don’ts.

As a result, design–dev inconsistencies dropped, and development became faster. The design system is now the foundation for new product features across platforms.