Tech Job Market Research 2026: AI Skills, Cybersecurity, Data, and Software Roles After the Slowdown
By Priya Raman
Research the 2026 tech job market with BLS data on AI-adjacent roles, cybersecurity, data science, software, and how candidates should position evidence.
Job Market Insights | Published 2026-05-30
The U.S. tech market has different signals by industry, occupation and time horizon. Use dated BLS measures carefully, then test a specific role lane against current postings and your own evidence.
August 2026 U.S. information-industry payrolls fell by 23,000, while BLS projects about 280,000 average annual openings in computer and IT occupations from 2025 to 2035. July JOLTS counted 7.3 million openings and 5.1 million hires across nonfarm employers. These measure different populations and periods, not current tech vacancies. Choose a technical lane using current local postings and show role-specific production, data, security or AI workflow evidence.
Short answer For a 2026 technology job search, separate current information-industry payroll data from decade-long occupation projections; they answer different questions. Use local postings to choose a target lane among cybersecurity, data, software, cloud and infrastructure, AI implementation, or technical management. Then connect your experience to the role's risks, decisions, and outcomes. The tech market is not one market The U.S. BLS August 2026 Employment Situation reported that information-industry employment fell by 23,000, after losses averaging 8,000 a month over the prior 12 months. That is an industry payroll measure, not a count of all technology occupations or technical job openings. The BLS Occupational Outlook Handbook projects about 280,000 average annual openings in computer and information technology occupations from 2025 to 2035, including growth and replacement needs. That is a decade projection, not today's posting count. The short-term industry measure and long-term occupation projection answer different questions. Short-term context Read the information-industry payroll series as one broad sector indicator; it does not count technical vacancies. Long-term projections Use occupation projections as decade-scale context, then check current postings for the role, location, and level you want. Candidate evidence Build examples that show how you shipped, secured, measured, automated, or explained technical work. Where the demand signal is strongest BLS 2025 to 2035 occupation projections show growth of 35% for data scientists, 21% for information security analysts, 22% for computer and information research scientists, 10% for software developers, 12% for operations research analysts, and 16% for computer and information systems managers. These are different occupations with different entry paths. A projection is not a ranking of current vacancies, so use recent local postings to choose a realistic lane. Demand pocket Roles to watch Evidence that travels well Cybersecurity Information security analyst, security engineer, GRC analyst, cloud security. Threat modeling, incident response, access control, vulnerability remediation, audit readiness, risk communication. Data and analytics Data scientist, data analyst, analytics engineer, BI developer. Decision impact, experiment design, data quality, stakeholder requirements, model limits, dashboard adoption. Software and platform Software developer, QA engineer, platform engineer, site reliability. Shipped systems, reliability, test coverage, incident learning, performance, maintainability, user outcomes. AI workflow implementation AI product roles, automation engineers, internal tools, AI operations. Human review, evaluation, privacy-aware prompts, workflow redesign, measurable time saved, quality controls. Technical leadership Engineering manager, systems manager, technical program manager. Prioritization, roadmaps, cross-functional alignment, hiring, delivery tradeoffs, risk management. How to document AI work "AI experience" is too broad to be useful. If a posting mentions AI, identify whether the work is using tools in a workflow, building or integrating a system, or evaluating and governing model behavior. These are different kinds of experience. A verifiable account can say where AI assisted, how output was checked, what sensitive-data controls were used, and which measure or decision changed. If you did not measure an outcome, describe the process and its limits without implying a result. AskMyCareer's AI job-search agents guide also discusses keeping human relevance in an automated workflow. Illustrative examples, not reported candidate outcomes: Replace the wording below with work you can substantiate. Weak AI claim "Used AI tools to be more productive." This is vague and easy to ignore. Stronger AI proof "Designed a human-reviewed triage workflow, defined a quality check, and kept escalation decisions with support leads." Weak data claim "Built dashboards." This says little about decisions or quality. Stronger data proof "Aligned churn metric definitions with sales and customer success, then validated them before renewal planning." Use JOLTS to keep the market in perspective The BLS July 2026 JOLTS release reported 7.3 million U.S. nonfarm openings on the month's last business day and 5.1 million hires during the month. JOLTS is an economy and industry measure, not a count of technical occupations. Read it alongside the information-industry payroll series and long-term occupation projections without treating them as interchangeable. For your own search, record current postings, location, seniority and response rates in the lane you are targeting. Change the evidence you lead with if one lane responds differently from another. For each target role, ask why this work matters to the organization now. Use the posting to connect your examples to revenue, risk, customer retention, security, efficiency, compliance, reliability, or product velocity. Describe the problem, your action, and the outcome instead of relying on a tool list alone. If the company says... They may be testing... Prepare evidence for... "We need someone who can move fast." Can you ship without creating cleanup work? Scope control, tests, reviews, rollback plans, prioritization. "We are using AI more." Can you improve productivity without lowering quality? Evaluation, human review, privacy, workflow design, measurable outcomes. "Security is a priority." Can you reduce risk without blocking the business? Threat modeling, access control, vendor risk, incident response, communication. "The role is cross-functional." Can non-technical teams trust you? Requirements discovery, tradeoff framing, stakeholder updates, adoption metrics. Quick local audit (method only, not a market count): Collect 20 distinct current postings in one metro or remote-eligible market, at a level you could apply for, across no more than two lanes. Search role-title variants, such as security analyst or engineer, data scientist or analyst, and software developer or engineer, then remove duplicate requisitions. Record collection date, posting date if shown, source URL, lane, level, work arrangement, required versus preferred skills, business domain, evidence requested, pay if listed, and whether AI or security is a core duty or an incidental mention. Compare counts only within this sample, and keep your own applications and responses separate from posting counts. Application strategy for tech candidates in 2026 Use your posting sample and application results to decide how to allocate effort. One option is to tailor deeply for high-fit roles and keep a lighter pipeline of adjacent roles where your evidence maps clearly. Track responses by lane so your next adjustment is based on your own results. Pick a technical lane Do not present as "software, data, AI, product, security, and strategy" unless you can prove the overlap. Lead with the lane the posting actually needs. Write proof-based bullets Use shipped systems, scale, reliability, incident reduction, customer impact, cost savings, adoption, model quality, or risk reduction. Avoid tool-only bullets. Build a portfolio that explains decisions For public work, show constraints, architecture, tests, tradeoffs, and what you would improve. Show the decisions, constraints, and tradeoffs behind public work, not only screenshots. Prepare for follow-up questions Practice explaining failures, tradeoffs, AI limits, privacy, system behavior, and how you worked with non-technical partners. Use AskMyCareer's resume-to-interview workflow to keep the resume claim and the interview story connected. If a bullet says you improved performance or security, store the decision path behind it before the interview. What career changers should do differently If you are changing careers, make the bridge between prior work and a technical target explicit. Possible bridges include healthcare operations to health data, finance operations to analytics, support to technical support or customer engineering, compliance to security GRC, operations to automation, or design to front-end or product systems. Illustrative scenario: A scheduling-dashboard story could name the operational problem, the data used, and a measurable result such as fewer uncovered shifts, if you have reliable data for it. "Built a dashboard" alone does not show which problem or decision the work supported. Choose one target lane and one adjacent backup lane. Translate prior domain knowledge into technical advantage. Use projects that mimic business constraints, not toy-only examples. Prepare stories about ambiguity, stakeholder management, and learning under pressure. Track response rates by role type so you can revise evidence rather than panic-apply. How AskMyCareer helps tech candidates stay precise AskMyCareer helps you keep technical evidence from fragmenting across resumes, portfolios, interview notes, and job boards. Store each technical project in the career graph builder with the problem, stack, constraints, stakeholders, measurable outcome, and what you learned. Then use the job application tracker to connect that proof to each role. This is especially useful for AI and security claims. The same project might be framed as workflow automation for an operations role, risk control for a security role, or product analytics for a data role. The evidence stays consistent; the angle changes by role. Frequently asked questions Can BLS tell me which tech jobs are open near me? No. The cited payroll series and decade-long occupation projections do not count current local postings by role. Use the local audit above as a dated sample, not a total vacancy count. Does every tech role require AI skills? No. Check whether the posting names AI as a core duty, an optional tool, or not at all. If it is relevant, be specific about the type of work and how you reviewed results and managed quality, privacy, and security. Next step Make your technical proof role-specific Use AskMyCareer to turn projects, incidents, automation work, and AI experiments into resume bullets and interview stories that match the role. Connect resume to prep Build technical evidence