At CheMondis “Team Engineering” is the company’s backbone. The team shapes and reshapes the marketplace while developing and optimizing existing and new features. Simply said: Team Engineering brings the CheMondis vision to life and lets you experience it on our marketplace.
Our Head of Engineering, Max, leads the team, combining both frontend and backend engineers. The Engineering Team is divided into three scrum teams with different focus areas, which split the workload logically between each other.
“The highly qualified team and further our company structure allow us to deploy almost any idea that pops up in our head,” says backend developer Roman. “This way, we can try out ideas instantly. Keeping them deployed, if they add value to users and dropping them, if they don’t,” he adds.
Driven by the CheMondis vision, the “Engineering Team” wants to help users experience the full range of a digital marketplace for chemicals. In order to do so, our developers constantly create new components and features for users to access. For instance, the new Agreement Management, which we previously showcased in our blog article here.
Our engineers are both at the start and end of our idea generation process. They are the technical experts that turn ideas into code and bring them to life – and generate new ideas on the way.
As described in our blog article “Team Product – Paving the CheMondis Path”, we work with Scrum. The agile product development process helps engineers deploy product increments effectively almost every day. In case you are interested in learning more about the scrum framework and what sprints and tickets are please click here to jump to an earlier blog article.
“Scrum really helps us get stuff done! We literally deploy new ideas every two weeks. And little changes even every day.” – Sufyan
After the sprint goals are clear, tickets are discussed between the product manager and the “Engineering Team”. Collaboratively, story points are agreed on and assigned.
These story points describe a unit of measure for the complexity of each specific ticket. Think of it like this: It may be hard to estimate how long, in terms of time, a feature will take to develop and deploy, but less hard to understand if it is more complex in comparison to others. Using story points as an estimation rather than time or quantity, allows our developers to work more efficiently.
Cross-functional Focus teams
The front-end and back-end engineers as well as the product designers from Team product collaborate in three autonomous, cross-functional focus teams. This predefined range of responsibility lets them work independently from each other and reduces technical dependencies. Instead of having a large group work on one task, three groups work on three from each other independent tasks simultaneously. By doing so, we are able to secure rapid development in terms of workflow.
Thus, we increase the speed. Each focus team consists of a set of front-end and back-end developers, as well as designers from the product team. Next to the development of new and the improvement of existing features and components, the “Team Engineering” sets its focus on data integrity. At CheMondis trust is a core attribute, which is cherished deeply. That applies just as much for the technological decisions which we take as for the individual customer validation.
“For a marketplace of our scale, data integrity is mandatory.” – Mazdak
In a nutshell
Our engineers are the last and most crucial step within the CheMondis process flow. They are the technical experts that turn ideas into code. Next to the development of new and the improvement of existing features and components, the “Engineering Team” set its focus on safe data storage and efficient data security for long term utilization.
Now it is up to you
Do you have more questions? Are you looking for a new challenge in Engineering? Leave a comment below and let us know.
Thank you for taking the time to read the CheMondis Blog.