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
Humanarchive

Firmware Engineer

  • Seen live on Humanarchive's site today
  • Mid level
Pay
CN¥80k to CN¥100k a year
Location
China
Open for
11+ days
First seen
Oct 24, 2026

Posting record

No flags

Open 11+ days

The posting's record, oldest first
  1. Humanarchive's 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 Humanarchive, so its true age is longer.

Last checked Nov 4, 2026.

How well do you match?

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

Upload your resume

What the posting discloses

Pay
CN¥80k to CN¥100k a year

Not stated: 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.

Skills mentioned

About the role

About Human Archive

Human Archive is a research lab backed by Y Combinator focused on modeling human embodied intelligence.

Humans are the most sophisticated biological systems we have ever observed, yet we still do not fully understand ourselves. Research into human physical intelligence — including the human hand, proprioception, and vision — remains largely unsolved. Our mission is to recover human embodied intelligence as a learned model. To achieve this, we build custom hardware products, deploy them globally at scale, and publish research. Today, our data is used for robotics and world modeling, but the broader opportunity is advancing scientific research into intelligence itself.

Founded by Stanford and UC Berkeley researchers, we are lean, deeply technical, and operate at extreme speed, taking on unglamorous and conventionally impossible problems that directly unlock step-function gains in model capability.

The deployment of capable humanoids at scale will permanently redefine human labor. Undesirable physical work will disappear, and human effort will shift toward a new era of abundant creativity.

We are building the infrastructure to accelerate that transition by assembling the Human Archive mafia. You will own meaningful systems from day one and see your work directly impact model capabilities. This is a once-in-a-generation inflection point. If you want to help reshape physical labor and work on problems that matter at civilizational scale, join us.

What you'll work on

We're hiring a firmware engineer to own the embedded software stack on our wearable capture hardware. Close-to-the-metal work at the intersection of high-bandwidth sensor data, precise timing, and constrained-power embedded compute. You read schematics, debug buses, and know when the bug is in firmware versus when it's in hardware.

System architecture

  • Firmware architecture on embedded Linux on ARM
  • System state machines: boot, capture, idle, fault recovery
  • Power management states and low-power transitions

Sensor integration and timing

  • Drivers for cameras, IMUs, microphones, environmental sensors
  • Sub-millisecond cross-sensor synchronization
  • Hardware-level timestamping infrastructure
  • Real-time sensor data alignment
  • Lightweight on-device fusion for orientation and worn-state estimation (Kalman variants)

Data pipeline

  • Multi-stream concurrent capture
  • Hardware video encoder pipelines
  • High-throughput storage writes
  • Industry-standard delivery format packing

Connectivity and fleet operations

  • Device-to-backend telemetry (battery, storage, session state, error events)
  • Secure OTA firmware updates with signed images and rollback protection
  • Remote configuration and fleet management commands
  • Communication protocols for device-cloud messaging (MQTT-over-TLS, HTTPS, WebSockets)

Hardware / software bring-up

  • Firmware-side board bring-up alongside electrical engineers
  • Validate hardware interfaces (I²C, SPI, USB, MIPI)
  • Diagnose timing, power sequencing, and communication faults

Required technical experience

  • Strong C/C++ for embedded systems on ARM
  • Python for testing, tooling, and automation
  • Camera driver experience (V4L2 or equivalent)
  • Deep familiarity with embedded interfaces: MIPI CSI-2, I²C, SPI, USB, interrupts
  • Comfortable reading schematics and datasheets

Systems and concurrency

  • Interrupts, race conditions, memory constraints, real-time scheduling
  • RTOS concepts and multi-threaded embedded environments

Strong plus

  • Qualcomm, NXP, or Ambarella BSP experience
  • SerDes driver integration
  • Hardware H.264 / H.265 encoder pipelines
  • Precise timing and synchronization (PTP, IEEE 1588)
  • High-bandwidth data acquisition
  • Sensor fusion and Kalman filter implementation
  • OTA infrastructure for deployed fleets
  • IoT telemetry stacks (MQTT, AWS IoT, Azure IoT Hub, or similar)
  • ROS, MCAP, or Foxglove

About this role Deep systems work. Long hours in the lab during board bring-up. Drivers nobody has written for the silicon you're working with. Firmware that runs unattended on real users for full shifts — and gets updated remotely without ever recalling a device.

Something wrong with this posting?