Open job and candidate details without the stagger

Prepare the whole working view

Approaching a job now prepares its Activity timeline alongside the job, candidates, and saved workflow. Candidate links prepare the candidate record, job history, linked notes, and organization team list together before navigation.

When that short preparation finishes before the click, Activity, History, and Assigned recruiter can use the ready session data immediately instead of starting separate requests after the rest of the page appears.

Show pipelines in their finished shape

Job pipeline cards now paint in their final column widths. Columns no longer expand from the narrow empty-stage layout when cached candidates become available, so the board appears as one settled view.

On a normal sub-second first load, RecruitIQ keeps the Candidates surface reserved and reveals the completed board together instead of flashing a short-lived spinner. A progress indicator still appears in the same reserved space when a load becomes genuinely slow.

Moving a candidate now updates the visible board and its prepared candidate snapshot as one operation. An older background request cannot briefly return the card to its source column, and the completed drop no longer plays a return animation before settling.

If the same candidate is moved again while an earlier save is still finishing, RecruitIQ keeps the newest drop on screen and saves those moves in order. Activity reflects each drop immediately, then quietly replaces the temporary entry with the confirmed history from the server.

The compact Activity card stays bounded to the latest three entries as new work arrives. See more opens the complete job history without allowing the overview card to keep growing down the page.

The related fragments share the same user-scoped session keys across hover preparation and the destination page. Repeated visits reuse a fresh result, while candidate movements, recruiter changes, and new notes refresh the affected fragment without replacing useful content with a full loading state.

Fresh data still wins

A true first visit, a click that beats the preparation request, or a slow connection can still show a normal loading state. RecruitIQ keeps these short-lived details in memory for the signed-in session rather than storing candidate notes or personal information in persistent browser storage.

This change does not move candidates, change a workflow, reassign a recruiter, or alter the underlying activity history. It changes when existing authorized data is prepared and how smoothly it is presented.