SRE – CodeShip

CloudBees provides the leading software delivery platform for enterprises, enabling them to continuously innovate, compete, and win in a world powered by the digital experience. Designed for the world’s largest organizations with the most complex requirements, CloudBees enables software development organizations to deliver scalable, compliant, governed, and secure software from the code a developer writes to the people who use it. The platform connects with other best-of-breed tools, improves the developer experience, and enables organizations to bring digital innovation to life continuously, adapt quickly, and unlock business outcomes that create market leaders and disruptors.

CloudBees was founded in 2010 and is backed by Goldman Sachs, Morgan Stanley, Bridgepoint Credit, HSBC, Golub Capital, Delta-v Capital, Matrix Partners, and Lightspeed Venture Partners. Visit www.cloudbees.com and follow us on Twitter, LinkedIn, and Facebook.

Location

Our preferred candidate will be located in an EMEA time zone to provide the best working hour coverage for our Engineering and Operational workloads.

What You’ll Be Doing

Maintaining – keeping the CodeShip platform running smoothly – applying patches, automating fixes, cleaning and generally keeping the place “ship-shape”

Supporting – helping the dedicated Customer Support team work with customers to resolve build issues and identify improvements

Thinking – coming up with new ways of solving problems – and working with the team to prove them out and then implement them

Documenting – describing problems, how your proposed solution solves those problems, and how your implemented solutions are operated.

Optimizing – working to ensure we minimize costs while maintaining an excellent level of service and performance

Coding – you’ll be writing code in Rails / Golang (there is some VueJS – but limited to the stable front-end)

Securing – working with our security team to drive organizational security changes (logging, auditing, monitoring, alerting)

Observing – adding the right monitoring so that we are alerted before our customers notice, and not alerted when the system is able to heal itself

Alerting – getting alerts and working with team members to solve the initial problem, documenting the problem and then working out how to stop them happening again

What You’ll Bring To The Team

• New ideas from where you’ve worked in the past – what worked well, what didn’t work, what CloudBees could do better?
• “the knack” – an uncanny ability to uncover the root cause of problems based on limited information because “it feels like something you’ve seen before”
• The courage to say – “I’m not sure” – and getting feedback from your colleagues on how to complete a task in our tech-stack
• No fear of saying – “Have you considered doing it this way” – and giving constructive feedback to colleagues on alternative ways of doing things

What you’ll work on

• IaaS – AWS
• Platform tools – AWS, ECS, Terraform, Docker
• Language tools – Golang, Rails, VueJS
• Engineering tools – Vault, CodeShip!, Auth0
• Operations tools – PagerDuty, Librato, PaperTrail
• Corporate tools – GSuite, GitHub, Jira, Confluence, Slack (we use these – rather than “work on them”)

There are a lot more tools – you should ask during your interview!

How You’ll Be Part Of The Team

You are:

• self-motivated and enjoy solving problems
• excited by the opportunity to automate yourself out of recurring work
• able to keep tickets up to date, so we don’t need too many status meetings (we’re async first due to our distributed nature)
• You will liaise directly with the support and customers, to meet our technical and non-technical objectives.

You have experience in:

• commercial experience programming in one of Ruby or Golang
• the “modern Ops stack” (e.g. monitoring, alerting, cloud-based provisioning, Docker)
• Linux systems administration
• cloud-based operations (GCP, AWS, or Azure)
• cluster orchestration and management tools (e.g. k8s / ECS / Terraform / etc)
• continuous integration / continuous delivery tools (Jenkins / CodeShip etc)
• modern software engineering practices: code reviews, unit / acceptance testing, source control, etc.

How you’ll work

• You work in a geographically distributed team (APAC, US, EMEA) of peers
• You choose your own work in tandem with the team and manager
• You report to the Director of Infrastructure Engineering (who reports to the CTO)
• Your working hours are flexible – while there will be some core hours required for meeting with teams – much latitude is given in getting work done. This includes determining your own start and finish times to accommodate family life.
• Travel is limited – but once things return to normal (whatever that looks like) we’ll have an annual offsite somewhere on the planet

On-Call

We prefer to avoid out-of-working-hours on-call where possible (and are geographically distributed to achieve this), however it is expected that you will be willing to respond to alerts out of hours on a best-effort basis. You don’t take your laptop anywhere unless you want to.

Work hours on-call is just known as “work” – if it blows up – you fix it or find someone who can fix it.

Engineering teams operate under a “Total Ownership” model – they own their entire stack and are empowered to fix it. They occasionally need help out of hours, and we provide best-effort support.

As an example –

• No one has been woken up for an outage in over 8 years
• There hasn’t been a weekend outage in the last 6 months
• We have had to triage security vulnerability reports (on weekends), but those have not required work beyond the initial fault analysis.
• There are occasional false-positives – that are easily silenced – and then resolved at a system level during normal working hours.

What You’ll Get

• Highly competitive benefits and vacation package
• Ability to work for one of the fastest growing companies with some of the most talented people in the industry
• Team outings
• Fun, Hardworking, and Casual Environment
• Endless Growth Opportunities

At CloudBees, we truly believe that the more diverse we are, the better we serve our customers. A global community like Jenkins demands a global focus from CloudBees. Organizations with greater diversity—gender, racial, ethnic, and global—are stronger partners to their customers. Whether by creating more innovative products, or better understanding our worldwide customers, or establishing a stronger cross-section of cultural leadership skills, diversity strengthens all aspects of the CloudBees organization.

In the technology industry, diversity creates a competitive advantage. CloudBees customers demand technologies from us that solve their software development, and therefore their business problems, so that they can better serve their own customers. CloudBees attributes much of its success to its worldwide work force and commitment to global diversity, which opens our proprietary software to innovative ideas from anywhere. Along the way, we have witnessed firsthand how employees, partners, and customers with diverse perspectives and experiences contribute to creative problem solving and better solutions for our customers and their businesses.