There’s no single reason why everyone likes working here.

There are actually quite a few.

Very attractive home office model
Flexible working hours
Individual further training
Flat hierarchies
Company pension plan and worldwide accident insurance
Free & delicious snacks, drinks and fruits
Great team and company events
Large sun terrace

Back to career

A day with an INNO …

Software Developer

08:03 O'CLOCK

Daily Stand-Up.

Java Full-Stack Development.

Web frontends with ReactJS, Redux, Typescript. Focus on high-performance display of large amounts of data in the browser.

Big Data backend development.

Database development (Elasticsearch, Minio).

Designing complex system components in a team.

Independent implementation of tickets previously created in the team.

Code reviews to improve code styles – own and/or those of colleagues.

Direct customer contact: not always, but more and more often, at INNO or at the customer – fascinating to see who we code for, what it is all about and which solution is really successful.

Integration into QA: direct and competent technical feedback.

“Developers Workshop” developer exchange: a great opportunity to gain insights into other technologies as well.

Support interns in their programming tasks, explain new technologies, review code.

17:06 O'CLOCK

Technical Consultant

08:03 O'CLOCK

8:03: Check in and off we go. First grab a cup of coffee and check yesterday’s emails.

8:30: Daily team Stand-Up, currently there are no blockers to complain about, so today it’s fast.

8:35: Set user story “in Progress” for the new visualisation in JIRA, start on a new feature branch.

10:45: A colleague in the kitchen asked for help with a rebase, after a few calls from Git (“reset –hard”), the Jenkins build is green again.

12:00: Lunch with colleagues at an Italian restaurant.

12:45: Back at work. During the lunch break, a critical bug report was received from the QA department. Fortunately, it’s locally reproducible in a unit test. Again a typical off-by-one-error and quickly fixed.

1:00: Concept meeting to improve the failure resistance of our systems. Depending on the location, it may take time for someone to see what’s going on, so the systems must run as autonomously as possible.

3:00: Continue with the visualisation story. Had good ideas at lunch on how to optimise data retrieval.

5:00: Time to leave. Walk a lap around the castle lake with colleagues – and jump in to cool off in warm weather.

17:00 O'CLOCK

Software Architect

Software Architect

08:03 O'CLOCK

Read emails.

Check meetings.

Drink tea.

Test systems, check that everything is still running.

Answer colleagues’ questions from the previous day about Mattermost.

A little programming.

Daily Stand-Up.

Answer colleagues’ questions about work packages and make design decisions.

Check project progress via JIRA.

Meet responsibility as team contact person: Look at developer’s work package and provide a short review.

Answer questions from colleagues on other projects or QK.

Lunch.

Write JIRA tickets for upcoming features.

Some meeting.

Technical review and testing of new functions.

Create concepts for new features.

Programme a little bit more. Thank God! Don’t get out of practice, because that’s what makes it so much fun.

Time to leave.

17:06 O'CLOCK

Project Leader

08:03 O'CLOCK

Morning starts with the ‘Daily-Stand-up’.

Coffee Break: discuss some topics with my collegues.

Clarify costumer questions and structure the team.

Sprint planning.

Yes it’s Tuesday: Participate at developer workshop weekly.

Backlog Refinement.

Customer Demo.

Retrospective.

Coding.

Working on my OKRs to reach my targets.

Yes it’s Friday: Afterwork at 4:00 p.m. with my collegues.

Yes it’s Weekend: No work for today.

17:06 O'CLOCK

Ready?

Find the right job or apply on your own initiative.

Job offers

Unsolicited application