Jonathan Blanchard

Full-stack developer. I am already thinking about tomorrow.

I turn the ideas around me into applications. I design them, deploy them on my own server, then evolve them as real needs emerge.

14-month apprenticeship, from September 2026. Six weeks in the company, two at school. Paris and Île-de-France.

Get in touch View my resume
Portrait of Jonathan Blanchard smiling outdoors

What I am looking for

The practical details first.

Contract
Apprenticeship, 14 months
Start
September 2026
Rhythm
6 weeks company, 2 weeks school
School
Web@cadémie by EPITECH, Paris
Location
Paris, mobile across Île-de-France
Target role
Full-stack developer, features owned end to end

My journey

For three years at Novelty, I dealt with incidents that had to be resolved quickly. But it was often by digging into those problems afterward, testing different approaches and exploring what could have been done differently, that I wanted to move to the other side: building the tools I had been missing.

See the full journey

Two applications, shipped and maintained.

Each case study opens on the problem. Then the decisions. Then what is still unfinished.

Episort

Maintained, in production

Sort a Plex library of thousands of files, and never lose one.

  • Java 25
  • JavaFX 25
  • Gradle
  • JUnit 5
  • TMDB API
GitHub Read the case study

Janus

Maintained, in production

Applications reach third-party APIs without ever holding the key.

  • Java 25
  • Spring Boot 4
  • Virtual threads
  • React 19
  • TypeScript
GitHub Read the case study

See all projects

Four choices I can defend in code review.

Four concrete risks: losing data, exposing a secret, missing an integration problem, or shipping without knowing how to operate it.

Plan the way back before writing

Episort shows every move before touching a file. The user approves the plan, the run is journalled, and the operation can be undone.

Use a secret without distributing it

Janus retrieves the key from OpenBao when the call is made. Services use it without holding it, and the audit log records the access without recording the secret.

Test an architecture by actually using it

Episort calls TMDB through Janus. When the gateway throttles calls, Episort paces itself: the architecture is tested in real use, not only in isolated tests.

Make deployment part of the work

GitLab CI builds the application, Traefik serves it, and my server runs it. Designing that path from the start makes every release reproducible and observable.

What I can be trusted with today.

Back-end & tests

Model data, permissions and errors explicitly. Prove it in CI.

Java · Spring Boot · REST API · JUnit 5 · PostgreSQL · PHP / Laravel · Node.js

Proven in: Janus, Episort

Front-end

Turn business rules into readable, accessible flows.

React · TypeScript · Vite · Tailwind · JavaFX

Proven in: The Janus console, Episort, this site

Operations

Build the environment. Ship the artifact. Keep it up.

Linux · Docker · GitLab CI/CD · Traefik · OpenBao

Proven in: Everything of mine that runs in production

Methods

The habits that make code survivable by someone else.

Git · Code review · Tests in CI · Application security · dev/prod separation

Proven in: 12 group projects, and my own on-call

Could we work together?

I am looking for a 14-month full-stack apprenticeship starting in September 2026.

Write to me View my contact details