Job offer: We're looking for a developer to work on OGP Toolbox!


Job offer: We’re looking for a developer to work on OGP Toolbox!


Nearly two years after its launch during the 2016 OGP summit in Paris, the OGP Toolbox has managed to attract contributors with a total of 1400+ tools, 240+ use cases and 500+ organizations added to help people find the right digital solutions for their open gov initiatives, civic tech projects and all kinds of collaborative endeavours.

The OGP Toolbox is definitely open: all informations can be added, edited and voted upon by users. This formidable mountain of data can be in turn used by others via our open API. All our code is also open.
:arrow_forward: How to contribute?

We’re also commited to work with other civic tech catalogs, while also harvesting many sources such as Wikidata and offering interoperabily, with the ultimate goal to unite similar efforts instead of putting our data in silos.

Join us!

New opportunity

Since our launch at the end of 2016, we’ve spent a lot of time with the community to decide the next steps. A roadmap was drawn up for 2017 (FR), then articulated into three priorities (EN/FR): pro/cons arguments, advanced search and comparison. The first was rolled out successfully (example), whereas the other features weren’t added, partly because of a lack of resources.

Since the beginning of the year, we’re working with the French Development Agency on an initiative to provide technical support to the open data community in francophone Africa and this gives us the opportunity to restart the development of the OGP Toolbox where we left it!

The offer

:star: We’re looking for a developer to do some paid work on in the next couple of months. :star:

The general goal will be to:

  1. Fix current problems, notably with the API.
  2. Improve the current experience of the Toolbox (see ideas above)

The scope of the issues to tackle would have to be decided with the developer, taking from the backlog or adding to it (some issues are very old, not relevant anymore). We have a user feedback meeting on October 18 in Paris to update exactly this in preparation for the dev work.

Johan Richer, a member of the original team at Etalab and now a volunteer administrator, would assume the role of Product Owner, assisted by our core team, members of our parent organisation Code for France, and inspired by our community.

Remote work is possible, even if a regular meeting in Paris would be preferable (at the beginning & end of each sprint for example). All communication and documentation would continue to be in English by default in order to make international contributions to the project easier.

Work could be spread on several months. Duration of each iteration/sprint would have to be decided beforehand.

An advanced practice of Python is required, as well as a knowledge of Elm or at least good practice of JavaScript.

Previous experiences would have to be presented, ideally with contributions to other open source projects.

Our budget allows us to pay the developer for more than 100 hours of work, at a rate of 75€ per hour. This is of course open to negotiation.


This is a first version of the offer, we will update it according to the demand. We would appreciate questions here or on our chat. If you prefer, you can also send private messages to

1 Like
pinned globally #2
made this a banner . It will appear at the top of every page until it is dismissed by the user. #3