What is a UX/UI Designer at Akima?

As a UX/UI Designer at Akima, you are stepping into a role that bridges the gap between complex technical requirements and intuitive user experiences. Akima is a massive enterprise that heavily supports federal agencies, military branches, and government contractors. Because of this, the design work you do will directly impact mission-critical systems, federal employee workflows, and public-facing government portals.

This position is critical because government and enterprise software often suffers from legacy bloat and usability issues. Your impact lies in modernizing these interfaces, ensuring strict compliance with federal accessibility standards (like Section 508), and advocating for the end-user in environments where technical constraints are often rigid. You will be tasked with transforming dense, data-heavy processes into streamlined, accessible, and highly functional digital experiences.

Expect a role that requires a delicate balance of strategic influence and hands-on execution. You will frequently interact not just with internal engineering and product teams, but also with contracted agency stakeholders. The complexity of the problem space makes this role incredibly rewarding for designers who thrive on untangling convoluted workflows and delivering accessible solutions at a massive scale.

Common Interview Questions

Getting Ready for Your Interviews

Preparing for an interview at Akima requires more than just a polished portfolio; it requires demonstrating how you operate within highly regulated, cross-functional environments. You should approach your preparation by aligning your past experiences with the unique demands of enterprise and government contracting.

Role-related knowledge – Interviewers want to see your mastery of standard design tools (like Figma and Adobe Creative Suite) combined with a deep understanding of enterprise UX principles. You can demonstrate strength here by highlighting your experience with design systems, responsive web design, and strict accessibility compliance.

Problem-solving ability – You will be evaluated on how you approach complex, ambiguous challenges. Akima looks for designers who can break down massive amounts of data or multi-step legacy workflows into simple, logical user journeys. Be prepared to walk through your end-to-end design thinking process.

Stakeholder management and communication – Because you will often be interviewing with and working alongside contracted agencies, your ability to articulate design decisions to non-designers is paramount. You must show that you can gracefully handle pushback, negotiate constraints, and build consensus among diverse groups of stakeholders.

Adaptability and resilience – Government contracting environments can move slowly and feature rigid technical limitations. Interviewers look for candidates who remain patient, adaptable, and focused on incremental user improvements rather than those who demand perfect, frictionless agile environments.

Interview Process Overview

The interview process for a UX/UI Designer at Akima is generally straightforward but involves multiple layers of stakeholders due to the nature of agency contracting. Your journey typically begins with a standard behavioral and background screen with an internal Akima recruiter. This call is primarily to assess your baseline qualifications, clearance eligibility (if applicable), and overall fit for the specific agency contract they are hiring for.

Following the initial screen, the core of the evaluation takes place in a comprehensive panel interview. This panel heavily involves representatives from the contracted agency you will actually be supporting. Because of this dynamic, the panel will focus heavily on how you present your work, how you handle live Q&A about your portfolio, and your ability to communicate with cross-functional agency leaders. Expect the difficulty to be average, but the behavioral scrutiny to be high.

One distinctive aspect of the Akima process is the communication timeline. Because feedback must be routed between the contracted agency, the hiring manager, and the recruiting team, decision timelines can sometimes be delayed. Candidates are expected to be proactive, and final status updates are frequently routed through the internal Workday portal.

The visual timeline above outlines the typical progression from the initial recruiter screen through the agency panel interview and final decision. You should use this to plan your preparation: focus early on your behavioral narrative for the recruiter, and reserve your deep technical and portfolio preparation for the agency panel. Keep in mind that timelines between the panel and the final decision can vary based on agency responsiveness.

Deep Dive into Evaluation Areas

To succeed in the Akima interview process, you need to understand exactly what the panel is looking for. Your evaluation will be split between your hard design skills, your understanding of specialized compliance, and your behavioral adaptability.

Portfolio Presentation & Case Studies

Your portfolio is the anchor of your panel interview. The agency stakeholders need to see proof that you can handle complex, data-rich interfaces rather than just consumer-facing marketing sites. They are evaluating your ability to tell a coherent story about a problem, your process, and the final outcome. Strong performance here means clearly articulating the why behind your design decisions, not just showing high-fidelity screens.

Be ready to go over:

• End-to-end process – How you move from initial discovery and user research through wireframing, prototyping, and final handoff.
• Handling complex workflows – Demonstrating how you simplified a convoluted user journey or modernized a legacy system.
• Measuring success – How you validate your designs using user testing, analytics, or stakeholder feedback.
• Advanced concepts (less common) –
  • Integrating UX metrics into agile sprints.
  • Building or scaling enterprise design systems from scratch.

Example questions or scenarios:

• "Walk us through a project where you had to design a solution for a highly technical or specialized user base."
• "Explain a time when your initial design was rejected by stakeholders. How did you pivot?"
• "Show us a complex user flow in your portfolio and explain the reasoning behind the navigation structure you chose."

Accessibility & Federal Standards

Because Akima services government contracts, accessibility is not an afterthought—it is a strict legal requirement. Interviewers will probe your knowledge of inclusive design principles and your practical experience implementing them. A strong candidate speaks fluently about accessibility standards and integrates them seamlessly into their design process from day one.

Be ready to go over:

• Section 508 and WCAG compliance – Understanding the specific requirements for federal digital products.
• Color contrast and typography – Practical application of accessible visual design principles.
• Screen reader compatibility – Designing layouts and semantic structures that work for assistive technologies.

Example questions or scenarios:

• "How do you ensure your designs are compliant with WCAG 2.1 or Section 508 standards?"
• "Describe a time you had to advocate for accessibility features when the engineering team was constrained by time."
• "What tools do you use within Figma to test for accessibility before handing off to developers?"

Navigating Agency Dynamics & Constraints

Working as a contractor means you are often an external expert advising an internal agency team. The panel wants to know if you possess the soft skills required to thrive in this environment. They evaluate your emotional intelligence, your patience with bureaucratic processes, and your ability to build trust.

Be ready to go over:

• Stakeholder alignment – Techniques for gathering requirements from non-technical government clients.
• Working within technical limitations – Designing around legacy tech stacks or strict security protocols.
• Cross-functional collaboration – How you hand off designs to developers and ensure quality assurance.

Example questions or scenarios:

• "Tell us about a time you had to design a feature with severe technical limitations. How did you compromise?"
• "How do you handle conflicting feedback from multiple agency stakeholders?"
• "Describe your ideal handoff process to an engineering team."