Gradle Engineering hiring process

Gradle Engineering consists of two teams: Gradle Build Tool and Gradle Enterprise. Both teams have grown significantly over the last five years, and with a high retention rate. Our hiring process is designed to identify engineers who will be productive, impactful and happy at Gradle in the long run.

Taking on a new engineer is a serious commitment for us. We understand that it is also a big commitment for you. We have designed our hiring process to determine whether you are a good match for us and whether we are a good match for you. We will assess your technical expertise and soft skills; both are equally important at Gradle.

Candidates that join Gradle Engineering will have demonstrated technical expertise and experience in delivering innovative, robust solutions to challenging problems. They strive for respectful interactions, they share our passion for providing users and customers with valuable products and services, and they contribute to the continuous growth of Gradle.

Overview

The hiring process for all Gradle Engineering positions consists of the following steps:

  • Introductory meeting
  • Technical evaluation
    • Code project
    • Technical interview I
    • Technical interview II
    • Wrap-up meeting
  • Employment discussions
    • Interview with our CEO
    • Agreement on compensation and benefits

In all meetings and interviews, we aim to get to know you better, and we also want you to get to know us better. We will ask questions and explore areas that are crucial to our daily work and collaboration. We will not ask you brainteaser questions that are irrelevant to our work like an estimation on the number of golf balls that fit into an airplane. We will not create traps for you to fall into. We want you to shine and succeed.

Over the course of the hiring process, you will meet four of the team’s most experienced engineers, the team’s VP of Engineering and our CEO, and those six people will have a chance to get to know you. This is important given the value we place on personal interactions.

Introductory meeting

In this very first meeting, we will describe what we find exciting about working at Gradle. We will also be honest about what can be challenging about working at Gradle. By the end of the meeting, you should have a good understanding of our work environment and culture so that you can determine if Gradle is a company where you will be productive, impactful and happy.

At the end of this meeting, you will decide whether you want to continue with the technical part of the hiring process or part ways. You may also think about it some more and give us your decision after sleeping on it.

Technical evaluation

The process of the technical evaluation is the same for all Gradle Engineering positions. In contrast, the content and people involved during the technical evaluation are specific to whether you apply for a position on the Gradle Build Tool or Gradle Enterprise team.

Code project

If you decide to proceed with the technical part of the hiring process, you will be asked to implement an instructions-based, self-contained code project. For Gradle Build Tool positions, the code project consists of building a utility which is designed to take a single day to complete. For Gradle Enterprise positions, the code project consists of building a web application which will take about twelve hours to complete.

You can start the code project on the date of your choice. We understand that you have other things going on in your life besides implementing code projects, so we allow four full days from receiving the code project to submitting your solution. This should provide ample time to deliver a polished solution without being under time pressure.

Once we have received your solution, we will need 24 hours to evaluate your submission. After completing the evaluation, we will inform you how it went and if we want to proceed to the next step.

Technical interview I

If you are successful with your code project submission, you will be invited to a first technical interview with two of the team’s senior engineers. They will ask a series of technical questions in order to assess your knowledge, experience and thinking. Some of these questions may relate to your code project submission. At the end of the interview, you will have a chance to ask questions.

Once the interview is over, we will discuss your candidacy internally and decide whether we want to move on to a second technical interview. You will be notified of our decision within 24 hours.

Technical interview II

If we decide to proceed, you will be invited to a second technical interview with a different pair of senior engineers from the team. They will again ask a series of technical questions to better understand your knowledge, experience and thinking. At the end of the interview, there will be a second opportunity for you to ask questions. 

Once the interview is complete, we will discuss your candidacy internally and decide whether we want to move forward to the next step in our hiring process. You will be notified of our decision within 24 hours.

Wrap-up meeting

Based on your code project and the technical interviews, if we believe you are a good match for the Gradle Build Tool or Gradle Enterprise team and we are excited about working together, you will have a conversation with the team’s VP of Engineering to wrap up the technical part of the interview process. During that conversation, we want to ensure that there is mutual agreement on the expectations of your role and responsibilities and that any remaining questions are answered.

Employment discussions

Interview with our CEO

If there is a reciprocal agreement on the expectations of role and responsibilities, and both you and Gradle are eager to work together, the remainder of the hiring process shifts towards employment-related topics. The interview with our CEO primarily focuses on the history, goals and vision of the company, as well as discussing all contractual aspects of employment at Gradle, including but not limited to compensation, equity, vacations, etc. This is also an opportunity for you to get the CEO’s perspective on topics that may be of particular importance to you like the market opportunity and development plans.

Agreement on compensation and benefits

If you are happy with what Gradle has to offer in terms of compensation, benefits, role and responsibilities, and you decide to join one of the Gradle Engineernig teams, we will execute the necessary paperwork, including finalizing a start date for your employment and journey.