what interviewers look for in a Figma file

[@AlicePackard]

Especially appreciate you saying "appropriate use of..." 🙏 it's always best to ground decisions in what makes sense for you, the designer, and the audience on the receiving end of your work (devs, recruiters, PMs). this encourages designers to pause and think about how they can optimize for their audience and not optimize for "so and so from the internet said this is a best practice so i'll roll with it!" 💪

[@p44v9n]

💯💯💯

[@boriskardzhiev3085]

Hey so glad I found this channel while looking for component + variable tutorials. Some ideas for future content: 1. Structuring page best practices. Some points I can think of are: How do you structure components libraries when going for an interactive prototype? In some cases if the component is in a different page, not to mention different file, interactions just won’t work. So everything needs to be on the same page and that’s difficult to organise and prettify. A precise example : I have a popup modal with plenty of buttons and options that require a confirmation modal to appear. Since some of the options are drop-downs with their own component + modal set up;variable triggers etc. Now if I want to have a confirmation modal appear when a dropdown option is selected, it’s incredibly difficult to place visually in the original design. Maybe I’m requesting too much from Figma at this point - this might be an edge case. 2. Interview guides and role play are great. Maybe you can go over a few different scenarios- whiteboard challenge/ technical review / take home challenge / team lead meeting. And go over about some frequent questions & best practices - in my last interview I asked the interviewer whether or not they had a design system in place because I love them and think they greatly improve turnover and she asked me what my favourite design systems were - I completely blanked out and couldn’t remember a name for any of my favourites for like three minutes😂

[@ira6109]

So glad I came across your channel! I have an interview coming up, and the interviewer wants me to show her one of my Figma files. Now I know what the best practices are. Thanks for sharing your knowledge Paavan🙏

[@p44v9n]

You’re so welcome! Good luck with the interview, you’ll smash it 💪

[@DjokovicIsOurLordAndSaviour]

Great stuff Paavan thanks!

[@chrisgoldsbrough3010]

Informative, confidence building round up 👍

[@basuki094]

Also I like your content as you are covering some unique topic

[@giordanolugo]

amazing stuff

[@ObaUIUX]

awesome content. 1 new subscriber

[@VivekSingh-kg5ql]

Why do you care how a designer use a tool...what a person makes with the tool should be the thing to see.

[@p44v9n]

Hey Vivek! I think the end outcome in code is totally important, more so than what happens in a UI design tool like Figma. For solopreneur apps it’s definitely worth focussing on that instead of making sure all your layers are named. However, this video is really aimed at people applying for UX/UI design jobs where they’ll be working alongside a team of designers. It’s so important to have well-structured files when you’re collaborating in a team. And, especially with how competitive the job market is right now I think nailing these things becomes such an important differentiating factor. (A friend hiring for senior product designers in London recently had 400+ applications within 48 hours!) Anyway thanks for watching!