Top 10 things hiring managers look for in resumes - UX Research
Top 10 things hiring managers look for in resumes - UX ResearchGetting your resume in shape for UX Research rolesIt’s the new year, a time when people start to think about making changes. I’ve reviewed hundreds of UX Research resumes. I wanted to share some things specific to the role that are critical to include to make your application stronger. When thinking about your resume, put yourself in the shoes of the hiring manager and what they might be looking for. Source: XKCD1. Show project impact without giving away competitive informationBalance showing what you have done without revealing the business strategy of your current company. Usually, prospective managers are not that interested in confidential information. By revealing too much information, you risk demonstrating a lack of ethics and your own personal code of conduct. A hiring manager or recruiter will be more interested in what you achieved in the project and how you moved it forward. An interesting article on impact to help you frame your work. 2. Demonstrate your skills throughout the resume itself with visual and clear communicationSometimes skills are easier demonstrated than talked about. If you want to show that you are good at communication - every item should show that - your resume, portfolio, LinkedIn and website. Visual and written communication are both important skills that a UX researcher should have. You can show this by - clear headings, ordering of information with most important information first. Treat the construction of your resume as guiding the reader to the best parts of your experience. Think about what the reader might be interested in and prioritise that. Examples of visual communication in a resume - appropriate use of fonts, headers, colours, icons (if needed). It’s less about doing full-on design work in the resume itself and more about making it readable and scannable. Your reader, the hiring manager will be looking through potentially hundreds of resumes. They will need to quickly ascertain whether to shortlist an applicant or reject them. 3. List out your research methods - and be prepared to talk about them and their applicationThe interviewer will be gauging your understanding of various research methods. They will also want to assess your experience of applying them appropriately. It’s always good to list your methods. Your portfolio can complement your resume by showing the application of various methods. Simply listing a research method is too often generic to ascertain skill level in a resume. A good interviewer will want to look into it further. 4. Keep it succinct and below 3 pages (ideally 2)There is a temptation to include everything. It’s also hard to trim a resume right down but imagine there is a limited attention span. I spoke to a recruiter and they advised me of this one and I would agree. Everyone is time-poor. A reviewer will likely be scanning first and then diving deep if the resume is interesting. 5. Know what should be in the resume vs your research portfolioFrom the point above - use your research portfolio to share details of the end to end process of your projects. Keep in mind the point above of keeping out confidential information. Use your resume to talk about impact. Most interviewers aren’t too interested in the findings and the proprietary information but the process. Why did you do what you did in that project? Ask yourself and make a mental note of what could have been done better on the project. 6. Compare the job ad with your resume and ensure there’s alignmentThere’s the obvious like scanning your resume against the job ad to make sure you have a good parallel of what they are asking for. Match things like terminology or titling e.g user researcher vs ux researcher. It seems painful but the first person looking at your recruiter is likely to be a recruiter and they will go for the easiest and obvious matches first. 7. Include tools but ultimately understanding methods is more important and tools can be learnedThere is a vast range of research tools and sometimes they tend to be more trend-based. A good understanding of research methods is more important. If you are a good researcher and understand the fundamentals, it should be relatively easy to pick up a new research tool. You can list tools but if you do have other more information like impact or project details I would prioritise that. 8. Order your information to most important at the top - design the resume to be scannableSimilar to the point above, create your resume in a way that it can be read quickly or in-depth. It ensures that the essential parts of your experience get read. It also demonstrates your ability to succinctly communicate in the form of your resume. 9. Minimise use of phrases, jargon and acronyms, particularly if it’s internal - or spell it outWhen creating a resume it should be as easy to read as possible. If the recruiter or hiring manager has to Google or guess what the acronym is they are likely to move onto a more straight-forward-to read resume. Sometimes those project names are internal and won’t have any meaning or context externally. Skip the internal naming and use plain language. It’s not a great idea to be discussing internal terms with people outside of your organisation. It can give people doubt on whether as an individual you know what is appropriate to discuss inside and outside of your company. 10. Include projects AND processesThe more senior you are, the more expectations that a UX Researcher will be doing more than just project work. It might include things like creating research processes, training people, templates. An experienced researcher should have more impact organisationally, as well as completing large scale projects. If you liked this post all about UX Research, Product, Design, career, why not share it? |
Older messages
Great newsletters to read for learning and professional development
Friday, November 26, 2021
For UX Research, Product Design and Product Development
How not to do “theoretical” research
Friday, November 19, 2021
Make your research more impactful
What I wish I knew starting out as a Product Manager (PM)
Tuesday, October 26, 2021
A perspective from someone who's been doing this for some time
What our peers are focusing on in 2021
Monday, October 18, 2021
Top focus for professional development this year - public speaking
What I wish I knew starting out as a UX Researcher
Sunday, October 3, 2021
They don't teach you this in school
You Might Also Like
178 / Visualize your dreams in 2025
Wednesday, January 15, 2025
Product Disrupt Logo Product Disrupt Half-Monthly Jan 2025 • Part 1 View in browser Welcome to Issue 178 Ever get curious about how this newsletter is doing? I shared the 2024 behind-the-scenes and
Mayer Rus on Loss, and Living, in LA
Tuesday, January 14, 2025
View in your browser | Update your preferences ADPro LA, I Love You Los Angeles has been my home for nearly 20 years, and the devastation here, now, is unfathomable. Entire neighborhoods have been
🐺 How to make a great first impression
Tuesday, January 14, 2025
With real examples. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
#490: Interface Design
Tuesday, January 14, 2025
How to design better interfaces, how to choose icons, optical effects, iconography, Gestalt principles and icon design. Issue #490 • Jan 14, 2025 • View in the browser Smashing Newsletter Buona
🐺LAST CHANCE to get 20%-off our PR Masterclass Series
Monday, January 13, 2025
Make 2025 your biggest press year yet. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Accessibility Weekly #431: Progressive Enhancement Brings Everyone In
Monday, January 13, 2025
January 13, 2025 • Issue #431 View this issue online or browse the full issue archive. Featured: Progressive enhancement brings everyone in "Early computers faced unexpected failures, and that
Conviction in a copycat league
Sunday, January 12, 2025
Issue 228: Holding beliefs in a world of emulation ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
🐺If they can get press, so can you.
Friday, January 10, 2025
Calling all product businesses and designers. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
🐺Are you overwhelmed when it comes to PR?
Friday, January 10, 2025
do this. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
#489: Web Performance
Tuesday, January 7, 2025
Instant navigation, Web Almanac 2024, INP debugging, font-face fallbacks and compression dictionaries. Issue #489 • Jan 7, 2025 • View in the browser Smashing Newsletter Hello Smashing Friends, Web