Jobio · Product-design decision

Connecting relationship context to recruiter outreach

Evolving linked companies and recruiters into a contextual preparation flow for starting a conversation.

Project context: An AI-powered application workspace for understanding roles, preparing documents and tracking a job search. The work spans the application, marketing website, payment model and practical service delivery.

My contribution: Design linked job, employer, recruiter and agency context. Connect that context to a role-aware recruiter-note flow. Move outreach beside recruiter information and retain review/copy boundaries.

The original tracking problem included remembering people as well as applications. An employer, an external recruiter and a recruitment agency can have different relationships to the same opportunity. That context becomes useful when the applicant wants to start a conversation.

Building the relationship context

Early work linked jobs, companies and recruiters, including creation within the application flow. Later contextual panels made related information available without sending the user away to a separate directory. Agency-specific information added another distinction to the relationship model.

The preparation question was then more specific than “write a networking message.” The product already knew which job and contact the user was considering. I used those relationships to shape a role/recruiter-aware note-generation flow with explicit prerequisites, short tone variants and saved output.

Putting the action beside its reason

The initial placement competed with general role insights. Later workspace guidance moved outreach into recruiter context, where the person and their relationship to the opportunity were already visible.

Alternative considered: Keep outreach as a competing block inside general role insights. The later revision brought the action closer to recruiter information instead of asking users to locate it in an unrelated preparation area.
Deliberate choice: Place recruiter-note generation in the recruiter context, with explicit prerequisites, tone choices and saved/copyable output.
Accepted trade-off: The scope supports preparation and copying; adaptation and sending remain a human task rather than an integrated messaging service.

That placement connects information to an action without making the contact panel into a full communications system. A user can generate and copy a note, adapt it and send it through their chosen channel. Jobio's delivered scope did not include sending on their behalf or an integrated messaging history.

Explanatory reconstruction: Start with the relationship. Opportunity: Saved job and employer. Relationship: Recruiter and agency context. Prepare a note: Relevant inputs + tone choice. Review + copy: The user adapts and sends. — Explanatory workflow reconstruction from project documentation; this is not a product screenshot. Saved output supports reuse. Message sending and improved response rates are outside the evidenced scope.

A bounded preparation capability

Saved results make the output available when the user returns, while tone choices give a small amount of control without turning the flow into another complex editor. The result connects relationship modelling, contextual interaction and model-backed writing around one application task.

Linked recruiter and opportunity context feeds a note-generation flow with tone variants, saved results and copy actions, later placed beside recruiter information.

The evidence establishes preparation behaviour, not improved response rates or an in-product sending integration. Networking-effectiveness claims in early brainstorms were hypotheses.

I owned the model and workflow design with AI-assisted implementation. The record shows what the experience makes possible; it does not establish that recipients replied more often or that every generated message was suitable. Human review and adaptation remain necessary parts of the task.