Career change · Technology

Moving into tech from a non-tech background: roles, steps and honest limits

You do not have to become a software developer to work in technology. Many roles value domain knowledge, so start by matching your strengths to a role.

6 min read Last reviewed

On this page
  1. Roles to consider
  2. A practical plan
  3. Using what you already know
  4. Time, money and realism
  5. Frequently asked questions
  6. Official sources to check
  7. Keep reading
  8. More in What to study next

The short answer

You can move into technology from almost any field, and the easiest path is usually through a role that already uses what you know. A person from finance may move toward business analysis or data work in a finance team. A person from teaching may move toward learning design or customer training. Software development is one option among many, and it asks for the longest learning. Pick a target role, build the specific skills with small projects, document them, and apply for roles that match both the new skills and your background. Expect months, not weeks.

Admission rules change; confirm with the official notice.

Roles to consider

Directions, not promises. Entry needs differ by company.

  • Business or systems analystUses domain

    Turns business needs into clear requirements for technical teams. Draws on domain knowledge, writing and structured thinking.

  • Data analystGood first step

    Cleans and studies data, builds reports and answers questions. Spreadsheets, SQL and a visualisation tool are the usual start.

  • Software tester or QAEntry route

    Checks that products work as intended and designs test cases. A careful, curious mind helps; some coding is added over time.

  • Technical support or customer successEntry route

    Helps users solve problems with software. Communication matters most; technical depth grows on the job.

  • Technical writer or content designerUses writing

    Writes clear documentation and help content for products. Writing skill plus the ability to learn a product quickly.

  • UX researcher or designerPortfolio-led

    Studies how people use products and shapes designs. Draws on psychology, design or research backgrounds.

  • Software developerLonger path

    Builds software. Needs steady practice in programming, problem solving and tools, usually over a longer period.

A practical plan

  1. Choose one target role after reading five real job descriptions and noting the repeated skills.
  2. Study the basics in a structured order, using free or low-cost courses and official material where possible.
  3. Build two or three small projects that solve real problems from your own field, and write up what you did.
  4. Learn to explain your move: a short story that links your past work to the new role.
  5. Look for bridge opportunities inside your current employer, such as data tasks or tool rollouts.
  6. Apply in steps: internal moves, referrals, contract or junior roles, then wider applications.

Using what you already know

The strongest candidates from outside tech do not hide their past. They explain how it makes them useful. An accountant who learns SQL understands what a finance report should show. A nurse who learns product analysis understands clinical workflows. A teacher who learns UX understands learners. Companies building for finance, health, education or logistics often need people who know those worlds and can talk to engineers.

List the skills from your past work that transfer: writing, planning, negotiating, analysing numbers, handling clients, process thinking, regulatory knowledge. Then list the new tools you need, such as spreadsheets at an advanced level, SQL, a dashboard tool, basic scripting, a ticketing system, or a prototyping tool. A short list is easier to learn and easier to show.

Aim for a role where you are about two-thirds ready on day one. That keeps the learning curve manageable and your value clear.

Time, money and realism

Moving into a new field takes time. Many people need several months of regular study and project work, and the job search can take longer. Plan your finances so that a slower path does not push you into a bad decision. If you are working, keep your job while you learn and test a small project before you resign.

Entry-level hiring can be competitive and varies by city, company and year. Do not rely on someone else's success story. Talk to two or three people in the target role about what they did and what the first year was like. Ask for their honest view of how long it took and what they would do differently.

Be open to a step sideways. A support or analyst role can be a sound gateway to a more technical one after a year or two. Judge an offer by what you will learn, the quality of the manager and the people around you, not only by the job title.

Frequently asked questions

Not for every role. Some roles, especially in development, may prefer one, but analyst, testing, support, writing and design roles often accept other degrees plus skills and a portfolio.
It varies with your starting point, the time you can give and the market. Plan for months of consistent effort and treat any shorter claim with caution.
Only after checking its real outcomes, fees, refund terms and teachers. Compare it with free structured learning and decide what extra support you actually need.
It depends on the role. SQL and Python are common for data work, while JavaScript is common for web. Choose after reading job descriptions for your target role.
Yes, many people do. Experience in a field is an advantage in roles that need domain knowledge. Be realistic about the entry level and the learning time.
Certificates help structure learning but employers look for evidence of skills. Projects and clear explanations of your work carry more weight.
Build projects on real data or problems, write about what you learned, contribute to shared projects and keep a simple portfolio page.

Official sources to check

Use these for current rules and dates. We do not set or control admission criteria.

More in What to study next

This page is general information to help you plan. It is not admission, legal or career advice, and it does not guarantee admission, jobs or outcomes. Rules, eligibility and exams change, so always confirm with the official source.

Turn your options into a clearer plan.

A personalised PDF roadmap built around your background, goals and next steps.