New Zealand’s tech sector runs on code, and an increasing share of that code is written by women who got here through wildly different doors. This is not an inspiration piece. It is a snapshot of three routes into the profession — career switching, computer science degrees, and self-directed learning — and what happens after the entry point.
Not a Novelty Story
The State of the Numbers
Roughly 27 percent of the New Zealand tech workforce is female, according to the most recent NZTech figures — a number that has budged only slightly in the past decade. That stat gets trotted out every March for International Women’s Day and then quietly shelved until next year. But it obscures something more interesting than its own mediocrity: the composition of that 27 percent is shifting. More women are entering as software engineers and developers rather than clustering in project management, UX, or support roles where the industry traditionally made room for them. The pipeline into code-writing roles specifically has widened, even as the overall gender split stays stubbornly lopsided.
Stats NZ workforce data shows the information and communication technology sector growing faster than most, with software development leading that charge. Inside that growth, women are a larger share of new entrants than of the existing workforce — meaning the ratio is improving through inflow, not because the industry suddenly developed a conscience. The women writing production code in 2026 got here through routes their predecessors rarely had access to. Understanding those routes matters more than hand-wringing over a percentage.
Why This Piece Is Not About Inspiration
There is a genre of tech journalism that frames every woman who writes code as a brave exception. She overcame. She persevered. She is now available for your next diversity panel. This is not that article. The women profiled here — composite characters drawn from real patterns across the sector — are not exceptional for being women. They are doing the ordinary, difficult work of building software in a small country with an outsised ambition for its digital economy.
The point is not to inspire anyone. It is to describe, as accurately as possible, what it actually looks like when women hold engineering roles across Auckland, Wellington, Christchurch, and the growing number of remote-first companies that technically exist in a co-working space in Tauranga. The daily texture of writing code, shipping features, arguing about architecture, and navigating a profession that still reflexively assumes competence looks like a bloke in a hoodie. The ordinary reality is the story.
Three Routes Into the Profession
The women writing New Zealand’s code did not all arrive via the same door. Three routes dominate. The first is the career-switcher — someone who spent years in another profession before retraining through a programme like Dev Academy Aotearoa or the University of Auckland’s postgraduate diploma in software engineering. The second is the computer science graduate who picked her major at 18, survived the attrition curve, and is now mid-career with a decade of production experience. The third is the self-taught developer who pulled herself through online courses, open-source contributions, and sheer stubborn experimentation until someone gave her a junior role.
Each route has its own costs and advantages. The career-switcher brings domain knowledge but faces a credibility gap. The CS grad has the credential but may have spent her twenties as the only woman in the room. The self-taught developer has proven grit but often finds her lack of formal qualification used against her at promotion time. None of them got here easily. All of them are building the systems that New Zealanders use every day.
The Career Switcher

From the Classroom to the Codebase
She was a Year 5 teacher in Lower Hutt for eight years before she enrolled at Dev Academy Aotearoa in Wellington. The decision was not a lightning bolt. It was a spreadsheet: teacher salary trajectory on one side, developer salary range on the other, and a growing certainty that she could not keep doing a job she loved in a system that was grinding her down. The 15-week bootcamp was the most intellectually intense experience of her life, and she includes giving birth in that comparison.
The transition period is the part nobody warns you about. Between finishing the programme and landing her first role at a Wellington-based SaaS company, four months passed. Four months of imposter syndrome so thick she could taste it. Her first PR was twelve lines of CSS. Her tech lead reviewed it like it was a moon landing. What she brought that her CS-grad colleagues did not was an instinct for explaining complex things clearly — a skill honed by teaching nine-year-olds fractions. Within two years she was writing technical documentation alongside feature work, and the company had quietly restructured its onboarding around materials she created.
What Gets Lost and What Gets Gained
The salary reset is real and nobody should pretend otherwise. Going from an experienced teacher’s salary to a junior developer’s pay meant a drop of roughly fifteen thousand dollars in her first year. The financial maths only works if you trust the trajectory, and trusting trajectories requires a privilege that not everyone has — savings, a partner’s income, or the willingness to take on debt through programmes like the Student Allowance system.
What she gained was harder to quantify but impossible to ignore. A professional identity that felt chosen rather than defaulted into. Colleagues who engaged with ideas on merit rather than seniority. And a growing realisation that software teams starved of diverse thinking produce mediocre software. Her background in education gave her a structural understanding of how people learn, which turned out to be directly useful in pair programming, code review, and the daily negotiations of collaborative development. The teams that hire career-switchers and then try to sand off everything that makes them different are missing the point entirely.
The CS Graduate Who Stayed
Surviving the Degree
She started her Bachelor of Science in Computer Science at the University of Canterbury with a cohort that was maybe 18 percent women. By third year the number had halved. Not because the women were failing — their grades were comparable or better — but because the environment had a slow erosive quality that is difficult to pinpoint and impossible to ignore. Group projects where her contributions were reflexively checked by male teammates. Tutors who addressed questions to the men in the group. A social culture built around LAN parties and energy drinks that she could technically attend but never felt designed for.
She stayed because she was stubborn and because the actual material — algorithms, systems architecture, database theory — fascinated her in a way that felt non-negotiable. The University of Canterbury’s School of Computer Science has made genuine efforts to improve retention, including mentoring programmes and revised teaching approaches. But the structural issue is upstream: by the time women reach third-year CS, they have already survived a filtration system that was never consciously designed to exclude them but does so anyway, with mechanical efficiency.
A Decade In and Still Proving It
Ten years into her career she is a senior software engineer at a mid-size Auckland firm that builds logistics software. She designs systems that handle millions of transactions. She mentors junior developers. She has opinions about microservices that she will defend with whiteboard diagrams and controlled fury. And she still, with grinding regularity, gets mistaken for a project manager in meetings with new clients.
The credibility tax at her level is not the overt hostility of university days. It is subtler: a slight pause before her technical recommendation is accepted, a tendency for her ideas to gain traction only when restated by a male colleague, performance reviews that praise her communication skills while her male peers get praised for technical brilliance. She has learned to document everything. Her architecture decisions come with written rationale not because the company requires it but because she learned early that verbal proposals from women evaporate from institutional memory faster. The documentation habit, born from necessity, has actually made her a better engineer. She is aware of the irony.
The Pipeline Problem Nobody Wants to Own
The pipeline framing is convenient because it lets everyone point at the stage before theirs. Universities blame high schools. High schools blame cultural norms. Cultural norms blame nobody because they are not a person. Meanwhile the actual throughput of women completing CS degrees in New Zealand remains stubbornly low. Universities New Zealand data shows computing and IT enrolments growing overall, but the gender split within those numbers has barely shifted.
The fixes that work are boringly practical. Visible role models in teaching staff — not visiting speakers for one-off events but permanent faculty who look like the students they are trying to retain. Assessment structures that do not penalise collaborative learning styles. Intervention at the first sign of disengagement rather than after the withdrawal form is signed. Canterbury, Victoria University of Wellington, and the University of Auckland have all experimented with these approaches to varying degrees of success. The evidence is clear on what helps. The bottleneck is institutional willingness to fund it at scale and sustain it beyond the initial enthusiasm of a single champion.
The Self-Taught Developer

Building a Career From Tutorials and Grit
She learned to code on her couch in Christchurch during the pandemic, working through freeCodeCamp tutorials after her hospitality job evaporated overnight. Nobody told her she could be a developer. She googled “jobs you can learn online” and started clicking. Two years later she had a GitHub profile with a dozen projects, a portfolio site built from scratch, and precisely zero formal qualifications in software engineering.
Getting the first job was an exercise in creative persistence. She applied to forty-seven positions before landing an interview at a Christchurch startup that was more interested in her portfolio than her CV. The technical interview nearly ended her — not because she could not code but because whiteboard algorithm challenges test a very specific kind of knowledge that self-taught developers acquire unevenly. She got the role because the hiring manager had the good sense to also assign a take-home project, where she built a functional API in a weekend that was cleaner than what several CS graduates had submitted. The credential gap is real, but companies that treat degrees as a proxy for competence are filtering out talent they cannot afford to lose.
The Gaps and How They Close
The honest version of the self-taught story includes the gaps. She did not know what a design pattern was until six months into her first role. Her understanding of networking was shaky. Git was a mystery she solved through memorised commands long before she understood what was happening underneath. These are not trivial gaps and pretending they do not exist does self-taught developers no favours.
What closed them was a combination of on-the-job learning, a senior developer who took mentoring seriously rather than treating it as an HR checkbox, and communities like She Sharp and the local Python NZ meetup group. The meetup circuit in particular gave her access to the informal knowledge transfer that CS graduates absorb through osmosis during their degrees: how to read documentation efficiently, when to optimise and when to ship, the unwritten rules of professional software development. Within eighteen months the gaps were functionally closed. What remained was a developer with a distinctive problem-solving approach — less bound by conventional patterns, more willing to question assumptions, and ruthlessly practical about what actually needs to work versus what would be theoretically elegant.
What They Build Together
The Companies Getting It Right
A handful of New Zealand tech companies have engineering teams where women make up more than a token presence. Xero has been public about its diversity targets and, more importantly, about the structural changes underpinning them: standardised interview rubrics, promotion criteria that value collaboration alongside individual contribution, and parental leave policies that do not treat having children as a career interruption. Vend (now part of Lightspeed) built engineering culture around pair programming, which had the side effect of making it harder for anyone to be invisibly sidelined.
Smaller companies often get it right by accident of founder values. A Wellington fintech startup with a female CTO hired its first five engineers on technical merit and ended up with three women on the team — not because of quotas but because the hiring process did not inadvertently filter them out. The pattern across companies that achieve genuine balance is remarkably consistent: structured interviews, clear promotion pathways, flexible working arrangements treated as normal rather than accommodations, and at least one senior woman in a technical role. None of this is revolutionary. It is just rare.
The Infrastructure You Do Not See
The software these women build is not abstract. It is the IRD tax system that processes your return. It is the hospital patient management software that tracks appointments across a district health board. It is the freight logistics platform that gets groceries to supermarkets in Queenstown and Invercargill. It is the banking app you check six times a day. Women software engineers in New Zealand are building the infrastructure that the country runs on, and they are doing it with the same mix of skill, frustration, and caffeine dependency as their male colleagues.
What makes their contribution worth naming specifically is not that it is better or different in kind. It is that it exists at all in a profession that spent decades telling them it was not for them. Every line of production code written by a woman in this country is also a quiet rebuttal to the cultural assumption that software engineering is inherently male. The code itself does not care who wrote it. The profession should be equally indifferent, and the fact that it is not is worth examining with clear eyes rather than motivational slogans.
What Comes Next
The next generation of women software engineers in New Zealand will have more pathways into the profession than any that came before. The expansion of bootcamps, the normalisation of career switching, the slow improvement in university retention, and the growth of remote work that lets women outside Auckland and Wellington access roles previously concentrated in two cities — all of these trends are compounding. The Ministry of Business, Innovation and Employment projects continued strong demand for software developers through the end of the decade.
But access is not the same as retention, and the sector has a historical pattern of opening doors and then making the rooms behind them uncomfortable enough that women leave. The women profiled here — the career-switcher, the CS graduate, the self-taught developer — are all still in the industry. That is not guaranteed. Retention depends on the daily experience of doing the work, and that experience is shaped by management practices, team culture, and the thousand small signals that tell someone whether they belong. The code is the easy part. The culture is the work that remains.
The women writing New Zealand’s code are not a trend piece or a diversity statistic. They are engineers building the systems this country depends on, and they arrived through every pathway the profession offers. The only question worth asking now is whether the industry will make staying as possible as arriving.