Hi, I'm BastienRemote Head of Engineering, from the Côte d'Azur
I help companies take a product from its first version to a team that scales, building only what they need, when they need it. Startup, growing business or a new product inside an established one: in 15 years, from developer to Head of Engineering, I've lived each stage myself, from shipping a first product and keeping it running to scaling it at the right moment and growing the team.
AI now writes code fast, for anyone. What it can't give you is judgement: what to build, what to leave out, and which shortcut will cost you later. That's what experience brings, and I use AI myself so you get there faster.
Deepest in Ruby, Rails, PostgreSQL, Redis, AWS, Kubernetes and AI agents. Different stack? My method reads delivery, code history and architecture, so it works on any mainstream web stack. See my stack
Questions I help leaders answer
Can AI build our MVP, and what will it miss?
We ship twice the code with AI. Why isn't the product moving faster?
When should we scale, and what will it cost?
Is my tech team ready to grow with the business?
Is this codebase a solid investment?
Clear answers, a concrete action plan, and jargon only if you want it.
AI writes the code fast. Experience decides which code is worth writing.
AI answers whatever you ask. I help you ask the right question: what to build, what to leave out, what can wait.
I use AI to read a codebase and its history, draft a plan, and build things I've never built before, learning fast from them. You get answers in days, not weeks.
The expensive part of AI is the mistake you find later: code nobody understands, a bill that grows with every user, data sent where it shouldn't go. I help you avoid it.
I've worked remotely my whole career, full time or part of the week: in Paris, then Munich, and since 2023 on the Côte d'Azur, with product teams spread across Europe and the US, on stacks from Ruby on Rails to Kubernetes and Terraform. Today, a growing part of my work is building AI workflows and agents, and helping teams adopt them well.
I care about technology, people and continuous learning. I like questioning established ways of working and finding better ones together with the team.
I believe good engineering cultures run on trust, accountability and ownership. Value counts more than visible hours. I'm a strong advocate of remote work: with the right communication, distributed teams do great work and people get more balance in their lives.
As a leader, I build environments where engineers take ownership, grow and do their best work. That's the lens I bring to every review and advisory session.
Leads engineering: hiring, coaching and the delivery process. Running a team every day is what keeps my consulting current.
Joined as a senior backend engineer and grew into the principal engineer role before taking over engineering.
Built the integration layer connecting Propertybase and its acquired sister companies; introduced consistent monitoring and an internal status page for all services.
Moved to Munich in 2016: a new country, a new market and work in English, so back to hands-on Rails. Relaunched autoplenum.de and 12neuwagen.de; brought Elasticsearch to 12gebrauchtwagen.de and cut test-suite run time drastically.
Started on .NET, then moved to Ruby on Rails with the team and worked on full-stack projects with teams in Europe and the US, including a European CV database and a career coaching platform on AWS.
A product grows up the way an engineer does: first you learn to ship, then to keep it running, then to scale, then to grow a team. It's the same path for a startup, a growing business or a new product inside an established company. I've been through each stage myself, from developer to Head of Engineering. Find where you are, and see how I help there.
Where is your product today? Pick your stage.
Not sure? Play Ship it, 2 min →You have an idea, a deadline and maybe no engineering team for it yet. You need a first version in front of users, without building what you'll throw away.
AI can build a demo in a weekend. I help you pick the one worth building, and make sure it survives real users.
My first years as a developer, on .NET, taught me that working code in front of users beats perfect code on a branch. At CareerBuilder we moved to Ruby on Rails as a team, learning it together along the way, and I've stuck with Ruby ever since.
Real users find what breaks. Releases get scary, shipping slows down and nobody can say where the time goes.
AI writes more code than your team can review. I set the tests, review rules and monitoring that keep releases boring.
Owning production taught me to make releases boring. At Propertybase I set up consistent monitoring and a status page for all services; at 12Auto I cut the test-suite run time drastically.
Usage grows, and so does the cloud bill. Scale the parts that need it, when the numbers say so, with infrastructure that matches real usage and budget.
AI features add a bill that grows with every user. I size infrastructure and model costs to real usage.
As a senior engineer I worked where products get slow or expensive: search, caching, queues, integrations. I brought Elasticsearch to 12gebrauchtwagen.de and built the integration layer between Propertybase and its acquired companies.
Hiring, first managers, a process that holds as the team doubles, and a CTO who needs someone to think with.
Your engineers already use AI. I help turn that into team practice: who reviews what, how juniors still learn, how you measure it.
From engineering lead at CareerBuilder, with teams in Europe and the US, to Head of Engineering at Werbezeichen: hiring, coaching and setting the process.
Investors, a buyer, a board or a new CEO want to know whether the tech is a solid base. Better to find the risks yourself, before they do.
Buyers now ask what your AI really does and who understands the code. I help you answer before they ask.
As Head of Engineering I learned to present tech as a business asset: risks, costs and a plan a board can read.
A coding assistant is not an AI strategy. I help you pick the few workflows worth automating, at every stage, with guardrails and cost and quality checks. Scoped on proposal.
Some problems aren't only technical. When your challenge touches product, design or data, I bring in trusted specialists from my network and coordinate their work with yours, so you deal with one point of contact.
Every engagement starts with a scoped proposal. Prices are typical starting points in EUR, excluding VAT, shaped around your team, your stage and what you actually need. Reverse charge applies to EU business clients in other member states. On proposal: building an MVP with my network, leadership coaching, investor-side due diligence, AI workflows and incubator workshops.
Running an incubator or accelerator? I run office hours and a workshop that walk a cohort through these five stages. Let's talk. Not sure where you are? Play Ship it: pick your stage, make six decisions, get a diagnosis.
The data, caching, queueing and infrastructure layers are where products get slow, expensive or fragile. That's where my experience runs deepest.
Enough to build an MVP front end, review front-end work and steer specialists who do it full time.
Delivery, data, caching, queues and failure modes follow the same principles in every stack. When a niche needs deep specialism, I bring in someone from my network.
A 30-minute call to define the question, the people involved and what a useful answer looks like.
Interviews with key engineers, a codebase and pipeline walkthrough and a delivery baseline.
Written findings ranked by severity, with a 90-day action plan your team can own.
A check-in on progress, plus optional advisory sessions if you want ongoing support.
Not ready for a call yet? Tell the game where your product is today, make six decisions on the problems that stage brings, and get a diagnosis: the biggest risk your choices reveal, and the one offer that addresses it. Your answers stay on the page unless you choose to send them.
Contact
Whether you're building a first product, releases are getting scary, the cloud bill grows faster than your users, the team is growing or investors are asking questions, a 30-minute call is enough to tell whether I can help and which offer fits your needs and budget. Send a few lines about your situation, your team or project, and the question on your mind.
Based in France (CET). Remote work, with in-person meetings possible on the Côte d'Azur. English and French.