Software & Chimpy? Yes, indeed!
Software & Chimpy? Yes, indeed!
Our very own Henning, awesome guy, family, two kids, Backend Engineer & SRE, sheds more light on the topic by sharing some of his thoughts and insights 🙏🏻
Our very own Henning, awesome guy, family, two kids, Backend Engineer & SRE, sheds more light on the topic by sharing some of his thoughts and insights 🙏🏻
First things first, what made Henning interested in working at Chimpy?
“Originally coming from the online advertising industry, it was super exciting for me to help develop a « real » physical product that I myself need from time to time. When I met the team and the company culture on site during my get-to-know days, it was clear to me: I want to work here. What I value most is the individual freedom – at Chimpy you are who you are and you decide how, when and where you want to work – and the great solidarity of the whole company with one another. Chimpy has managed to keep its cool culture, while other companies think it’s done with a pizza evening once in a while.”
The Software Department at Chimpy, at the moment counting four people, is not just a group of individual excellent programmers but a great team, working together.
“Skills can be trained, so personality is most important. Nothing is set in stone. If you have a better solution to a problem and you can communicate its advantages, you are ready to go. For example, when we were implementing the software for our Chimpy Stations we found out very quickly that we would hit our limits with Ruby. So we switched to Golang and are happy with the solution.”
So, what have they been working on in recent months?
“Due to the rapid growth and expansion into other European markets in recent months, we as the software department have ensured that our services also work smoothly in all new countries. We also developed the whole software behind our newest product, the stations. To rent a powerbank from a station, customers can now scan the QR code, pay online, automatically receive it and get their deposit back after returning it.”
Last but not least, what about the technical stack they use?
“In the backend we are mainly using Ruby-on-Rails with PostgreSQL and Redis. In the frontend mainly JavaScript (lately also Typescript) with ReactJS and React Native. We are deploying to Heroku and use CircleCI and Github Actions for our CI/CD. But as mentioned before, we are open for new solutions if they are more suitable to get the job done.”
Thanks @ Henning for sharing and being an important part of the team!