#2: Meeting with GoJob

written by
Pierre Launay

What is GoJob?

Recruiting and contracting with more than 1,500 temps per week, GoJob connects companies and temps by offering a 100% online service. Nestled in the heart of the Aix countryside facing the majestic Sainte-Victoire mountains, the company has experienced very strong growth since its creation in 2015.

One might ask what the relationship is between temping and NoCode ? If GoJob is not a publisher or an agency NoCode, the start-up is among the most ambassadors of these new technologies.

Indeed, a large part of its internal process is a dense and coherent chain of tools NoCode where data is exchanged, shared and displayed. The NoCode is also present to test and diversify their offers externally to open new markets.

Thibaut Watrigant, Head of Product at Gojob and Anthony Manto, Product Builder at Gojob, agreed to welcome us in their offices to share their vision of the use and perspectives of NoCode for the company.

As the latter states:

Digital is not our product, it's a way for us to recruit and contract automatically and at scale to keep the human element where it makes the most sense.

Make it viable and scalable!

Scaler, scaler, scaler... When we went to meet them, the 2 key words, real common denominators in each presentation, were: viable and scalable.

Beyond the deep-rooted culture NoCode of the internal teams, this demand for performance on all initiatives, this culture of efficiency, of the permanent fight for the creation of value from the improvement of processes or the capacity to innovate rapidly by testing new offers were particularly striking.

If GoJob is undoubtedly an ambassador of NoCode, it is above all the ambassador of optimization and scalability.

Today, the company has more than 150 employees in the following departments: Marketing, Sales, Ops, Admin, Care and Tech.

The Tech team combines traditional development skills (front and back-end developers, data analysts, data scientist), product skills (product manager, product designer) and NoCode (Maker, Product Builder).

A closer look at its organization shows that the tools and technologies used are truly complementary. A hybridization between Code and NoCode which links all the services in an optimal way.

Mapping of the different projects NoCode at GoJob

Which stack NoCode , and especially, for which use case?

The first containment related to COVID-19 brought out the competence NoCode at GoJob.

Favouring the code in the construction of interdependent core-product parts, the teams quickly allowed themselves to carry out certain core developments with NoCode.

With more than 30 traditional developers, all of them welcome the complementary skills that NoCode brings.

Some developers like it and want to do it, others see the technology in a neutral way by simply collaborating. Sometimes there can be a feeling that innovation is only for NoCoders and that traditional developers are only there to execute what has been tested in NoCode, but this is in the minority.

The main use cases are the creation of tools / new solutions and the optimization / automation of internal processes.

Mapping of the different projects NoCode at GoJob

Thus, the first steps in NoCode started with Make (ex-Integromat) in view of the important need for internal automation. One of the first automations was to connect the CRM to the product's back-office:

What is the best trigger? What data should be retrieved? How to connect these two services? etc...
A Make automation chain used at Gojob

Gojob has even gone so far as to set up a spreadsheet to monitor the execution of daily Make scenarios in order to monitor the deficient automations, the details of their dysfunctions and this, in order to be able to quickly solve the problem by adapting the scenario to the missing variable (the majority of bugs identified).

Using a Google sheet spreadsheet, the teams track all the KPIs related to the Make scenarios, quantifying the number of automations per week and identifying potential anomalies. As this optimization progressed, the scenarios were strengthened and included more and more variables from the business processes, even leading the solution to be slow at times, given its automation density.

Mapping of tools used at Gojob

The connection between Hubspot (CRM), Make and the entire Gojob back-office has fueled many other automations. Their number has multiplied to form a coherent set of scenarios, especially with the growing use of two other tools: NoCode and Slack.

Slack and Notion have taken prominent positions to facilitate exchanges and data flows between teams. Slack has gone beyond the messaging stage by becoming a real task management interface, directly linked to Notion as a task management base (product/tech backlog) and resource centralization (training content, tips and documentation related to internal processes).

Notion allows to centralize experiences, knowledge. It's open to all collaborators, everyone can write and discover how to use Graph SQL, how to get data from Airtable, etc.

The problem of documentation and system legacy quickly arose. Setting up a new optimized scenario based on a recent observation is not necessarily very time-consuming (except for certain connections requiring code and a heavier implementation).

In addition, potentially adapting all past scenarios to this change while documenting the new modalities to all teams involved can be an extremely time consuming task.

This is why the Gojob teams strive to implement viable (functionally optimized) and scalable (ready to accommodate many variables in the medium or long term) automations in order to avoid making too many changes in the technical legacy.

In order to carry out an efficient documentation, writing formats have been set up with associated automations: naming of scenarios, association of a collaborator (example: squad leader), generates a google format etc.

Intuitive innovation: creating value with minimal effort

This concept is directly linked to the values of NoCode : speed, resource rationalization and iterations.

The idea is to be able to test ideas / new offers internally or externally with the minimum of effort and resources, in an extremely short time. Thibaut talks about "innovation by intuition" in the sense that an idea is put in place while waiting for a hypothetical customer to bite. At the time of the market touch, the sales people co-construct the new offer with the first customers and consolidate the value proposition in a few weeks.

Intuitive innovation changes the relationship between Go to Market: we reverse the discovery phase, where we start with an idea, conduct 2 or 3 user interviews and develop intuitively. In 2 weeks, the MVP is released and we wait for it to bite. Instead of spending months doing interviews, we launch ideas in a few days, which can lead to opening up a whole market! The objective: to innovate in co-construction with the customer with the beginning of a viable product.

This is how Gojob made the decision to open the American market. Indeed, after having decided internally to expand the business internationally, an initiative NoCode was launched to test the American market and validate the opportunity while learning the rules of recruitment and hiring across the Atlantic

The development NoCode was quite basic:

  • Back office on Airtable
  • Front end on Notion
  • Result = more than 7000 applications in a few weeks in the United States

In just two weeks, thousands of responses were received from the U.S. market, allowing salespeople to adapt their offer in real time.

It took longer to train American recruitment consultants to use Airtable and Notion than it did to implement them for them.

Skills NoCode : Maker and/or Product Builder ?

At GoJob, the career of the NoCoder starts with the position of Maker (technical mastery of the NoCode solutions) of the tool, before being able to take on the role of Product Builder (technical mastery and understanding of the business, product). Each NoCoder is associated with a Product Manager in charge of identifying and prioritizing business needs.

It is not possible and even coherent to become a Product Builder without having been a Maker before. You start as a technician by producing and creating technical value and you become a Product Builder when you think about the product. As long as you are not able to produce viable and scalable products, you are not a Product Builder.
Structure of the career tracks NoCode at Gojob

At Gojob, the NoCode teams observe a real imbalance between the number of juniors and seniors on NoCode technologies, very few NoCode developers are capable of setting up complex, viable and scalable projects.

This is why Gojob has set up an in-house NoCode Academy (an initiative that is still not very widespread) in order to support the development of employee skills.

We have weekly rituals, 1 hour per week to share the projects we are working on.

On a weekly basis, resources are put online on the Notion of the company with biannual points on various topics: Product, Tech, Data etc.

In conclusion

GoJob recently raised over 23 million Euros to internationalize its temporary staffing offering.

There is no doubt that the optimizations and diversification brought by the NoCode tools have helped to strengthen their growth.

One more proof that NoCode is shaking up the world of the web and the competitiveness of small, medium and large companies.