Getting Into a Tech Job

Enter the Tech Career without a Tech Degree (or Any Degree)

Hey there 👋

Welcome to another issue of Arc - the writing sandbox.

I've been meaning to write about career roadmaps for a while now. Not because I love frameworks for every situation (even though they can work sometimes), but because too many people ask for them.

See, frameworks can be powerful. Roadmaps, templates, ladders - all of them can help you skip guesswork and accelerate progress. But only if you actually understand what they’re for. Most folks just stack a few LinkedIn carousels on top of each other and hope that solves their confusion. It doesn’t.

So that disclaimer aside, I want to share a roadmap that’s been useful to me - and many others like me - who wanted to break into tech without a traditional software degree. It’s simple, repeatable, and most importantly, realistic.

And yes, I’m also writing this so I can just send a link next time someone asks me “how do I get a job in tech?”

Everyone Knows Where the Money Is

It only takes 10 minutes at a public event to realize that most people know the game by now. If you want a career that pays well, evolves with time, and gives you remote options - you probably want to be in IT, tech, or digital.

That part’s obvious.

The problem is: everyone thinks that only means becoming a software developer.

They hear “tech” and instantly assume it means learning JavaScript, pushing code to GitHub, and crying over StackOverflow answers. And while that’s one valid path, it’s just one.

The tech world is wide. Wildly wide. There’s product, design, marketing, ops, QA, customer success, analytics - and a whole bunch of stuff in between. But no one tells you that at the beginning. They just hand you a Leetcode tutorial and a YouTube crash course and hope for the best.

The Roadmap That Actually Works (For Most)

This is the path I took. It's the same one I've seen many others take too.

It's not magic. But it works - especially if you’re starting from scratch with no degree, no experience, and no tech background.

Here’s why it works well:

• You don’t need an IT-specific degree. You don’t really need any degree.

• You don’t need experience. You can genuinely start here if you’re willing to learn.

• It gives you maximum exposure to how tech companies work - and lets you pivot later into different departments.

Let’s break it down.

What You Actually Need (Before You Apply Anywhere)

Just two things.

1. Good English Communication

This is non-negotiable.

You need to be able to speak, write, read, and listen in English with confidence. Not perfect grammar. Not accent training. Just good, solid, understandable communication.

If you’re unsure about your current level, take a test like IELTS. Not because it’s required, but because it’s a decent benchmark. And yes, it also helps on your resume.

If you're reading this, you’re already savvy enough to know that there are millions of free videos, courses, and apps (Duolingo, YouTube, podcasts) that can help you get better. So use them.

But please - don’t skip this step. It’s the biggest filter for entry-level jobs in tech.

2. Basic Computer and Tool Fluency

You’re trying to enter the digital world. You need to know the tools.

No one expects you to know Figma or Salesforce or Jira right away. But you should be comfortable with:

• Google Workspace or Office 365: Docs, Sheets, Slides, Email

• Email writing: Not just typing, but structuring replies, forwarding, etiquette

• Communication tools: Slack, Teams, Zoom, Meet

• Task management: Trello is a great place to start

This isn’t deep tech. It’s just digital literacy. Learn the tools people use every day.
It makes you hireable.

Your First Job

Once you know these 2 things here’s what you’re gonna do.

You're going to look and apply for Tech Support Representative jobs at Product Companies.

Why this combo?

If you read my recently article:

You know that the BPO/Call center world is full of scams.

The best way to avoid that is to apply to a Product company to start with. You can still go for a BPO style company - but it might not give you the result because of what is about to come.

See, in

• Product companies (ones that build their own software or app) tend to care more about how you think and communicate than what degree you have.

• These jobs often require no prior experience.

• They include 2–4 weeks of paid training - so you learn on the job.

• Lastly, you get exposure to multiple departments and start seeing how companies actually operate. This being the biggest factor you won’t find in a BPO style company normally.

Stick to companies that build and run their own apps or tools. Local or international.

You Got the Job. Now What?

You’re now a Tech Support Rep.

Your job is to understand the product, assist users, solve problems, and document tickets.

But beneath the surface, you’ll need to learn the following:

• What the product actually does

• How users behave and what they complain about

• What tools the team uses internally

• How decisions are made in the company

• Which departments you can shadow or collaborate with

You’re sitting at the crossroads of everything.

Use that position.

Stay curious. Stay useful. Ask questions. Volunteer for small extra things.

Because if you do this well for a year (sometimes even less), you’ll start seeing openings - roles in Ops, QA, Marketing, even Project Management.

And here’s the kicker: you’ll be the best candidate for those roles.
Because you already understand the product and the team.

Bringing the point back home, a lot of Product companies open internal hiring BEFORE external hiring. If you’ve been there, have put in the hours, know their Product, just with a few hours spent on side learning - you can easily transition into a new role.

Have trouble figuring out when to learn new things? Listen to this:

Why This Path is Underrated

Tech Support has a branding problem.

It gets lumped with BPOs, grunt work, “turn it off and on again” memes. So most ambitious people overlook it completely.

But the truth is: tech support at a product company is one of the most strategic places you can start your career. Especially if you don’t have a CS degree, a polished resume, or industry referrals.

Here’s why. And more importantly - how to leverage each part to move forward.

Get in the Door Without Experience

Let’s be honest: the tech industry gatekeeps hard.

• No degree? Rejected.

• No GitHub profile? Ignored.

• No startup experience? Ghosted.

But tech support roles at product companies tend to break that pattern. Why?

Because the bar to entry is set around soft skills and basic digital fluency - not technical credentials.

They’re looking for:

• Clear English communication

• A willingness to learn

• Patience and empathy with users

• A basic understanding of computers and web tools

That’s it.

This is the crack in the wall most people never notice. A rare case where you can enter a high-growth industry without having to fake credentials or undersell yourself. And once you’re inside? Everything changes.

How to leverage it:

• Don’t treat the job like a call center gig. Show up as a sponge.

• Ask questions during training. Understand why things are done a certain way.

• Get familiar with the product’s backend, workflows, and edge cases. This will set you apart from reps who just follow scripts.

Learn How the Sausage is Made

Most people in tech only see their slice of the product. Designers design. Devs code. Marketers market.

But tech support? You see everything.

You get a front-row seat to:

• What features users struggle with

• Which bugs go unprioritized (and why)

• How the dev team responds to escalations

• How product decisions are made (and where they fall apart)

• What the gaps are between what the company says - and what users actually feel

It’s like being the therapist, detective, and translator between the company and its users.

Done right, this role turns you into an internal knowledge hub. You’ll know more about the real-world usage of the product than most of the actual builders.

How to leverage it:

• Start documenting patterns. Which complaints show up the most? Which features are confusing users?

• Share insights during team meetings or write internal memos - yes, even if no one asked.

• Get good at turning chaos into clarity. This makes you look like a product thinker, not just a support rep.

This isn’t extra credit. It’s what high-impact product managers and operations folks eventually have to learn anyway. You’re just doing it from day one.

Build Trust Internally

There’s a shortcut to promotions that no one talks about: trust.

If people at your company trust you to be reliable, thoughtful, and useful - they will open doors for you. Tech support gives you more chances to build that trust than most early-career roles.

Why?

Because you’re interacting with:

• Product managers (for bug reports and feedback loops)

• Developers (for escalations and reproduction steps)

• QA teams (for testing edge cases)

• Operations (for customer data)

• Even marketing (if you help with tone, comms, or content)

You’re already in the room. You just need to show up with value.

How to leverage it:

• Be the rep who closes loops. If a dev asks for a bug video, deliver it fast and clearly.

• Be proactive in team Slack channels. Offer help. Share context. Surface recurring issues.

• Don’t just report problems - suggest fixes. Or better yet, help prioritize which issues matter most.

Most companies are starved for people who take initiative without stepping on toes. If you master that balance, people will remember your name.

Pivot to a High-Leverage Role Later

This is the part no one tells you: tech support is one of the best springboards for internal transitions.

Once you’ve been in the role for a year (sometimes even six months), you’ve got something that most other job applicants don’t:

Context.

You understand:

• The product

• The user pain points

• The internal tools

• The team’s working style

• The gaps between departments

That context becomes leverage. You can pivot into:

• Product Management: You already know the users’ voice. Learn how to turn that into feature requests.

• Quality Assurance: You’ve seen bugs in the wild. Now help prevent them upstream.

• Marketing/Content: You understand the language users respond to. Help refine messaging.

• Customer Success or Onboarding: You can prevent problems before they start.

• Ops or Biz Support: You already know the workflows and where they break.

How to leverage it:

• Start small. Shadow someone in the department you’re interested in.

• Take an online course to build some technical muscle. (e.g., product courses, marketing analytics, Notion/Excel mastery)

• Offer to help on an internal project outside your scope. That’s where the pivot begins.

• Ask your manager how you can grow. Set expectations early that you’re interested in more.

Remember: horizontal growth is easier when you’ve already proven you’re valuable.

You Get Paid to Learn

Most jobs expect you to know everything on day one. Most bootcamps and certifications charge you to learn.

But tech support? You get paid. To learn. On the job. In public. With real users. Inside a real product company.

There is no bootcamp in the world that can replicate that.

You learn:

• How teams work together (or don’t)

• How customers behave under stress

• How real software breaks (not just theory)

• How decisions get made when resources are tight

And you build the muscles that every other department eventually needs: communication, prioritization, triage, empathy, clarity under pressure.

How to leverage it:

• Think of the job as real-world training in how products and people actually work.

• Reflect weekly on what you’re learning; not just about the product, but about the company’s DNA.

• Document what you're good at and what you're curious about. That becomes the pitch for your next role.

This Isn’t Just a Theory

I’ve done this. I started in a role adjacent to tech support. I used that to learn, to connect, to move laterally. I’ve seen dozens of others do the same.

If you want to know my path, then go listen to this:

They started out answering tickets and now:

• Run product teams

• Manage QA departments

• Lead customer success orgs

• Build operational systems

The roadmap works. But only if you treat the job like a runway, not a rest stop.
This isn’t a dead-end. It’s a launchpad.
But you have to show up like you want to fly.

---

Now if you got this far, here is what I have to say.
Am I saying this is the only way to get into Tech if you don’t have a degree?
Certainly, No.

But it is a way that makes the most logical sense to me given the market conditions we have here. Time and time again, people come to me to ask about getting into the Tech Industry, and my default response has been this.

If you have a degree or a plan already that works, use that - THIS ISN’T FOR YOU.

But if you are someone who knows this is where they want to be, and have no idea where to start - Then perhaps this will be of use to you.

At the end of the day, you carve your own path, and the results you get, will vary based on what actions you took - all this article does is provide you with some direction.

If it helped, save it. Or send it to someone who’s asking where to start.
This is the link I wish someone had sent me years ago.

With or without my help – I wish you the best.

---

The Wandering Pro is a quiet, steady corner of the internet for people figuring out their next move in tech.

Whether you’re a freelancer, a junior developer, or someone building something for the first time - this is a space for showing up, learning, and making progress at your own pace.

No big promises. No hustle noise. Just a supportive community of people trying to get better - one challenge, one project, one honest conversation at a time.

If that sounds like what you need, come be a part of it.