Dashdoc

Dashdoc

Tech team

Joining Dashdoc's tech team means dealing with complex issues and processes that must be simple to use for our customers. We must remain attentive to fully understand and identify the work of our users in order to be able to transcribe it precisely into our code.

We are a team of 20 people, fully involved in making decisions and choosing the features to develop. We feel useful because we are working on a product that has a direct impact on the daily lives of our users.

Employee breakdown

  • Developers

    80%

  • Design

    8%

  • Product

    12%

Technologies and tools

    Backend

    • Python
      Python
      100%
    • PostgreSQL
      PostgreSQL
      100%

    Frontend

    • React JS
      React JS
      100%
    • JavaScript
      JavaScript
      100%

    Devops

    • Google App Engine
      Google App Engine
      100%

Google App Engine ⚙️

Our backend is deployed on App Engine, allowing us to focus on business logic and not infrastructure!

CircleCI ⚙️

All our developments are continuously tested and deployment is automatic.

Notion ⚙️

Our technical documentation, our meeting notes, our draft articles are centralized in Notion!

Organization and methodologies

We work with the Shape Up method. It's a 6 week cycle, during which teams of 3/4 people (tech and product) work together on a specific problem. Then, they enter a two-week "cooldown" period whose goal is to reduce the technical debt, do refactoring but also technical improvements.

Our best practices:

  • Code review
  • Continuous integration
  • Continuous deployment

Projects and tech challenges

This is a link to the tech tam blog https://medium.com/dashdoc. You will discover our team and our projects in more details.

Recruitment process

  • An exchange with Solène, our head of HR, to make sure that we are both looking for the same thing

  • A technical test to be carried out at home (2-3 hours of work)

  • 1/2 day at the Paris or Nantes office to debrief the test, meet Corentin, our CTO, and several members of the technical team

  • Discussion with Benoit, our CEO