How to Get a Job in Tech: A Practical Plan for Any Background

To get a job in tech, pick one target role, build visible proof that you can do it (projects, a portfolio, a certification where the role values one), and get in front of hiring teams through referrals and targeted outreach rather than mass applications. Most people who follow that sequence for about three months will know whether it is working.

Definition: A tech job is any role at a technology company, or any technology role at a company in another industry. That includes engineers and data analysts, and also product managers, designers, salespeople, recruiters and operators at software and AI companies.

The second half matters. A lot of tech hiring happens outside the companies you can name.

The tech job market in 2026: harder at the entry level, not closed

The headlines swing between doom and boom. The data says something more boring and more useful: the market is open, but the bottom rung is crowded.

Start with new graduates. Per the New York Fed's tracker of recent college graduates (ages 22 to 27), the unemployment rate for that group held at about 5.6 percent in the second quarter of 2026, and the underemployment rate edged up to 42 percent.

The by-major numbers get shared the most. In the New York Fed's annual table (released in February 2026, built on 2024 Census survey data), computer engineering showed a 7.8 percent unemployment rate and computer science 7.0 percent, among the higher figures on the list. Treat those carefully: in our view, a single major's figure rests on a far smaller sample than the headline rate. The same table also shows the other side: underemployment of about 19 percent for computer science grads and 16 percent for computer engineering grads, against about 39 percent for all recent grads in that table. Weaker than a few years earlier? Yes. A collapse? The data doesn't show one.

Job postings tell a similar story. Indeed's index of US software development postings stood at 77.3 on September 18, 2026, where February 2020 equals 100. That is about 23 percent below the pre-pandemic baseline and roughly two thirds below the early-2022 peak, when the index topped 230. The frenzy is gone. The baseline demand is not.

Other signals point the same way:

Tech unemployment is still lower than the national rate. CompTIA's Tech Jobs Report for September 2026 (released October 2, 2026) put unemployment for tech occupations at 3.3 percent against a national rate of 4.2 percent. It also counted 625,633 active tech postings, the most in more than three years.
AI skills are spreading. CompTIA also found postings asking for AI-related skills up about 282 percent since May 2024.
The top of the market is hiring again. Gergely Orosz's Pragmatic Engineer, using TrueUp's tracking of openings at top-paying, mostly US tech companies, reported in May 2026 that those companies were hiring about 20 percent more than a year earlier, with AI engineering the fastest-rising demand.
Entry-level hiring plans improved in spring 2026. NACE's Job Outlook 2026 Spring Update (April 2026) found employers planned to hire 5.6 percent more graduates from the class of 2026, up from a projected 2.4 percent decline in the fall. It is a small survey (185 employers), so we'd read it as direction, not a forecast.
The long run still favors tech skills. The Bureau of Labor Statistics projects computer and information technology occupations to grow faster than the average for all occupations from 2025 to 2035, with about 280,000 openings a year. The group's median wage was $109,470 in May 2025, versus $50,980 for all occupations. Our guide to the fastest-growing tech careers breaks those projections down by role.
Tech talent is moving outside tech companies. CBRE's Scoring Tech Talent 2026 report found the finance, insurance and real estate sector added 90,530 tech jobs since 2022, while the high-tech industry shed 21,262.

Our read: the market rewards people who aim precisely and can show their work, and it is hard on generic resumes sent everywhere.

How to break into tech: map the roles before you pick one

Tech isn't one job. It's three rough families, and your background likely fits one.

Role family	Example roles	Proof that tends to help	Common way in
Technical	Software engineer, data engineer, QA, IT support, security analyst	Shipped code, a portfolio repo, a security or cloud certification	CS or related degree, bootcamp plus projects, internal transfer from IT
Hybrid	Data analyst, product manager, solutions engineer, technical writer, UX designer	Case studies, dashboards, a product teardown, writing samples	Analyst or support roles, domain expertise from another industry
Non-technical	Sales, customer success, marketing, recruiting, operations, finance	Results from a prior job, a quota you hit, a campaign you ran	Sales development, customer success, operations at a startup

A few notes on the map:

Technical roles have the clearest proof and the most crowded entry level. The BLS counts about 1.7 million software developers and projects 10 percent growth for developers, QA analysts and testers from 2025 to 2035.
Hybrid roles are where career changers often land. A nurse who learns SQL is a credible health-tech data analyst. Domain knowledge is the edge. For product management, Lenny Rachitsky has called an internal move at a larger company generally the easiest and quickest route in, ahead of junior PM programs or joining a startup.
Non-technical roles are the quiet front door. Sales development and customer success hire in volume at many software companies, and they teach you the product from the customer's side.

Pick one target role, not anything in tech

Being open to any tech job sounds flexible. To a hiring manager it reads as unfocused.

Pick one role and one or two adjacent backups. A simple way to choose is to score each option from 1 to 5 on three questions:

Evidence: could you show a hiring manager something real in the next eight weeks?
Fit: does your past work (any work) transfer to it?
Demand: do you see enough recent postings for it in your target locations?

Take an illustrative example. A 26-year-old retail store manager scores sales development 5, 4, 4 (13), customer success 4, 5, 3 (12) and data analyst 2, 3, 3 (8). The answer isn't data analyst, at least not first. It is sales development, with customer success as the backup.

Your target role then drives everything else: which projects to build, which people to contact and which postings to read. If AI is the pull, our guide on how to get a job in AI breaks that field down role by role.

Build proof that you can do the job

Hiring teams look for shortcuts. Proof is the one you control. If you're starting from zero, our plan for getting a tech job with no experience shows how to build it fast.

For technical roles, one finished project beats five tutorials. Build something a real person uses: a small tool for a club, a data pipeline for a local nonprofit, a bug fix merged into an open source project. Add a short README on the problem, your choices and what you'd do next.

For hybrid roles, make case studies. A data analyst candidate can publish two dashboards on public data with a one-page memo on what they found. A product candidate can write a teardown with three improvements and how to measure them.

For non-technical roles, translate past work into numbers: a store manager ran a team of 12 and grew monthly sales 18 percent. Then write a short account plan for one of the company's target customers.

Certifications help in some places and not in others. They tend to matter most in IT support, cloud and security, where employers often list them in the posting. Our rule of thumb: get one if postings for your target role keep naming it, and skip it if they don't.

What about a degree? The BLS notes software developers typically need a bachelor's degree in computer science or a related field, and large employers often screen for one. Without it, the path is narrower but real, usually through IT support, sales, customer success, QA or a startup that hires on demonstrated skill. Our guide to getting a tech job without a college degree covers those routes and their limits.

How to find a job in tech: get seen, don't just apply

Here's the math that should change your week. Per Ashby's 2026 Recruiter Productivity report (published April 2026, covering more than 100 million applications since 2021), applications per hire roughly tripled from 2021 to 2024 and averaged more than 300 through 2025, and candidates are about half as likely to get an interview as they were five years ago.

Blasting out 200 applications into that funnel mostly buys silence.

Referrals carry real weight. A study of call-center, trucking and high-tech firms by Burks, Cowgill, Hoffman and Housman (Quarterly Journal of Economics, 2015), found referred applicants were more likely to be hired and more likely to accept offers than non-referred applicants with similar observable characteristics, and they quit less. A referral doesn't make you a better candidate. It gets you read.

You may have heard that 80 percent of jobs are never posted. We haven't found solid data behind that number, so we'd treat it as a slogan. What the evidence does support is narrower: many roles are filled through networks, and a posting is often the end of a search, not the start. Our guide on how to find hidden jobs covers the unposted side in detail.

A weekly mix that tends to work better than mass applying:

Targeted applications: 8 to 12 a week, each to a role that matches your target, each with a resume tuned to the posting's language.
Outreach notes: 8 to 12 a week to people one level above the role or on the hiring team, ideally alumni or former colleagues.
Fresh postings first: apply within a few days of a posting going up. The 1752vc careers board shows each employer's own posting date, so on the startup track you can filter to Entry and Past 7 days and work only on recent roles. Our roundup of the best tech job boards covers the rest.

An outreach note you can adapt

Subject: Question about the [role] role on your team

Hi [Name], I saw the [role] opening on [team] and wanted to reach out directly. I'm moving into [target role] from [background], and I recently [one specific piece of proof, with a link]. I noticed [something specific about their product or a recent launch]. Would you be open to a 15-minute call, or pointing me to the right person? Either way, thanks for reading.

Keep it under 120 words: one detail about them, one piece of proof, one small ask.

How to get through tech interviews

Most loops test three things: can you do the work, can you explain your thinking, and would the team want to work with you.

Technical roles usually involve a coding screen or take-home, then live problem-solving, and for some roles a system design round. Practice out loud. In our view, talking through a half-right solution clearly can score better than a silent correct one.
Hybrid roles lean on case questions: how would you measure this feature, why did this metric drop, what would you build next.
Non-technical roles often include a role-play (a mock discovery call or a customer escalation) and questions about results you can quantify.

Expect it to take time. Ashby's data puts median time to fill at about 11 weeks (76 days) for technical roles and 8 weeks (56 days) for business roles, so a strong first month may not turn into offers until month three.

Before you accept, read the offer properly. At a startup, the equity can be a large part of the package; our guide to startup compensation and equity explains how founders think about it.

How to get into Silicon Valley, and whether you need to

Short answer: you don't have to move, but where you live still changes your odds.

The Bay Area remains the top-ranked tech talent market in CBRE's Scoring Tech Talent 2026 report, followed by Seattle, Toronto, New York and Austin. But the same report found New York's tech workforce grew to 394,300 between 2022 and 2025 while the Bay Area's shrank to 375,730, so New York is now the larger pool by headcount.

Remote work is real but narrower than social media suggests. Per the Survey of Working Arrangements and Attitudes (September 2026 update), 62 percent of full-time US employees were fully on site, 26 percent hybrid and 12 percent remote full time over September 2025 to August 2026. Information, finance and professional services had the most hybrid and remote workers.

What that means in practice:

Remote-only searches tend to be crowded, since applicants from anywhere can apply. Early in a career, a hybrid role in a city you can reach often has better odds, and you learn faster near people who know more than you.
If you want the Bay Area, consider getting there through a role, not a move. Join a company with an office there, then transfer.

On the 1752vc careers board you can filter by location, including remote and major US cities, to see where roles at your level are posted before deciding whether to move.

How to get your first tech job: a 12-week plan

Here is one illustrative plan for someone with 10 to 15 hours a week.

Weeks 1 to 2: choose and research. - Score three roles and pick one target plus a backup. - Read 30 recent postings for the target and list the skills that show up most. - Build a list of 40 target companies, mixing large companies, startups and non-tech employers that hire tech roles.

Weeks 3 to 6: build proof. - Finish one substantial project or two case studies tied to the skills you listed. - Rewrite your resume and LinkedIn around the target role, leading with results and proof. - Start five informational conversations a week with people in the role.

Weeks 7 to 12: get seen. - Each week: 10 targeted applications and 10 outreach notes, which adds up to 60 of each over six weeks. - Prioritize postings from the past week. On the 1752vc careers board, the AI jobs track and the startup track both filter by level and time posted. - Practice interviews twice a week, out loud, with a friend or a recording. - Track every application in a sheet with these columns: company, role, date posted, date applied, contact, referral (yes or no), stage, next step, notes.

If 60 notes produce, say, six to ten conversations and two or three interview processes, the system is working. If they produce nothing, the problem is more likely the target or the proof than the effort, so revisit week one before sending more.

"Isn't tech too saturated to start now?"

It's a fair question. Software development postings are well below their 2022 peak, applications per hire have tripled, and AI tools are changing what junior work looks like.

But.

Saturated is not the same as closed. Tech occupations still had lower unemployment than the national rate in CompTIA's September 2026 data, and the BLS still projects faster-than-average growth over the next decade. What changed is that the default path (apply widely, wait) works worse than it used to. A focused search with real proof still gets through, in our view.

Common mistakes

Applying to any tech job. It spreads your proof thin.
Collecting certificates instead of building things. Outside IT, cloud and security, a project usually says more.
Applying to postings that are weeks old. Fresh postings get read; old ones often already have finalists.
Hiding your past career. Domain knowledge from teaching, nursing or retail is an edge. Lead with it.
Treating rejection as a verdict. At over 300 applications per hire, a silent no usually says more about volume than about you.

Where we land

If we had to compress the advice: one role, real proof, warm paths, fresh postings, and a weekly rhythm you can sustain for three months.

That is our answer, not the answer. Your background, location and finances will change the mix.

To start, open the 1752vc careers board, filter by your level and Past 7 days, and save ten roles that match your target. If the startup path appeals, our guide on how to get a job at a startup goes deeper on choosing a stage and evaluating an offer.

The bottom line

The tech job market in 2026 is harder at the entry level and still open to people who aim precisely.

Applications get you counted.

Proof and people get you hired.

Key takeaways

The tech job market is tougher at the entry level in 2026, but tech unemployment (3.3 percent in CompTIA's September 2026 data) remains below the national rate.
Tech jobs span technical, hybrid and non-technical roles, many outside tech companies.
Pick one target role and build proof for it: a finished project, case studies or quantified results.
With roughly 300 applications per hire in Ashby's data, targeted applications and referrals tend to beat mass applying.
You don't need to move to Silicon Valley, but remote-only roles are a small and crowded slice of the market.
A 12-week plan (choose, build proof, then reach out) shows you whether your approach works.

Frequently asked questions

How do I get into tech with no experience?

Start with a role that values transferable skills, such as sales development, customer success, IT support or QA. Build one piece of proof for that role, like a project, a case study or a quantified result from past work. Then reach out to people on hiring teams directly, since referrals tend to get applications read faster than cold submissions do.

Can you get a tech job without a degree?

Yes, though the path is narrower. Many large employers still screen for degrees, and the BLS notes software developers typically hold a bachelor's. Without one, candidates often enter through IT support, sales, customer success, QA or startups that hire on demonstrated skill, and they lean more heavily on portfolios, certifications where postings ask for them, and referrals.

How long does it take to get a job in tech?

For a focused search, about three to six months is a reasonable expectation, though it varies widely. Ashby's 2026 data shows a median time to fill (from a role opening to a hire) of about 11 weeks for technical roles and 8 weeks for business roles, and the weeks you spend building proof come before that.

Where can I find entry-level jobs in tech?

Use job boards with level filters and posting dates, company career pages, university portals and your network. On the 1752vc careers board you can filter by Entry or Internship and by Past 7 days. Apply within a few days of a role being posted, and pair each application with a short note to someone on the team.

Do I need to live in Silicon Valley to work in tech?

No. The Bay Area still ranks first in CBRE's 2026 tech talent report, but New York now has the larger tech workforce, and Seattle, Austin, Boston and Washington are major hubs too. Remote-only roles exist, yet they are a small share of jobs and draw applicants nationwide, so a local or hybrid role can be easier to land.

Sources

Disclaimer: This guide is for general education only and is not legal, tax or investment advice. Laws, market data and program terms change, so it may not reflect the latest developments or fit your situation. Treat it as a starting point, not a source of truth, and talk to a qualified lawyer, accountant or financial adviser before you make decisions.