Apply for Backend Engineer, Working Student

EngineeringMunich (preferred) / Remote (Germany)Working Student

Full name*

Email*

Phone

Location*

LinkedIn, GitHub, or portfolio

CV / résumé*Click to upload

PDF or Word document, up to 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

Earliest start date

How did you hear about us?

I agree that Aqarios may store this information to consider me for a role.*

A person reviews every application. We never auto-reject. Read our data protection notice

Fill in the required fields to submit.