Getting Job Ready

Crafting a Strong Professional Profile

Your professional profile is not just your CV. It is the complete picture a recruiter or hiring manager assembles from everything they can find about you before they decide whether to invite you in. That includes your CV, your LinkedIn profile, your portfolio if you have one, and anything they might find when they search your name.

The Key Elements

Before you apply for a single role, make sure these are in good shape:

Element	Why it matters
A clear, current LinkedIn profile	Your profile picture, headline, work experience, and skills section need to be up to date and reflective of where you’re headed, not just where you’ve been.
A well-structured CV	This is covered in depth in the next section. In NZ, IT recruiters generally want three to five pages of detail, particularly for technical roles.
A portfolio or GitHub profile (if relevant)	For developers, designers, data professionals, and engineers, showing your work is often more persuasive than describing it.
A consistent professional narrative	What you say about yourself across all platforms should tell a coherent story. A mismatch between your CV and your LinkedIn profile creates unnecessary doubt.

Your Elevator Pitch

Be able to answer ‘Tell me about yourself’ in two minutes or less. This is not a request for your life story. It’s an invitation to connect the dots between your background and why you’re the right person for this particular opportunity. Practice it out loud. It sounds different than it reads.

The most important elements of a strong professional profile are having up-to-date, consistent information across platforms, and being able to clearly articulate what you’ve actually delivered, not just what your role description said. Chris, Younity

How to Write a CV That Stands Out for IT Roles

In New Zealand, IT CVs are different from what you might expect if you’ve come from an overseas market. Here’s what actually works.

The NZ IT CV at a Glance

Element	Guidance
Length	Three to five pages for experienced candidates. Senior or highly technical candidates may go slightly longer. One page CVs from experienced professionals are usually too thin.
Structure	Contact details, professional summary, technical skills summary, work experience (reverse chronological), education and certifications, and a brief section on interests or community involvement if relevant.
Technical skills section	Put this near the top for technical roles. List languages, frameworks, tools, platforms, and operating systems you’re genuinely proficient in. Don’t overstate.
Work experience	Lead with the most recent role. For each role, include a brief description of the organisation and team context, then two to three key achievements, not just duties.
Older experience	Roles more than ten to fifteen years old can be summarised in a brief table at the bottom. Hiring managers want to see your recent work, not your full career history in detail.
Gaps	Explain them briefly. Career break, travel, family, study. A clear label removes the question and keeps the focus on your skills.

Writing Outcome-Focused Bullet Points

The most common weakness in IT CVs is listing responsibilities rather than achievements. Hiring managers know what a software developer or project manager does. What they want to know is what you specifically delivered. A simple test: if the bullet point would be true for anyone in that role, it’s not specific enough.

Weak version	Stronger version
Responsible for managing infrastructure upgrades	Led migration of on-premise infrastructure to AWS, reducing hosting costs by 40% and improving uptime from 98.2% to 99.9%.
Worked as part of agile development team	Contributed as a senior developer in a seven-person agile squad, shipping four major features per quarter across a 200,000-user platform.
Business analysis and requirements gathering	Facilitated requirements workshops with seven business stakeholders to define scope for a $1.2M CRM replacement programme, reducing project scope creep by 35%.

If you’ve been working for 30 years, focus on the last five to ten years. You don’t have to go into the details of older roles, just put them in a table at the bottom. People want to see where you’ve come from, but they want the detail on what you’ve been doing recently. Jane, Younity

What CV Reviewers in NZ IT Look For

When experienced NZ IT recruiters review CVs, these are the signals they’re looking for beyond keywords:

Tenure that makes sense. A pattern of reasonable tenures, particularly for permanent roles, signals reliability and the ability to integrate with a team. Very short tenures across multiple roles prompt questions.
Progression over time. Does the CV show someone who has developed their skills and taken on more responsibility? Lateral moves are fine, but stagnation across many years raises questions.
Achievements that are proportionate to the role. Entry-level achievements look different from senior-level ones. Make sure yours are appropriately scoped.
Clarity and readability. A CV that is hard to skim quickly will be skimmed quickly, and not in your favour. Clean formatting, consistent spacing, and logical structure matter.
Listing technologies you barely know creates problems in interviews and technical assessments. Stick to skills you can actually speak to.

Cover Letters That Show Value Not Just History

The cover letter has become less common in NZ IT recruitment over the last decade. For most roles, and particularly for contract positions, it is not expected and may not be read. But when it is requested, it matters.

When a Cover Letter Helps

Cover letters remain most useful in a handful of situations:

When explicitly requested as part of the application.
For senior roles where motivation, judgement, and communication style carry significant weight.
When you’re making a career transition and need to explain why your background, though different, is relevant.
When you genuinely have something specific and compelling to say about why this particular organisation interests you.

What a Good Cover Letter Does

A strong cover letter does three things: it demonstrates that you have done your homework on the organisation, it connects your experience to the specific needs of the role, and it gives a sense of your personality and communication style that a CV cannot.

What it does not do: repeat your CV, open with ‘I am writing to apply for’, or rely on generic phrases that could appear in anyone’s letter.

Write it yourself. Use your own language. Cover letters that have been generated by AI are very obvious. They all look the same. They won’t make you stand out in a good way. Jane, Younity

Cover Letter Structure

Opening paragraph. State the role you’re applying for and why this particular organisation interests you. Be specific. ‘I’m drawn to your focus on open banking infrastructure because…’ is better than ‘I am excited about the opportunity to join your team’.
Middle paragraph(s). Connect two or three specific aspects of your background to the most important requirements of the role. Use concrete examples.
Closing paragraph. Reiterate your interest, note that you’d welcome the opportunity to discuss further, and thank them for their consideration. Keep it brief.

Keeping Your Profiles Current on LinkedIn and Job Boards

Many candidates set up their profiles when they’re actively looking and then let them go stale when they settle into a new role. This is a missed opportunity, because the best roles often find people who are not actively looking.

What to Keep Current

Job title and employer. Update your LinkedIn current position as soon as you start a new role.
As you learn new tools and technologies, add them. As others become outdated, consider whether they’re still relevant to where you want to go.
Recent projects and achievements. Don’t wait until you’re looking for a new role to document what you’ve delivered. Add achievements while they’re fresh.
Contact and location details on SEEK and other boards. Recruiters filter by location and contact preference. Ensure yours reflect your current situation.

Open to Work Settings

LinkedIn’s ‘Open to Work’ setting lets you signal to recruiters that you’re open to new opportunities without broadcasting it to your entire network. For most people in employment who are open to a conversation without being actively job hunting, this is a useful setting to have on.

Update your profiles more often than just when you’re looking. The best roles often come from recruiter reach-outs when you’re not actively searching. Keeping your profile current means you don’t miss those conversations. Hayley, Younity

Showcasing Projects, Tools, and Technical Skills Clearly

For many IT roles, what you can do matters more than what jobs you’ve had. Showing your work clearly, in a way that non-technical recruiters and technical hiring managers can both understand, is a skill in itself.

Structuring Your Technical Skills Section

A well-organised technical skills section at the top of your CV helps recruiters match you to relevant roles quickly. Consider grouping your skills by category:

Category	Examples
Languages	e.g. Python, JavaScript, Java, C#, SQL
Frameworks and Libraries	e.g. React, Angular, Django, .NET, Spring Boot
Cloud and Infrastructure	e.g. AWS, Azure, GCP, Kubernetes, Docker, Terraform
Databases	e.g. PostgreSQL, MySQL, MongoDB, Oracle, Snowflake
Tools and Platforms	e.g. Jira, Confluence, GitHub, Jenkins, Salesforce
Methodologies	e.g. Agile, Scrum, SAFe, DevOps, ITIL

Describing Project Work

When describing specific projects or work examples, a useful structure is:

Context. What was the organisation, team, or problem environment?
Your role. What were you specifically responsible for?
Tools and approaches. What technologies, methodologies, or frameworks did you use?
Outcome. What was delivered, and what was the measurable impact?

Show the technologies clearly and early. If they’re not on the CV, it will generally be assumed you don’t have those skills. Recruiters search on keywords, and what’s not there simply won’t come up. Andy, Younity

Portfolio Basics for Developers, Designers, and Engineers

For certain IT disciplines, a portfolio is not optional. It is the most direct way to demonstrate that you can do the work.

What Belongs in a Portfolio

Role Type	What to include
Software developers	Three to five projects that demonstrate different aspects of your skills. Include the problem you solved, the technologies used, and a link to a live version or the code repository. Explain the decisions you made and why.
UX and UI designers	Case studies, not just screenshots. Walk through the problem, your research process, the decisions you made, and the outcome. Show that you think, not just that you make things look good.
Data scientists and analysts	End-to-end projects that show data ingestion, cleaning, analysis, and visualisation. Notebooks published on GitHub or Kaggle work well. Frame each project around the question you were trying to answer.
Engineers and architects	Diagrams, design documents, and descriptions of systems you’ve built or contributed to. If you can share the code, do. If not, describe the architecture and your role in it clearly.

Where to Host Your Portfolio

The standard platform for code and technical project documentation. A clean, active GitHub profile is often more compelling than a CV for development roles.
Personal website. A simple site with a portfolio section, your CV, and contact details gives a professional impression and a single place to direct people.
Behance or Dribbble. Standard platforms for design portfolios.
For data science and machine learning work.
Medium or Dev.to. Publishing technical articles demonstrates communication skills as well as technical knowledge.

A simple but effective portfolio just needs to show three things: the problem you were solving, what you built or designed, and what the result was. The ‘why’ behind your decisions is what separates a strong portfolio from a list of projects. Andy, Younity