Loading…

Hiring is a two way process.... Sensitive

Sawhneyroshni
Public 13 conversations 21 thoughts 42 upvotes 0 downvotes 0 series

Recruiters often forget that hiring is a two-way process. Yes, candidates may be actively searching for jobs, but that does not mean their time and efforts should be ignored. After preparing, attending multiple interview rounds, and waiting for feedback, candidates deserve clear communication. If a company is not moving forward, a simple update shows professionalism. Endless waiting and unanswered follow-ups make candidates feel undervalued.

In groups

Post content

Hiring Is a Two-Way Respect Process

Recruiters often forget that hiring is a two-way process. Yes, candidates may be actively searching for jobs, but that does not mean their time and efforts should be ignored. After preparing, attending multiple interview rounds, and waiting for feedback, candidates deserve clear communication. If a company is not moving forward, a simple update shows professionalism. Endless waiting and unanswered follow-ups make candidates feel undervalued. Behind every resume is a person, not just an applicant.

Thoughts

  • Arubanuus

    I adree with the idear

    Permalink
  • 404_brain

    Genuinely on your side here, but I'll be the annoying one. Two-way means both ways. I've had candidates no-show a final round with zero notice after I moved three people's calendars for it. Companies should go first because they hold the power, but the ghosting problem isn't only pointed in one direction.

    Permalink
  • half_a_thought

    maybe it's just me but the "behind every resume is a person" line is the whole thing. the fix is cheap, a two line email, and places still skip it. feels like it's just not anyone's actual job to care, so it doesn't happen. idk.

    Permalink
  • SeanArmitage

    Having sat on the hiring side for a while: most of the silence isn't malice, it's structural. The req gets frozen mid-loop, the recruiter who owned your file changes teams, and nobody reassigns the "send the no" task because it's on nobody's roadmap. None of that is the candidate's fault and none of it is an excuse. It just means the fix is a process one. Make "close the loop" a step in the pipeline, not a favor someone happens to remember.

    Permalink
  • readonly_friday

    This is just basic respect, right? I've been on both sides of the table. The awkward part isn't sending the rejection email. It's that most places treat it as optional. A quick "we're moving forward with someone else" takes minutes, and it's the difference between a candidate feeling heard and spending weeks wondering if you even read their application.

    Permalink
  • SeanArmitage

    Having sat on the hiring side for a while: most of the silence isn't malice, it's structural. The req gets frozen mid-loop, the recruiter who owned your file changes teams, and nobody reassigns the "send the no" task because it's on nobody's roadmap. None of that is the candidate's fault and none of it is an excuse. It just means the fix is a process one. Make "close the loop" a step in the pipeline, not a favor someone happens to remember.

    Permalink
  • readonly_friday

    This is just basic respect, right? I've been on both sides of the table. The awkward part isn't sending a rejection email—it's that most places treat it like optional. A quick "we're moving forward with someone else" takes minutes, and it's the difference between a candidate feeling heard and spending weeks wondering if you even read their application.

    Permalink
  • 404_brain

    Genuinely on your side here, but I'll be the annoying one. Two-way means both ways. I've had candidates no-show a final round with zero notice after I moved three people's calendars for it. Companies should go first because they hold the power, but the ghosting problem isn't only pointed in one direction.

    Permalink

Related posts

  • Will a Meta engineer tell you the comp before the company he works for?

    Meta bought the best engineers in the industry with the fattest comp packages anyone has ever seen, and got exactly what it paid for: a workforce of well-paid mercenaries who feel nothing for the place and will not say its name out loud at parties.

  • Do you have to miss your goals to get promoted?

    Three years ago I watched my manager hit every single quarterly target two years running. Clean dashboards. Green everywhere, all the time. She was the most reliable person in the building, and at the next planning cycle his team got carved down by four engineers out of 35 and folded under someone else. Nobody framed it as a punishment, but rather as "efficiency" and "we want to invest elsewhere". The lesson landed anyway, and not just on me. Sadly, never on my manager.

  • Will AI replace you, or will a coworker using AI replace several of you?

    A lot of office workers are comforting themselves with the wrong question. They keep asking whether AI can do their whole job. That is not the threshold their employer will use. The real question is whether the output can be produced cheaply enough, and checked cheaply enough, that the role starts looking expensive. It's not if AI can fully do our job, is "can it accelerate it long enough so only half of my team is needed?". Because the answer to that, sadly, is yes.

  • Do tech companies actually benefit from employees who can't afford to quit?

    I've been moving through tech orgs long enough to recognize a pattern that many of you will recognize as well. Some teams are passive, they ship on time, hit targets, run clean processes, and yet nobody ever kills a bad idea in the meeting. Nobody says this is the wrong thing to build. The roadmap has a thing, or six, on it that three people privately talk about how it won't work, but it moves through planning without a word, with smiles even. You watch the lead engineers nod at something...

  • Does splitting 'hard' and 'soft' skills make people worse at both?

    Hard skills are measurable, specific, and teachable abilities or technical knowledge gained through education, training, or experience, which is often directly related to a particular job or industry. Examples include data analysis, programming, graphic design, accounting, dancing, painting… They are usually the core of a profession, particularly the part of it excluding interaction with other people. On the other hand, soft skills are mostly defined as “personal attributes, interpersonal....

  • Is AI driving managers medically insane?

    There is a new executive fantasy in circulation, that AI can replace workers. Although it is certainly re placing some, executives have a fantasy that makes them feel they can do their report's job on their own, with AI. That they can code! Just open a dashboard full of named agents, watch tasks move across panes, ask for an update in a commanding tone, and get features done at a whim. It feels like a dream, specially when you run your "think big ideas" through it and the AI tells you that...

  • Does stack ranking turn coworkers into enemies?

    Stack ranking always ends in politics because it changes what competence means inside an organization. Once employees are judged relative to each other instead of against a stable standard or objective, your smartest coworker stops being an asset that you can learn from and collaborate with, and starts becoming competition. Their success can lower your standing. Their visibility can cost you promotion space. Their expertise becomes a threat to your own security.

  • Are the managers who bet AI would replace engineers being replaced the fastest?

    Last year my LinkedIn feed had a genre. A program manager or a "delivery lead" or someone with Agile in their headline would post a screenshot of an AI writing a function, add a line like "and they said this job was safe, just learn how to code" and collect four hundred likes from people who do the same job. The implication was always that the typing part of engineering was the engineering, and now that a model can type, the typing class was finished.