So you're looking for someone to write test automation for your game? That’s great news. But if your job description isn’t clear and precise, you risk attracting candidates who aren’t the right fit, or worse, turning away the ones who are.
To help you write an effective job description, here are some important elements you should include:
1. Use the word automation in the title
This might sound obvious, but you’d be surprised how often this gets overlooked. If the role involves automation, say so explicitly. Titles like "QA Automation Engineer", "SDET", or "Test Automation Engineer" are all good options.
Leaving out the word “automation” can lead to a flood of applications from candidates without any test automation experience.
2. Specify that it's for game frontend
Game automation is still a niche area, and many candidates may assume the position relates to backend systems or web-based frontends. If your role focuses on automating interactions with a game frontend, make that clear early in the job description.
3. Mention the game engine
Automating tests in Unity is not the same as doing so in Unreal Engine, and it’s a whole different story if you’re using a proprietary engine. Include the specific game engine the candidate will be working with.
This helps filter candidates who already have relevant experience and reduces onboarding friction.
4. Outline expected team collaboration
Let candidates know which teams they’ll be working with. This paints a picture of your team structure and helps candidates understand the communication dynamics.
Bonus points: mention who the role reports to. It’s a small detail that adds clarity and helps understand if the way you’re operating is familiar.
5. Clarify responsibilities around CI
Will the test automation engineer be expected to manage their own corner of the CI pipeline? Or is there a dedicated DevOps team handling that?
Defining ownership here is crucial, especially if you expect the candidate to build or maintain the testing pipeline themselves.
It will likely change salary expectations as well.
6. Say if there is an existing test infrastructure
Are you starting from scratch, or do you already have a foundation in place? Let candidates know whether they’ll be improving an existing test suite or building infrastructure from the ground up. Some engineers don’t have experience with greenfield projects, having this discussion helps both sides find a good match.
While not every detail needs to be spelled out in the first paragraph of your job listing, including these info somewhere in the offer (or communicating it clearly in early conversations) will help you attract the right candidates.