Our technical team is organized independently: we have a lot of flexibility in the choice of tools and processes. We hold a daily standup to discuss our challenges succinctly and find opportunities to help each other (especially in pair programming). We meet every week to take a more comprehensive look at technical advances and challenges, share our intelligence and do demos.
Continuous learning is very important: we have a book budget, a conference budget and we meet every two weeks to learn together during a “lunch & learn”.
Our current composition: 3 Data Scientists, 2 Data Engineers, 1 CTO
1. Visio to present Octopize to you, describe our challenges, the proposed role, answer your questions, and decide together to continue the process
(30 min)
2. Open source contribution or exercise to better define your skills
3.Technical video (1 hour) to iterate on your exercise and give you interactive feedback
4. On-site interviews:
➡️ Technical interviews according to profile
➡️ Meeting with the CEO (1 hour)
➡️ Informal meeting with the team (lunch or coffee)
Of course, we can adapt according to profiles. Do not hesitate to let us know your feedback on this point.
Anonymization is a fairly recent subject and techniques (defense and attack) are progressing rapidly - that's what makes it exciting! For a first overview of anonymization techniques, you can consult this article:
What anonymization techniques to protect your personal data?
The aim of these tips is to help you show your best self!
• We recommend that you practice interviewing someone else. Nothing beats a real simulation to be able to progress.
• If the question is not clear, or if you feel stuck, feel free to ask questions.
• Interviews also allow you to better understand if our environment is right for you - you can really ask any questions you want to find out more about our daily lives, our technologies, etc. You will find lists of questions that can inspire you here: Questions to ask your interviewer, viraptor/reverse-interview
The objective of this interview is to give you a complete feedback on your open source exercise or contribution, and to make some changes in pair programming mode.
A few tips to prepare yourself:
Objective: to work together on a piece of code.
This interview is done in real conditions, i.e. you use your computer with your editor and your setup. Of course, you can use all the tools you normally use, including Google and Stack Overflow.
We recommend choosing a programming language that allows you to focus on the given problem rather than memory management, types, etc. Many recommend Python or Javascript/TypeScript for this exercise.
A few tips to prepare yourself:
