About the role

Robotics Applications Engineer / Technician Robotics | Linux | Python | ROS | Field Service | Technical Troubleshooting
Location: Ann Arbor, MI Job Type: Contract-to-Direct, Full-Time Work Arrangement: Field-Based / On-Site / 1st Shift and 2nd Shift Openings
The Opportunity: We are seeking a Robotics Applications Engineer / Technician to support the deployment, troubleshooting, and operation of advanced robotic systems. This is a hands-on technical role for someone who enjoys working with robots, diagnosing complex problems, and solving issues across hardware, software, and networking. The ideal candidate may come from a traditional robotics/automation background, but we're also interested in candidates with robotics projects, drone programming, college engineering projects, robotics competitions, or strong personal projects.
What You'll Do: Participate in intensive training covering robot kinematics, electrical controls, mechanical systems, and proprietary robotics software. Develop expertise in robotic system assembly, disassembly, troubleshooting, and software systems. Provide Tier 1 and Tier 2 technical support for robotic hardware and software. Perform root-cause analysis using diagnostic logs, system telemetry, test protocols, and system data. Troubleshoot issues involving robots, sensors, actuators, embedded computers, software, communications, and networking. Work extensively in Linux-based environments to diagnose system problems. Use Python for scripting, diagnostics, troubleshooting, and automation. Work with ROS 1 and/or ROS 2.Provide R&D with detailed bug reports, reproduction steps, diagnostic logs, and operational information. Work with engineering teams to reproduce and resolve field issues. Document failure modes, root causes, workarounds, and troubleshooting procedures. Maintain technical knowledge bases and deployment documentation. Maintain local service tools, diagnostic equipment, and spare-parts inventory. Support field deployments and customer-facing technical activities as required.
What We're Looking For: 2+ years of experience in robotics, technical support, field service, applications engineering, automation, or complex electromechanical systems. Bachelor's degree in Robotics, Mechatronics, Electrical Engineering, Computer Science, Computer Engineering, Mechanical Engineering, or related field preferred. Strong Linux experience. Experience with Python. Experience with ROS 1 and/or ROS 2.Basic understanding of computer networking and network troubleshooting. Understanding of robotics, sensors, actuators, and electromechanical systems. Experience troubleshooting hardware and software issues using logs and diagnostic information. Familiarity with ticketing, incident-management, or bug-tracking systems. Strong written and verbal communication skills. Ability to clearly communicate technical issues between end users and engineering/R&D teams. C++ is a Plus — Not RequiredC++ experience is helpful, but our primary focus is on candidates with strong Python, Linux, and ROS skills.
The Ideal Candidate: We're looking for someone who: Enjoys figuring out why something isn't working. Can troubleshoot across both hardware and software. Is comfortable working in Linux. Has hands-on robotics experience or significant robotics-related projects. Can work independently while knowing when to involve R&D.Communicates technical problems clearly and documents solutions thoroughly. Enjoys working in a hands-on, field-oriented environment. Wants to develop into a robotics subject matter expert. Apply TodayIf you have a strong technical foundation and a passion for robotics, Linux, Python, ROS, and solving difficult technical problems, we'd like to hear from you. Professional robotics experience isn't the only path into this role. If you've built robots, programmed drones, worked with ROS, completed robotics projects in college or high school, or have significant personal robotics experience, we encourage you to apply.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this