Laid Off From Tech: Resume for a Move Into a Non-Tech Industry

A resume that tries to suit every non-tech employer ends up fitting none of them. Pick one industry and one or two kinds of roles, then pull up five to ten real job postings for them. Highlight the words that repeat: the duties, the tools, and the terms the industry uses for its own work. Tech skills often land in roles that don't look like tech from the outside. A product manager might aim at operations or program management at a hospital system. A software engineer might go for an internal systems or data role at a bank, insurer, or logistics company. A recruiter, marketer, support lead, or analyst can often keep the same job title at a company that sells something else. The postings tell you which of your experiences to push forward and which to cut. If five postings ask for vendor management and reporting, and your tech job included both, those items go near the top. The same goes for anything you did with budgets, compliance, or customers. Our guide on [tailoring a resume to a job description](/how-to-tailor-resume-to-job) covers the mechanics. For a non-tech move, the main point is to copy the employer's vocabulary wherever it honestly matches what you did.

A hiring manager at a regional bank or a manufacturer may not know what a sprint, a roadmap, or a stack is. An applicant tracking system may not find those words in the job posting either. Replace insider terms with plain descriptions of what you did and what changed because of it. A few swaps to try: - "Ran agile sprints" becomes "Planned and tracked two-week work cycles for a team of 8" - "Owned the product roadmap" becomes "Decided which projects the team would work on, based on customer feedback and budget" - "Managed stakeholders" becomes "Kept sales, finance, and customer support leads informed and agreed on priorities" - "Shipped features" becomes "Delivered new customer-facing tools on schedule" - "Reduced churn" becomes "Kept more customers from canceling" Here is a before and after for one bullet. The numbers are examples, so use your own real ones. Before: "Led cross-functional standups and managed Jira backlog for SaaS onboarding flow." After: "Coordinated a 9-person team across engineering, sales, and support to rebuild customer onboarding; cut average setup time from 14 days to 6." The second version says who you worked with, what you did, and what improved, and none of it needs tech knowledge. If you have no exact figure, use a safe approximation like "about," or describe scope instead, such as "for 40,000 customers" or "on a $300K budget." See [how to quantify achievements](/how-to-quantify-achievements) for ways to find numbers you didn't track.

A layoff is not a mark against you, and a mass layoff especially isn't. You don't need to put "laid off" on the resume at all. List the job with its dates, and if there is a gap since then, deal with it in your cover letter, a short note, or the interview. If you want to say something, keep it to one neutral line: "Position eliminated in company-wide reduction of about 20% of staff." Only include that if it's true and you're comfortable with it. Don't badmouth the company or explain at length. Be ready to answer the question out loud. Something like this works: "My team was cut when the company reorganized. I'd been thinking about moving into healthcare operations anyway, because I like work where the results affect real people, so I've spent the last few weeks learning how hospitals handle scheduling and billing." It's short, it's honest, and it points forward. If you've been out of work for several months, put what you've done in that time on the resume: a course, freelance work, or volunteering. Our articles on [resumes after a layoff](/resume-after-layoff) and [explaining employment gaps](/how-to-explain-employment-gaps) go deeper on wording.

Your summary is where you tell a non-tech reader why they should care. Name the role you want, give the strengths that carry over, and mention the industry. For example: "Operations and project professional with 7 years of experience managing budgets, vendors, and cross-team projects. Strong in process improvement, reporting, and training new users on software. Looking to apply these skills in healthcare administration." Avoid a summary that opens with "Laid-off software engineer seeking new opportunities." It leads with the loss and says nothing about what you can do. Titles need care. Some tech titles, like "Member of Technical Staff," "Growth Hacker," or "Customer Happiness Lead," mean little elsewhere. You can keep your official title and add a plain description after it, such as "Customer Success Manager (account management for 60 business clients)." Don't change your title to something you never held. Employers verify titles, and a mismatch can cost you an offer. In your skills section, keep tools that non-tech employers also use: Excel, SQL, Tableau, Salesforce, Jira, Smartsheet, Google Workspace. Trim a long list of programming languages and frameworks unless the job asks for them. A hospital data analyst posting wants SQL and reporting, not a list of 15 libraries. Put the skills that match the posting first. For more on this, see [transferable skills](/transferable-skills-resume).

Non-tech employers often worry about a few things when they see a tech background: that you'll leave when tech hiring picks up, that you expect tech pay, or that you won't like slower, more regulated work. Your resume can quietly answer those worries without mentioning them. Add signs of real interest in the industry. That could be a short certificate, an online course, a relevant license, or volunteer work. Examples include a food bank's inventory system for someone heading to logistics, a free-clinic scheduling project for someone aiming at healthcare, or a bookkeeping course for someone eyeing finance. Put these in a short "Training" or "Additional Experience" section near the top if they match the posting well. See [how to list certifications](/how-to-list-certifications) and [volunteer experience](/volunteer-experience-resume) for formatting. Prior contact with the industry also counts. If you built software for a hospital client, handled payments data, or supported a retail chain as a customer, say so: "Supported 30 hospital clients using our scheduling platform." Last, keep the format plain: one column, standard headings, a chronological layout, and one or two pages. Non-tech employers often use software that reads simple files best, and a clear layout helps the person skimming too. Save it as a PDF unless the application asks for Word. If you already have old resumes, performance reviews, or project write-ups, aNewJob can build the resume from those documents through a short interview, so you don't have to start from a blank page.