Engineering Enablers
Last updated
Last updated
These are some of the people who enable our engineering:
A-team
has a few folks with vast experience and knowledge that not only lead our engineering initiatives but also - by working with teams - coach and help other colleagues grow. ...
Availability and reliability is a necessity:
Especially when you have numerous teams and numerous deployments per day;
We also have teams from 12 different countries, different backgrounds, seniority and practices;
And, obviously, availability downgrade isn't something acceptable for us.
Oouf.
That‘s why we introduced SRE (Site Reliability Engineering) team, whose main purpose is to share proven good practices and to point out the risks of the system as a whole. SRE's role isn't to maintain others' systems, as teams are the owners of the systems end-to-end. It‘s to standardize the metrics on the reliability and to point out the risks. SRE team's role isn't to play the blame game, but to improve the system's availability as a whole. Again, teams can override and build on top of the practices proposed by SREs.
Our dear People Operations team is the warmth in the organization. People are important, and we truly believe that's by far the best investment, so we try to keep our people happy and engaged. Each Requirement area has an assigned POP member, and they work with both members and managers, sharing best practices and good ideas from different teams and industry. Depending on initiatives, we've had situations where POP invested months on coaching and mediating. In the long run - this approach proved so much more valuable.
We have quite a big Infrastructure team (~200 ppl) and they collected all the best practices from the industry and Infobip history. Their purpose is to provide leverage for all the other teams, so teams don't have to "reinvent the wheel".
"How do you build or deploy or expose your service, do you need a managed database, you want to run it on K8s cluster, how you monitor or troubleshoot your app..." are all questions that Infra can help you with. You are free to use the practices/libraries/frameworks/solutions from Infra, or you can go on your own, for example when you're working on a proof of concept project. However, keep in mind that "If you want to go fast, go alone. If you want to go far, go with the (infra) team".