Door Not Mouth

Periodically I get asked for advice on getting a job in software testing with no experience as a tester. It happened again yesterday.

As a hiring manager I hired many testers, some with and some without testing on their CV. What's most important to me is the way people do their work, how they think and talk about their work, and how they deal with other people around their work.

But I'm probably not the hiring manager you're approaching right now, so bear in mind that the suggestions I'm making below are generic, and mine, and should be taken only to the extent you think they fit you and your situation.

CV, Application Form, Cover Letter

Lead with the skills you have and the value you provided by using them. Make the skills that you think are transferrable to testing most prominent on the list.

Think very carefully before leading with a list of responsibilities such as "attended daily Scrum, reviewed proposals, edited the website". This says almost nothing that a job title won't already cover and suggests you don't think about the value you could deliver.

Find things that you have done that you think are analagous to testing (e.g. proof-reading, reviewing, investigating customer support problems) and say why you were good at them and why the skills transfer to testing.

Explain how your specific background can help you be an asset as a tester. For example, you've worked in the area you're applying for, you have been on the business side and can talk to project stakeholders in a way they'll understand, or you're an experienced user of this kind of software and know how other users will engage with it.

I am probably in a minority but I really like a cover letter. In particular I like it as a direct line from the candidate to the hiring manager. Make a cover letter that explains the generic stuff, but include a sentence or two near the top that talks about the role you are applying for. Why are you a good for this company, this team, this context?

Lacking Technical Skills and/or Background

"Not technical enough" is a very weak piece of feedback when you've been turned down for a role. I'd guess it often stands in for "you don't have programming experience." Now, you don't need to be able to program to be able to test but my strong bias is that if you choose not to learn a little programming you are ruling out a huge set of tools that could help you to test.

I said "a little programming" and I mean it. You can get an extremely long way with very rudimentary skills. Find some courses and work through them, and be ready to explain what you've done and what you've learned.

If you know that you need certain tech experience, perhaps because you are looking to work in a specialised domain, seek out experience there. Maybe there's an open source project you can test on. Being able to point at bug reports you filed, PRs you made, or documentation that you reviewed and updated, will be a positive.

Consider doing some work for one of the crowd-sourced testing companies to give you testing experience, exposure to some of the tooling that testers use, and interaction with other testers.

Find something "technical" that you have learned and explain how you were able to learn it, use it, teach others to use it, add value to the company by exploiting it, and so on. Perhaps you've used SQL in a marketing role and built a dashboard for the team to see hourly updates on the responses to a new social media campaign. OK, it's not Selenium but it is technical and gives you chance to explain how you overcame problems, taught yourself something, collaborated with the IT department or whatever.

Know Why You Want This

Have convincing answers to questions like these

Why do you want to move into testing?
What is testing, for you?
What makes you a good tester?
What have you done to learn about testing?
How do you think you can contribute to the company/team/role you're applying for?
How will you'll deal with a situation where everyone on the project has more experience of technology X than you?
What did you do in your current role to get relevant experience?

Demonstrate Your Skills

What skills do you think a tester should have? Can you demonstrate those skills in your CV, in your phone interviews, in any technical exercises you are given?

Perhaps you haven't been a tester yet, but you can take every opportunity to show that you are ready to be one.

Make your CV concise, comprehensive, and clear.
Ask reasonable clarifying questions to establish context, and then by provide well-structured answers with the important stuff flagged.
Explain how you will approach a task and why, and the risks and benefits of that.
Show that you have researched the company and role you're applying for.
When the interviewers ask questions that seem pointed, deal with them professionally.

Network

I find it tough to advise this one because I don't enjoy networking and I don't think I'm very good at it. However, I do know that making contacts with other testers, and hiring managers, can help you to get a job.

Try attending meetups regularly and talking to others about the fact that you are looking for work. Maybe show that you have something about you by asking questions after a presentation, questions that show you were listening and can think of angles that weren't covered.

Find testing conversations on social media and contribute where you feel comfortable to do so.

Smaller communities such as Slack groups for particular topics, or geographical areas, or types of role, might be an easier first step. They'll often have jobs channels that give you an idea who is hiring, and who the hiring managers are.

This is unlikely to be an overnight win tactic, but turning up in the same places as testers and test managers on a regular basis can make people aware of you and refer you when asked for recommendations.

Summary

Promote yourself. Find the things you've done that the company you want to join will value. Emphasise them. Don't apologise or make excuses for what you haven't done. Don't bullshit.

You want to get your foot in the door, not put it in your mouth.
Image: https://www.flickr.com/photos/oddsock/6226206588

P.S. The Association for Software Testing's Career Day webinar is worth a look and I saw that Nicola Lindgren has just published a book, Starting Your Software Testing Career, which covers some of the ground above and much more.

Comments

Meet Me Halfway?

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answ...

The Best Programmer Dan Knows

I was pairing with my friend Vernon at work last week, on a tool I've been developing. He was smiling broadly as I talked him through what I'd done because we've been here before. The tool facilitates a task that's time-consuming, inefficient, error-prone, tiresome, and important to get right. Vern knows that those kinds of factors trigger me to change or build something, and that's why he was struggling not to laugh out loud. He held himself together and asked a bunch of sensible questions about the need, the desired outcome, and the approach I'd taken. Then he mentioned a talk by Daniel Terhorst-North, called The Best Programmer I Know, and said that much of it paralleled what he sees me doing. It was my turn to laugh then, because I am not a good programmer, and I thought he knew that already. What I do accept, though, is that I am focussed on the value that programs can give, and getting some of that value as early as possible. He sent me a link to the ta...

Can Code, Can't Code, Is Useful

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested ...

Beginning Sketchnoting

In September 2017 I attended Ian Johnson 's visual note-taking workshop at DDD East Anglia . For the rest of the day I made sketchnotes, including during Karo Stoltzenburg 's talk on exploratory testing for developers (sketch below), and since then I've been doing it on a regular basis. Karo recently asked whether I'd do a Team Eating (the Linguamatics brown bag lunch thing) on sketchnoting. I did, and this post captures some of what I said. Beginning sketchnoting, then. There's two sides to that: I still regard myself as a beginner at it, and today I'll give you some encouragement and some tips based on my experience, to begin sketchnoting for yourselves. I spend an enormous amount of time in situations where I find it helpful to take notes: testing, talking to colleagues about a problem, reading, 1-1 meetings, project meetings, workshops, conferences, and, and, and, and I could go on. I've long been interested in the approaches I've evol...

Don't Know? Find Out!

In What We Know We Don't Know , Hillel Wayne crisply summarises a handful of research findings about software development, describes how the research is carried out and reviewed and how he explores it, and contrasts those evidence-based results with the pronouncements of charismatic thought leaders. He also notes how and why this kind of research is hard in the software world. I won't pull much from the talk because I want to encourage you to watch it. Go on, it's reasonably short, it's comprehensible for me at 1.25x, and you can skip the section on Domain-Driven Design (the talk was at DDD Europe) if that's not your bag. Let me just give the same example that he opens with: research shows that most code reviews focus more on the first file presented to reviewers rather than the most important file in the eye of the developer. What we should learn: flag the starting and other critical files to receive more productive reviews. You never even thought about that possi...

How do I Test AI?

Recently a few people have asked me how I test AI. I'm happy to share my experiences, but I frame the question more broadly, perhaps something like this: what kinds of things do I consider when testing systems with artificial intelligence components . I freestyled liberally the first time I answered but when the question came up again I thought I'd write a few bullets to help me remember key things. This post is the latest iteration of that list. Caveats: I'm not an expert; what you see below is a reminder of things to pick up on during conversations so it's quite minimal; it's also messy; it's absolutely not a guide or a set of best practices; each point should be applied in context; the categories are very rough; it's certainly not complete. Also note that I work with teams who really know what they're doing on the domain, tech, and medical safety fronts and some of the things listed here are things they'd typically do some or all of. Testing ...

Express, Listen, and Field

Last weekend I participated in the LLandegfan Exploratory Workshop on Testing (LLEWT) 2024, a peer conference in a small parish hall on Anglesey, north Wales. The topic was communication and I shared my sketchnotes and a mind map from the day a few days ago. This post summarises my experience report. Express, Listen, and Field Just about the most hands-on, practical, and valuable training I have ever done was on assertiveness with a local Cambridge coach, Laura Dain . In it she introduced Express, Listen, and Field (ELF), distilled from her experience across many years in the women’s movement, business, and academia. ELF: say your key message clearly and calmly, actively listen to the response, and then focus only on what is relevant to your needs. I blogged a little about it back in 2017 and I've been using it ever since. Assertiveness In a previous role, I was the manager of a test team and organised training for the whole ...

Software Sisyphus

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "How can I possibly test 'all the stuff' every iteration?" Whoa! There's a lot to unpack there, so let me break it down a little: who is suggesting that "al...

Not a Happy Place

A few months ago I stopped having therapy because I felt I had stabilised myself enough to navigate life without it. For the time being, anyway. I'm sure the counselling helped me but I couldn't tell you how and I've chosen not to look deeply into it. For someone who is usually pretty analytical this is perhaps an interesting decision but I knew that I didn't want to be second-guessing my counsellor, Sue, or mentally cross-referencing stuff that I'd researched while we were talking. And talk was what we mostly did, with Sue suggesting hardly any specific tools for me to try. One that she did recommend was finding a happy place to visualise, somewhere that I could be out of the moment for a moment to calm disruptive thoughts. (Something like this .) Surprisingly, I found that I couldn't conjure anywhere up inside my head. That's when I realised that I've always had difficulty seeing with my mind's eye but never called it out. If I try to imagine ev...

Why Question?

Questions are a powerful testing tool and, like any tool, can be used in different ways in different scenarios with different motivations and different results. A significant part of my role is generating questions and I will generally have a lot of them. I will rarely ask them all, though, and I've put a lot of time and effort into learning to be comfortable with that. A couple of examples: I was in a meeting this week where the technical conversation was too deep for me to give a perspective from a position of knowledge. I could have disengaged, but I didn't. Instead, I asked occasional questions, not wanting to derail the discussion or disrupt the flow. Some were detail questions, to help grow my understanding. Some were scoping questions, to help understand motivations. The one that really landed, however, was about the focus of the meeting. Although I couldn't contribute at a low level, I understood enough to suspect that we were not discussing the key problem tha...

Hiccupps

Search This Blog