Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Slip Robotics

Robotics Hardware Integration Engineer

  • Seen live on Slip Robotics' site 3 days ago
  • Senior
  • Remote
Pay
Not stated
Location
Atlanta, Georgia, United States
Open for
10+ days
First seen
Oct 25, 2026
Apply on Slip Robotics' site (opens in a new tab)

Posting record

No flags

Open 10+ days

The posting's record, oldest first
  1. Slip Robotics' site dates the posting
  2. Ghostless first sees this listing
  3. Last checked: still up
How we know

It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.

Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Slip Robotics, so its true age is longer.

Last checked Nov 1, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What it asks of you

5+ years of experience
“5+ years of professional experience in hardware-software integration for robotic systems at a robotics, autonomous vehicle, or industrial automation company” (quoted from the posting)

What the posting discloses

Not stated: Pay, real vacancy, AI screening.

Why these three

Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the role

Slip Robotics is transforming freight logistics with autonomous robotic systems that load and unload trailers faster, safer, and more reliably than traditional methods. Our robots operate in demanding real-world environments alongside people and heavy cargo every day. We are a small, high-impact team based in Atlanta building products that are already deployed in production.

The Role

We are looking for a Robotics Hardware Integration Engineer to own the interface between software and hardware on our robot platforms. This means sensor drivers, motor controllers, embedded communication buses, power management interfaces, and the low-level software that makes the physical robot work. You will be the person who makes sure software commands translate into reliable real-world motion and that sensor data flows cleanly into the perception and navigation stacks.

This is not a pure embedded firmware role and not a pure software role—it sits at the intersection. We need someone who has worked at a robotics company integrating sensors, actuators, and compute hardware into a cohesive system. You should be equally comfortable reading a datasheet, writing a Linux device driver, and debugging a CAN bus trace.

Key Responsibilities

  • Develop and maintain drivers for sensors (LiDAR, cameras, IMUs, encoders) and actuators (motor controllers, hydraulics, pneumatics) on Linux-based robot platforms
  • Own the communication layer between onboard compute and hardware subsystems (CAN bus, EtherCAT, serial, I2C/SPI)
  • Design and implement hardware abstraction layers that give upstream software teams clean, reliable interfaces
  • Integrate new sensors and hardware components as the robot platform evolves, including requirements definition, component selection, bring-up, calibration, and validation
  • Monitor and manage robot system health: power, thermals, hardware diagnostics, and fault handling
  • Build and maintain AWS IoT Greengrass components for fleet-level device management, OTA updates, and cloud telemetry
  • Collaborate with mechanical and electrical engineers on hardware design reviews to ensure manufacturability and software compatibility
  • Manage Linux configurations and setup for robotics software host machines
  • Develop and maintain CI/CD processes for hardware-interfacing software, including hardware-in-the-loop testing where appropriate
  • Support field-deployed robots by diagnosing and resolving hardware-software integration issues

Requirements

  • 5+ years of professional experience in hardware-software integration for robotic systems at a robotics, autonomous vehicle, or industrial automation company
  • Strong proficiency in C++ and Python on Linux platforms
  • Hands-on experience writing and maintaining device drivers and sensor interfaces for real robot hardware
  • Working knowledge of communication protocols: CAN, EtherCAT, serial (RS-232/485), I2C, SPI
  • Experience with ROS or ROS 2 for hardware interface nodes and system integration
  • Familiarity with AWS IoT Core, Greengrass, or similar edge-cloud platforms for fleet device management
  • Ability to read schematics and datasheets and collaborate effectively with electrical engineers
  • Experience debugging hardware issues using oscilloscopes, logic analyzers, and protocol analyzers
  • Strong communication skills and ability to work across software, electrical, and mechanical teams

Benefits

  • Competitive salary and equity in an early-stage robotics company
  • Comprehensive benefits including health, dental, and vision
  • Permissive time off policy
  • A small team where your work has direct, visible impact on shipped products
  • The chance to work on robots that are operating in production today—not a research project

Something wrong with this posting?