What I do:75% of my work is:- reviewing specifications- writing tests- managing test campaigns- automating tests- reviewing test related codeThis is focused around 3 "batch-like" AI products and 1 web-UI The other 25% are in the category "helping my co-workers with many different tasks", such as:- leveraging my experience as a video producer to record interviews at events- doing workshops to onboard more people into the culture of feedbackWe mostly function as an horizontal organisation: each incepti's expertise and opinion has value. Something along the lines of "alone you go fast, together we go further": we build the company together.The tech I use:- git + GitHub- python + Playwright + Gherkin + Behave- Google Cloud Platform- Kubernetes: kubectl- Jira + XRay- Allure- DICOM

I acted as a test-lead for a small team of test-automation engineers (1 permanent developer, 3 interns, 1 product owner)I coached the team about technical decisions (mostly regarding the use of Selenium and Node.js) and about functional aspects of testing (keeping the "why" of what we code)Some notable projects: - I coded a POC to answer "can our end-to-end tests that touch multiple interdependent services be automated ?"- I worked on making the results of automated tests easier to read - updated the structure of the report, added screenshots- I led the migration of our testing codebase from Javascript to Typescript, that aimed to implement strong typing and improve the maintainabilityThe technologies I use:- Node.js + Javascript (and soon: Typescript)- Mocha + Mochawesome- Chai- Selenium- Axios- Git + GitHub

Automating regression tests was fun, but the projects were growing, so was the development team, and we needed to evolve in order to improve the quality of the software.We created the Testing Department: my boss, about 5 new testers and I, and it basically improved everything. As a test manager, I helped my colleagues with their work by transmitting the client-specific knowledge I gathered over the past few years, and by mentoring them in the discovery of testing methodologies. The mentoring was actually very simple since my colleagues were exceptional: I never had to explain anything twice, and when they had some doubts and requested a second opinion to confirm their choices, 99.9% of the time my evaluation was "I agree with you, this is the best decision".

I automated regression tests for a website and some API for a health insurance company.In other words: I did not code the software, I coded some robots to help me test it. Here was my usual process:- First, I read the specifications: I need to understand them to craft a good test scenario. Testing the specs is a very important task- I then send my scenario to my colleagues for a review; this serves 2 purposes: proofing my understanding of the specifications, and broadcasting what exactly I intend to test.- Next step: I code the script. - Finally, I make use of the results of the tests (executed several times a week) and send bug reports to my colleagues.Bonus: I figured out that the developers, projects managers, our client's testers and I shared some of the same needs: we need test data and test accounts. These are not trivial to obtain. I first hacked some rudimentary scripts for my own use, then refined them and eventually transformed them into some very useful and much appreciated internal tools.Tech: git, gitlab, javascript, jenkins, ruby, sahi, soap-ui, svn, watirHere were my feeling after a year at this position:- I really enjoy working on test automation. Regression Testing is repetitive, and doing these tests manually can take a toll on your mental health. Thankfully, my robots turn this into a fun task.- I also enjoy the fact my co-workers and bosses are professional and respectful people, and I learn a lot from them.- I very much enjoy the global absence of bullshit in my work environment.- I am proud to think and say "I really like this job and this company"!- I have yet to find something to dislike about my situation. Lucky me!

I replace a worker at very short notice, without any time to pass-on knowledge. The team had to complete a major technical migration for a school-management application, and had to get it done by en of AugustI performed exploratory testing sessions to chart the behaviour of the old version of the app, and extracted tests cases and tests scenarios from it. I ran 2 test campaigns and documented it, thinking "I cannot stay, so let's make it easy for my co-workers to continue"I also automated a few API tests and helped my co-workers to learn how to do it too.I very much liked: - the mission and the customer. I experienced meaningful agilty for the first time, SCRUM leveraged by people who understood it.I was deeply unsatisfied with: - the management at Ausy

For the electronic money module of a banking software package, I carried out these activities:- Coding and maintaining features (front-end and back-end)- Writing functional specifications- Conducting code reviews and training for newcomers- API testing (functional, performance)Some of my most memorable activities: - This was my first job. I met a mentor who showed me that coding and tech watch can really be fun.- I helped automate tests on web-services.- I took part in a performance testing campaign on these web-services.- I fed our wiki a lot to perpetuate our knowledge (which was still essentially based on oral transmission).- With my mentor, we explored the (proprietary) language documentation to experiment with concepts and produce more readable, high-performance code. This enabled us to take part in some interesting discussions. Technologies: Genero (Informix 4GL), SoapUI, svnThings that I liked about this experience:- Sopra gave me a real opportunity to begin a career as a software developer,- Meeting a dev mentor was really sweet- I met some incredible people there that taught me so much,- My manager did his best to keep things interesting.I had trouble with:- The corporate culture,- The "old school" technological stack and sub-optimal programming culture,- The high level of bullshit and global lack of logic and reason of the upper management,- My income.

Carried out an assessment study for a yachts producer.

Provided technical support for a friend who wanted to start a new industrial project;Created of the bill of specifications for a new product; Translated the wishes of the designer into technical drawings et specifications;Established contacts with suppliers and subcontractors.

Created and published technical drawings for a yachts producer.