Job Description

The role of the BA has never mattered more

Everyone can write a requirements document now. AI can summarise a meeting, generate user stories, and produce a BRD from a transcript. That’s not the job anymore and honestly, it never really was.

The job is being the person in the room who asks the question nobody else thought to ask. Who can tell a client “that’s not actually your problem” with enough credibility that they listen. Who knows when to slow a project down because the brief isn’t right yet, and when to accelerate because the team has everything it needs.

That’s what we’re hiring for. A BA who brings structure to ambiguity, builds trust quickly with clients, and can hold the space between business intent and technical delivery without flinching when the two don’t align.

About Enlighten Designs (Te Toi Hapara)

We’re an award-winning data and software agency, one of New Zealand’s leading Microsoft Partners, and at the forefront of AI-enabled delivery. From Waikato to the world, we design and build intelligent technology solutions that create real impact for our clients.

With 25+ years behind us and the energy of a start-up, we combine deep technical capability with a genuinely people-first culture. We recently sponsored Outstanding AI Implementation at the Aotearoa AI Awards. We care about doing great work, building strong relationships, and creating an environment where talented humans thrive.

A week in your life

No two weeks are the same, but here’s a flavour:

• Monday: You’re facilitating a discovery workshop for a new client. You’ve prepared a Miro board, read their industry, and put together a set of questions designed to surface what they haven’t said yet. By the end you’ve mapped the current state, identified pain points the client hadn’t explicitly named, and you know what the next phase needs to look like.
• Tuesday: You’re writing up yesterday’s findings. You’re doing the work that actually takes judgement deciding what matters, what’s noise, and what the BRD needs to say to be genuinely useful to a dev team six weeks from now.
• Wednesday: You’re doing a job shadowing session at a client’s site alongside one of our UX designers. You’re watching two users do their actual jobs, not describing them but doing them. The gap between what came up in Monday’s workshop and what you’re seeing now is significant. You’re capturing it in real time, and by the end of the afternoon you and the UX designer are aligning on what the requirements need to say versus what the interface needs to do.
• Thursday: A smaller client has a new idea. It’s not a big project, maybe a gap analysis or a prioritisation workshop, but they’re a growing account and the relationship matters. You scope it, write the quote, and send it across. That’s organic growth that wouldn’t have happened without you.
• Friday: You’re presenting discovery findings to a leadership team. You’ve got a set of slides, a clear recommendation, and the confidence to hold the room when someone pushes back on the numbers.

What you’ll be doing

• Leading discovery engagements: facilitating workshops, mapping current state, defining problems, and shaping solution options clients can actually evaluate
• Running job shadowing and user walkthrough sessions, getting alongside real users to understand how work actually happens, not just how it’s described in a meeting room. The best requirements come from observation, not assumption
• Partnering with UX designers to connect business requirements to user experience. You bring the business intent, they bring the design lens, and together the brief gets sharper
• Writing requirements that a development team can work from, clear, traceable, and grounded in real business intent
• Building trusted advisor relationships with clients across a range of industries and sizes
• Using AI-augmented workflows to work faster without compromising quality — knowing which parts of the job AI accelerates and which parts still require a human in the room
• Contributing to scoping, estimation, and proposal work alongside account managers and solution leads
• Keeping delivery teams honest — flagging when scope drift is happening, when a brief needs revisiting, or when a client conversation is overdue
• Growing accounts you own by staying curious about what the client needs next

What you bring

You’ve worked on enough projects to know that a requirements document no one reads isn’t a deliverable, it’s a liability.

• 2–4 years of BA experience, ideally in a consulting or agency environment
• Demonstrated client-facing skills. You’ve run sessions, presented findings, and had the hard conversations
• Strong workshop facilitation: you can hold a room, manage time, and draw out the people who aren’t talking
• A comfort with ambiguity, you don’t need a perfect brief to get started, and you know how to structure your way to clarity
• Some exposure to integration or enterprise projects. You don’t need to speak API, but you need to know when the technical complexity changes the requirements conversation
• Comfort working in a multi-discipline team alongside UX, developers, and project managers. You know where your lane is and when to step out of it
• An interest in AI-enabled working, not just as a tool, but as a genuine shift in how BA work gets done
• Familiarity with tools like Miro, Azure DevOps, and Microsoft 365
• A relevant degree or equivalent experience

Why you’ll want this role

• Your work directly shapes what gets built and what doesn’t
• A varied portfolio: discovery engagements, enterprise builds, integration projects, and everything in between
• Work at a firm genuinely leading AI-enabled delivery across New Zealand
• Be part of a small, high-trust BA team where your voice carries weight
• Complex clients who value good thinking, not just fast delivery
• A collaborative, human environment in Hamilton. Hybrid working, with at least three days a week in the office
• Grow with us: this is a team with ambition, and there’s room for the right person to grow into it