Has anyone actually ever given you a good description of what SRE is?
Recently I've met dozens of companies implementing an SRE function. Half are just rebranding an ops team (because Ops ain't cool), some don't want to call the additional silo they have created 'DevOps' (because apparently that's the wrong thing to do) so they're calling it SRE and the rest actually don't really know how to describe what they're doing. And if you can't describe it simply, you don't know what it is, chief (because Google do it, isn't the right answer).
That was until today, when I met a company who actually white boarded their vision for a brand new Site Reliability Engineering function they're building from scratch.
They talked about production infrastructure, optimisation, automation and focusing on the deployment process rather than the build. We discussed Kubernetes, Prometheus and API Gateways. Most importantly, they spoke like they knew what the hell they were on about. Not just about SRE, but on the whole Engineering process.
This is a company with at the top of their game, who are about to introduce a brand new monitisation model to a web environment already producing millions of unique hits. A company who boast ex Googlers, Facebookers etc on their exec team.
It's an opportunity for you to work with a blank canvas, to use your voice and opinion to help them build this new team. You can use your ability with Software Development and build on this adding the likes of Golang/Python (great if you already have this) on top. You get to be instrumental in the process procedure and strategic direction. We're looking for people who truly understand DevOps and Site Reliability Engineering and want to work with like minded individuals.
It's also an opportunity to move towards the future of engineering, with a company who really really know what they're doing. Great internal tech culture, working with awesome people on interesting tech challenges.
Get in touch with me for a chat, no CV necessary.
#J-18808-Ljbffr