We do our best to choose the best tool for our customer's job. Today, we tend to prefer full-stack JavaScript, but we also have projects in Symfony, Python and Go.

We follow the evolution of the web stack very seriously. We dedicate 10% of our time to research and development, during which we test new approaches, languages, or libraries. When those new technologies actually bring an advantage to our customers projects, we do not hesitate to use them in production. Using this approach, we started using Node.js in 2012, d3.js in 2013, React.js in 2015, Serverless in 2016, GraphQL in 2017, TypeScript in 2018, and it's only the beginning!

If you're passionate about web & mobile development, Marmelab will be a great opportunity to level up.

Backed by agile methodologies (SCRUM, Kanban, Lean Startup), we focus on the end user value to design and build features. We are directly and constantly communicating with our customers and their domain specialists.

We develop in an iterative manner, in two weeks sprints. We deliver to production continuously, and collect domain specific metrics from end users. Customers prioritize the work every 2 weeks, based on the feedback from earlier sprints. We design each new feature in collaboration with our customers, so they can confront their vision to what the web stack can offer. We look for shortcuts to build a better product faster. We refactor continuously to avoid technical debt.

We talk to the customer Product Owner every morning in a short video conference. And at the end of every sprint, we meet in person for a demo and retrospective. Customers are always aware of the work we do and the problems we solve. This constant communication helps us avoid waste, and the nasty tunnel effect. Customers see us as partners more than contractors.

At Marmelab, developers propose their own solutions to the customers needs. They choose the technologies themselves, making sure their are a good fit for the customers context. We choose standard, durable, and fun to use solutions. When we hand over the code to our customers development team, we make sure they become autonomous.

We make decisions as a team, and we share the responsibilities. This autonomy promotes a deep involvement in our customers projects. It makes us have a strong impact on the direction they take.

When we make architecture decisions, we tend to document our key learnings in our blog, see for yourself.

At marmelab, we keep ourselves up to date with web and mobiles technologies. We regularly attend Tech / UX / Agile / Product conferences - it's part of the job description.

We constantly look for tools that help us solve our customers problems faster, or address a complex use case in a simple way. We experiment these tools early on, so we can know them when a customer needs them. We share what we learn in the open, because we learn a lot from other people doing the same.

We also regularly go to conferences as speakers. If a particular subject catches your attention, marmelab will invite you to talk about it publicly.

We organise a hackday every two weeks. Marmelab employees choose a technical subject of interest, and work on it the whole day. It doesn't have to be related to the project they're working on.

It can be a new language to discover, a tool to build, a methodology to learn about. The goal is to learn something new, and to leverage this learning for the others, with a blog post or an open-source project.