Show critical metadata for each plan
7pm Chris @Koja
Yelle - Tu Es Beau
You: hi to everyone og!
John OrlandSep 16
You: though i dont really know...
Meet Peristyle, a new sans serif
Secrets of the Playa🔥
Follow Up from UX Slack🌟
Go back in time with Sublime
Accept Katt's Invitation to Melbourne
Lyft Ride ReceiptYesterday
Your ride with Vanessa
Education / Teaching Assistant🌟
Sink into Helsinki
Seeking Life Advice🌈
(No Subject) - Draft 1📝
Machine, We Invented Time.
Online Success PlanToday
Make over $8,614 working at home🚮
Get the Latest from The Weeknd🗑
Optimal Tax ReliefWed
Stop living in Fear!🚮
Hey heyheyjjmoi !!🚮
Waiting For Your Response🚮
Lyft Ride ReceiptTue
Your Ride With Ben.html🗑️
Classic Cases for iPhone X🗑
(No Subject) - Draft 1📝
#cold email 1
I'm a lead designer and I came across your profile and I'm impressed with your work and background. Reaching out regarding your career and an opportunity with us. We have openings for UX roles in the Bay Area, CA. If you're interested, shoot over your resume to me. If not - would you recommend someone that seems like a good fit with us? Thanks - looking forward to hearing back soon!
#cold email 2
I came across your profile and I really like your work and background. I’d love to learn more about you in general and also share a bit about what design means to our team and where it’s heading. If you are up for a coffee here at our office or a phone chat, I’d be thrilled. Looking forward to hearing from you.
#rejection email 1
I really appreciate that you took the time to consider us and participated in our whiteboarding exercise. We’ve genuinely enjoyed getting to know you and learn about your passion for design. While you were a fantastic candidate in many ways, we’re looking for candidates with more experience for the team right now. We hope you don’t mind if we reach out to you in the future when another role becomes available within our company for which you would be well-matched.
Thank you again for your time and considering us in your search.
#rejection email feedback
consider giving high-level feedback about how they didn’t meet expectations while not getting into details that would require more time from those who took part in it
also start building more of that feedback time into you and your team’s expectations for time invested in the hiring process
you should be able to distill reason(s) not to hire into something more meaningful than “we want someone more experienced”
right now, the rejection letter that you’ve got here is a generic one. Thanks for coming in, you were great, but we want more experience, and maybe we’ll reach out one day if we want someone junior. There’s nothing in here that the candidate can use to consider how to develop their skills to have a better chance at a role with you in the future.
just remember, if you choose to send a generic rejection email, you can never ever complain if you get a generic rejection email yourself
the best I got was an email directly from the head of UX I interviewed with, and I followed up asking for feedback, and he quickly responded with "hey, only 1 in 100 got an interview, so feel good about that, and we really need someone with specific hands-on experience in building stadium-sized interfaces, so it's not a failure that you don't have that"
similar to “it’s not you, it’s us” rejection. state frankly that while they were qualified you needed someone with more years of experience on paper to convince corporate to hire a UX
i think you can give a generic reason if it’s early in the interview process and they are wildly not a good fit, but if you’ve spent 3 interviews with someone, it’s a very kind thing to give some specific feedback. You can make a world of difference in the life and self-esteem of someone who is job hunting if you’re a little more direct with rejection feedback when it’s just a case of needing something different than they have.
the best rejection letters I've got have stated plainly where I was lacking in what the company is looking for. eg: we're going with another candidate who has d3.js experience. (company stack had d3.js) or eg: we were hoping to see more iOS specific design solutions in your designs (which there weren't, i knew)
reasonable open discussion is always good. I like to think I'm a reasonable person.
even if the company has a strict zero feedback policy, but after all that effort of getting through to the final stages, would have been nice to know where are the missteps