HRI Engineer
Human–robot interaction: perception, behaviour and on-robot integration.
Apply
IntSenseIntSense
Sense Humans. Guide Machines.
The human interaction layer that helps machines understand when and how to engage.
Your fleet already plans routes and avoids people reliably. What nothing decides is whether to approach this person, right now, at this angle — or wait, ask, or back off. That gap is where staff take manual control, where people get startled, and where rollouts stall.
We agree the site, the embodiment and the one interaction that keeps costing you time. Data scope and retention are written down before a single sensor is switched on.
Machines already know how to move. IntSense decides when and how they should engage with the person in front of them — and hands that decision to the stack you already run.
IntSense fuses multimodal human signals into an interaction state, predicts the likely human response to each candidate action, and emits a single decision your controller can accept or ignore. It is a policy layer — never a motion planner.
Voice and intonation, vision, language, distance and optional wearables — captured on device.
Gaze, engagement, intent, crowd density, zone rules and the robot's current task.
P(human outcome | state, context, candidate robot action), with a calibrated confidence.
One high-level call: SLOW · STOP · REROUTE · ASK · ENGAGE · DISENGAGE, with alternatives.
Your planner and controller execute the motion exactly as they do today.
Every decision carries a confidence and an expiry. Your controller decides whether to act on it, and your existing safety layer always has the final word. Nothing we emit can override a stop.
Each decision is logged with the human outcome that followed it — approach accepted, path abandoned, handover completed. You get a benchmark against your current navigation baseline, not a demo reel.
Every time an operator takes control because the robot handled a person badly is a logged event. That count is the first number we move.
Robots that read the room stop freezing in shared aisles and stop making people detour. Cycle times hold closer to the model in your business case.
You leave the pilot with a written benchmark against your current baseline — the evidence your operations and safety leads ask for before a fleet rollout.
If your stack accepts a high-level suggestion — over a topic or an SDK call — it can run IntSense. No hardware change, no model swap, no vendor lock.
Decisions, not trajectories or joint commands — your motion stack and its validation stay as they are.
The whole loop runs on the robot or a local edge box. No connectivity needed, no audio leaves the site.
Scope, retention and use rights go into the contract before the first sensor is switched on.
The cheapest moment to decide how a machine behaves around people is before its hardware is frozen. One unit or one lab is enough — no volume, no fleet commitment.
A robot that keeps its clearance can still startle, crowd or interrupt a person. IntSense makes that moment an explicit, logged decision — and your certified safety functions keep the final word.
Your embodiment, your stack, the interaction that costs you time on site.
Written, specific to your controller — where the decision enters and what it can and cannot touch.
One site, 8–12 weeks, a fixed price and a benchmark defined before we start.
The policy is the same everywhere; the thresholds, zones and acceptable interruptions are calibrated per site during onboarding.
Mixed aisles where pickers and AMRs negotiate the same lane. The robot learns when to hold back and when to keep moving, so fewer runs end in a manual override.
Corridors and wards where interrupting the wrong person at the wrong moment is the real failure mode. The layer reads readiness before the robot ever speaks.
Approach that reads as helpful rather than intrusive — and a clean disengage the moment the answer is no, without the robot trailing the customer down the aisle.
Embodiments people read socially, where posture, timing and voice carry as much weight as the path. One policy travels across every body you deploy.
Every engagement starts as a paid pilot with a benchmark agreed before the work begins — and you keep that written benchmark whether or not you licence anything. Prices below are list ranges; scope sets the final figure.
IntSense builds the human interaction layer for physical AI.
We’re hiring for the human interaction layer for physical AI. Send your CV and portfolio.
Human–robot interaction: perception, behaviour and on-robot integration.
ApplyCompact speech and vision models that run on the robot itself.
ApplyAnother role in mind? Write to hello@intsense.ai.