Finding top talent to build a culture of collaboration can be time consuming and difficult; with the largest network of DevOps/SRE professionals across the United States – you’re in the right place.
Harrison Clarke International is the only dedicated DevOps/SRE recruitment partner. With a highly committed team of market experts, our goal is to provide both clients and candidates an exceptional service, by helping companies achieve their hiring needs and identifying a unique and life changing opportunity for candidates.
We have and continue to partner with leading VC Funded Startups through to Fortune 500 Companies across the United States. We advise on DevOps/SRE hiring strategy and implementation, reinforced by our unique network of DevOps/SRE talent.
We understand that every company is different. That’s why we go above and beyond, taking the time to understand your company’s needs. If you are hiring for a DevOps/SRE professional and would like help and advice in building a DevOps/Site Reliability Engineering team from scratch; then reach out to us today and a team of expert recruiters who live and breathe this market will dedicate their attention to your business – tailoring a recruitment solution focused on your company requirements.Enquire Now
As DevOps/SRE recruitment experts, we have the knowledge and experience to place you in high profile VC Backed Startups as well as Post-IPO Companies across the United States. We know how valuable your time is and the frustrations associated with finding the right position. We have a history of connecting talent with companies in our portfolio that truly understand the need for a DevOps/SRE function within their business – one that aligns with their exit strategy or growth plans.Get in Touch
At Harrison Clarke we understand that DevOps/SRE is a culture of collaboration. This mindset enforces the relationship between Development, Quality Assurance, and Operations.
The Netflix model and the Google SRE model are self admittedly not exactly DevOps. At Netflix the Operations team simply does not exist on the streaming side and at Google it is implemented as an Engineering Organization that also has Operational Duties. Early stage startups will actually be closer to the Netflix, NoOps, model, usually because the whole company is made of a handful of Software Developers and the problems of Reliability, Reproducibility, Security, Auditing, Disaster Recovery and Scaling are just not present yet or are not painful enough to justify the additional headcount. Startups with actual customers and online traffic will start to prioritize reliability and hire an Operations, or DevOps team to handle the problems which need people that have strong Operational experience to start improving Uptime. Uptime is not a one time investment, it is an ongoing process that needs constant nurturing, and is as much the responsibility of the Development team as it is the Operations team. When planning the development work, Uptime should be your first feature because when your service is down none of your features matter. How do you guarantee that you will improve Uptime and how do you enable rapid delivery? One key item is Collaboration. With Collaboration you want to break down the organizational silos, increase empathy between the roles and increase Respect. To balance on-call duty, Google requires a minimum of 8 people for a single site on-call rotation. It does not mean that you need 8 Operations personnel, spread it with the Development team. Also do not make the rotation too large to avoid Operational Underload, in which case the person on call might lack the experience to fix the outages. Make Root Cause Analysis mandatory after each failure, and have the Development Team responsible for writing them: they write the code, they are the one that should best understand how it works and how it can be updated to be more fault tolerant. You will want blameless RCAs, the goal of the exercise is to make sure the same outage will not happen twice, not to point fingers. The RCA should have a meeting with the key stake holders, that is the Developers and Operations. Thrive to develop, in your code base, solutions to tolerate the root cause of the outages. For example if a service became unstable and required to be restarted following a network glitch, fixRead Article
New Development Culture One of the biggest misconceptions about DevOps is probably that it is a new ways of doing Operations. In reality it is as much, if not more, a different way of doing Development. There are several articles from well respected experts on the topic that affirm “There's No Such Thing as a Devops Team”, or that “DevOps is Dead”. In these articles the stated problem is that the Software Industry is trying to build and/or hire DevOps teams to bring in Continuous Integration, Continuous Delivery and Continuous Deployment so that the Development team can be more Agile and respond to Marketing requirements in record times. This new team is doomed to have limited impact without a cultural shift from the Development team as well. There is no one size fit them all DevOps solution, some companies, have been hugely successful thanks to a culture that enabled Operational Excellence which in turn enabled their massive growth, two of these companies are Netflix and Google. Freedom and Responsibility Netflix Engineering Culture is highly respected in the software industry. Netflix was launched in the mid 90s as an online DVD store, then they became very famous in the US with the red envelopes as a DVD rental by mail business. At the time they had a traditional, relatively small development team, developing a low/medium traffic site designed as a monolithic centralized service that scaled vertically and operated by an Operations group in a traditional datacenter. In 2008 netflix.com had an outage that lasted several days. As the customers still received DVDs in the mail if they had a queue this was not a massive problem, but Netflix plan was to transform itself into a streaming business, where such an outage could destroy it. At the time Netflix stock was trading around $3. Since the streaming service would be a, mostly, completely new software stack, they decided to completely revisit how they operate. In fact they no longer have an Operations group for streaming. If you ask Netflix how they think about DevOps their answer is that they don’t. By deciding to delegate the physical operations to AWS and make the development teams 100% responsible for uptime, they did not need that Operations group to run Streaming. The cultural transformation was completely on the shoulder of the developers. This is an extreme model, but is a good example of why aRead Article
If you work in the software industry you must have heard the term DevOps by now. It is one of the hot words in the Silicon Valley at the moment and it seems that everyone wants to do DevOps. Unfortunately just like Agile which is often times a cool buzzword to justify lack of planning and pretend that the chaos is designed, the DevOps term is misused more often than not. The “we need to do <buzzword>” attitude is not new and that behavior was highlighted as far back as in 1995 by Dilbert with the mauve SQL database. There are two most common inaccurate definitions of DevOps in job postings. The first one is “Operations that Develops”, usually seen as a System Administrator writing Ansible, Puppet, Chef or Salt Stack script as part of his duties. This is actually not new as Puppet has been used by Operations since 2005, and System Administrators have been writing Shell Scripts to automate their tasks for decades. The second common definition is “Developer that works in Operations”, a Software Engineer that is tasked with all Operational duties, but often times lack the experience and has a different mindset than a true Operations veteran. While these positions are not entirely incompatible with DevOps, their implementation is definitely not in its spirit. So what is DevOps? DevOpsDays DevOps was coined in 2009 for the DevOpsDays conference in Ghent, Belgium. It was “The conference that brings development and operations together”, note that it was not called the conference that “changes the way to do operations”, no it was about “development and operations”, “together”. DevOps is not and cannot be a one side change of how you manage operations, and if anything is mostly a cultural change that must happen on the development side of things. Nowadays the DevOpsDays organization has grown and has dozens of events each year all around the world. Scaling Vertically, the Old Fashion Way Traditionally Operations is on the receiving end of Development and has extremely limited influence and input on the architecture and features delivered. This is often requirements such as the hardware architecture needed to run the software, the OS, RAM, CPU, etc… the Operations team then take the requirements, estimate the cost to obtain the resources and runs with it until scaling up is physically impossible. In the traditional model the development team often used a Waterfall modelRead Article
Continuous Integration (CI) The DevOps culture has eliminated the stress that businesses endure when releasing new code. With DevOps, there is no longer a need for multiple QA cycles and relying heavily on untested code as new features and codes will have already been tested during the development process. Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Quite simply, this takes out the concern out of new releases and allows developers to put forward code that has already undergone numerous testing, giving them immediate and actionable feedback. In a DevOps Culture, the testing process is automated, creating an environment where internal teams are empowered, imparting confidence and allowing them to release new features and services quickly, benefiting the customer and the company. Continuous Integration (CI) and continuous monitoring In a DevOps Culture, continuous monitoring is encouraged ensuring teams are confident in their ability to respond to problems quickly. Continuous Deployment In a DevOps Culture, customers will have insight into new code and this helps a business gather feedback into potential improvements, ultimately implementing a continuous deployment strategy will identify problems and allow a business to make improvements by releasing new features and responding to failures efficiently and quickly. Resilience With a DevOps Culture comes a continuous delivery pipeline, where businesses are able to respond to failures and return to full functionality quickly. This is the ultimate benefit of a DevOps Culture designed to build an automated, high-quality business infrastructure built on collaboration. Harrison Clarke International (HCI) has the largest network of DevOps professionals in the United States. HCI acts as a consultant talent partner, that assist your strategy and roadmap with our selective network of DevOps professionals. If you are a business that is looking to implement the DevOps Culture, or you would like to understand how DevOps can benefit your team, Harrison Clarke can provide you with advise and assistance and connect you with a network of professionals. If you are a candidate looking for the next step in your career, then get in touch today as we have built the largest portfolio of clients in the United States! Email us on firstname.lastname@example.org or contact us directly on +1 (646)Read Article
We are currently looking for tenacious professionals to join our growing team. Harrison Clarke are offering professionals to join our business with a real opportunity to develop an incredible career.
Industry leading training and development with a structured plan from trainee to management.
A bespoke career plan designed to maximise your potential at each stage of your progression. We have created a completely meritocratic environment, where your performance dictates how fast your career can develop.
You will benefit from an industry leading commission scheme, which facilitates unparalleled wealth opportunities throughout your career.
Our exciting reward and incentives scheme includes 5 star lunches, breakfast clubs, designer watches and holidays to Dubai, Cancun, Miami & Las Vegas!
Your package will include private health care courtesy of Harrison Clarke.
You will also be given a company laptop.
Should you have any questions or wish to get in touch with Harrison Clarke please either reach out to us directly or fill out the contact form below.