Joined Robotics+Mechatronics Engineer

Location: Lyngby, Denmark — Full time, from the office (hybrid to be agreed)

About us

At Erletek we're building construction robots for a smarter, stronger and more sustainable construction industry. We're looking for two ambitious engineers to join our robotics team — one on the hardware/mechatronics side, one on the robotics software side — as we advance our concrete printing robot from prototype toward field-ready product.

You'll contribute in a fast-paced, collaborative small team. Architecture and design decisions are made jointly with the CTO, but you'll be expected to own implementation, testing, and troubleshooting of your area end-to-end — validated against the realities of real construction sites, not just simulation.

Role A: Mechatronics - Embedded Systems Engineer

You'll own the hardware that makes the robot work: motor drives, sensors, actuators, and the embedded/power systems tying them together — feeding directly into the ROS 2 stack. Expect a mix of designing new mechatronic subsystems and reworking existing ones as the robot matures.

Responsibilities

• Develop and maintain embedded systems (hardware + firmware): sensor signal processing, actuator control

• Design custom PCBs for new/upgraded subsystems, with firmware and clear interface documentation

• Integrate and tune motor drives and actuators (AC motor drives/VFDs, steppers, and similar), closing control loops using encoder or other feedback

• Work with communication protocols across the stack: UART, I2C, Modbus/RS-485, CAN, and GPIO-level signaling

• Support power system design and debugging (AC/DC distribution, power budgeting across subsystems)

• Improve the layout, enclosures, and cable management of the robot's electronics over time, for better serviceability, diagnosability, and safety (e.g. E-stop circuits, MCBs, indicator lights)

• Troubleshoot electrical and firmware issues on physical hardware, both on the bench and in the field

• Collaborate with the robotics software team so your subsystems integrate cleanly with the ROS 2 hardware interfaces and control layer

• Write clear interface specs and communicate your designs and findings to technical colleagues

Qualifications — Essential

1. Basic Linux experience: have you written and run programs on Linux, more specifically Ubuntu?

2. Embedded firmware experience: have you written C/C++ firmware for a microcontroller (Arduino, STM32, or similar)?

3. Version control experience: Git and GitHub — have you submitted and/or reviewed pull requests? Have you ever had your code reviewed by another engineer?

4. Electronics fundamentals: can you read and draft a schematic, wire up sensors/actuators/drives, and debug a circuit with a multimeter (oscilloscope a plus)?

5. Some experience with PCB design/schematic capture (e.g. KiCad, Altium, Eagle) — you'll be designing a small custom board early on.

6. Experience with at least one serial/industrial communication protocol: UART, I2C, SPI, Modbus/RS-485, or CAN.

7. Some exposure to motor or actuator control (steppers, DC/AC motor drives, VFDs, or similar).

8. Experience debugging hardware running outside of your own development machine (i.e. on a physical device/robot, not just in simulation).

9. Comfort with problem-solving on technical, partially undefined tasks.

10. Capacity to take ownership of execution while collaborating closely on design.

Additional things we would love to see

1. Work experience in (mobile) robotics or hardware startups outside of academia.

2. Familiarity with Linux communication protocol libraries or device drivers.

3. Experience with PlatformIO or the Arduino ecosystem.

4. Experience with industrial motor drives over Modbus/RS-485 or CAN.

5. Familiarity with ROS 2 — have you written a ROS 2 node or launch file, even a basic one? (Not required, but helps you see how your subsystem fits into the larger robot.)

6. Experience configuring or tuning industrial Variable Frequency Drives (VFDs) or similar motor controllers.

7. Familiarity with electrical safety practices around AC power (RCDs, MCBs, emergency-stop circuits).

Role B: Robotics Engineer (Software)

You'll contribute to the core software that makes the robot go. We are working on improving the entire stack, so there are many different challenges to tackle depending on your expertise and desire to explore — perception and navigation, the high-level task planning module, and the auxiliary software that supports our operations.

Responsibilities

• Develop robust localization and state estimation capabilities, fusing GNSS, INS, and other odometry sources to perform reliably in construction environments.

• Design and implement camera-based, lidar-based perception algorithms tailored to our operations, based on a sensor suite that you will help select.

• Extend the robot's mission/task orchestration to support more versatile operations.

• Communicate your designs and implementation to other technical colleagues.

• Test and troubleshoot the different components of the robot both in simulation and real life.

Qualifications — Essential

1. Basic Linux experience: have you written and run programs on Linux, more specifically Ubuntu?

2. Minimum of one year working with robotic or autonomous systems.

   1. Experience debugging on real systems running outside of the developer's computer

3. Experience with ROS 2; have you ever written a ROS 2 node or a launch file?

4. Some experience with computer vision, navigation and/or control software.

5. Good programming skills in Python and C++

   1. Experience with object-oriented programming

6. Experience in problem-solving on technical, partially undefined tasks.

7. Capacity to take ownership of execution while collaborating closely on design.

Additional things we would love to see

1. Work experience in (mobile) robotics outside of academia.

2. Experience with long-lived projects: have you worked on a project that's spanned over 1 year?

3. Larger (robotics) programming experience: have you designed something beyond a single-file program? Are you familiar with design patterns and (robotics) software architectures? Have you used/integrated open source software?

4. ROS 2 expertise: have you worked with Nav2, Behavior Trees?

5. Development environment experience: have you worked with Docker, Foxglove, Git and GitHub? Have you submitted and/or reviewed pull requests?

Company values

At Erletek, many different skills come together, so we look for people who share how we work, not just what they can build:

• Transparent, honest communication — everyone should be free to voice their view on work topics without fear of judgment or reprisal.

• Trust — we believe in autonomy, and trust each other to self-manage and work at the rhythm that suits us best.

• Sense of belonging — we want everyone to feel part of the effort, which is why we prioritize regular social gatherings outside of work.

• Ownership and commitment — work here often demands more than expected; we look for people who stay committed to seeing things through, because real success lies at completion.

• Personal development — we aim to stay flexible and open, tailoring tasks to each person's own growth goals.

Practicalities

1. Full time - Working from the office. Hybrid work to be agreed with us.

Application

Send an email with your CV attached and one of the following subjects:

• "Robotics Engineer Application - <your name>" (for Role B)

• "Mechatronics Engineer Application - <your name>" (for Role A)

Questions?

Contact Jonathan