A guide to hiring a Perl developer
Perl is a scripting language known for its strength with text. It has been used for decades for system scripts, data jobs, reports and web applications, and a lot of that code still runs today. A Perl developer keeps it healthy: fixing bugs, updating modules, making jobs faster and making the code easier to change. If your business relies on Perl code that nobody fully understands, ask for a Perl developer by name.
What the job covers day to day
Writing new code is only part of it. A Perl developer reads existing scripts and modules, finds the cause of a bug, adds a feature and checks that nothing else changed. Time also goes to talking with the people who depend on the code, writing down what it does and planning upgrades. In many teams the Perl code is old and has no tests, so the first job is often to make it safe to touch.
Where Perl is still used
Perl shows up in scripts that move and clean files, jobs that read logs, programs that convert data from one format to another and reporting tools. It also runs older web applications built with CGI or mod_perl, and newer ones built with frameworks such as Catalyst, Dancer2 and Mojolicious. Some research and lab teams use it for data handling too. A candidate who has worked in the same kind of setting as yours will find their feet faster.
Text processing and regular expressions
Perl is famous for regular expressions, the patterns that find and change text. They are powerful and easy to make unreadable. A good developer writes patterns that do the job, adds comments that explain them and tests them against real examples, including the strange ones. Ask a candidate to explain a pattern they wrote and what input would break it. The answer tells you how they think.
Reading and repairing legacy code
Perl lets people write the same thing in many ways, so old code can be dense and surprising. Global variables, deep references and long modules are common. A careful developer does not rewrite on the first day. They read, run the code with sample data, write down what happens, add tests and only then change small parts. Our PHP developers follow the same habits on older web code.
CPAN and dependencies
CPAN is the large archive of Perl modules, and most Perl programs lean on it. That is a strength and a risk. Old modules may no longer be kept up, and an update can change behavior. A good developer lists what the project depends on, pins the versions, replaces modules that are no longer cared for and avoids adding a new one for a job that a few lines can do.
Databases and web apps
Perl programs usually reach databases through DBI. The developer writes queries with placeholders to keep input safe, handles errors and keeps connections under control. In web apps they also look at sessions, forms and how pages are cached. Many older apps have security gaps, such as unchecked input, so a review is often the first step.
Testing and quality
Perl has a strong testing tradition. Test::More is the common tool, prove runs the tests and Perl::Critic points out style problems. A developer who adds tests around old code makes every later change cheaper. Even a few tests for the most important paths are better than none, and they give the team a way to check an upgrade.
Upgrades and moving away from Perl
Some teams want to stay on Perl and bring it up to date. Others want to leave it over time. Both are valid. Upgrading means moving to a current Perl 5 release, fixing text encoding problems and replacing old modules. The safer way to move away is one part at a time, with the old and the new running side by side until the new one proves itself. Our Python developers often take on the new parts, and our Linux developers look after the servers.
When a Perl developer is a good fit
- You run scripts or web apps in Perl that your business depends on.
- The person who wrote the code has left and nothing is documented.
- A text or data job is slow or breaks on odd input.
- You plan to upgrade the code or move it to another language in stages.
If you are starting a new project with no Perl code, another language may be an easier choice. A developer who says that out loud is giving you honest advice.
Interview questions worth asking
- How would you add tests to a Perl script that has none?
- What makes a regular expression hard to read, and how do you fix that?
- How do you handle text in different encodings?
- How would you check that a module from CPAN is safe to rely on?
- How would you move one part of an old Perl program to another language?
Good answers come with a reason and a past project behind them. If someone knows the syntax but cannot say how they would prove a change was safe, keep looking.
Try a small paid job
Hand every finalist the same piece of your real work: a short script with a known bug, say, or a request to add tests to one routine. Pay them for it. Then compare the work, the questions each person raised and how plainly they explained the result.
Setting up for the long run
Settle the routine in week one: where the code lives, who reviews a change, how a release reaches the servers and who is told when a job fails. Keep the code in version control, record the Perl version and the modules in use and add a short note on how to run the tests. That note saves the next person many hours.
Mistakes to avoid
- Rewriting working code before there are tests to compare against.
- Updating modules all at once with no way back.
- Leaving unchecked input in scripts that call the shell or the database.
- Judging by a list of languages on a resume with no real Perl project behind it.
Related help: our back-end developers cover the wider server side, and our DevOps engineers help with deploys and monitoring.















