As a team working closely with Platform, Cloud, and Infrastructure systems that support development and deployment processes, we’re responsible for the tools that our developers rely on to build services and deliver them to production. Our goal is to ensure that end users enjoy fast, user-friendly, and high-quality digital experiences. We design services that run in production environments while continuously monitoring them to ensure reliability. And of course, we aim for everything to run seamlessly across the entire workflow.
“I’d like to call out,that is idea of ownership and I think ownership is something that is absolutely fascination about s3, but AWS engineer all up, that way that Amazon builds” —This quote from Andy Warfield, VP & Distinguished Engineer at AWS, has become a core philosophy in shaping our team culture as Platform Engineers.
Team Ownership ≠ Just Writing Code
True ownership goes beyond simply completing tasks. It means understanding the purpose behind what we’re building and the impact if it fails. Real system ownership means adopting a mindset—every time we implement something new.
A clear example from our daily work is Jenkins, a core tool for building and deploying software. For us, Jenkins is not just another tool—it’s a service we own. This includes securing the server, performing regular patching and upgrades, building monitoring dashboards, and ensuring a smooth user experience.
Even the pipeline code we write is rigorously tested across use cases, complete with documentation, so we can be confident that every new version we release works as expected for every user.
Automation Is Not Just a Script
Many people think automation just means writing scripts or Jenkins pipelines. But in the world of Platform Engineering:
❝Automation = System Design❞
It’s about designing systems that don’t rely on manual operation—systems that can scale, recover, and adapt with flexibility.
We constantly look for solutions that reduce repetitive work, cut down on human error, eliminate the need for manual deployments, and—importantly—enhance security and compliance at the same time.
For example, we work in a card-based workflow using Jira. By integrating Jira Webhooks with Jenkins, we automate task execution—such as adding users or stopping/starting machines during off-hours, often triggered by special requests.
Picture : https://www.jenkins.io/
- Validating cloud resource tagging using OPA (Open Policy Agent) to strengthen FinOps practices
- Managing Kubernetes policies and governance via OPA Gatekeeper to enforce quality deployments
- Cleaning up idle resources with Cloud Custodian to reduce unnecessary costs
- Provisioning and destroying infrastructure with Terraform to prevent manual errors and control costs
Make it Happen !!
Whether it’s maintaining system stability, designing intuitive tools, or building smart automation—everything we do serves one goal:
To create value for our internal teams, enabling them to deliver the best to our external customers.
Because we believe great Platform Engineering is not just about “keeping systems running.” Every action we take is done with standards, sustainability, and excellence in mind.
At SCB TechX, we strive to live up to the value of Delivering Excellence.
