I work in Bet Trading tribe in Customer Integration. Our squad owns some critical data pipelines that power the Bet Customer tribe and some internal risk management applications for traders.
In our squad, our older tech (3-5 years old) is primarily node deployed with chef to our own datacentre. Our apps are backed by MySQL and AMQP. Our frontends are largely in React.
In a recently developed service, we have adopted the new SBG stack of Kotlin, Kubernetes, and Kafka – with a React frontend using GraphQL through Apollo for streaming data and state management. Whilst the other services we own are also robust and highly available, the introduction of Kafka and Kubernetes brought our HA capabilities to a new level.
What does a typical day in your squad look like?
We start off the day with stand-up meetings. We either review our task board or quickly go around the room each talking about what we’ve done in the past day and what we’re going to do today. The daily check-in keeps everyone aligned on our squad goals and is a key part of our effective delivery.
After we all top up on water, tea, or coffee, work begins. At SBG, we take ownership of the entire process of getting to live. This means you’re not just coding day in day out. One day you might be picking up a new feature and coding it up. The next could be spent talking through your code in code review. You may need to put in some additional work to ensure your code is covered by tests, so you may be working on testing strategies. Finally, you may be deploying what you’ve created through environments up to live.
The varied responsibility keeps every day fun and engaging – you’re not just focused on pumping out code. You’re thinking about how your code is going to be supported – tested, deployed, kept stable and managed in service. At the start of a new project, you may also be heavily involved in architecting the project. There are expert architects at SBG, but they live next to the squads in a supporting role rather than far away dictating decisions. This gives every engineer a more intimate understanding of the systems they will be developing by taking ownership of the systems architecture.
What has been your proudest moment at SBG?
I introduced GraphQL to our squad, proposed it as a fundamental part of a new service, and saw that service through to live and into service.