The system, files, and unfinished work
Before interviewing, collect the equipment list, processor information, current drawings, and available project files. Write down which rooms are ready and which functions still need work. If you’re taking over another integrator’s installation, find out what access and backups your company actually has.
That preparation changes the conversation. You can ask about the project instead of spending an hour discussing the candidate’s favorite platforms and discovering later that the job needs different experience.
Tell them whether this is an employee position, a defined project engagement, or a service assignment. Include the site visits, travel, and support available. A person finishing the controls for one house may have a different working arrangement from the person covering your service calls.
Crestron Home or custom programming
Crestron Home configuration and custom control programming aren’t interchangeable hiring requirements. Crestron’s current configuration documentation describes Configure Pro as a platform with no-programming tools. Its system overview points older equipment to legacy documentation.
Name the installed platform, processor generation, and software in your brief. For custom programming, specify the tools, interfaces, and integrations the person will maintain.
Ask about a comparable house: “Which parts did you configure or program yourself?” Follow up on the controls, testing, changes, and closeout. Installation experience on a Crestron job may be useful, but it doesn’t tell you who wrote or configured the system.
Equipment decisions and programming support
The programmer needs decisions about how the rooms should work. The installation crew needs to finish its connections. Someone needs to deal with the network and the homeowner’s changes.
| Work | Person to name before the hire starts |
|---|---|
| Room behavior and customer changes | Project manager or designated customer contact |
| Equipment installation and unfinished field work | AV lead |
| Network dependencies and access | Network owner |
| Controls, tests, and current project files | Programmer or assigned commissioning lead |
One person may fill more than one role. Check their availability against the actual schedule. A lead can’t spend the same morning supervising another house’s rough-in and finishing this home’s demonstration.
Touch-panel faults and service notes
Give the candidate a short fictional diagram: a touch panel intermittently fails to select a source, while another interface works. Ask what they’d need to know before making changes.
They should be able to describe the failure, identify shared parts of the control path, ask about recent work, and explain what each check would establish. Ask when they’d involve the AV lead or network owner.
Then have them write a few lines for the service department. The note needs the complaint, observations, approved work, result, and remaining action. That tells you how another technician would pick up the call.
Use a training example or redacted sample. Don’t ask applicants for customer source files, credentials, or private household details.
Source files and customer handover
Include room tests, current files and backups, a change record, the homeowner demonstration, and an honest punch list in the assignment. Decide who accepts the work and who handles later service. Record the company’s file ownership and access arrangements through its normal contracting process.
Put those duties in the opening alongside the platform, location, pay range, and site attendance. The BEJ Crestron programmer hiring guide has a job-brief template you can adapt.