Figma
Sarah Peters, Jake Becker, Conor Quigley
Designer (solo)
Handshake is a three-sided platform for early-career talent. The first side is students. Our overarching mission is to help students and recent grads find and get those first few jobs or internships to start their career. Second side: universities. We partner with over 800 schools, serving as the tech engine of their Career Services departments. Third side: employers. (This is what I work on.) We help companies find and recruit the best early talent based on their specific needs.
Time of outreach
Messaging efficacy
Success with underrepresented groups
School strategy
The team decided to fix that by automating the report-generation process and making the generated PDF files available for download when they are ready. I designed the page that would host these, featuring the two most recent reports and listing the others below in a lightweight list.
The other problem we solved was that managers had no in-product way to tell how their teams were doing when it came to outreach.
To help alleviate this, we built a leaderboard to house messaging results by recruiter.
Handshake was never meant to replace anyone's Applicant Tracking System (ATS). We've always been a pre-application sourcing tool for funneling applicants in. But because of that, we've never been able to fully prove our value when companies are now, more and more, measuring success by hires.
The obvious solution to this is integration with ATS systems, which could sync with a company's Handshake account and provide the feedback needed to measure true success of recruiting efforts. However, integrations are difficult and require cooperation and partnership. There are also a good number of ATS systems out there to integrate with. What we needed was an interim solution.
This is where the concept of List Upload came in. Import a list from your ATS into Handshake, and we do the syncing for you.
We decided to take a phased approach with this feature, releasing it only internally at first for our Customer Success team to use. That way, we can pinpoint improvements and make them before a wider release. To keep things simple for our engineers, we decided to punt on column matching in version one, and we focused on what seemed to be the primary hesitation: data security.
We wanted to empower our customers to answer their own questions with this feature: how many of my applicants had received a campaign from me? How many of my applicants had we met at a career fair? Of those we hired, how many had we met at some sort of event?
These questions can all be answered with a simple set of filters, which are extensible for later versions. We were also able to reuse our existing filters to save on engineering time. The touchpoint data changes based on the jobs and the statuses you select.
After our initial release, we'd like to add more measurements (did an applicant follow your company? did they visit your company page?), and we'd like to add a more robust funnel analysis. What that looks like, we're certain of right now, but I'm excited to design a Sankey diagram if it comes to that.