Why pre-screen RFID engineers before the technical interview
This technology works beautifully in a demonstration and disappoints on site. Metal detunes tags, liquid absorbs the signal, motors and lighting add noise, and a read rate quoted from a datasheet becomes something much lower on a real shelf. Engineers who have deployed know this, survey the environment before committing, and can quote the read rate they achieved. A short screen asks for that number and how they got there.
What actually matters when screening RFID Engineer candidates
- 01
Technical depth
Probe command of EPC Gen2 / ISO 18000-6C air interface: Q value tuning, session flags, dense reader mode, link profiles, plus antenna gain, polarization and near-field versus far-field behaviour.
- 02
Work that shipped
Ask for deployed systems: portal or overhead reader arrays, Impinj R700 or Zebra FX9600 fleets, SGTIN-96 encoding schemes, and the read accuracy achieved in production.
- 03
Diagnosis under uncertainty
Test how they chase intermittent misreads: liquid or metal detuning, multipath nulls, reader-to-reader interference, cable loss, and use of Voyantic Tagformance or spectrum analysers.
- 04
Working across the org
Check work with operations, IT and vendors: middleware or EPCIS integration, ARC tag selection, FCC Part 15 constraints, and training warehouse or line staff on tag placement.
Pre-screening questions to ask RFID Engineer candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Deployments they built
4 questions01What is your experience with radio frequency identification technology?
Listen forDeployments with scale in readers and tagged items, and their own scope rather than a vendor's delivery.
Experience described from evaluation or specification, or scale left undescribed.
02Have you been involved in setting up a system from scratch?
Listen forA deployment from site survey through commissioning, with the read rate achieved after installation.
Installation performed by a vendor with no involvement, or no measured read rate after commissioning.
03What sectors have you developed or managed these solutions for?
Listen forSectors named with their particular difficulties, such as metal in manufacturing or liquid in retail.
Sectors listed with no environmental differences, or solutions treated as portable between them.
04What is the largest deployment you have worked on?
Listen forReader and item counts with the data volume it produced, and how that was handled downstream.
Scale claimed with no numbers, or no consideration of what happens to the read data.
Why reads fail
3 questions05Can you discuss the different types of tags and their uses?
Listen forTag selection driven by the material being tagged, with detuning on metal and absorption in liquid understood.
Tags chosen from a catalogue by price, or no awareness of why a tag fails on certain products.
06Do you have experience with near-field and far-field systems?
Listen forThe physical difference understood and used deliberately, with a case where near-field solved a problem.
The distinction not understood, or one approach applied to every read requirement.
07Have you worked on passive, active or semi-passive systems?
Listen forThe trade-offs between cost, range and battery life reasoned about, tied to a decision they made.
One type used exclusively with no comparison, or active tags proposed with no maintenance plan.
Diagnosing a site
3 questions08How do you go about resolving technical issues in these systems?
Listen forDiagnosis that separates tag, reader, antenna placement and environment, with measurement at each step.
Readers replaced as a first response, or missed reads attributed with no site measurement.
09How do you approach system testing, and can you describe your troubleshooting process?
Listen forRead rate testing under realistic conditions with the products and speeds the site will actually use.
Testing with sample tags in ideal conditions, or commissioning with no read rate acceptance criterion.
10Are you comfortable working with protocol and spectrum analysis tools?
Listen forSpectrum analysis used to find interference from motors, lighting or other equipment on site.
Interference assumed rather than measured, or no experience with analysis equipment.
Standards and security
2 questions11What experience do you have with the relevant standards and protocols?
Listen forStandards understood including regional frequency and power limits, which differ by jurisdiction.
Standards named with no regional awareness, or equipment specified that would not be permitted locally.
12How do you ensure the security of these systems against interception and cloning?
Listen forAwareness that basic tags can be read and cloned, with authentication used where the application needs it.
Tag identifiers treated as secure credentials, or no consideration of cloning in an access application.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Technical depth
35%5Explains Q and session choices against tag population size, and links antenna polarization and power settings to measured read reliability.
Work that shipped
30%5Names specific deployments with before and after read rates, tag counts, site conditions, and their own role in commissioning and tuning.
Diagnosis under uncertainty
20%5Describes an isolation sequence from tag to antenna to reader to middleware, with measurements taken at each step before changing anything.
Working across the org
15%5Shows they translated RF constraints into workable process changes and got operations and IT teams to adopt them without escalation.
This works beautifully in a demonstration and disappoints on a metal shelf near a motor. A one-way video screen asks what read rate they measured on site.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish what they deployed, test their understanding of read failures, and hear how they diagnosed a difficult site.
How much physics should I expect?
Enough to explain why a tag fails on a particular product. An engineer who selects tags from a catalogue without understanding detuning and absorption will specify a deployment that underperforms and cannot say why.
Evaluating answers
What is the strongest signal when screening this role?
A read rate they measured after installation. Engineers who deploy know theirs and know it is below the datasheet figure. Anyone quoting only vendor specifications has not commissioned a real site.
How do I test their environmental understanding?
Ask why a tag might fail on one product and work on another. Real answers cover metal, liquid and tag placement. Anyone who attributes read failures to the reader alone has not surveyed a site.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
