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
Neura Robotics Gmbh

Software Support L2 Engineer – Robotic Hands (human)

  • Seen live on Neura Robotics Gmbh's site today
  • Mid level
Pay
Not stated
Location
Munich
Open for
2 days
First seen
Nov 3, 2026
Apply on Neura Robotics Gmbh's site (opens in a new tab)

Posting record

No flags

Open 2 days

The posting's record, oldest first
  1. Ghostless first sees this listing
  2. 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.

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

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

Your mission & challenges

BU-Hands builds the robotic hands for our humanoid 4NE-1 and our cognitive robots, and delivers them to internal robot teams and external customers. As our hands move from prototypes into series production, you take over the firmware, SDK and communication issues that 1st level service cannot solve. You reproduce the problem, find the root cause and either fix it yourself or hand it to our developers with a clear reproducer. Your goal: the same issue never reaches you twice.

  • Escalation ownership: Own tickets escalated from 1st level service, RMA and field teams. Triage them, reproduce them on a bench hand and close them or route them to development.
  • Embedded troubleshooting: Debug firmware on ARM Cortex-M MCUs with JTAG/SWD, read crash dumps, fault registers and RTOS traces, and check motor control, sensor readout, boot and firmware update behaviour.
  • SDK & integration support: Support internal robot teams and customers integrating our hands through our SDK, including reviewing their code and configuration.
  • Communication analysis: Analyse traffic between hand and robot to separate wiring, timing and protocol faults.
  • Fault routing: Work with test engineering and the RMA bench to decide whether a fault is electrical, mechanical or software, and route it to the right owner.
  • Fixes: Write small firmware and SDK fixes with tests and code review, and verify them in the field.
  • Diagnostic tooling: Build tools and scripts for log collection, health checks and firmware flashing that 1st level can run without you.
  • Knowledge & feedback loop: Turn every solved issue into a known-issue entry, troubleshooting guide or release note, and report recurring faults to product management with numbers.
  • On-site support: Travel to customer sites and NEURA locations when a remote session cannot solve the problem.

What we can look forward to

What you bring

  • Education: A degree in Computer Science, Electrical Engineering, Mechatronics or a related field.
  • Firmware experience: 3+ years writing or supporting C/C++ firmware on ARM Cortex-M or similar MCUs, including RTOS-based systems.
  • Structured troubleshooting: You can walk us through hypothesis, test and evidence on a root cause others missed.
  • Lab tools: Hands-on with JTAG/SWD debuggers, oscilloscopes, logic analysers and Wireshark, and able to read schematics well enough to probe a board.
  • Developer support: Experience supporting developers who use your libraries or APIs: reproducing their setup, reading their code and explaining the fix.
  • Tooling: Comfortable on the Linux command line, with Python for test and log analysis scripts, and Git.
  • Protocols: Working knowledge of at least one fieldbus or real-time protocol, such as EtherCAT, CAN/CAN-FD or Ethernet-based protocols.
  • Communication: Clear written reports and a calm manner on calls with frustrated users.
  • Languages: Very good English skills; German is a plus.

Nice to have

  • ROS 2: Experience with ROS 2 and robot-side integration of grippers or hands.
  • Industrial Ethernet & embedded Linux: Previous work with industrial Ethernet stacks or embedded Linux.
  • Motor control: Understanding of BLDC motor control and sensor data paths, to tell a control bug from a hardware fault.
  • Support processes & safety: Exposure to support processes (ticketing, SLAs, known-error databases) and to functional safety (ISO 13849, IEC 61508).

Something wrong with this posting?