A guide to hiring a Struts developer
Apache Struts is an open source framework for building web applications in Java. It follows the model, view and controller pattern: a request comes in, an action class does the work, and a result decides which page or data goes back. Struts was one of the first widely used Java web frameworks, and a great many business systems were built on it. Today most Struts work is about keeping those systems running, safe and up to date. If you run one, you need someone who knows the framework by name, not only the Java language.
What the job covers day to day
A Struts developer fixes bugs, adds features and answers the question every owner of an old system asks: what happens if we change this? Time goes into reading code that someone else wrote years ago, writing tests around it, and making careful changes. Reviews, release notes and server updates take their share too. The best people leave the app easier to understand than they found it.
Struts 1 and Struts 2
There are two generations, and they are quite different. Struts 1 is the older one, and the Apache project no longer supports it. Struts 2 is the newer one. It grew out of another framework called WebWork and brought interceptors, plain action classes and a simpler way to bind form data. Many companies still run Struts 1 code or a mix of both. The first task for a new developer is to find out exactly what you have, because the right plan depends on it.
Actions, interceptors and results
Three ideas sit at the heart of Struts 2. An action is a class that handles a request. An interceptor is a step that runs before or after the action, for things like checking a login, reading parameters or handling errors. A result tells the framework what to send back, such as a page, a redirect or JSON. A developer who can explain these in plain words, and draw the path of one real request, understands your app. Ask for exactly that in the interview.
Configuration and pages
Struts apps are wired together with a configuration file, often called struts.xml, and sometimes with annotations. Pages are usually built with JSP and Struts tags, and some projects use FreeMarker or Velocity. Reading this setup is a skill of its own, because one line in a config file can change the behavior of many screens. If your pages are the main problem, our JSP developers focus on that layer.
Security and updates
This is the part that matters most. Struts has had serious security problems over the years, and the Apache project publishes bulletins and fixes for them. Running an old release, or one that has never been patched, is a real risk for any app that faces the internet. A good Struts developer keeps an eye on those bulletins, updates the framework and the libraries around it, and checks that input from users is handled with care. Ask any candidate how they would find out whether your app is behind on updates.
Java, Spring and the rest of the stack
Struts sits on top of Java, and most apps also use a database layer such as Hibernate or plain JDBC, and often Spring for wiring. A Struts developer needs to be comfortable across all of it. Our Java developers cover the language and the wider back end, from Spring Boot services to APIs, and the two skill sets work well together on a bigger system.
Keep, upgrade or move
There are three honest options for an old Struts app. You can keep it as it is, if it is stable and supported. You can upgrade it in steps to a current release. Or you can move it to a newer framework such as Spring Boot, one screen or service at a time, while the old parts keep running. A full rewrite sounds tidy, but it often takes longer and costs more than planned. A developer who lays out the three options with their costs and risks is worth far more than one who just says yes.
When a Struts developer is a good fit
- Your business runs on a Java web app built with Struts, and the person who knew it has left.
- You need an older Struts version brought up to a supported one.
- You want to move to Spring Boot without stopping the business.
- You need bug fixes and small features while a bigger plan is decided.
If you are starting a brand new product, a developer who knows current Java frameworks may suit you better. A Struts developer who says so is giving you honest advice.
Interview questions worth asking
- How does a request travel through a Struts 2 app, from the browser to the page that comes back?
- What is an interceptor, and when would you write your own?
- How would you find out which Struts version and libraries an app uses?
- An old release has a known security problem. What are your first three steps?
- How would you move one screen from Struts to Spring MVC without breaking the rest?
Good answers come with a reason and a past project behind them. If someone knows every tag but cannot explain what happens when a form is sent, keep looking.
Try a small paid job
Give every finalist the same piece of your real work: a form bug on a test copy of your app, or a short review of how your app is configured and what is out of date. Pay them for it. Then compare the code, the notes they wrote and the questions they asked about your system.
Setting up for the long run
Settle the routine in the first week: who reviews a change, how a release reaches the live server and who answers when something breaks. A short page that explains how to build the app, how to run the tests and where the config lives will save the next person many hours.
Mistakes to avoid
- Leaving an old release in place because nothing has gone wrong yet.
- Changing code with no tests around it.
- Starting a full rewrite before anyone knows what the old app really does.
- Hiring by a list of framework names, with no real Struts project to show for it.
Related help: our software engineers cover wider build and design work, and our SQL developers can tune the database behind the app.















