With more than a decade of experience in software development, project management, and entrepreneurship, I can help you make faster and smarter decisions. Unlock the power of your team by implementing better workflows, best practices, and modern management approaches.
You can schedule an initial, free of charge, 30-minute call to discuss your project. My rates are $150/hour (€140/hour) for 1:1 coaching, code review, and short-commitment projects, and $110/hour (€100/hour) for longer term applications, such as project or program management.
I have more than a decade of experience developing software for complex
scientific instruments, with real-time data analysis options, and User-Interface design.
I have worked on projects ranging from automating measurement benches, to building software for microscopy.
I also have a background as an entrepreneur, which means I can help you focus on the key features your customers want. Are you building an MVP? Rest assured we speak the same language.
After the initial discussion, we lay out a plan. It includes milestones and timelines. It is also important to have clear deliverables, such as reports, presentations, or meetings with different stakeholders.
Most projects (but not all) specify the total number of hours allocated. I will keep you informed on the progress, and remaining time budget so you can prioritize tasks according to your needs. Transparency is a core tenant of my way of working.
I am based in Paris, France. Depending on the size of the project, I am willing to periodically commute to your location. Ideally, most of the time I'll engage in remote interactions with your team members.
These are some of the topics I have experience with.
Feel free to challenge me with new questions!
Below you can find some examples of how I have helped individuals, companies, and teams. Perhaps these scenarios can serve as inspiration for other projects.
I was contacted by the CEO of a company that works in instruments for medical equipment testing, a highly regulated environment. The question was very concrete: what is the smartest way to transition to Python.
we set up the project as weekly meetings over a period of a month. During those meetings, we would discuss about the current implementation, and I would use the in between time to research and prototype some solutions.
Implementing the acquisition software directly in the instruments, leveraging FastAPI, and multi-processing. A server with access to the LAN would keep experiment records and data, ensuring compliance.
A microscopy company needed a reality check to ensure that their software development efforts were aligned with best practices and future-proof.
We set up a couple of sessions with the in-house developers to discuss the code, the management, and the future. In total, we spent about 10 hours going through the code base and the challenges.
I delivered a detailed report on the team composition and future threats such as lack of engagement, lack of
I also provided an overview of elements to improve in the code architecture, efficiency, and documentation.
More importantly, I also delivered a strategic plan focusing on a detailed SWOT analysis, and alternative paths.
A startup needed software to control a complex instrument. The challenge included electronics control, fast data acquisition, analysis, and storage.
The company didn't have a software developer, but the CTO was a capable programmer.
Since this was an ambitious project, we organized it as a long-term commitment, with a dedicated number of hours per week. I estimated the total length of the project, and there would be a half-way evaluation.
Together with the CTO of the company, we defined the specifications of the software, and agreed on a multi-step
approach to quickly test with users and iterate based on their feedback.
Instead of developing software myself, we agreed that hiring a developer in-house would be the best solution.
I focused on coaching and managing the person and project. This was the best approach to keep costs constraint, and achieve a speedy delivery.
In just over 2 months, a first version of the software was ready to test with users. The initial feedback
was instrumental to plan improvements on the UX, and to implement them as quickly as possible.
The production version of the code was completed and shipped to customers in just under 6 months, much earlier than the expected 1-year timeline the company initially had.