Anne Lambert says she 'stumbled' into software testing and loves it but doesn't have a lot of experience. She wants to know how to show employers she's a good risk. Showing how skills translate from one career to another is key, said resume consultant Elissa Poma. 'A lot of people are scared to try something new, because they feel like their resumes don't adequately prove they're qualified for the role,' she said. 'That doesn't have to be the case.' Poma recommends using a functional-style resume instead of a chronological one. That keeps it focused on what Lambert knows how to do -- not exactly what she did. To start, look at job postings and resumes of people already in software testing and determine the key traits for a good tester. Under three or four broader headers -- such as project management, research and analysis, or communications -- Lambert should give examples of work she has done that demonstrate those skills. Experience related to software testing goes first. Poma says Lambert should make sure the examples are descriptive, clear and specific. She needs to show how her experience and skills are similar to those that a software tester with more experience would have. The current resume has 'a case of the vagaries,' Poma said. Lambert can fix that with numbers and details about money saved, people supervised and exact roles taken. Wrap up the resume with a simple list of work experience, with titles, companies and dates; education information; and skills and other accomplishments, Poma recommends. 