A guide to hiring a Babel developer
Babel is a free, open source tool for JavaScript. It reads the code your team writes, including newer language features and JSX, and rewrites it into a form that older browsers and tools can understand. It works on the shape of the code, called a syntax tree, which is also why people use it to build their own code transformations. A Babel developer looks after that step. If your project depends on a long chain of build tools and nobody on the team is sure how they fit together, this is the person to ask for.
What the job covers day to day
Most of the time the work is calm: keep the config tidy, bump versions, read the odd error and make sure a new feature of the language works in the build. When something breaks, the job turns into detective work. A developer compares versions, reads the output of the compile step and finds the plugin or setting that changed the result. The rest of the time goes to documenting what is there, so the build stops being a mystery.
Presets, plugins and the config file
A plugin is one small change to the code, such as turning an arrow function into a plain function. A preset is a bundle of plugins that belong together. The settings live in a file, usually called babel.config.json, and the order of the entries matters. A developer who knows Babel can explain why a plugin runs where it does, and can remove entries that no longer do anything. That alone often cuts build time and makes upgrades safer.
Choosing browser targets
The biggest decision in a Babel setup is which browsers you support. A wide target means more rewriting and a larger bundle. A narrow one gives smaller, faster code but leaves some visitors behind. The right answer comes from your own visitor data, not from habit. A good developer asks who your users are, reads your analytics with you and writes the target down in one place so that every tool agrees.
Polyfills
Some newer features cannot be rewritten, because the browser must supply them. A polyfill adds the missing piece. Used carelessly, polyfills bloat the page. Used well, they are added only for the browsers that need them. Ask a candidate how they decide what to include and when to remove old ones.
Babel beside your app code
Babel and the app are different jobs. Our JavaScript developers write features, screens and server logic. A Babel developer works on the build layer that makes that code runnable. Many people do both, and it helps to say in your brief which one matters more. If the app is the problem and not the build, a JavaScript developer is usually the better first hire.
Bundlers, tests and TypeScript
Babel rarely runs alone. It plugs into webpack through a loader, into Rollup through a plugin and into Jest for tests. Each tool has its own settings, and conflicts between them cause some of the strangest errors. With TypeScript, Babel strips the types but does not check them, so a separate check is needed. See our TypeScript developers if your team wants help with the typed side.
Custom plugins and codemods
Sometimes you need a change no existing plugin makes, such as renaming a function across a whole repository or removing a pattern you no longer allow. Babel lets a developer write a plugin or a codemod that does the job on every file in the same way. That turns weeks of manual edits into a script that can be reviewed and tested. Ask candidates for an example they have written.
Babel, SWC and esbuild
Newer compilers, such as SWC and esbuild, run much faster than Babel, and some frameworks use them by default. They do not support every Babel plugin, so a move needs care. A sensible developer will compare what you use today, test a small part of the repo first and keep Babel only where a plugin still needs it. Be wary of anyone who says one choice is always right.
When a Babel developer is a good fit
- Your build is slow, flaky or only works on certain machines.
- Your project carries years of config that nobody wants to touch.
- You need custom code changes across a large repository.
- You support older browsers and want to stop shipping more code than needed.
If your framework already handles the build for you, a general front-end developer may be enough. Hearing that from a candidate is a sign of honest advice.
Interview questions worth asking
- How would you choose the browser targets for a new project?
- A build passes on one laptop and fails on another. What do you check first?
- What does Babel do with TypeScript files, and what does it leave undone?
- How would you find out which step makes a build slow?
- When would you move a project from Babel to SWC, and when would you stay?
Look for answers that tell a story from a real project. Someone who can name every plugin but has never fixed a broken release may not be the right fit.
Start with a small paid task
Give each finalist the same piece of real work, for instance tidying one config file or finding why one build step is slow. Pay for the time. Then compare the changes, the notes and the questions each person raised before they began.
Keeping the build healthy
Write down what each tool does and why it is there. Pin versions, run the build in the same way on every machine and update a little at a time, not once every few years. A single page that describes the build will save the next developer a lot of time.
Mistakes to avoid
- Supporting every old browser without checking whether any visitor uses it.
- Adding plugins to fix one error and never removing them.
- Letting several tools each compile the same files.
- Hiring on a list of tool names when no real build backs it up.
Related help: our front-end developers build the screens that sit on top of your build, and our React developers work with JSX every day.















