Blog
Qovery
5
minutes

Inside Story: How We've Automated the Onboarding Process Experience at Qovery

Last October, we organised a Hackathon at Qovery. My teammate and I decided to work on an internal project to improve the onboarding process experience…with a limited budget!  Let me tell you more about what enabled us to win the 3rd prize! (I consider that, as I was in front of developers' teams working on Qovery’s product improvements, it is not that bad ;) )
September 26, 2025
Marie Mallassi
Senior People Manager
Summary
Twitter icon
linkedin icon

First, why do we decide to work on the onboarding topic?

The first few days at a new job can be exciting and overwhelming. As a new team member, you’re eager to make an excellent first impression, learn the ropes, and contribute to the organisation.

Conversely, HR and leadership are keen to integrate new talent efficiently into the company’s culture and operational processes. This is where onboarding workflow automation steps in, transforming the experience (hopefully) for both the team member and the company.

What’s the problem?

Traditionally, the onboarding process means tons of paperwork, countless forms, and a mountain of administrative tasks.

Below is (only) a part of the tasks to accomplish when a newcomer joins. It’s a simple table on Notion with the task's name, the required info, the owner, and a due date.

The previous onboarding experience managed through on a simpe Notion's page


Quite efficient but boring, isn’t it? But above all, it required a lot of manual actions from 1 person: Me.

What if I forget to send an email? to send a reminder to the task’s owner? To add some info on an email? To forget some follow-up on onboarding preparation advancement?...

I am sure you got it.

Automation to the rescue

This is where automation can change your life.

By automating your onboarding workflow (and HR processes in a more general way), you can address multiple objectives:

  • Avoid manual errors
  • Avoid forgetting actions
  • Standardise the onboarding process
  • Ensure an excellent experience for your newcomers
  • Obviously, save time

When part of a big company, you can invest in some fantastic tools on the market where new hires can complete forms online, reducing the need for physical documents and ensuring accuracy in record keeping. I appreciate the Lucca Suite Software on my side.

But wait, I’ll add one more constraint… a limited budget!

Then, you’ll have to choose some tools…

Many automation tools on the market propose a free plan to do some simple automation. I can tell about Zapier, Automate.io, for instance. Benchmarking with Romain, my crime partner, we chose Lido.io because of its simple interface and commands. I mean, I was at ease using this tool, but you might choose another one depending on your abilities and feelings. The final purpose stays the same.

Here we are!

You’ll find a simple Excel sheet:

A Google Sheet file


Then, it's up to you to create actions (send an email, send a Slack message, schedule actions…, etc.)

Step by step with a concrete example: automate the sending of a welcome email

  1. Put all the required information in each cell:
    A2 = Name; B2 = Surname; C2= Email address receiver; D2= Email address sender; E2= Email subject; F2= Email’s body
  2. Then, in “G2”(you can call it: Welcome Email task”, you’ll enter the formula to run automatically the action to send the welcome email to your newcomer:
    =SENDGMAIL(D2,C2,E2,F2)
  3. Click right and choose “run action” in the drop-down menu
  4. If your formula is correct, you’ll see the cell shortly appear in green with “Success” written
  5. Normally, your newcomer should have your email in their inbox!
  6. To replicate it for another newcomer, you only need to add his name/surname/contact detail and drag and drop the other cells.

In the same way, you can run actions on Slack (with the formula =SENDSLACK), and you can schedule your activities by choosing “add automation” in the drop-down menu.

Google sheet: How to schedule your activities by choosing  “add automation” in the drop-down menu.

Of course, I am not exhaustive. You can customize your actions for HR (what I have presented above is replicable for all HR processes), but why not Marketing/Sales and create campaigns to send your emails automatically?

What I observed

To be transparent, I’ve just started automating the HR workflows, but I could not resist sharing what I have learned, even early on.

  1. I have avoided manual errors such as forgetting important info in an email or sending an email: 0% of manual errors since I started this dashboard. And that’s all the purpose: automation minimizes the risk of human errors. You can enlarge it: from payroll calculations to regulations compliance, automated workflows ensure accuracy and reduce the likelihood of stupid mistakes.
  2. Each team member has been onboarded the same way. And it is even more crucial when a fully remote company. Each HR process must be considered accessible to any team member, receiving the same level of information at the right time,.
  3. For now, I only received good feedback from our newbies. They have been surprised by the onboarding process quality, considering that Qovery is an early-stage start-up.
  4. I will save time, but it is challenging to evaluate this item precisely. Indeed, this dashboard is helpful, but setting it up requires a bit of time. I think it is more obvious when onboarding dozens of newcomers each month.

The only cons I would highlight is that this system is scalable but with a limit.

It is a cool bridge between a fully manual system and when you can invest in HR software. This dashboard will eventually become too big and difficult to read/update. Thus, a self-service portal for new hires is missing, and the UI could be better when there are a lot of new hires.

Long story short, you got it. HR processes can be automated, agile, and efficient. With small tips like this, you can easily simplify your work.

Share on :
Twitter icon
linkedin icon
Tired of fighting your Kubernetes platform?
Qovery provides a unified Kubernetes control plane for cluster provisioning, security, and deployments - giving you an enterprise-grade platform without the DIY overhead.
See it in action

Suggested articles

Compliance
Kubernetes
 minutes
Enforcing security baselines across 1,000s of Kubernetes clusters

The part teams consistently underestimate is that OPA Gatekeeper, the tool most people reach for first, only enforces policy at the cluster level. It blocks non-compliant resources from being created within a single cluster. Propagating consistent Gatekeeper policies across 300 clusters, and detecting when those policies drift, is a fleet orchestration problem that Gatekeeper was not designed to solve.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
AI
 minutes
7 best AI deployment platforms for production Kubernetes workloads in 2026

Training a model in a notebook is easy. What breaks teams is the step after, serving it reliably without haemorrhaging cloud budget or burying your SREs in YAML. The common trap: picking a platform that handles the model but not the surrounding stack. An AI deployment platform should orchestrate the full application graph (inference endpoints, vector databases, caching layers, and frontends) inside a single VPC, with GPU autoscaling that doesn't require a dedicated platform engineer to babysit.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
7
 minutes
Kubernetes multi-cluster architecture: the Day-2 enterprise strategy for 2026

The mistake teams make early is assuming Kubernetes namespaces provide sufficient isolation between workloads or teams. They do not. Namespaces share the control plane, the node pool, and the underlying network fabric. A misconfigured workload in one namespace can exhaust node capacity or crash the API server for every other namespace simultaneously. That is when the multi-cluster conversation starts.

Morgan Perry
Co-founder
Cloud Migration
Developer Experience
Engineering
 minutes
[Alan] From nginx to Envoy: What Actually Happens When You Swap Your Proxy in Production

Migrating from nginx Ingress to Envoy Gateway? Discover how Alan migrated 100+ services in one month, the technical hurdles they faced (like Content-Length normalization), and why staging isn't always enough.

William Occelli
Platform Engineer at Alan
DevOps
Kubernetes
 minutes
How to reduce AI infrastructure costs with Kubernetes GPU partitioning

Kubernetes assigns an entire physical GPU to a single pod by default. NVIDIA MIG solves the hardware partitioning side: one A100 becomes up to seven isolated slices. The part teams underestimate is the orchestration layer: device plugin configuration, node labeling, taints, and pod affinity rules all need to be correct before Kubernetes can actually schedule onto those slices.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
8
 minutes
Kubernetes management in 2026: mastering Day-2 ops with agentic control

The cluster coming up is the easy part. What catches teams off guard is what happens six months later: certificates expire without a single alert, node pools run at 40% over-provisioned because nobody revisited the initial resource requests, and a manual kubectl patch applied during a 2am incident is now permanent state. Agentic control planes enforce declared state continuously. Monitoring tools just report the problem.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
6
 minutes
Kubernetes observability at scale: how to cut APM costs without losing visibility

The instinct when setting up Kubernetes observability is to instrument everything and send it all to your APM vendor. That works fine at ten nodes. At a hundred, the bill becomes a board-level conversation. The less obvious problem is the fix most teams reach for: aggressive sampling. That is how intermittent failures affecting 1% of requests disappear from your monitoring entirely.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
 minutes
How to automate environment sleeping and stop paying for idle Kubernetes resources

Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.

Mélanie Dallé
Senior Marketing Manager

It’s time to change
the way you manage K8s

Turn Kubernetes into your strategic advantage with Qovery, automating the heavy lifting while you stay in control.