At IGT (International Game Technology), a UX/UI Designer plays a critical role in shaping the future of global gaming, lottery, and digital betting experiences. This is not a standard web design role. Your work will directly impact millions of players worldwide, spanning physical casino slot cabinets, digital lottery terminals, mobile applications, and complex enterprise casino management software. The challenge lies in balancing highly engaging, visually rich gaming aesthetics with rock-solid usability, accessibility, and strict regulatory compliance.

You will design interfaces that must captivate users in high-stimulus environments while maintaining intuitive task flows. Whether you are optimizing a player-tracking interface on a dual-screen cabinet, designing a mobile lottery app, or crafting the layout of a digital betting platform, your designs will bridge physical hardware constraints with modern software capabilities. This requires a deep understanding of user psychology, platform architecture, and cross-functional engineering processes.

By joining IGT as a UX/UI Designer, you become part of a global, cross-functional team where your design rationale must stand up to rigorous technical constraints. You will collaborate closely with product managers, software developers, and compliance experts to turn complex game mechanics and transaction flows into seamless, delightful player journeys.

The interview questions you will face at IGT range from casual conversations about design philosophy to rigorous technical deep dives into how your designs integrate with front-end architectures. The questions below represent real patterns reported by candidates across various global offices, including Reno, Providence, London, and Lima.

Technical & Platform Integration

This category evaluates your understanding of how UI designs translate into working software. Because IGT builds both digital applications and hardware-integrated terminal software, interviewers will test your knowledge of development frameworks and technical constraints.

• What is the MVVM (Model-View-ViewModel) architectural pattern, and how does it influence your UI design process?
• Can you explain the basics of WPF (Windows Presentation Foundation) architecture and how you design interfaces for it?

Preparing for a UX/UI Designer interview at IGT requires a dual focus: mastering your creative craft and understanding the technical platforms your designs will live on. You should approach the interview process not just as an artist, but as a systematic problem solver who understands the realities of software development.

Technical Platform Literacy – IGT interfaces often run on specialized systems. Demonstrating familiarity with desktop and interactive architectures, such as WPF and the MVVM pattern, will set you apart. You do not need to be a developer, but you must know how to design for these technical environments.

Design Rationale & Defense – You must be able to explain the "why" behind every pixel. During portfolio reviews and practical tests, the interviewers will focus heavily on your decision-making process, user journey maps, and how your designs solve specific business or player problems.

Cross-Functional Collaboration – You will be evaluated on your ability to work within an agile framework alongside developers, product managers, and QA engineers. Be ready to share concrete examples of how you have negotiated technical trade-offs without compromising the core user experience.

Global & Remote Adaptability – As a global company, IGT teams are highly distributed. You must demonstrate strong communication skills, self-motivation, and the ability to collaborate effectively across different time zones and cultural contexts.

The interview process for a UX/UI Designer at IGT is generally straightforward, though the exact steps and duration can vary based on the office location (such as Reno, Providence, London, or Lima) and the specific team. Typically, the process takes anywhere from two weeks to a month and is designed to evaluate both your cultural fit and practical design capabilities.

The journey begins with an initial HR phone screening to discuss your background, salary expectations, and high-level alignment with IGT's goals. This is followed by a practical stage, which often includes a design assessment or ability test where you will create wireframes or visual mockups based on a prompt. Once the practical evaluation is complete, you will move to the panel stage. This typically involves an interview with a cross-functional agile team—including developers, product managers, and peer designers—and a final conversation with senior design leadership.

The timeline above details the typical progression of the interview stages for this role. Candidates should use this sequence to pace their preparation, focusing first on high-level portfolio storytelling before diving into design test practice and technical architecture review. Note that while some locations like London emphasize a structured 3-stage process, international offices like Lima may include additional English language and cognitive ability assessments early in the cycle.

To succeed in the IGT interview process, you must understand the core competencies the hiring team evaluates at each stage.

Technical Architecture & UI Integration

IGT's product suite relies heavily on robust software frameworks to power physical cabinets and digital applications. Designers who understand the underlying technology are highly valued because they design with fewer unrealistic assumptions.

Be ready to go over:

• MVVM Pattern Integration – Understanding how the View (UI) separates from the ViewModel and Model, and how this separation affects UI state changes and animations.
• WPF & XAML Basics – Knowing how layouts are structured in Windows-based environments, including grid systems, control templates, and styling.
• Asset Optimization – How to prepare, slice, and hand off high-performance assets for systems that may have strict hardware memory or processing limitations.
• Advanced concepts (less common) – Responsive layouts for dual-screen environments, tactile/button deck integration, and localization-friendly UI scaling.

Example scenarios:

• "Explain how you would design a dynamic UI element that needs to update in real-time based on data-heavy backend events, keeping the MVVM structure in mind."
• "How would you approach designing a UI that must scale seamlessly across a 10-inch terminal screen and a 42-inch overhead display?"

Practical Design & Wireframing

For many IGT teams, particularly in London and Lima, you will be required to complete an ability test or a practical wireframing challenge. This stage is designed to assess your rapid prototyping skills and your logical approach to user flow creation.

Be ready to go over:

• Information Architecture – Structuring complex transaction screens (like lottery purchase screens) so they are intuitive and error-resistant.
• Visual Hierarchy – Using typography, color, and contrast to guide players through high-stakes actions, such as placing a bet or claiming a prize.
• Design Systems – Leveraging reusable UI components to build consistent, scalable mockups quickly.

Example scenarios:

• "Create a wireframe flow for a digital lottery ticket purchase on a mobile screen, ensuring compliance warnings are visible but not disruptive to the purchase flow."
• "Present a high-fidelity visual mockup of an interactive game dashboard and walk us through your visual hierarchy choices."

Cross-Functional Collaboration & Agile Alignment

Because IGT design teams work embedded within agile development pods, you must prove that you can collaborate effectively with non-designers.

Be ready to go over:

• Developer Handoffs – Your process for translating design files into clear specifications, redlines, and behavior notes for engineering teams.
• Handling Technical Constraints – How you react when developers state that a design element is technically unfeasible within the sprint timeline.
• Ambiguous Environments – Navigating projects where product ownership or specific requirements are still being defined.

Example scenarios:

• "Describe a time when a developer challenged your UI layout due to performance concerns. How did you negotiate a solution?"
• "How do you gather feedback on your designs from QA engineers to ensure edge cases are accounted for?"