Zeffy
Tech team
Our technical team is divided into three squads: two in Paris and one in Montreal. Each team is made up of a Product Manager, a Product Designer, a Team Lead and 3 to 4 developers of varying seniority.
Each squad works on a high-level business objective, which may evolve marginally over the course of the year, with the idea to keep everyone's expertise on certain parts of the application without being too rigid.
All our developers are full-stack, although each may have their own preferences. In order to prioritize Tech objectives, all devs meet every 2 weeks, and everyone can bring points they'd like to discuss. At the end of the meeting, all the prioritized points will be addressed in the following sprints or defined as objectives for the next 2-month period. We measure the effort put into Tech points as well as Product points to try and keep a good balance between Product velocity and Tech scalability.
Employee breakdown
Full-Stack Devs
71.0%
Product Managers
21.0%
Product Designers
5.0%
3
Number of tech quads
Technologies and tools
PostgreSQL
100%Node.js
100%Nest JS
100%TypeScript
100%React JS
100%Next.js
100%Heroku
100%GitHub
100%AWS
100%
Backend
Frontend
Devops
Next.js
Used for server-side rendering (SSR), Next.js improves our performance and SEO.
Bull/Redis
Our queuing system makes it possible to delegate the most time-consuming tasks to workers, thus improving application scalability.
GitHub Actions
Our CI/CD solution to automate testing and deployment, ensuring a high frequency of production releases.
Organization and methodologies
We designed a customized agile process tailored to the needs of our three teams. We work with objectives over 2-month periods, broken down into one-week sprints, with almost daily production releases. Here are some of the rituals we participate in:
-
Grooming (weekly) : The product team presents new priority tickets to the development team, which evaluates them.
-
Fortnightly: All devs meet and everyone can come with points they want to address. At the end of the meeting, all prioritized points will be addressed in the following sprints or defined as objectives for the next 2-month period.
-
Retro (monthly): We discuss what to keep, drop or start in our ways of working. Each decision is assigned a manager to implement it.
Recruitment process
-
Call with Recruiter (30min)
-
Meeting with CTO or Tech Lead (1.5h)
-
Case Study (2h)
-
Meeting with both co-founders and Head of Success (1h)
-
Reference Check
-
Job Offer
The recruitment process typically takes around 2-3 weeks but can be accelerated if needed.