Tech ways of working
We see software development and technology as one of our core competencies.
We implement microservices for otto.de, Germany's largest online store and marketplace, which is constantly changing and evolving in the fast-moving e-commerce market. We develop concepts, designs and features that make shopping easier for our customers and turn it into an experience. These are our tech challenges.
We build Self Contained Systems that are continuously deployed live through our CD pipeline. We are responsible for our part of the product - technically and also for the operation in AWS. Technical decisions are made by us and not by managers. We also shape the nature of our collaboration ourselves and find new ways together in diverse teams. For us, that is autonomy.
This means both iteratively developing solutions and promoting cultural change with the goal of reacting quickly and flexibly to changing market conditions. Our work is self-organized and cross-functional with Scrum and the methods of agile software development such as Test-Driven-Development (TDD), Pair-Programming or Continuous Delivery.
Our high development drive leads to a regular reflection of our behavior and work results. We exchange ideas at (international) professional conferences like Code Talks, GOTO Berlin, JAX, DEVOXX, internal professional events, hackathons and tech talks or meet-ups.
How we describe ourselves? Technology-oriented and sometimes nerdy - in a positive sense. When the daily madness gets out of hand, we face it together with humor. At the same time, we enjoy a high degree of autonomy and freedom for our own ideas - this is also reflected in the flexible working hours. Free choice of hardware and cross-departmental co-determination are some of the many other advantages - as is the choice of team mascots. That's our culture.
The choice of tools and technologies are often team decisions, and a lot of value is placed on them. The diversity of our roles results in a highly heterogeneous use of technology, which varies from team to team. We like to experiment with new technologies and programming languages and weigh the benefits for us.
## Philosophy
agile | xp | tdd | devops | kanban | scrum | continuous-integration | continuous-delivery | continuous-deployment | continuous-everything | responsive-design | microservices | event-sourcing | self-contained-systems
## Programming Languages
java | scala | clojure | javascript | swift | python | kotlin | elixir | go | c | haskell
## Frameworks & Tools
spring-boot | edison | akka | finatra | phoenix | swagger | dropwizard | react | redux | vue.js | vaadin | JavaEE/JakartaEE | eclipse microprofile | nodeJS | kafka
## Mobile
google-play | arkit | scenekit
## Versionation / CI
git | jenkins | gitlab-ci | lambdacd | circleci | gocd
## Frontend
html5 | css3 | sass | less
## Build Tools
gradle | gulp | groovy | babel | cucumber | jasmine | selenium | junit | testng | geb
## Data Storage
mongodb | apache-kafka | solr | hadoop | spark | redis | amazon-s3 | postgresql | lucene | elasticsearch | maven
## Cloud
AWS | azure | GCP
## Platforms
docker | android | iOS
## Infrastructure as Code (IaC)
terraform | cloudformation
"I don't just sit alone in front of the computer all day and write codes around the clock, but I'm in regular exchange with my colleagues."
Jan, Job Ambassador Software Development