Installation or independent service
A new installation needs cable work, device placement, and a panel schedule someone else can read. A service call needs a person who can work through a reported fault and leave the office a useful answer. If the vacancy covers both, say how much of the week each takes.
List the panel families you actually support. Ask which ones the applicant has installed, configured, and serviced personally. Someone who pulled cable alongside a programmer hasn’t necessarily done the programming.
Keep fire-alarm work in a separate brief. If you need monitoring coordination or network changes, decide who handles those tasks before putting the employee on a customer’s calendar.
Panel schedules and field changes
Ask for a panel schedule or installation record with customer information removed. Have the applicant explain where a service technician would find a device, its identifier, the last change, and any unfinished work.
Then ask: “The drawing and the wiring on site don’t agree. What do you do?” Find out how they raise the discrepancy, get a decision, and update the record. The problem shouldn’t disappear into a handwritten note that never reaches the service file.
For a lead, ask how they check another installer’s work. Which items are ready for functional tests, and which still need correction? That answer tells you whether the reported progress means anything.
Intermittent faults and service notes
Give them a fictional complaint: an intermittent fault appears overnight, but the system looks normal during the visit. Ask what information they want and what they’d check first.
Look for questions about the timing, affected device, history, and recent work. Ask them to explain what each check would establish and when they’d call the lead or manufacturer support.
Finish with a short service note. If they couldn’t reproduce the fault, can they say what was checked, what remains uncertain, and what happens next? “No fault found” on its own leaves the next visit starting from scratch.
Programming, tests, and customer handover
For a programming hire, discuss one completed job. Who agreed on the system behavior? What did the candidate configure? How did they compare the installed devices with the schedule and prove the agreed functions worked?
Ask who arranged the customer’s test window and any monitoring contact. Those details can make or break the final appointment. State who owns configuration records and service access after handover.
Platforms, hours, and pay
- Supported panels and the split between installation and service.
- Work required independently, supervision, and platform training provided.
- Programming, testing, customer instruction, and service records expected.
- Service territory, reporting point, hours, and the actual on-call rotation.
- Pay range, benefits, vehicle, tools, and travel expenses.
When the assignment is settled, use BEJ’s security technician hiring guide to prepare the vacancy. Give applicants the work and terms you can offer now.
