About this opportunity
The CTO Product Development team supporting IAS seeks to hire an R&D Controls Software Engineer(m/w/d). Responsibilities are development, support, and delivery of control software for automated systems and material handling products.
We offer:
Benefits of an International MDax Group (KION Group)
Plenty of room for creativity in a rapidly growing company
Flexible and mobile working
Individual support and development
Employee discounts
Tasks and Qualifications:
What You Will do in This Role:
Analyze customer requirements, user stories, and project specifications to define software and controls solutions.
Design, develop, test, and optimize PLC and control system software for industrial automation applications.
Execute functional, integration, stability, and scalability testing to ensure product reliability and performance.
Troubleshoot and resolve software, controls, networking, and system integration issues identified internally or by customers.
Collaborate with cross-functional engineering, product development, and field teams throughout the product lifecycle.
Create and maintain technical documentation, including software architecture, system design, and user guidance.
Provide technical expertise and support to engineering teams, field resources, and business partners.
Mentor and support junior engineers in software engineering principles, controls development, and PLC programming practices.
Utilize diagnostic, simulation, and network analysis tools to validate system performance and identify root causes.
Ensure software quality, maintainability, and compliance with engineering standards, best practices, and development processes.
What We’re Looking For:
Minimum 5 years of experience in controls software engineering.
Experience working within a team environment and ability to take a lead role in controls system development, and support.
Experience in PLC programming with a software focus, specifically in Siemens or Rockwell, is required.
Experience with at least one high-level programming language (C#, or Python).
Experience developing and maintaining unit and integration tests.
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.
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.