Intern / Working Student (m/f/d)

You join a team building the simulation, optimization and agent infrastructure behind adago's planning products, and you take real work packages from the start. Depending on where your strengths lie, that might mean extending the simulation engine, implementing and testing an optimization routine, building the data pipeline that feeds a model, or working on the agent tooling around it. You take responsibility for individual components and develop them largely independently, with a senior engineer close by rather than looking over your shoulder.

We are looking for people who can do both. Reading a paper and reasoning carefully about a stochastic model or an optimization formulation is necessary here, but it is not sufficient. The work only counts once it is code that runs, survives review, and does not fall over the first time somebody else touches it. If you enjoy the point where a mathematical idea has to become a working system, this is the right place. If you would rather stay on either side of that line on its own, it probably is not.

Most people start with an internship, move into a working student role alongside their studies, and where there is a good fit finish with a Bachelor's or Master's thesis built on real adago work. We run close cooperations with several professors, particularly at the University of Mannheim, so a thesis here plugs directly into active research questions we are working on rather than sitting to one side of the company. Several of our engineers joined exactly this way, and it remains the most common route into a full-time role with us.

Depending on your interests and background, you lean either toward the optimization side, working alongside our AI Engineers on the mathematical and simulation backbone, or toward the applied side, closer to what our Forward-Deployed Engineers do, getting these systems working against real client complexity. You do not need to know which one you want before you start.

• Currently enrolled in Mathematics, Data Science, Computer Science, Physics or a related field, ideally past the fourth semester of your Bachelor's or in your Master's.
• You can understand complex mathematical models and objects, and you can build them into software. Both halves matter, and the second is the one most people underrate.
• You care about how software is put together, not only whether it gives the right number. Tests, structure and readable code are part of the work, not an afterthought.
• Ideally some exposure, even if only from coursework, to optimization, simulation, time series, or supervised and unsupervised learning. A seminar project counts.
• Curiosity, and the willingness to say out loud when you do not understand something. In a team this size that is far more useful than quietly pretending otherwise.
• We care less about which languages you have already used than about whether you can pick up whatever a problem needs. Most of our work happens to be in Python.

8 to 20 hours per week during the semester, with more possible during semester breaks. Internships run flexibly between two and six months. Compensation is competitive and discussed individually based on role and stage.