Re:Tell HN: Interviewed with Triplebyte? Your profile is abo...
by cactus2093 on Saturday May 23, 2020 @04:41PM
(#23286220)
I don't think the parent comment was complaining about the nomenclature. I interpreted it as pointing out that in any hiring activity, the candidate/applicant/whatever is the product. A company pays a recruiting service in exchange for hiring a candidate.
(Of course, the candidate also receives value because presumably they are looking for a job and get one in this transaction. But the whole "you are the product" trope always ignores the fact that the "product" person is receiving value in the transaction).
Re:Tell HN: Interviewed with Triplebyte? Your profile is abo...
by mkagenius on Saturday May 23, 2020 @09:25AM
(#23282734)
Not sure we are talking about database tables here. A user friendly email looks like [email protected] or [email protected], not [email protected]
I’ve worked at 3 different companies in the hiring space across two continents and “candidate” is the internal term they all ended up using internally for people seeking jobs. “Applicant” is too vague and “job seeker” is long and hard to scan (and it’s too similar at a glance to “job”, which is also not often used).
If “candidate” has bad connotations for you, I’d love to hear a better suggestion. But I still haven’t seen a more appropriate name for my database table.
Company / candidate / role / resume / profile / interview / offer. These are the terms almost everyone uses.