Back to home

Understand real needs. Build useful tools.

I’m Pierre Pluton. My background connects social sciences, product design and software engineering. I build tools for practical needs, using AI whose value and limitations I can explain.

Pierre Pluton
Pierre Pluton

A background built through practice

  1. Understanding people

    A political science graduate from Paris 1 Panthéon-Sorbonne, followed by studies in sociology. This background informs my attention to people, social context and the practical effects of a product.

  2. Building with no-code

    My first web development training used Bubble, followed by user journeys, API integration and data handling. No-code taught me to turn a need into a usable tool.

  3. Contributing to Lecturer

    Nearly eighteen months as an apprentice, contributing to the creation of a higher education tool. An experience connecting education, product development and technology.

  4. Developing software and data skills

    Python, APIs, scraping and back-end development, followed by TypeScript, React, Next.js, NestJS and mobile apps with Expo. GitHub and DataCamp certifications, independent learning and project work.

  5. Creating and evolving products

    Co-founder of Unifête and CTO of Le Grenier du Motard. I connect product design, interfaces, architecture, web and mobile development, integrations and ongoing improvements.

  6. Building a structured AI practice

    The OpenClassrooms AI Engineer programme complements my practice with modelling, evaluation, RAG, MLOps and model adaptation. I hold the professional certification “Expert en ingénierie et science des données”, RNCP level 7 (Bac+5).

My approach

Curiosity and analysis

I want to understand the need, constraints and reasons behind a technical choice. My social science background informs this approach.

Autonomy and learning

I learn through building and independent research. Moving from no-code to full-stack development and AI engineering reflects this progression.

Organisation and responsibility

I connect product priorities with architectural decisions and delivered improvements. My CTO role also includes quality and incident follow-up.

Communication and reflection

I aim to explain choices, make limitations visible and distinguish a demonstration from a validated result. Feedback from my training provides examples of this practice.

This presentation reflects my self-assessment and experience. It is not a numerical measurement of soft skills.

Projects supporting this background