I don't just block ads, I block elements on sites I don't care about with :has-text RegEx rules. You can't do that on Chrome even on desktop anymore.

I'm this close to swapping to the Android as my primary device-- it's iMessage that has me chained. It's just too dang nice to respond to chats from my Mac during work so I don't need to pick up my phone.

Everything else is better on the Android. Don't get me started about the iOS keyboard or Siri.

There is a term for this. "Getting stuck up your own butt." It wouldn't be so bad except that said people often take on an air of absolute superiority because they used "only logic" and in their head they can not be wrong. Many people end up thinking like this as teenagers or 20 somethings, but most will have someone in their life who smacks them over the head and tells them to stop being so foolish, but if you have enough money and the Internet you can insulate yourself from that kind of oversight.

[0] https://www.reddit.com/r/thebeachboys/comments/137tx33/the_o...

Honestly I think for this role the interview should be more a gut check on personality and expectations, after you’ve seen their work and read their case studies.

That said I’d go for a deep dive on the work product from their portfolio that is most analogous to the problems your team is solving.

The best lead/senior designers I’ve worked with share some traits you should look for.

1. They are flexible, not prima donnas— but they DO have standards they’re willing to stand up for.

2. They can fluently explain WHY they made their choices, and recognize and articulate trade-offs.

3. They understand enough about research methodology to be able to internalize research results in their work product.

4. They understand development enough to know what not to do, and when to push the devs to try harder to implement.

5. They’re very quick on the uptake, and can understand the BUSINESS problem at hand, not just the visual or interaction or information problem.

6. They are clear, grammatical, concise writers. Lest you think this is irrelevant, keep in mind it’s often the UXD writing the micro copy. 7. They fully understand design systems, tokens, atomic designs and are HIGHLY organized.

In our world of UIs and complex product interactions, design systems and tokens, it’s much less important that a designer be concerned with aesthetics. The roles of wireframes (typically what I have done in the past as a UXR/generalist) is merging with the design skill. (Personally I think that trend ought to go the other way, but it is what it is.)

Think about what you want out of a UX designer to make your work better.

What is their design process like? Do they involve engineering early on to be a part of the process? Do they have experience writing creative briefs or contributing to engineering design docs? What do their deliverables look like? Do they love prototyping with real data? Will they push you (FE) to go above and beyond on the projects you work on. And the other way around, how do they work around roadblocks like infra constraints and spaghetti code when they cant get their initial design vision built?

There are more questions you can ask, but again, you want to be trying to find out if you will enjoy working with them as a partner and not someone who just throws designs over a wall and is inflexible on engineering constraints.