How feedback in the four weeks since launch led us to add screening questions and simplify our matching language, and what we’re still working out for fit summaries.
One thing we’ve been intentional about in the new product is creating tight feedback loops, so we’re constantly tuned in to what people are experiencing.
Since launch, it's been overwhelming (in a good way)! After half a year of building, real people are now using the upgraded Hatch platform to find jobs or hire - pushing it, poking it, and telling us exactly how it’s going.
The feedback comes through loud and clear in Slack:

It’s been a gift. These feedback loops have massively shaped our product roadmap. People need it? We build it. People are confused by it? We re-work it.
So today, I wanted to share a few things we’ve changed in the four weeks since launch and one we’re still thinking about.
Screening questions were always on the roadmap, but to get the beta out faster, we launched without them. It didn’t take long for employers to tell us they needed them, both to save time and to improve clarity for jobseekers.
As Sam Turner, our PM, said: “We’ve already designed it. We know people want it. Let’s just do it.”
So, we did, and screening questions are live as of this week!

A big part of our upgrade is making hiring more human through introducing “matching”, a more real and direct way for candidates and TA members / Hiring Managers to learn about each other and match for a job. Either side can send a match request to the other. We’ve heard a lot of excitement from our customers and candidates about the new way to match.
However, we’ve also heard confusion around the call to action “Send match request”, not knowing if it’s equivalent to a job application or what to expect when they press the button.

So, we’re simplifying. For candidates, the button will now say “Apply”, and we’ll reserve the “match” language for when an employer accepts an application! For employers, proactively sourcing will still be called sending a “match request” and if the candidate accepts, it’s a match!

I believe that direct and human-centric matching between a candidate and a hiring manager or TA member is a better experience for both sides, and so we’ll continue to use the term “match” and build a platform that helps more people find better matches faster. But we’ll keep our language simple so everyone understands intuitively how the platform works.
One of Hatch’s key promises is better matches for both job seekers and employers. Right now, fit summaries are how we deliver on that, but we want to make them even more valuable.
We’re exploring how to visualise things like values fit - building on the values spidergraph people loved in the last version.
Pictured is a fit summary design.
