Bewirb dich für Software Engineer, Working Student (m/f/d)

Software EngineeringMunich (preferred) / Remote (Germany)Working StudentNur auf Englisch verfügbar

Vollständiger Name*

E-Mail*

Telefon

Standort*

LinkedIn, GitHub oder Portfolio

Lebenslauf*Zum Hochladen klicken

Nur PDF, bis zu 10 MB.

How many hours per week are you available?*

Please rate the following skills to give us a good first impression.

Honest ratings help us more than perfect ones. Nobody is strong at everything.

Structuring a Python project: packaging, dependencies, modular code*

Never done it

Tried it a few times

Capable with guidance / AI

Independent and confident

Expert / Mentor to others

Building REST APIs (FastAPI or similar)*

Never done it

Tried it a few times

Capable with guidance / AI

Independent and confident

Expert / Mentor to others

Working with relational databases (PostgreSQL, SQL, ORMs)*

Never done it

Tried it a few times

Capable with guidance / AI

Independent and confident

Expert / Mentor to others

Docker, CI/CD pipelines, and deployment*

Never done it

Tried it a few times

Capable with guidance / AI

Independent and confident

Expert / Mentor to others

Git and collaborative workflows (branches, pull requests, reviews)*

Never done it

Tried it a few times

Capable with guidance / AI

Independent and confident

Expert / Mentor to others

Writing automated tests (pytest or similar)*

Never done it

Tried it a few times

Capable with guidance / AI

Independent and confident

Expert / Mentor to others

A few questions with no right answers.

We read every word of these. Personal and specific beats polished.

Tell us about the messiest technical problem you have personally dealt with, in a project, thesis, or job. What made it hard, what did you try that did not work, and how did it end?*

We care about the dead ends as much as the solution. 150 to 300 words is plenty.

0 / 2.000

Think of an API or backend service you have used or built, one you have a real opinion about. What is one design decision its authors made that you think was right, and one you would have done differently? Be concrete about what the decision was and why it matters.*

Could be a public API you integrated, a library, or something from your own project. We care about the reasoning, not whether we agree.

0 / 2.000

Imagine it is your third week at Aqarios. It is Friday afternoon, nothing is assigned to you, and you have full access to our codebase, docs, and team. What do you actually do with those four hours? Be honest.*

There is no correct answer. Poking around the codebase, fixing a small annoyance, and asking people questions are all legitimate uses of a Friday.

0 / 2.000

Frühester Starttermin

Wie bist du auf uns aufmerksam geworden?

Ich stimme zu, dass Aqarios diese Angaben speichern darf, um mich für eine Stelle zu berücksichtigen.*

Ein Mensch prüft jede Bewerbung. Wir lehnen niemals automatisiert ab. Unseren Datenschutzhinweis lesen

Fülle die Pflichtfelder aus, um abzusenden.