Gradle Technologies Interview Questions
& Process

After applying, a senior recruiter contacted me to set up an initial chat. The recruiter was understanding when I missed our scheduled time due to a time zone confusion. The recruiter chat went well, and I then spoke with the hiring manager. My chat with the hiring manager was great and we really connected. After that, I was scheduled for a final interview with two other team members. I had to wait a couple of weeks for this after the initial interviews because of a company-wide meeting. The recruiter kept me informed about everything, which made the whole process a good experience.

Got a call from a recruiter to chat about the role and company. Then had a meeting with the hiring manager about the role and my background, which went about 15 mins over. The next interview was also with the hiring manager, where I did a take-home assignment and gave a presentation, finishing a bit early (over an hour but less than 1.5). After that, I met with a Sr Leader who asked about my superpower and walked me through hypotheticals on how I'd handle GOAL, adding new constraints as we went. Finally, I spoke with the CRO, who was mainly there to answer my questions, and we ended up just chatting casually for about 15 minutes past our scheduled time. Honestly, everyone I met was so unique and enjoyable to talk to.

The hiring process kicks off with a 1-hour presentation from the SVP of engineering covering product, teams, and the hiring process. While the presentations were generally interesting and useful, it was a bit of a one-sided conversation where they didn't seem interested in learning about my background. The next step involved a coding project: building a web application based on PDF instructions, expected to take about twelve hours. I had 4 days to submit it, and it needed to be done in a specific web framework, which was new to me. After submission, my application was rejected. Upon requesting feedback, I learned that the actual requirements were unclear and differed significantly from the instructions. They expected a fully polished, production-ready, bug-free project with comprehensive tests (unit to top-level), and some unspecified use cases not clearly stated or even possible within the given instructions. So far, they showed minimal interest in my experience. It's unfortunate they expect significant time for the project but don't engage in a meaningful conversation, which felt disrespectful.

I started with a take-home assignment that had a tight deadline of 4 days and a lot of requirements. A big hurdle was using an unfamiliar Java web framework (starts with R, ends with K) with a complex DSL. I struggled with its documentation and UI options, even Stack Overflow was unhelpful. After barely getting a sparsely documented option to work, I switched to a React frontend for speed. Because of the steep learning curve and time lost, I couldn't meet all requirements, missing UI tests and specific functional parts. I was aware of this, anticipating a rejection, especially after seeing similar experiences online. The feedback came from HR, and I never spoke to anyone technical. The HR person was kind, acknowledged the process's issues, and mentioned they were working on improvements. I'm disappointed to miss this chance, as developer productivity is a field I'm passionate about, and I've heard good things about the company for engineers despite this hiring process. I gave it my absolute best, working on it constantly and submitting it at 3 AM on the due date. It felt like much more than the estimated 12 hours, but I can confidently say I didn't fail from lack of effort.