Build where research meets industry.
Work in a small team on ambitious AI problems and turn research into things that work in practice.
What makes a Solutioneer?
-
You build.
You don’t wait for someone to turn the problem into a ticket.
You’ve built things before because you wanted them to exist.
-
You go deep.
AI isn’t just an API call.
Late Bachelor’s or Master’s in computer science, information systems, business informatics or something close to it. And a habit of looking beneath the abstraction.
-
You scope.
Ambiguity doesn’t scare you.
You turn a messy problem into something concrete enough to build, then defend the decisions that got it there.
-
You own.
You’re responsible for what happens next.
Not just implementation. Decisions, trade-offs and outcomes.
Real work, real responsibility,
-
You don’t build alone.
Which is where the rest of the team comes in.
Building is a team sport.
You own a piece of the work. You don’t do it on your own.
Small teams.
Close enough to challenge each other.
You sit with the people making the decisions, including the ones who disagree with you.
Serious collaboration.
Think together. Build together. Get better together.
The academics on the team (HPI, MIT, University of Münster) sit in the same conversations as everyone else. You learn while solving the problem, not in a seminar about it.
Not just an offsite.
Time to think deeply, build together, challenge ideas, eat together and figure out where Launch Labs goes next.
Two days of arguing about approaches, showing each other what we built, and deciding what Launch Labs takes on next.
What stands out most to me is the atmosphere. There’s a lot of trust, people are open with each other, and you have real freedom in how you work.
You’re trusted with real responsibility, but you’re never left alone with it.
Meet the team.
The Solutioneers and the academics who mentor them, side by side, because that is how the work runs.
Could this be you?
- Can you turn an ambiguous problem into something concrete?
- Do you understand what’s happening beneath the abstraction?
- Have you built something because you wanted it to exist?
- Do you want responsibility for the outcome?
- Do you want to build with people who will challenge you?
Then we should
talk.
No application window and no form. Either way you end up in a conversation with a person.
Send what you’ve built
A repo, a system, something you made because you wanted it to exist. Add a line on what you want to own next. That tells us more than a CV does.
info@launch-labs.ai