A guide to hiring a Selenium developer
Selenium is an open source project for controlling web browsers with code. Teams use it to build automated tests: a script opens your site in Chrome or Firefox, signs in, adds something to a basket, and checks that the right thing appears. A Selenium developer is the person who writes and looks after that code. The job sits between programming and testing, and it rewards people who treat test scripts as real software.
What the job covers day to day
Most of the time goes into three things: writing new tests for new features, keeping old tests working as the product changes, and working out why a run failed. A Selenium developer also tidies the shared code, updates browsers and drivers, and trims the time a full run takes. Much of the value is invisible when it works. The build is green, releases feel calm and the team stops clicking through the same screens before every launch.
Selenium and your QA engineer
Selenium work is not the same as general QA work. A QA engineer decides what to test, explores a new feature by hand and writes bug reports a developer can act on. A Selenium developer turns the checks that must run again and again into code. Small teams often need both skills, and some people have them. Our QA engineers cover the planning and the hands-on side. This page is for the person who builds the automation itself.
WebDriver, Grid and the IDE
Three names come up often. WebDriver is the core of Selenium and the part most teams use: your code sends commands and the browser obeys. Selenium Grid lets you run many tests at once across browsers and machines, which matters when a suite grows. Selenium IDE is a browser add-on that records clicks and plays them back. It is handy for a quick try, but recorded steps rarely make a lasting suite. Ask a candidate which parts they have used in a real project.
Selectors and waits
Two habits decide whether a suite lasts. The first is how a test finds an element. A long path copied from the browser breaks the first time a designer moves a box, while a stable id or a label survives. The second is how a test waits. Pausing for a fixed few seconds wastes time on a fast page and still fails on a slow one. A careful developer waits for a clear condition, such as a button that can be clicked or text that has appeared. If you want the path-writing skill on its own, see our XPath developers.
How the test code is organized
A suite with no structure turns into a pile of copy and paste. A better pattern is the page object: one small class for each page or part of a page, holding its selectors and actions. Tests then read like a short story, such as log in, open the report, check the total. When the page changes, one file changes. Ask a candidate to show how they would lay out a project with two hundred tests, and listen for names, folders and shared setup.
Languages and test runners
Selenium has bindings for Java, Python, C#, JavaScript and Ruby. The language matters less than whether your team can read it. Java teams often use TestNG or JUnit, .NET teams use NUnit, and Python teams use pytest. If your product is built in Java, a Selenium developer who also knows the language can pair well with the people who build it, and our Java developers can help on that side.
Flaky tests
A flaky test passes on one run and fails on the next with no change in the code. They are the main reason teams give up on automation, because each false alarm trains people to ignore the red build. Common causes are timing, tests that share data, a page that loads in a different order and a test environment that is slow or busy. A strong developer tracks failures, finds the pattern and fixes the cause. Ask for a story about the worst flaky test they ever solved.
Running tests in a pipeline
Tests that only run on one laptop are not much use. A Selenium developer sets up the suite to run in your build service on every change, or every night for the long ones. Good setups save a screenshot and a log for each failure, split tests so they run side by side and show results where the team already looks. Browsers run without a visible window on a build server, and the developer should be comfortable with that.
When Selenium is a good fit
- Your web app has key paths that must never break, such as sign-up, payment and search.
- You release often and manual checks before each release take too long.
- You need to test on several browsers and want one set of scripts for all of them.
- You already have a Selenium suite that is slow, flaky or owned by nobody.
If your whole front end is new and in JavaScript, a newer tool may suit you. A developer who says so out loud is giving you honest advice.
Interview questions worth asking
- How do you wait for an element, and why do you avoid fixed sleeps?
- A test passes on your machine and fails in the build. Where do you look first?
- How would you lay out the code for a suite of two hundred tests?
- Which checks would you move out of the browser and into API tests?
- How do you run tests in parallel without them affecting each other?
Good answers come with a reason and a past project behind them. If someone can list every method in the library but cannot explain why a test failed, keep looking.
Try a small paid job
Give every finalist the same piece of your real work: automate one short user path on a test site, or take a look at a test that fails now and then. Pay them for it. Then compare the code, the way they handled waits and the questions each person asked about your product.
Setting up for the long run
Settle the routine in the first week: who reviews test code, what happens when a test fails, and who may switch a test off and for how long. A short page that explains how to run the suite and how to add a test will save the next person many hours.
Mistakes to avoid
- Testing everything through the browser when many checks could run faster at a lower level.
- Letting failing tests pile up until nobody reads the results.
- Copying the same steps into many tests instead of sharing them.
- Hiring by a list of tool names, with no running suite to show for it.
Related help: our software engineers build the product under test, and our JavaScript developers suit work that is not tied to one test tool.















