Protect an engineer's privacy during a confidential search

A confidential search starts with specific permission. A recruiter should ask where a profile may go, who may be contacted, and which information needs protection. These details matter especially when a candidate still has consulting work or personal legal questions in progress.

Eli, a software engineer, said, “I do not want former colleagues called, and I do not want my profile sent everywhere.” Noor replied, “I will not share your profile without your authorization. Let us name the organizations you would consider and the people you permit us to contact. Are there references you want held until a later stage?” Eli said, “Yes. I also have a noncompete review with my lawyer. Does it apply?” Noor answered, “Your counsel can advise you on that question. I can record that you want to review each opportunity before any submission and that no former colleague is a reference without your written approval.”

Noor should write the permitted employers, prohibited contacts, approved profile version, and the point at which references may be requested. She should avoid keeping informal notes that a colleague could misunderstand. The recruiter does not need the substance of a candidate’s legal advice to follow a clear consent boundary.

The decision is to send Eli a concise confirmation of sharing permissions for approval. When a suitable role appears, Noor can provide the verified opportunity facts and ask again for role specific consent. That second decision is meaningful because circumstances and employer names change.

For practice, build a consent checklist containing profile sharing, employer names, reference contact, and feedback preferences. Roleplay a candidate who changes one boundary halfway through the call. Review how you record the update and how you tell anyone already working on the search.