Meet Clément, Developper Back End
Captain Data
Tech team
As Captain Data has been founded by 3 engineers, tech is everywhere: in the product, in the processes, in the "way of thinking". What was once a "weakness" - we all know engineers suck at marketing/sales - is now a strength.
If you're looking for a technical challenge, you're in the right place ✌️ For so many other SaaS out there, it comes to a point where you've seen it all, you're not learning anything new.
What's great with Captain Data is that the platform won't be "finished" anytime soon:
- the market is moving very fast, we always need to adjust to new automations or business expectations
- market verticals are endless, we're doing sales automation today but tomorrow we aim at the whole web
Employee breakdown
Front
20%
Automation
60%
API & Orchestration
20%
In figures
1
at least 1 deploy per day
Technologies and tools
Python
100%PostgreSQL
100%Node.js
100%MongoDB
100%ExpressJS
100%puppeteer
100%Angular
100%Kubernetes
100%Google Cloud Platform
100%Docker
100%
Backend
Frontend
Devops
Notion ⚙️
centralizes everything when it comes to conception, product sprints, best practices.
Linear ⚙️
to follow-up with sprints development and interact with the product while developing.
Gitlab ⚙️
as our base for CI/CD.
Organization and methodologies
Different styles depending on the squad.
Automation squad has to be very reactive and pro-active:
- Morning daily to identify issues to correct
- Afternoon squad daily to help with any blockers
- Active reviews upon deployments
Front squad is very autonomous, dailys are programmed when necessary.
Back-end squad has to align with Front & Automations squad as the "pillar".
There's a weekly on Monday 2p.m. to align everybody on priorities. We tend to prioritize development with a short, mid and long-term window.
We always try to implement "buffer" efforts to give teams room to properly test & release.
Projects and tech challenges
Micro-Services Architecture
Captain Data's CEO, Guillaume, likes to say: "we don't write complex code, what's hard however, is how everything communicate".
Our job at Captain Data is to create APIs: everything we do, any automation that can be run, is, by definition, an API. Needless to say that we have an increasing number of micro-services as well a complex orchestration architecture to scale every job that needs to be run.
Our architecture is always evolving, as it has to be adapted between new features, keeping a high-level of data consistency and a strong semantics.
Web Automation & Semantics
Our general idea and vision is to automate the web, as in, the whole web.
To do this, we've been working over the past years on our proprietary framework, enabling our developers to code less. For some APIs and web scrapers, we don't even code: it's JSON-first.
Beyond industrializing features, we need to be able to work with structured data.
Long-term goals are, for example:
- defining a website's layout automatically
- recognizing entities on any website
- assisting developers & customers with Machine Learning
The web is vast, and we probably won't be able to automate it all. But we sure as hell will do our best to provide anyone with the right tools to ease data automation.
Recruitment process
- 15/30 min call to assess if what you're looking for is what we'd like to offer
- 1h15 with our CTO (or a tech lead) to assess technical skills
- 1h product tour with our COO (or business lead) to understand how you think and how comfortable you are with Captain Data
- 30/45 min final wrap-up with founders