Exploring a Career in IT

Choosing IT as a Career

New Zealand has a technology sector that punches well above its weight. From Wellington’s public sector digital transformation programmes to Auckland’s growing startup scene, there’s agenuine depth and variety of work on offer. If you’re weighing up whether a career in IT is right for you, here’s what the picture looks like right now.

Why IT in New Zealand Makes Sense

The demand for skilled IT professionals in New Zealand has remained resilient even through
tighter economic cycles. Organisations across banking, healthcare, government, energy, and
retail all rely on technology teams to function, and that need isn’t going away. For candidates,
that translates to a sector where strong skills are valued and rewarded.

Some of the most compelling reasons to consider IT as a career in New Zealand:

Consistent demand across industries. Every sector needs technology capability, which
means IT professionals have genuine choice about the kind of work they do and the
environment they do it in.
Strong salary benchmarks. Experienced IT professionals in New Zealand command
competitive salaries, and the contracting market can offer additional earning potential
for those who want it.
Variety within the field. IT is not one job. From user experience design to cloud infrastructure, from business analysis to cybersecurity, there are dozens of distinct pathways, each with its own flavour.
Remote and hybrid flexibility. The technology sector normalised flexible working early
and many IT roles continue to offer genuine flexibility around where and how you work.
A constantly evolving environment. If you enjoy learning and adapting, IT rewards that
disposition. The tools, languages, and approaches change regularly, which keeps the
work interesting.

Who Thrives in IT?

One of the most common misconceptions about IT is that it suits only one type of person. That
is simply not true. The IT professionals who do well over the long term tend to share a few
characteristics that cut across personality types:

Characteristic	Why it matters in IT
Curious about how things work	Whether it’s systems, people, or problems, curiosity drives better outcomes in almost every IT role.
Comfortable with change	Technology evolves rapidly. Professionals who adapt and keep learning tend to go further.
Strong communicators	Technical skills matter, but the ability to explain complexity clearly is what separates good IT professionals from great ones.
Problem solvers	IT is fundamentally about solving problems. The context changes, but this core skill stays relevant across every specialisation.
Detail-oriented but not rigid	The best technical people balance attention to detail with an ability to see the bigger picture.

Beyond these traits, IT welcomes people from a wide range of academic and professional backgrounds. Some of the most effective business analysts, project managers, and product owners started out in completely unrelated fields. A background in communications, health, finance, or the arts can actually be a genuine advantage when working in cross-functional teams.

“The job you end up applying for in ten years might not even exist yet. The best thing you can do is build transferable skills and stay curious.” Sian Clements, Younity

The NZ Tech Landscape at a Glance

Region	Character of the Market
Wellington	Strong public sector focus, significant government digital programmes, growing fintech and startup community
Auckland	Largest commercial market, strong in retail tech, banking, SaaS, telecommunications, and professional services
Christchurch and regional centres	Growing tech hub post-rebuild, strong in engineering tech, agritech, and health tech

Further Reading

NZTech Workforce Report Annual data on the NZ tech sector workforce, skill gaps, and employment trends. nztech.org.nz
Careers New Zealand: IT Careers Overview of IT career paths, qualifications, and earnings across different specialisations. careers.govt.nz
TechWomen New Zealand Resources and community for people entering or growing in the NZ tech sector. techwomen.nz

Different Pathways and Roles in NZ Tech

The IT sector is one of the most varied professional environments you can work in. Understanding the main role types, and how to find your fit within them, is the first step to building a career that actually suits you.

The Main Role Families

Rather than listing every job title (new ones appear regularly), it helps to think about IT roles in terms of what kind of work they involve:

Role Family	What it involves	Traits that tend to fit
Development and Engineering	Building software, applications, and systems. Includes software developers, full-stack engineers, backend engineers, frontend developers, mobile developers, and DevOps or DevSecOps engineers.	Strong logical reasoning, comfort with code, attention to detail
Data and Analytics	Working with data to generate insight or power systems. Includes data engineers, data scientists, database administrators, business intelligence analysts, and machine learning engineers.	Mathematical ability, pattern recognition, ability to translate data into stories
Design and Experience	Shaping how people interact with digital products and systems. Includes UX designers, UI designers, product designers, and service designers.	Creative thinking, empathy, curiosity about how people behave
Business Analysis and Product	Bridging the gap between business needs and technology solutions. Includes business analysts, product managers, product owners, and systems analysts.	Listening skills, structured thinking, ability to synthesise information and communicate clearly
Project and Programme Management	Coordinating delivery of technology initiatives. Includes project managers, programme managers, scrum masters, delivery managers, and agile coaches.	Organisation, stakeholder management, ability to navigate complexity and keep people moving
Infrastructure and Security	Keeping systems running and secure. Includes network engineers, cloud architects, security analysts, systems administrators, and cybersecurity specialists.	Methodical thinking, risk awareness, technical depth
Testing and Quality	Ensuring software and systems work as expected. Includes QA engineers, test analysts, automation testers, and performance testers.	Scepticism, thoroughness, ability to think about failure modes
Leadership and Architecture	Senior roles shaping technical direction. Includes solution architects, enterprise architects, technical leads, CTO, and head of engineering.	Strategic thinking, deep expertise, communication across technical and non-technical audiences

How Role Titles Evolve

Role titles in IT shift more quickly than in most other sectors. DevOps engineers barely existed as a job title fifteen years ago. Data scientists became a mainstream role only in the last decade. AI engineers and machine learning operations specialists are still evolving as distinct disciplines. This means a few things for people entering or transitioning in the sector:

Don’t get too attached to a specific job title. Focus instead on the kind of work and the skills it requires.
Titles vary between organisations. A ‘business analyst’ at one company might do work that another calls ‘product owner’ or ‘solutions consultant’.
New specialisations will continue to emerge. The candidates who thrive over a long career are those who build strong foundations and adapt, rather than those who narrowly optimise for a single role.

Switching Paths

It is entirely possible to change direction within IT, particularly if you are willing to find opportunities to build experience before making the move. Some practical approaches:

Identify the gap between where you are now and where you want to go. What skills does the target role require that you don’t yet have?
Look for overlap within your current organisation. If you’re working in help desk support and want to move into business analysis, there may be BA work happening that you could contribute to.
Volunteer your skills. Charities and community organisations often need technology help and will give you genuine experience in return.
Build and document your own projects. Side projects, open source contributions, and personal portfolios demonstrate initiative and capability.
Talk to people in the role you want. Informational conversations, whether at meetups or through LinkedIn, can save you months of guessing what a role actually involves day to day.

How to Know Which IT Roles Suit You

Choosing a direction within IT doesn’t have to be a stab in the dark. There are practical ways to work out what will suit you, and they all start with understanding yourself before trying to match yourself to a job description.

Start with How You Think and Work

Before looking at job titles, it’s worth spending some time honestly assessing the way you naturally approach work. A few useful starting questions:

Question	What it might suggest
Are you more logical or creative?	Both are valued in IT, but they tend toward different role families. Logical thinkers often gravitate toward development, infrastructure, or data. Creative thinkers often find their home in UX, product, or business analysis.
Do you prefer working with systems or people?	Some IT roles are deeply technical and relatively independent. Others, like project management or business analysis, are fundamentally about people and communication.
Do you like structure or ambiguity?	Testing and infrastructure roles tend to involve clear processes. Product and startup environments often require comfort with uncertainty.
Are you drawn to depth or breadth?	Specialists go deep in one area. Generalists or architects often work across many. Both are valuable, and both lead to different kinds of careers.
Do you want to build things or improve things?	Developers and engineers often build from scratch. QA, BA, and change management roles often focus on improving existing systems or processes.

Online personality and strengths assessments can also be useful here. Tools like the Myers Briggs Type Indicator, StrengthsFinder, or even free assessments like 16Personalities are not definitive, but they can surface things about how you work that you might not have put into words before.

Researching Roles Before You Commit

Once you have a rough direction, do some research before committing to a training path or job application:

Read ten to fifteen job descriptions for roles that interest you. Look for patterns in what is required. What skills, tools, and experiences come up repeatedly?
Reach out to people who are already doing the role. LinkedIn is useful for this. A brief message explaining that you’re exploring the field and asking if they’d be open to a short conversation is often warmly received.
Attend meetups in your area of interest. Auckland and Wellington both have active tech communities across different specialisations. Showing up is the fastest way to understand what a role actually feels like from the inside.
Look at what training or qualifications are commonly expected. Some roles (like cybersecurity or cloud architecture) have established certification paths. Others are more about portfolio and demonstrated experience.

Don’t Over-Pigeonhole Yourself

A word of caution: the traits above are useful starting points, not rules. Security engineers are not all detail-obsessed introverts. Product managers are not all extroverted storytellers. Business analysts are not all tidy note-takers. The best IT teams tend to have a mix of working styles within each role, and people who bring unexpected combinations of strengths often add the most value.

Building Skills and Experience Before You Apply

Getting your first IT role, or transitioning into a new area of IT, almost always requires some evidence of capability before a hiring manager will take a chance on you. The good news is that there are practical ways to build that evidence before you ever have a formal job in the field.

What Employers Are Actually Looking For

When it comes to entry-level or transitioning candidates, most hiring managers are looking for signals of three things: technical foundation, learning agility, and initiative. The specific technical skills matter, but they’re often teachable. What’s harder to teach is someone who takes ownership of their development and shows they can figure things out independently.

Practical Ways to Build Experience

Formal Study

Degrees and diplomas in computer science, information systems, software engineering, or IT remain a well-regarded foundation for many roles. They’re not always necessary, particularly in more experienced hires, but they provide structure and credential recognition. New Zealand universities and polytechnics offer a range of programmes. Shorter bootcamp programmes have also grown significantly in the last decade and can provide a faster route to job-ready skills, particularly in development.

Online Courses and Certifications

Platform courses from providers like Coursera, Udemy, LinkedIn Learning, and edX allow candidates to develop specific technical skills at their own pace. Certifications from major vendors (AWS, Microsoft Azure, Google Cloud, CompTIA, Cisco) carry genuine weight in the NZ job market, particularly for infrastructure, cloud, and security roles. These credentials demonstrate both the skill and the discipline to complete structured learning.

Side Projects and Personal Portfolios

For development, design, and data roles especially, showing that you build things in your own time carries significant weight. A GitHub repository with real projects, a portfolio website, a data analysis published on Kaggle, or an app you built for a personal need all demonstrate capability in a way that a CV bullet point never can.

Contributing to Open Source

Contributing to open source projects gives you real-world experience working on production-grade code with other developers. It also demonstrates collaborative skills and the ability to work within established systems and standards. Starting contributions to a project you actually use is often the easiest entry point.

Volunteering

Charities, community groups, and not-for-profit organisations frequently need technology help they can’t afford to hire for. Offering your skills in exchange for genuine project experience is a legitimate route to building your portfolio, and it’s one that many hiring managers view favourably.

Internal Opportunities

If you’re already working and want to transition into IT, look within your current organisation first. Many companies have digital transformation initiatives, IT projects, or cross-functional teams where someone from a non-technical background with the right attitude can contribute. Talk to your manager about your interest and ask if there are opportunities to get involved.

Area	Ways to build experience before your first role
Development and engineering	Side projects on GitHub, bootcamp projects, contributing to open source, coding challenges on platforms like LeetCode or HackerRank
Data and analytics	Kaggle datasets and competitions, personal analysis projects shared on GitHub, SQL practice on Mode Analytics or similar platforms
UX and design	Design portfolio on Behance or a personal website, volunteer UX work for community organisations, redesign case studies of existing apps or products
Business analysis	Documenting and analysing processes within your current role, volunteering for nonprofit project coordination, internal secondments
Project management	Leading initiatives in your current role (even informally), volunteer project coordination, online PM certifications like CAPM or Prince2
Cybersecurity	Practice environments like TryHackMe or HackTheBox, CompTIA certifications, participating in capture-the-flag competitions

Neurodiversity in Tech: Your Strengths Toolkit

The IT sector has long attracted neurodiverse professionals, and for good reason. Many of the cognitive profiles associated with ADHD, autism, dyslexia, and other forms of neurodiversity align naturally with the demands of technical work. At Younity, we see this regularly and believe strongly that neurodiverse candidates deserve to understand their own strengths and how to communicate them confidently.

What Neurodiversity Looks Like in IT

Neurodiversity is an umbrella term covering a range of differences in how people’s brains process information. In an IT context, candidates with these profiles are common, and many are exceptional at their work. Conditions that frequently appear in the IT community include:

Profile	Potential strengths in an IT context
ADHD (Attention Deficit Hyperactivity Disorder)	Often associated with hyperfocus on interesting problems, creative thinking, ability to work well under pressure, and strong ideation.
Autism Spectrum Conditions	Often associated with deep domain expertise, pattern recognition, methodical attention to detail, strong memory for technical specifications, and a direct communication style.
Dyslexia	Often associated with strong big-picture thinking, creative problem solving, spatial reasoning, and the ability to approach problems from unexpected angles.
Dyspraxia	Often associated with creative thinking, verbal reasoning, and persistence through complex problems.

The Assessment Challenge

One area where neurodiverse candidates can face genuine disadvantage is in formal technical assessments. Timed, exam-style tests reward a particular cognitive style and can underrepresent the capabilities of candidates who think differently. If you know that formal assessments are not where you show your best work, it is worth knowing that many employers, particularly those who work with recruiters like Younity, are open to alternative approaches such as portfolio reviews, whiteboard discussions, or take-home projects.

Some of the best performers in the business, when we’ve pushed employers to get their existing team to do a technical test, get 20% on the assessment. What does that tell you about whether the test is measuring what matters? Mark, Younity

Communicating Your Strengths Confidently

When it comes to applications and interviews, neurodiverse candidates often underestimate how valuable their different way of thinking is. A few practical approaches:

Lead with outcomes. Talk about what you have built, solved, or delivered. The results you achieved matter more than the process you used to get there.
Use concrete examples. ‘I find patterns in complex data quickly’ is more compelling when followed by a specific example of where you did that and what it produced.
Frame your working style honestly. You don’t need to disclose a diagnosis to describe how you work best. ‘I do my best work when I can go deep on a problem without interruption’ is completely professional and informative for an interviewer.
Find employers who get it. Some organisations actively value cognitive diversity on their teams. Ask interviewers how the team works, what the culture is like around different working styles, and how they support people to do their best work.

Seeking Support

If you’d like support navigating the job search process as a neurodiverse candidate, Younity’s consultants are experienced in working with candidates across a wide range of backgrounds and working styles. We’re happy to discuss how we present you to employers and to flag any concerns about specific steps in a hiring process.

Using LinkedIn and Other Platforms to Understand the Market

LinkedIn has become essential infrastructure for IT professionals in New Zealand. Whether you’re actively job hunting or simply trying to understand what the market looks like, using it well is a genuine competitive advantage.

Your LinkedIn Profile as Your Digital CV

Employers and recruiters will look at your LinkedIn profile before they meet you, and often before they respond to your application. Think of it as your always-on professional presence. Key elements to get right:

Profile photo. A clear, well-lit headshot makes you look approachable and professional. It doesn’t need to be expensive or formal. Just clear, and ideally you’re smiling.
Headline. Most people default to their current job title. A stronger approach is to describe what you do and what you’re good at. ‘Full Stack Developer specialising in React and Node.js’ tells more of a story than ‘Software Developer at XYZ Ltd’.
Summary. Use this section to describe where you’re headed, not just where you’ve been. Keep it concise, human, and authentic. AI-generated summaries are obvious and forgettable.
Work experience. Prioritise outcomes over responsibilities. ‘Led migration of legacy system to AWS, reducing infrastructure costs by 30%’ is more compelling than ‘Responsible for cloud migration’.
Skills section. Ensure your technical skills and tools are listed and current. Recruiters use keyword searches and your skills section directly affects whether you surface in them.
Featured section. Use this to link to your portfolio, GitHub, published work, or any projects you’re proud of.

Using LinkedIn as a Research Tool

Beyond your own profile, LinkedIn is one of the most useful tools available for understanding the NZ tech job market:

Follow companies you’re interested in. Their posts, job ads, and announcements will keep you informed about their direction, culture, and hiring patterns.
Connect with people in roles you aspire to. A genuine connection request with a short note about why you’re reaching out is usually well received.
Look at who companies have hired. The experience and backgrounds of recent hires in a target company can tell you a lot about what they value.
Engage with content in your area. Thoughtful comments on relevant posts get you noticed by people in the industry. You don’t need to publish constantly, but showing you have an opinion and can engage professionally is valuable.
Monitor what hiring managers and technical leaders are posting. Following the conversation tells you what people in your target field are thinking about and how they talk about their work.

Other Platforms Worth Knowing

Platform	What it’s useful for
SEEK	New Zealand’s dominant job board. Essential for monitoring advertised roles and understanding what employers are asking for.
Trade Me Jobs	Still relevant for certain sectors and smaller employers. Worth monitoring alongside SEEK.
GitHub	Critical for developers, data scientists, and engineers. Your public repositories are part of your professional profile.
Dev.to / Medium	Publishing technical articles or tutorials here demonstrates expertise and builds your professional reputation.
Industry Slack communities	Many NZ tech communities have active Slack groups where jobs are shared informally before being advertised. Worth finding the communities in your specialisation.
Industry meetups and events	Dev Day, SaaS conferences, fintech expos, and sector-specific events are excellent places to understand what’s happening in the market and meet people doing the work.

Exploring a Career in IT

Key takeaways

Choosing IT as a Career

Why IT in New Zealand Makes Sense

Who Thrives in IT?

The NZ Tech Landscape at a Glance

Different Pathways and Roles in NZ Tech

The Main Role Families

How Role Titles Evolve

Switching Paths

Further Reading

How to Know Which IT Roles Suit You

Start with How You Think and Work

Researching Roles Before You Commit

Don’t Over-Pigeonhole Yourself

Further Reading

Building Skills and Experience Before You Apply

What Employers Are Actually Looking For

Practical Ways to Build Experience

Formal Study

Online Courses and Certifications

Side Projects and Personal Portfolios

Contributing to Open Source

Volunteering

Internal Opportunities

Further Reading

Neurodiversity in Tech: Your Strengths Toolkit

What Neurodiversity Looks Like in IT

The Assessment Challenge

Communicating Your Strengths Confidently

Seeking Support

Further Reading

Using LinkedIn and Other Platforms to Understand the Market

Your LinkedIn Profile as Your Digital CV

Using LinkedIn as a Research Tool

Other Platforms Worth Knowing

Further Reading