About this opportunity
AMR Project Engineer Discover your impact with KUKA
KUKA offers an enormous spectrum of possibilities to advance your career, live your passions and unlock your potential. We´re one of the world's leading automation specialists, offering global opportunities in areas such as robotics, automation, logistics, software solutions and electronics. If you´re a go-getter, a visionary with bold ambitions and believer in collaboration and mutual respect, then you're poised for success here at KUKA. Responsibilities Make an impact Responsible for the installation, commissioning, integration, and acceptance of AMR and related systems.
Lead on-site project delivery, provide on-site technical support, and resolve technical issues that arise during system operation.
Provide training to customers on the operation and maintenance of the AMR system, ensuring they can independently run and maintain the system.
Conduct regular inspections and maintenance of the system, identify and resolve potential issues, enhancing system efficiency and stability.
Manage project documentation, collect, compile, and output relevant documents, and conduct regular project summaries and knowledge sharing.
Communicate with customers, understand their needs, gather feedback, and provide suggestions for improving AMR product quality.
Application Requirements What you need to succeed University degree in engineering,
Basic understanding of AGV/AMR systems,
Strong proficiency in English (both written and spoken) is required, and Chinese language skills are considered an advantage,
Field experience in automation, AGV/AMR preferred,
Basic programming skills required,
Experience in AMR related software development,
Familiar with C/C++/Python/JAVA, TCP/IP/UDP, ROS/ROS2, Docker, SQL, Git, and CMake,
Strong initiative, with a sense of project delivery management, promoting and advancing project delivery and acceptance,
Good communication skills and a spirit of teamwork,
The role requires frequent international travel; candidates are asked to consider this when applying.
Job details
How this role compares
Computed from every other active Controls Engineering role in our database, not just this employer's listings.
We currently track 496 comparable Controls Engineering roles across 18 employers.
Salary context
36 of 496 peers report a salary range (USD, annualized)
Peers share this role's job function. This posting doesn't list a seniority level, so peers aren't narrowed by seniority either -- the range below may span more levels than usual.
Where these roles are based
Top locations among the 496 comparable roles
+ 39 more countries
Seniority mix
139 of 496 peers have a known seniority level
Similar opportunities
The closest matches from our peer group, ranked by how similar they are, not how well you'd qualify for them -- treat this as market context, not a guaranteed shortlist; a weak match is labeled as one below.
Matched on job function only -- seniority, specialty, and location weren't confirmed as aligned.
Notify me about similar jobs
Get an email when we spot other openings like this one – same job function, comparable seniority, roles you'd actually want to see.
Or follow every new Controls Engineering job, narrowed by PLC/SCADA platform, location and employer: set up a job alert.
How we calculate "similar"
No black box, no LLM guesswork: a deterministic score built from four normalized attributes. Here's this role's own peer group at different match levels, so you can see the mechanism, not just the result.
Every comparison starts from the same 100-point budget: 25 for working in the same function, 40 for the same therapeutic area, 20 for the same or adjacent seniority, 15 for the same country. A dimension we can't confirm on both sides contributes nothing, never a guess, never a free pass.
0 points, never a partial guess. A role we know almost nothing about beyond its function bottoms out at 25%; it never inflates to 100% just because there's little to compare against. Seniority uses a defined ladder (Associate → Manager → Associate Director → Senior → Principal → Director → Senior Director → Executive/VP) so "Director" and "Senior Director" count as adjacent, but "Director" and "Executive/VP" do not.