Evaluate Symbiotic Technology Integration Consultant candidates across 4 weighted areas: technical depth, work that shipped, diagnosis under uncertainty, and working across the org. Technical depth leads at 35%, so check depth on human-machine coupling stacks: EEG or EMG signal chains, Lab Streaming Layer, ROS 2 middleware, exoskeleton fitting protocols, and human factors. Use the rubric to compare role-specific evidence consistently.
For technical depth, look for evidence the candidate names specific sensor stacks, latency budgets and calibration routines, and explains why a given coupling method suited the wearer population. For work that shipped, look for evidence the candidate cites named client rollouts with operator counts, uptime figures, and evidence the augmentation stayed in use after the pilot ended.
Apply the written 1–5 anchors to every answer, record the evidence behind each rating, and use the factor weights to reach a consistent overall assessment.
Complete evaluation framework
What to assess and how to score it
Review the evidence signals before interviewing. Then use the anchored descriptions—not instinct alone—to choose the score that best matches each answer.
01
Evaluation factor
Technical depth
35% weight
Check depth on human-machine coupling stacks: EEG or EMG signal chains, Lab Streaming Layer, ROS 2 middleware, exoskeleton fitting protocols, and human factors metrics such as NASA-TLX.
Evidence to listen for
Explains the physics or mechanism behind their work, not just the tooling
Names the standards, tolerances, and constraints they designed against
Can defend a design decision under follow-up questions
Distinguishes what they personally engineered from what the team delivered
Five-point scoring guide
1
Poor
Cannot explain the fundamentals of their own stated specialism.
2
Needs Improvement
Knows the vocabulary but not the underlying mechanism; struggles under follow-ups.
3
Satisfactory
Solid working knowledge for the role; depth thins out on edge cases.
4
Very Good
Strong command of the domain; explains trade-offs and defends decisions well.
5
Excellent
Names specific sensor stacks, latency budgets and calibration routines, and explains why a given coupling method suited the wearer population.
02
Evaluation factor
Work that shipped
30% weight
Probe deployments that reached daily use: number of operators onboarded, sites live, adoption rates after 90 days, and integration into MES, EHR or WMS systems of record.
Evidence to listen for
Names specific programmes, parts, or systems that reached production or field use
States their own scope inside the project
Can give measured outcomes: yield, cycle time, cost, failure rate
Explains what went wrong and what they changed
Five-point scoring guide
1
Poor
No delivered work; experience is coursework, lab-only, or purely observational.
2
Needs Improvement
Contributed to projects but cannot say what shipped or what their part was.
3
Satisfactory
Has delivered real work; outcomes described without numbers.
4
Very Good
Names shipped work and their scope, with some measured results.
5
Excellent
Cites named client rollouts with operator counts, uptime figures, and evidence the augmentation stayed in use after the pilot ended.
03
Evaluation factor
Diagnosis under uncertainty
20% weight
Test how they isolate faults when a wearable underperforms: drift, electrode impedance, RF interference, fatigue effects, or plain user rejection, and how they separated each cause.
Evidence to listen for
Describes a real failure they chased to root cause
Shows a method: isolate variables, reproduce, measure, eliminate
Distinguishes correlation from cause
Says what they ruled out and why, not only what the answer turned out to be
Five-point scoring guide
1
Poor
No diagnostic method; guesses or escalates immediately.
2
Needs Improvement
Trial and error with no structure; cannot explain how they narrowed the cause.
3
Satisfactory
Reasonable method on familiar problems; less structured on novel ones.
4
Very Good
Clear systematic approach with a real root-cause story.
5
Excellent
Walks through a messy field failure, lists hypotheses tested with data logs, and admits which suspected cause proved wrong.
04
Evaluation factor
Working across the org
15% weight
Assess how they align safety officers, works councils, IT security and end users; look for ISO 13482 or IEC 62304 reviews, consent handling, and change management artefacts.
Evidence to listen for
Explains technical constraints to non-technical stakeholders without condescension
Has negotiated scope, cost, or timeline with manufacturing, product, or suppliers
Documents decisions so others can act on them
Takes review feedback without defensiveness
Five-point scoring guide
1
Poor
Cannot communicate outside their specialism; dismissive of other functions.
2
Needs Improvement
Communication gaps cause rework; avoids stakeholder contact.
3
Satisfactory
Works adequately with other teams; documentation is thin.
4
Very Good
Communicates clearly across functions; reliable collaborator.
5
Excellent
Describes winning over sceptical union reps or clinicians using trial data, written risk assessments and negotiated opt-out terms.
Evidence-led prompts
Interview questions for a Symbiotic Technology Integration Consultant
Use these prompts to surface evidence for the weighted factors above and compare candidates against the same role-specific criteria.
01
Can you provide examples of integration projects you delivered successfully?
02
Can you describe an integration project that failed, and what you learned?
03
Can you describe customising a solution to meet specific client needs?
04
How do you assess whether an organisation is ready for an integration?
05
How do you align technology decisions with business goals?
