Interview the Team, Too: UX Interviews with Jenny Huang

← THE UX GROWTH PODCAST
SEASON 06 · EPISODE 05 / CAREER GROWTH & UX INTERVIEWS

Interview the team, too.

What can you learn in your first UX interview that makes you better prepared for the second? Jenny Huang shares how she asks what a team needs, chooses what work to show, and decides whether the role fits.

Hosted by Nick Mann

Jenny HuangProduct Designer at Philo
Jenny Huang, product designer at Philo
IN CONVERSATION WITHJenny / Philo
ASK BETTER.
CHOOSE BETTER.
THE CONVERSATION

Learn what the team needs.

45 min 54 sec · Season 6, Episode 5

A FEW THINGS TO TAKE WITH YOU

Bring better questions
to the first call.

  1. Learn what the role is actually for.

    Ask what skill or perspective the team is missing. The answer can tell you more about the job than the posting does.

  2. Pick a case study that answers that need.

    Use what you learned in the first call to choose what to show next. Give the interviewer the context they need to understand what you did and why.

  3. Make the important parts easy to skim.

    Read only your case study headings. If they don’t tell a coherent story, revise them and ask someone to explain the project back to you.

  4. Pay attention when the fit feels off.

    The hiring team is deciding whether you can help. You’re deciding whether the role will let you do the work you want to do.

ABOUT THIS EPISODE

Your first interview can inform
your next one.

After a decade in software engineering, Jenny Huang began interviewing for design roles. One recruiter pointed to her résumé and told her the team was hiring a designer. She took that feedback seriously and changed how she presented her work.

Jenny and Nick talk about what to ask early in a hiring process, how to pick and explain a case study with the team’s needs in mind, and why you should be evaluating the team too.

They also discuss what makes a portfolio easy to skim, how to work with engineers and product managers, and when a smaller design system will serve a team better.

A QUESTION TO TAKE INTO YOUR NEXT INTERVIEW
What skill or perspective is missing on the team right now?
FOLLOW THE THREAD

Explore the
conversation.

From changing careers to interviewing, portfolios, and design systems.

  1. Moving from software engineering into product design
  2. Using an early rejection to improve how you present your experience
  3. Asking recruiters what the design team needs
  4. Choosing and explaining a relevant portfolio case study
  5. Making case studies easier to skim and retell
  6. Working with engineers and product managers
  7. Right-sizing a design system for the team
  8. Finding a stepping-stone role and learning from interview feedback
Jenny Huang
MEET THE GUEST

Jenny Huang

Product Designer at Philo

Jenny spent a decade in software engineering, including at Salesforce, before moving into product design. She previously designed at VIZIO and now mentors designers through ADPList.

EVERY WORD, AT YOUR PACERead the Full Transcript

Automated transcript. It may contain transcription errors.

Hi, this is the UX Growth Podcast, the podcast that helps people learn and grow in UX design industry. I'm your host, Nick Mann. Today on the show, we have Jenny Huang, a product designer, and she's also a dedicated mentor on ADPList, helping hundreds of junior designers grow their careers. Jenny, welcome to the show.

Thank you, Nick, for inviting me. I am so happy to be here.

Jenny's Journey: From Software Engineer to UX Desgner

So how did your journey into UX actually begin? Sure. I think I have a pretty unusual career, or maybe it is usual. I think a lot of people come into design with, , pretty unique career paths. As for me, I started off as a software engineer.

, I studied computer science in school, for four years, and after that, I actually went into software engineering. And I worked as a software engineer for 10 years, including performance testing, APIs, and also full stack. Be- I was at Salesforce for a few years before leaving, taking a gap year, and then trying to figure out what I wanted to do with my career, before deciding, to pursue design.

And here's where I am for the past three years. What made you decide, design was gonna be the choice? That is a very good question. I actually, when I left, I had- I actually started off, this might date me a little bit, but when I started off, I was a web designer, when I was, in high school.

Um, and back then the options were you go into programming or you pursue computer graphics or you do animations. And I decided I was no good at, um, I was no good at graphic design. And so I decided to pursue programming. So that's what led me to, um, studying software engineering in college. Back in the day it was a lot of, like, slice and dice web design.

So I always had an interest in it. But, that was just never the cards for me to pursue, because product design UX did not exist back then, right? , So when I was, when I left Salesforce, I was wondering, I was really burned out and I was wondering, did I really, was I really done with, software?

Was I really done with product? Did I even wanna work in tech? And I had to figure out all those questions on my own. And then actually, half year, half a year into my gap year, I actually went back and interviewed for software, software positions. And then halfway through my interview I had to drop out of them 'cause I realized I didn't want to do software anymore.

I didn't want to do any more programming. And what I wanted to do was really, , I wanted to pursue design a bit more seriously. Because a few years before that I had taken a, UX boot camp full time on top of my full-time job. That sort of sparked my interest.

'Cause prior to that I had no idea, what product design was. So I actually decided, yeah, I was gonna pursue, design, although it was definitely an uphill journey. Yeah. I to- I totally get that feeling because, from when you mentioned from graphic design, I was in I was a graphic designer for 10 years.

Wow. Yeah, no. And I understand it. There is a level of, talent involved, and being able to process, which colors, which typography, and the placements. And there's so much teaching you can do, where a lot of it helps to be innate with that ability to do it.

But also, I'm just like that. I cannot do software engineering. I don't understand any of what I'm doing. Isn't it amazing that we have vibe coding nowadays, right? It really enables a lot of people to do a lot of things. But it's so interesting how, we all have an innate ability,

so I'm just curious to know, what was the biggest mental hurdle that you had to go through from becoming a software engineer to a UX designer or product?

The Biggest Mental Hurdle: Making the Career Switch

The biggest hurdle. The biggest hurdle, honestly, was the very beginning. And I remember this very distinctly, because I was actually going, And I'll rewind back to where I left off earlier, was, when I started applying to jobs, I wasn't ready to let go of software completely. So I actually went through...

And I considered UX engineering roles, and actually went through, a series of rounds at Google- ... up until, the team matching. And I actually... And that was during the time when there was, hiring freezes. I was just going on and off and on and off. So that process got delayed for months and months.

And I talked to many amazing teams. And then by the third team, I realized, oh, I, don't know if I wanna continue writing code. And then I dropped out of, the, interviews. And so after that, I thought I was gonna just double down on design, 'cause I was like, okay, if I'm gonna do it, I'm gonna do it seriously.

But... And then I actually got a couple of, interviews, thankfully, and I remember one of them very distinctly, where, I was talking to the recruiter. He was like, yeah, we were really vibing. It was- ... feeling really good. The conversations were smooth. We built amazing rapport, and he was like, Jenny, I think you'd be a really wonderful person to work with.

And you seem, super cool and smart and all that." And then he pointed to my resume, like "But we're hiring a designer." And then, my resume had zero design experience on it. And the only thing on there, was software roles. And he was like, "I'm sorry." And I was like, "That's fair. Perfect sense," right?

So I was like, okay, what is it going to take? That's feedback, right? That's great feedback. And then so I was like, okay, what is it gonna take for me to get through this hurdle? So I really thought about it one hurdle at a time, and really like- ... what were the case studies that people wanted to see?

How do I position myself? And I knew having worked- about a decade in tech. I knew I could communicate. I have mentored before, I have hired before. . So I knew the ins and outs a lot, more than a lot of people just coming out of school, right? So I knew that I had a- an advantage in that case, but I didn't have the case studies that I needed, um, to actually get through that round.

So for me, that was the first step. And then it was just step by step, right? How do I gear up my presentations? How do I do all this stuff? And then eventually, how do I get to the final round and through all those rounds? Yeah, no, I, I like how you're like analytically breaking this down into steps.

Yeah, and, and it definitely makes sense because of the fact that once we go through, like we solve one problem, we are gonna encounter another problem, and then another problem till we succeed. Yeah, and it's very overwhelming, right? 'Cause I talk to a lot of, um, junior designers who, they're, they come out of school, they're so overwhelmed.

There's so much to learn. It's like infinite- ... amount of things to, learn, and there's just, it's impossible to do it all, because there's just too much. And, where do you put your time, right? And I think- ... breaking apart in terms of like what is the first step, um, and it, first of all, it gives you focus.

Also you can focus your time on what really matters, and then you're, getting the feedback, so you're tightening up the feedback loop so you can actually perform more efficiently- ... and get farther in the interview process. Yeah, that, that's super useful for getting feedback, and I've gotten tons of feedback too that really helps in the process of like you need to answer your questions deeper, I remember.

Well, it wasn't like the exact wording, but essentially was the idea, and like that helped a lot because I think there's always like missing context that we assume and that the interviewer doesn't know, and that's how they, like they c- because they, like they need to figure out like where do you fit on the team with everything else- Mm

as a whole. And if they can't identify that in a clear way, they're just gonna just be like, "Oh, I'll j- I'll just go to someone else who can," because they're not gonna guess. They're, it's, there, there's risk involved. And is it not also so much for the best fit, but also what is the least risk as well?

Interview Strategy: How to Stand Out as a Designer

Absolutely correct. A lot of people go into interviews thinking it's one-way. It's really two-way, right? It's like- ... speed dating. You are trying to find a company that fits, what you have to offer, that are looking for what you have to offer. And then they're looking for someone who, has skills that they are lacking in their team, right?

So instead of taking a back-seat approach and just answering questions, during your recruiter call, you should be, a lot of candidates should be asking, gathering information, building rapport, and, asking- ... hiring managers, "Hey, what is the team makeup like? What are some skill gaps?

What are you really looking for? What direction is the company going? And how do those skill sets match with the direction in which that company is going?" And then that, basically they're giving you all the answers, for, to prepare for the next interview. Um, so that's- from my experience, the best way to do it, building rapport and- Asking those very important questions, and then building your narrative and your deck, exactly tailored to what they're looking for.

So the moment they see it, they're like, "Yes, this is exactly the person that we're looking for," because they already gave you all the answers in the beginning. Yeah, that, that is so huge, to really go into, what are they really looking for? Because as as we find out from these job, descriptions, and talking with the initial s- screen- screener interview, like, there's always gonna be different mismatches that are gonna be from what the hiring manager, and then what is the overall team gonna be looking for, like for the other people involved who are going to play a factor in the hiring decision.

Yeah, sometimes you can sense those mismatches very early on. And sometimes, like, genuinely there just could be a communication error between the recruiter and the hiring manager. But sometimes when you actually start talking to the hiring manager and you sense, a mismatch, usually that's, that's a sign.

Don't ignore it completely, right? Sometimes that could just mean it's not a good match. I found the most success, with hiring managers that really know what they're looking for, that are, like, really deeply invested in finding really the right person for their team. Um, because those are the ones that are more motivated to find the right match.

Mm-hmm. A lot of hiring managers are the ... You know, if they're in a mindset where they're like, "Yeah, we're just trying to find someone to fill the role. Like, we don't really care too much, we're not super invested," or they're looking for- Mm-hmm ... a contractor, so they're not, like, really trying to, like, needing to find the right person, um, or the perfect fit.

Um, those might be harder because they're looking for a very gen- general sense, set of skills. And that might be a little bit hard if you have, like, a very, like, unique value proposition where, you know, they're maybe not seeing the most value in it. And they're looking in terms of like, oh, utility, we're just needing someone to fill this contract role.

Um, so that tends to be, like, when they are focused on a utility-type hire. You're basically, um, they're not looking for a differentiated hire. I think that puts the candidate in a worse spot sometimes, because, let's look, if you think about utility, that means they're trying to hire the best candidate for the lowest price.

Um, and they're looking for- Mm ... this set of skills that are very general, and so it's really hard to compete when a lot of people also have those same exact skills. Um, so that's my experience.

So I'm curious to know for a designer who has limited experience working with a software engineering team, what will you give some tips to be able to make sure that they can be able to use their feasible work into a way that integrates with their workflow?

Working With Engineers: Influence Over Conviction

I mean, at the end of the day, software engineers are human. And I think, working with engineers is no different than working with any cross-functional partner.

You're all a team. You all have different motivations, just like a product manager. A product manager is focused on business outcomes, success of that product or feature area. Um, software engineer is responsible for, efficiency, execution, and all that. So- ... understanding, having a little empathy I think every- everyone understands at the baseline level of, like, the value of having empathy for others.

However, I think it's also important to, in times when there is a little bit of conflict, I think that's the situation where you're alluding to, is that when conflicts arise due to different people having different values, what are some... what can you do to make that situation better?

One thing is to realize that design, just because, like, designers are doing design doesn't mean design- ... is always the most important thing at that moment for that feature. Um, so there's a, in order to influence, um, the outcome, understanding what situation you push, what situation you pull, understanding when design is more important or less important, what your non-negotiables are.

Um, and then you, to do that, you have to understand the perspective of the engineer, um, in what case is it okay to sacrifice a little bit design for, faster execution. You know, I think- ... PMs are like, "Let's ship things faster." Engineers are like, "Let's write the best code possible and do this in the most efficient way, and most robust way."

Designers are like, "Let's ship the most beautiful thing, user-friendly thing." Um, so understanding other perspectives, that's the only way to really find the best outcome, right? So don't think that, for a lot of junior designers, don't think that, um, just because your focus area is in design, that is always what is the most important thing.

Because ultimately, your goal is not to convince others anything. No, your goal, a lot of, like, I think a lot of people think, "Okay, my job is to, as a designer, is to convince other people that design is important." And the moment you have that mindset of needing to convince, you're already putting yourself, at a disadvantageous position, and you're trying to, like, get them to believe something that they may not.

Um, rather than that- You know, what, understanding what their values are, like PM's values, engineer's values, CEO's, whoever it is. Um, their values, understanding what their goals are, and then, you know, helping them understand and crafting a narrative, um, that helps them understand what the best outcome is.

If you can control that conversation, it's a better position to be in to actually influence others and the final outcome.

Yeah. Yeah. I do think like one thing, because you make it so v- such a great point of understanding, like where are the PMs, where are the devs? Like, where are they all coming from, and what they value most? And I think instead of telling them, like how they should, like what they should value in order to make designers feel relevant and useful is, like we use that as a form of, of influence about here's what happens when s- uh, when my values also meet your values.

Because it's not, you're ch- you're not changing people's values, you're just looking at it from a different perspective. Exactly. So it's like instead of thinking what I... Or thinking that, you have to convince. Because you're convincing... If you're convincing someone, you're putting them on one side, and you're putting yourself on the other side, and sometimes it can feel like you're really, like pushing, a boulder uphill, and it can be very- Mm-hmm

frustrating, right? 'Cause at the end of the day, like, look, designers are doing very important things. They understand the users the most, uh, out of everyone typically, right? At the end of the day, everyone is still human. They have their values, right? What you're saying is how do we draw a circle around it, and like how do, you know, my value versus PM's value versus engineer's value, is like what, what is the platform in which we can all coexist and find the best possible, uh, solution together?

Mm-hmm. Yeah. That's also like to add a tidbit that most people, uh, uh, most people don't actually know, like if, if UX designers or product designers don't know the user as much, but then who else? It's customer service team. They know. Exactly, yeah. Definitely. Sometimes even more than me, honestly. Oh, yeah.

Absolutely. That's why, like, I always re- be a reminder, man, they are like the greatest resource in solving problems because they hear about it every day. 100%. Yeah. So that's v- very much, uh, I always like to mention that as much as possible, because so many people don't know how to utilize that as much as they should.

Yeah, definitely agree. I definitely agree with that. . So what is the number one mistake junior designers make that causing hiring managers to immediately reject their application?

Portfolio Mistakes That Get You Rejected

Ooh, okay. It's getting fun. Um, okay, yeah. I think by the time that it gets to the hiring manager, it's already gone through one or a couple levels of screening, by the recruiter, typically. So I would say first impression, uh, matters a lot. So that is the first five seconds, um, of what you're doing.

So they're identifying the moment, like, the first five seconds, they're identifying whether or not you're even in the right realm- Mm-hmm ... for them. But that's typically, I would say, like, screened by the recruiter. Um, so if the recruiter thinks, they look at your portfolio and they're like, "Okay, this person looks like a service designer," or, "This person doesn't even look like a designer based on their portfolio.

It looks like, um, a software engineer's portfolio", um, things like that. Or, like, what is, you know, your selection of case studies, and what is the branding you're giving off? Um, whether you choose to convey that or is accidental- Mm ... um, what kind of designer do they think you are? Because they're first going to identify whether you fit in that industry or not, like, whether you're a fintech designer, um, or, a designer for a TV streaming service.

Do your skillsets match what they're looking for off the top? That's the first thing. Um, so I- Mm ... am assuming by the time they get to the hiring manager, there is already a match there, because otherwise you wouldn't get there, I'm assuming. So your question is, okay, by the time you get to the hiring manager, what is the first thing?

I would say narrative, story, storytelling. They click into the first case study. What I see a lot is that the headlines are not effective, um, and they're not really optimizing for the right story or the right, um, length of story. So for example, what I mean by that is can I look at your case study and understand the problem, the outcome, um, and how you solved it- Mm

within 30 seconds of just reading headlines? So a lot of designers' case studies, what I see is, like, they will use very little titles. They would say research, um, iterations- Mm ... solution, right? So when I scan it, I'm like, "I am not getting any information from this," because I really just have, like, 30 seconds to look at a portfolio.

And, you know, a lot of hiring managers, they'll do a first skim through, um, you know, in between meetings, and they just don't have that much time, right? So you really wanna optimize for the 30 seconds. And then when they do have time, sometimes- Mm ... like during their lunch break, they'll look at it again and they'll say, "Okay, like, let's dive a little bit deeper.

I have one minute, five minutes." No more than 10 minutes. Typically, 10 minutes, they're really invested in you and they really wanna re- they would, like, really wanna talk to you, right? Mm-hmm. Um, so you know, make sure that definitely under five minutes they can get everything. Um, and that's not making things too complicated.

So if the first thing is utilizing titles, um, effectively, utilizing imagery. Some of the imagery is just way too complicated. It's a lot of screenshots, um, very complicated, um, multi-panel. There's a lot of UI going on where I look at something and I'm like, "Okay, I don't know what is it is that you did," and there's just a lot of, like, visual complexity.

So not really, like, keeping the visuals really neat and really polished, um, and really simple and easy to digest. And then third thing is trying to cram too much information, um, into one page. So not really using that, like, negative space to help facilitate the storytelling where you're scrolling and you're really just getting, like, one bit of information at a time, and you're not really inundated with information and captions and images.

Fourth thing is some, some portfolios, um... I know that a lot of people use Framer, I know a lot of people use all these amazing software that helps them build their portfolios a lot faster, um, and it makes it really easy to add animations, and sometimes there's a little too much going on. Um, and for animations, I think sometimes, um, less is more.

Just thinking about, hey, like, not maximal, just keep it simple. Um, and that can be super underrated. Mm-hmm. Mm-hmm. I know. I was like, "Oh, man. Where do I begin with that?"

So I know the, the, the recent one was also on my mind. I know I definitely hear some designers are very, uh... they get bogged down on the details of like which, you know, p- uh, website platform they should use, and I think it, it really doesn't matter. The content matters. Absolutely. You can use, you can use Framer.

You can build it yourself. Um, you can do- I- ... whatever. Yeah, whatever works for you. It's just whatever is the most simple, um, for you to do, and can help you iterate without causing a significant amount of overhead. Obviously, I said you could build it yourself, but like- Mm-hmm ... if every time you iterate you have to go and manually do a bunch of things, I think that's, like, a little bit impractical, right, in the long term.

So whatever's the most simple, really focus on the storytelling. Um, focus on your brand, focus on storytelling. You can do that with any, um, site builder or any software. Mm-hmm.

You wanna show off your skills and see- show that you can do complexity like it's nobody's business and how, it's easy it is. Yep. But then we kind of f- we forget, forget the user of what they're trying to do out of this information because portfol- or these case studies are essentially our products, and the user is the hiring manager.

So, like, we f- we, we forget that. We forget that aspect of it. Yeah, definitely. Because now the... Yeah, I know, and it's like all this information they're trying to decipher. What is it that I need to do? Like, and if they need to zoom in on an image, I think it's too detailed. There's way too much going on that they have to zoom in.

That's 100%, and I've been guilty of it. I'm like, "Oh, look. I'm gonna put this entire, um, diagram up there just to show people how smart I am." Uh, but at the end of the day, right, um, I'm gonna be real. Mm-hmm. Like, I have never zoomed in, um, on a site map when I'm scrolling- I'll, sometimes- ... a portfolio, right? What I...

I'll sometimes do just because I like to see, like, what am I even looking at, but that's not, like, a good thing. That's not a good thing. Yeah, I know. Um, and also, like, context, man. We need context of everything that's going on here. If, if it's going to be a complex image, like, there has to be some sort of, like, annotation to be able to help me decipher.

Like, I think the most... Well, also, like, a very impactful thing I've learned about, about all these portfolios is don't assume the, the reader is going to understand everything as they are going through. Like, don't... make it painfully obvious about what exactly is going on here, because a lot of people also, uh, forget that, these hiring managers, they're, they're tired.

They're going through multiple and several sessions, so, like, it's a lot on top of their job. Yeah. So, like- Yeah ... if you make it easy as possible for them to understand, like, the better it is for them to say yes. Yes, I 100% agree with that, and oftentimes I think it's easier said than done, 'cause it's actually so much harder making something simple than it is to make something complicated.

Um- True ... and, you know. And so, uh, I think there's also blind spot as well. So what I mean by blind spot is that when this is some- a project you have worked on for six months, you have every context possible, and you're so familiar with the ins and outs, and all the, like, lingo in sort of, like, that domain area, or in that company that no one else knows.

Mm-hmm. And then there's really, like, no way... Like, I think that you can... It's really easy to be blind to, and use a bunch of acronyms and things, um, and contexts that don't exist to somebody that is, like, not in your company working on that project, right? So a really good, um, guardrail, I would say, to implement, um, if, you know, uh, people listening to this are wanting a more concrete strategy, is to send it out to your friend, um, who is...

Whether they're in design or not. I mean, honestly, this portfolio should be easily and readily understandable by somebody who is not in design. So send it out to your friend. Hey, be like, "Hey, here's a minute. Tell me, tell me, um, tell me, like, about this case study. Do you understand it? Like, read it back out to me," right?

Um, and then also to another designer, um, you can send it to another product manager, um, just to get their feedback. Someone who has no context, but maybe, like, is in tech, and see the differences in their reaction, and that's, like, very good feedback. That's like, is it simple enough? Uh, oftentimes that- Mm-hmm

like, they're going to identify exactly where it doesn't make sense. If you just look at their eyes and they're, like, glossed over, um, then I think another iteration- Mm-hmm ... is necessary, right? Yeah, I know. Es- especially, um, I know your- our own blind spots, like for example, like when we work on teams, we have our own blind spot of, like who did what, and we think it's obvious for what we did because we, uh, we remember so well.

But then we, we kind of forget how to actually state that in a case study where it is very obvious, okay, I did this, and how someone else did something else. Where a lot of times we just say we. Mm-hmm. Mm-hmm. Does that... Is that a problem, you know, you're identifying... Or you're saying that, you know, sometimes it's hard, um, to kind of like identify what part of the work you did?

Is that a problem that you've seen a lot of people have? I think it's, uh, they know how to self-identify, they just don't know how... They just forget to identify that into a case study. That is true. Um, that's definitely true. And then sometimes, you know, not thinking about that, um, I have seen some people use we a lot, um, but then that leaves me wondering, what did they do?

Yeah. Um, yeah. For sure. , So for , the designers that are working at companies where the design process is like completely chaotic, how can like a lone designer start advocating for like a structured design system without getting ignored by management?

Because I, I hear design system problems all the time with my listeners. Hmm.

Design Systems: How Much Is Enough?

,

so... I think there's a lot of implicit assumptions in design field that design system is important, um, which it's not...

I'm not saying that it's not, by the way. Mm. And I think there's also a lot of implicit assumption that UX research is important. But I'm not saying it's not, by the way, right? I, I'm saying that just like research and design system, there's a certain amount of system that is necessary based on the maturity and needs of the company.

So my perspective generally, right, like, if you wanna operate a company at the most effective way, um, what is the least amount of something you can do to maximize the amount of outcome, um, based on the needs, right? So how, how little system do you need? Because if you implement more system, that's more overhead cost, um, more maintenance, more designers' time, more engineering's time, and it's expensive, right?

Mm-hmm. So that is something to always focus on when thinking about how much system you need to build. It's really easy to say, "We need a system because it's inherently important." I think that's the same, uh, vein as why, you know, design is important- Mm ... because design. Um, and, you know, taking that lens of, well, not everyone has those values, yeah, not everyone looks at design system the same way.

So if you can communicate it in a way where what, what business value is it adding and how is it actually, like, improving the speed of the execution of designers- Mm-hmm ... improving the velocity of engineers. , The Salesforces, they need the system because without the system, everything will fall apart. And- Mm-hmm ... you know, you just can't... It's, like, impossible to operate without it, right? So I think that's maybe one good measure is, like, if you're, , remove a system and see what happens, right?

I think that's a good way to gauge impact. Um, remove, um, if you remove your design system today, what chaos will it cause, right? And you scale back, um, will you still survive? If you scale back a little bit on your design system, will it still operate perfectly fine? I think if that's the case, if that's true, then you might be, , having a little bit too much system than you actually need.

I always like to hear these different takes because w- because it, it gets boring when you hear the exact same answer in a way or the sa- the same thinking level.

And so, like, it's always so good to hear from other different perspectives because this is how we improve ourselves yeah. It's really easy to have,, fall into an echo chamber sometimes and, , I'm glad I can, , provide- Absolutely ... an outside looking in perspective.

Mm-hmm. Yeah. And like, it also is a good way to answer that, , dreaded question of like, why should we hire you? That is, , that is a good question. , Do you have any thoughts about that?

I'm, I'm not the biggest fan of that question. However, I get why they ask it. Because it really puts into perspective about how you are able to value - yourself, and how you see yourself in the company. And then that's, because that information tells you, , does that align with what the hiring manager thinks, and what they desire from a designer on their team?

Right. Right. What do you think is a better question, if you think that it's not an effective question? Maybe it's the wording of it I think is a little too direct, personally. Mm-hmm. But, , but I would say look at it as, , your design strengths. , What do you value the most?

What,, needs more like behavior-based of, , putting into situations, and then you can really see. Because that also, shows them as a person, because we are gonna be spending time together. So that's the reason why I look at it as a way to see how can we get deeper to their values and who they are as a person on top of being a designer.

Mm-hmm., I definitely think that is a very important question. In fact, when I ask behavioral questions, I score pretty highly or I value pretty highly,, self-awareness. I think self-awareness is not something that everyone identifies, , during an interview, something they pay attention to.

But for me, it's really important, just being aware, , of what your strengths are as a candidate. Just knowing what you're good at and what your, blind spots might be. Mm-hmm. Just having a little bit of self-awareness in how you work in teams. Obviously, that requires you to, sit and reflect and think about it, like what companies you actually thrive in and why.

, For example, if you're someone who thrives in a very structured company- Mm-hmm ... like, you might want, , a 2,000-plus, , company. And because you like structure and having the systems in place, that's really important insight. Whereas on the opposite side- Mm-hmm ... if you're somebody who thrives in chaos, , what really makes inside you, again, like we said in the beginning, , what is that innate thing that makes you tick that is unique to you?

Because the more you're aware of what your strengths are, the more likely you'd be able to thrive in the situation. If I know that,, the situation in which you thrive is a situation in which the company can provide for you. Mm-hmm. Mm-hmm.

, So Jenny, I'm very curious to know, , when you look at all your ADP lesson mentoring, what would you say is the - the most reoccurring problem that your your mentees are facing?

The Current Job Market for Junior Designers

The reoccurring problem that my mentees are facing Honestly, let's be, let's address the elephant in the room is that it's very hard to find a job right now as a designer.

That is just a fact. , So I would say that is the most difficult problem out there facing is really the change in the job market, right? , If you look at 10 years ago, graduates are, or like college students are graduating in a job market where there's an abundance- Mm-hmm ... and then so the values are different, right?

So if there's a s- a huge demand, , that means, , the scope of hiring is just much broader. That means if you have, , even a generic resume, you are likely to get an interview because there's just so much, demand, right? So in that case, like it- if you apply to 100, it's really just a numbers game, 10 years ago.

Now it's really not the same thing, right? Mm-hmm. , Right now the demand has... , the needs have changed. The skillsets that is demanded from companies has changed due to AI. , I think that's yet to play out what exactly those skills are. Um- Mm-hmm ... but also the amount of hiring has decreased, and that means that it's really the employer's game, right?

And that means that employers, because there's so many, , there's so much supply out there, they can spend more time finding that right candidate, and they're going to be more selective, right? So and that's why the strategy for hiring must be different from the candidates. And that's why self-awareness is important, being super aware of what you are good at, being able to pinpoint yourself and find the match, right?

And when you talk to somebody that's actually the right company for you? Because if you do know and you do realize that there's like a connection there, double down on it. And if you , don't, right? , That self-awareness is super important because that self-awareness helps you differentiate yourself in this very competitive market.

So I say like right now the can- like can- , my mentees are having the most time being strategic in their job search because obviously, , it's not something that's taught in school. It's something you have to learn, right? And that's where- Mm-hmm ... I think that mentorship or talking to somebody,, is if you have the, , privilege of talking to somebody who is more experienced and getting their opinions and, and learning from them, that's where it's super important, right?

How do you position yourself? How do you become more strategic? , And how do you really like practice, , your communication skills because you're gonna get fewer opportunities to practice live. So you have to make sure that you're going in, , everything's, , super, proofread, everything's buttoned up and good to go.

Mm-hmm. Mm-hmm. Yeah, I, and when I started with my career where I would just be applying to absolutely anything and everything, and would just - Because, like, when you're starting from zero, like, you just have to accept anything. Mm-hmm. And - the problem is is, like right now with the market, like it does not reward that behavior because everyone- Right

else is also doing that. And I think once we... , you find what you're good at, what you've, what, , what you like the most and, like, what, know, connects with you, and then you double down on it, which is, that's good. That's... I highly recommend it. But for, , junior designers, , they don't have the experience to know which one is gonna be the best for them.

That's 100% true, right? So that advice is very hard to do, and it's almost, unfair in a way- Yeah ... because in order to have self-awareness, you really need to do things, right? And until you do things, until you experiment, until you ac- actually go in and do some animation, you can be like, "I hate animation," but you would never know until you actually do it, right?

Mm-hmm. So the way I think about it also is, yes, differentiation is important, but at the same time, choose, . it's also, yeah, choose one area to focus on at a time, even if you, you come out of school without a whole lot of, , experience, , and you just don't know. You're still figuring it out.

I think that's fine, right? , But sometimes it's hard to position your portfolio for every single discipline, and, , if it makes more sense just focusing on one area that you think you're particularly strong in, then do that first, right? And also, you said, before the system rewards applying to everything.

, Now it's different. And also thinking, , career is really a long game, right? So it's not like the, you're just trying to get to from A to B. You're trying to get from A to B to C. So my advice would be to think about the plus one step, the next step, right? Mm-hmm. So if you're looking for a product design job, and like, we said earlier, oh, , I don't have...

I don't know enough. , I haven't tried enough 'cause I just graduated from school. I just don't have the experience. What is, what are, what is, , that outcome? So y- if your goal is to get a product design role, what are those skills that you need to develop in order to get there? And, , what is that half step, , steppingstone job that will get you there?

So thinking about your career as leapfrog might be effective sometimes 'cause it's nonlinear. It's, , might not be easy, uh, because to find a direct path into product design if you are just out of school and you just don't have a lot of experience because a lot of companies just aren't hiring juniors.

So in that case, , I think it's especially important right now to look at that middle step, and really looking at, like- that job, , and broaden your search, and seeing, what- Mm-hmm ... skills can you learn in that job. , Whether it's visual design, whether it's, growth. Whatever discipline, whether it's you could be doing animations, , et cetera.

So what are the s- or even development. What are the skills , that you can learn from that job that can get you to that ultimate job that you do want? Mm-hmm. Mm-hmm. And, , this is all, s- the steps of what we, , you need to overcome. And that's the reason why it doesn't feel so daunting, because it, you don't have to climb the whole mountain of getting hired in one day.

Mm-hmm. Exactly. So thinking about it as a long-term, long-term game. And if you think about it- Mm-hmm ... that way, the perspective of what you choose to accept changes, right? 'Cause, look at it. If, for example, you get two job offers. One job offer where as, for example, they give you a 100K salary, , more room for growth, whereas another one they give you- Mm-hmm

like 140K salary, but then this is, , absolutely a job you hate, and it's not anything you would ever want to do, that will never lead you to the career path you actually want. Which one will you take, right? If it's... It depends on, at the end of the day, , where... If you think about the plus one, the next step, what is the role that is going to get you to where you actually wanna go?

Yeah, and it feels like a lot of people also need to learn the hard way that you can't put a price on your mental health. Yeah. Yeah, because, yeah, some of these companies, , they can take a toll on you. Well, yeah. , You live and you learn, right? Mm-hmm. Mm-hmm. Yeah, there's a lot of people who think oh, , they can, they can tough it out, or they think that they're the problem.

, Oh, it's just burnout , I'm just not focusing correctly. Yeah. Yeah. I think this happens to, , people that have a lot of grit. Um- Mm-hmm ... who innately have a ton of grit, and then so they will have a hard time, and they'll be burned out, and they'll just try to power through, and they'll just keep trying to power through, , until they're beyond burnt out, , until they can like no longer work and they're like...

I've, I've heard of people like having to go to the hospital. They're getting heart palpitations. They're, they're, all their burnout is manifest- manifesting physically into symptoms where they have to go to the ER. So it's, , take care of your mental health. , At one point you definitely have to learn, but, listen to your body, listen to your, , listen to your heart,

it will be telling you something is not going right, and sometimes you just have to, , stop and listen and receive the signals and , give yourself some feedback. Because at the end of the day, your body is giving you feedback all the time. The job market is giving you feedback all the time. There's feedback, , if you are listening.

Yeah. Oh, man, that's a very,- a powerful note on there. So, I also wanted to do, , I know there's the big topic of AI, not only for what's happening all over tech and pretty much everyone's lives, but also in the fact of hiring. So I'm curious to know,

AI's Impact on Hiring and the Future of Design

where do you see that AI is, , impacting hiring the most?

Hmm. Well, the thing is, , my current company has not hired in the past year or two for designers. It's, , I think it- the realm has changed a lot- Mm-hmm ... , and it's still changing. I don't think it's fully settled down yet. , How has AI changed the job market? For now, what I'm seeing in practice is that AI is enabling- Mm

, A lot of things to get built faster. A lot of people think that AI is just something that replaces jobs. I don't see that being true. , In a way, maybe, but really it's, making people more efficient. And then if designers are more efficient and engineers are more efficient, that means you can hire fewer engineers and produce more output.

, So not necessarily mean that, , you'd be replacing anyone. , For now- Mm ... it's still a tooling. But what that means is that juniors are in a less favorable position, Mm ... because a lot of those roles, for example, like some doing user research, synthesizing research, all of those things could have been done by juniors, but now is being, made more efficient, right?

So there's less reason to hire juniors, or there's just going to be fewer junior roles available. , So that's the impact that I'm seeing, , in terms of how it's affecting hiring and demand Yeah, yeah, that's true. It's less about jobs loss, it's just more about not hiring,, not needing as much help for, to hire.

Yeah. And- That's definitely, that's definitely where I'm seeing it go. Yeah. But at the end of the day, what that means... what does that mean for the newer generation, is that it's still not good, right? Because you do need a younger generation of designers and to be able to cultivate it, and just so many companies are looking to operate more efficiently nowadays, , that, h- junior hiring is either deprioritized or not happening.

So that's, a way that has changed. But at the same time, I think that juniors can definitely learn, , these new tooling, and often they might have a new perspective on how to use them that, is not available to someone who's been doing the same thing, , for a very, very long time. I mean, a lot of even software engineers and designers have been doing, working in a very similar way for , many years.

And the longer you work and do something for so- that long, you , it's like hard to shift, especially when it's working for you. , That's one advantage that I see, right? Is that a lot of- Mm-hmm ... new grads have a very fresh and very new perspective in how to creatively use this tooling.

100%. I think, , I'm just seeing so much like a, renewed energy, , for tech in a way, just because there's AI now that can do so many things, and really the limit is your own creativity, like you said.

Yeah. , A- f- for PMs, , and designers especially, they had to rely on engineers before

Vibe Coding, Creativity, and Avoiding Burnout

then synthesize it myself and use a bunch of sticky notes.

Now you, there's no need. I haven't touched any sort of sticky note in a while., AI can synthesize all that almost immediately. So that's something that, , s- really saved me so many hours, so many hours in a week. , Yeah. I definitely, I definitely have experienced that as well, and sometimes it's good to program in, , those breaks. And that's something that I recommend for a lot of, , mentees that I meet as well, right? , How do you program breaks? They're , in a very similar mindset, where they're grinding from one interview to another interview to working on a portfolio to this and that, and they're burning themselves out.

, But you have to remember that also, , what I tell them, is you have to, ... In order for your brain to synthesize information, you just can't keep pumping in more information, - Mm-hmm ... and just keep going. Because if you don't give yourself the space, , that mental space is where you actually, , synthesize information, , into the way you work, the way you think, , your thinking patterns, , into yourself.

So, , that is... Give yourself that moment. , If it's every Friday, , or every Sunday, , whatever works for you, right? Because if you think about it, , if you just keep jam packing information without any rest, um, interview after interview, feedback after feedback, then you're, , sort of, like, overloading your brain, and then things start leaking.

You start, , not retaining things. It's like you're trying to cram for a final, and then by the end of the final you have, , already- Mm-hmm ... dumped out all the information. You can't retain any of it. So, , I think that time, , programming some time, , to really just absorb, reflect, and, , you yourself, you're, , in iteration too.

You, you are the product. You are the most important product. , So iterate on yourself. Mm-hmm. And those moments that you create, that those breaks, are, , very vital to that iteration process. Yeah. Yep, I think, I think that's a good note to, to end on as we're drawing close to this episode. Yeah. So, yeah,

Closing Thoughts

so Jenny, what's the best way to check out your ADP list?

, The best way to check me out is, well, I am on ADP list. , My handle is Huang Jenny. You can find me, , there, and if you so desire, , feel free to book a chat if you're looking for career advice or anything like that, or just wanna talk to me. I'm available most Saturdays, , Pacific Time. , So that's where you can find me, or LinkedIn.

Yeah. And you can find Jenny's ADP list and LinkedIn, found in the show notes, so you can easily, , be able to connect with her. So yes, , Jenny, any closing words you would like our audience to know about? Closing words. Okay. I would say, you are the most important product that you will ever work on, and so think of it as a long game, right?

And, , take it step by step. Things will change, and everything's okay. Do your best with the information you have, and get feedback regularly, , from mentors, from other people, from peers, from hiring managers, and, , I wish you all the best. Yes. Hey, thank you so much, Jenny, for sharing your wisdom.

It was a pleasure talking with you. Silly. Thank you so much, Nick, for inviting me onto this podcast. I had such a great time chatting. The hour just flew by, and, I hope that this conversation is valuable for the audience because I know it's super valuable for me. Mm-hmm. Absolutely. So please do check out our guest, and until then, you just listened to the UX Growth Podcast.

I'm your host, Nick Mann. Thank you for listening.

UX GROWTH PORTFOLIO HELP

Great work deserves
a better story.

Your portfolio should help people understand the decisions behind your work, not just the finished designs. Explore how UX Growth can help you tell that story more clearly.

Explore Portfolio Help ↗
Interview the Team, Too: UX Interviews with Jenny Huang
The UX Growth Podcast
Next
Next

What Makes a Designer Valuable Beyond the Tools? with Michael McWatters