One person cannot print to a shared printer. How would you narrow the problem?

Example Answer

I'd first confirm the selected printer and whether this job needs badge release. I'd ask the user not to send repeated copies while we investigate. The colleague's successful print suggests a narrower problem, but I'd verify the timing and current printer status before ruling out a shared fault.

I'd inspect the queue for the user's job, its status, and any error, without opening other people's documents. I'd check the device display for paper, toner, or an offline condition and confirm the user chose the intended queue. If permitted, a small nonsensitive test from another application would distinguish a document or application issue from their general printing path.

If only their job is stuck, I'd ask permission to cancel that specific job and resend one test after addressing the observed cause. I'd confirm it has not already printed or moved to the release queue. I would not clear everyone's jobs or restart a shared spooler as an initial fix.

If other users now fail too, I'd escalate the common queue and device evidence to the print administrator. I'd close only after the employee collects the correct output, checks its pages, and confirms no duplicate or confidential copies remain unattended.

What the interviewer is assessing

Essential: Check selection, release requirements, job ownership, and shared scope before intervening.

Stronger: Use one nonsensitive comparison print and verify physical output, including possible duplicates.

Red flags: Clear the entire shared queue, restart shared printing without authority, or treat a disappearing job as proof it printed.

Follow-up

What if the job disappears from Windows but nothing comes out?

I would check the printer or badge-release queue and the device status before resending. A job can leave the local queue without producing a collected page, and an immediate resend could create duplicates later.