Experience 🚀
+4 Years of Experience
UX/UI Designer
December 2023 - Present
UI/UX Designer
May 2023 - November 2023
UI/UX Designer & Integrator
May 2023 - November 2023
Interviews Questions 🌙
These are some questions I have been asked during interviews and how I answered them
One major challenge I faced was analyzing two new modes we were adding to the system. Since the results of this analysis would directly guide the AI team’s work, it was critical to get it right. To avoid blind spots, I reached out to a data analyst colleague whose strong critical thinking skills helped me validate my reasoning. After refining the findings, I translated them into user flows in Figma, along with detailed notes the AI team needed to consider. This collaborative and structured approach ensured accuracy and made the insights actionable.
An unexpected challenge I faced was not knowing how to properly analyze competitor data during my first research project. To overcome this, I applied a user-centered approach by collaborating with a data analyst colleague who helped me frame the right questions. I then transformed the findings into user flows in Figma, with notes that highlighted key considerations for the AI team. This ensured the insights were both actionable and directly tied to user needs, turning a difficult situation into a clear, user-focused design solution.
One of the major challenges I face when presenting wireframes to clients or the team is that they often don’t fully understand the idea. To solve this, I create a fully working prototype that covers all the possible flows. While this can be time-consuming, it significantly reduces the amount of feedback, since people focus more on the user flows and avoid questions like “What happens if I click here?”
One of the major challenges I’ve faced is that some clients, especially in the Saudi Arabian market, often struggled with wireframes that lacked color. For example, I frequently got questions like ‘Why is this button black?’, which took time to explain since wireframes aren’t the final design. To solve this, I started applying colors from our UI kit and creating fully interactive prototypes. Before presenting, I always clarify that it’s still a wireframe and subject to change based on feedback. This approach significantly reduced unnecessary questions and allowed me to focus my energy on more meaningful discussions.
Yes, I’ve faced this situation many times. When clients request new features during a presentation, I don’t just say ‘yes’ immediately — I first discuss with them whether it’s really needed and how it impacts the overall goals, because agreeing to everything can create scope creep. If the feedback is related to UI details, I usually note it down directly in the Figma file as comments, rather than making changes live during the presentation. This helps keep the session focused on discussion rather than small edits. Of course, there are times I may miss something, so I always make sure to follow up, apologize if needed, and double-check requirements by taking clear notes. This way, I can ensure that by the next meeting everything is aligned with their expectations.
Usually, I try to prevent misalignment by agreeing on the visual direction and brand identity at the very beginning of the project. I do this by creating moodboards, exploring different styles, and discussing the client’s preferences and needs. Once we align on a direction, I rarely face major conflicts later on. However, the biggest challenge is often translating the client’s imagined visual identity into something concrete. I’ve faced situations where their vision was not fully clear or easy to articulate. To overcome this, I organized several meetings, presented multiple mockups—some based on their requests and others on my design suggestions—and iterated until we reached a solution that satisfied both the client’s vision and design best practices.
I dedicated a lot of time to creating illustrations for the landing page, even though it wasn’t initially part of my tasks. Since I was already working on the product itself and handling the website content, I took the initiative. Another designer had started working on the visuals, but after I completed my tasks, the PM asked me to support with the design. I suggested taking full ownership of the landing page design from scratch. I created almost all the illustrations that represented the content, and then the designer transferred my work into Framer and added animations.
I spent a lot of time creating illustrations for the landing page, even though it wasn’t part of my assigned tasks. Since I was already working on the product itself and responsible for the website content, I decided to take the initiative. Another designer had started on the visuals, but after finishing my tasks, the PM asked me to help with the design. I suggested taking full ownership and redesigning it from scratch. I created most of the illustrations that represented the content, while the designer later transferred my work into Framer and added animations.
My first time doing research was quite challenging because I had to compare many competitors and understand what they offered and what they didn’t. At that time, I wasn’t sure how to properly read and analyze the data, so I reached out to a colleague who is a data analyst. I knew she had strong analytical skills, and she was very approachable, which made it easy to ask for her help.
I also have a habit when joining a new company: I observe and analyze the strengths of the people I work with. This helps me understand who I can collaborate with or seek support from in the future.
One challenge I faced was doing a full analysis of two new modes we were adding to the system. Since the results of my analysis would guide the AI team’s work, it was important to get it right. To make sure my findings were accurate, I reached out to a data analyst who has strong critical thinking skills and often asks the right questions. This helped me validate the reasoning and avoid blind spots. After analyzing the findings, I presented them as user flows in Figma, supported by clear notes and considerations that the AI team needed to keep in mind. This way, the team could easily understand both the big picture and the important details they had to apply.
When working on our project Ejaad, I had to analyze integrations by looking at two main competitors, Dashworks and Guru. I reviewed 13 integrations for both and quickly realized that if I simply listed the findings in a document, the client and team would lose interest — it would feel too abstract and data-heavy. To adapt my presentation style, I decided to create flows in Figma. I used screenshots from each integration and added clear notes, so instead of reading through long text, the client could visually follow how each integration worked. This creative approach made the findings more tangible and engaging, and it helped the client and the AI team immediately see the value and make informed decisions about which integrations to prioritize.
My writings ✨
Explore the real-world challenges I tackle, from complex user flows to seamless interactions. See how I solve problems and bring ideas to life through thoughtful design.
Read more articles
