Collecting Interview Feedback

The pattern#

Five interviewers see a candidate on Tuesday. By Thursday, three have written something, one has not, and the fifth needs to be asked twice. The hiring decision waits on the slowest response, and the candidate waits on the decision — often while holding another offer.

What Vela does#

After the interview happens, Vela follows up with each interviewer to collect their feedback, chasing the ones who do not respond the same way it chases scheduling replies. The recruiter gets the debrief assembled rather than a to-do list of people to nudge.

Why this belongs with scheduling#

The two tasks look separate and are actually the same skill: politely, persistently getting an answer out of a busy person who has no reason to prioritize your request. That is the work Vela was built to absorb, whether it happens before or after the meeting.

Making it explicit#

You can ask for it on the original thread:

Looping in Vela for the panel. Collect feedback from each interviewer afterward.

Or afterward, on any thread Vela is already on:

Vela, please chase feedback from the panel.