You are a D365 Finance & Operations consultant, developer or architect, and two conversations are live at once. One is a greenfield implementation: blank page, design workshops, a partner or an internal programme about to kick off. The other is a programme already two or three years in, rolling out to the next country, the next business unit, the next set of legal entities. The recruiter tells you both are good roles. You want to know which one actually does more for you.
That is the question worth answering properly, because the two look similar on a position description and feel completely different eighteen months later.
What we are seeing at the moment
Across a recent 60-day window, we recorded 78 market signals tied to D365 Finance & Operations, spread across 78 distinct company records. These are recorded signals based on when something was last seen, not verified live vacancies, so treat them as a read on direction rather than a count of open jobs. The pattern that matters is the spread: breadth across many organisations rather than one or two large programmes hiring repeatedly.
The interpretation we draw from that is simple. In most of these organisations you are not joining a bench of twenty F&O people. You are the F&O capability, or one of two or three. That changes what you should ask for.
The titles sitting alongside F&O in those records are also telling: a senior project manager for D365, a D365 technical architect, a finance systems analyst, a junior system analyst. That is a mix of programme leadership and internal run-the-system roles, which is what you would expect when rollouts are continuing rather than starting. Industries named include mining, retail and technology, with locations across Australia and New Zealand and a visible concentration in Sydney and New South Wales.
The three phases, and what each one does to your CV
Design and build
This is where you get the conversations that make you better: chart of accounts decisions, costing method, intercompany design, where Supply Chain stops and a bolt-on starts. If you want to move from consultant to solution architect, you need two or three of these in your history, and you need to be able to explain the decisions you argued for and lost as well as the ones you won.
The risk is that greenfield programmes slip. A start date in March becomes a start date in July, and a business case can be reopened before you have cut a single configuration. If you leave a stable role for a greenfield build, understand where the funding sits and whether the design authority exists yet.
Rollout waves
Underrated, and often the better commercial move. The template exists, the hard decisions have been made, and your job is localisation, data migration, integration, cutover and hypercare for the next entity. You will learn more about data quality and change management in one difficult wave than in three design workshops.
The thing to check is whether the template is genuinely reusable or whether every wave is being rebuilt. If it is being rebuilt, you are doing greenfield work with none of the design authority. Ask directly how many entities are live, how much of the last wave was template versus bespoke, and what the hypercare exit criteria were.
Run and optimise
Internal finance systems analyst and support-lead roles are real careers, and they pay steadily, but they narrow quickly. Two years of one tenant, one chart of accounts and one set of ISVs is hard to sell into a programme role afterwards. If you take one, negotiate upfront for a named improvement stream: Copilot and automation in finance processes, a Power Platform extension, a move onto Fabric for reporting, a version upgrade you own end to end.
Questions to ask before you say yes
- Where exactly is the programme? Not “in flight”. Which entities are live, which are next, and what is the go-live date you are being hired against?
- Who owns the design decisions? If there is no solution architect and no design authority, you will either become one informally or be overruled by whoever shouts loudest.
- How many F&O people are there today? If the answer is “you will be the first”, that can be a strong role, but price it and resource it accordingly.
- What is the partner arrangement? Knowing whether the partner is leading delivery or supporting an internal team tells you what you will actually be doing on a Tuesday.
- What happens after go-live? On a perm role, ask what the post-go-live roadmap is. On a contract, ask whether hypercare is in scope and funded.
- What is the data story? Migration readiness is the single most common reason rollouts slip. If nobody can tell you who owns master data, assume the timeline moves.
Permanent or contract
Contract still suits the design and build phase: the work is intense, time-boxed, and you are paid for the experience you already have. Permanent suits you when the organisation is far enough through the rollout that a multi-year roadmap exists and you want to own the application rather than hand it over.
One practical note. If you are weighing a perm offer against a contract rate, compare the whole picture over 24 months, including likely bench time between contracts, leave, and what training the employer will fund. We see plenty of consultants take a perm role specifically to get a funded F&O or Fabric certification path and a real crack at Copilot and agent work inside finance processes, then re-enter the contract market stronger two years later. There is more detail on how these roles and rates are shaping up in our Dynamics 365 Finance & Operations 2026 Australian guide.
What to avoid
Avoid the role where the title says consultant and the work is ticket triage with no roadmap. Avoid programmes that cannot name a go-live. Avoid taking a step into a sector you do not know at the same time as a step up in seniority, unless the organisation has a strong functional lead to work beside. And be careful with roles where the scope spans Finance, Supply Chain, integration and reporting for one person. That is three jobs, and it usually ends with you being blamed for the two you could not get to.
The skills that travel best right now are the boring and the new in combination: clean functional depth in one module, genuine data migration and integration experience, and the ability to show where you have used Power Platform or Copilot to remove manual steps from a finance process. Being able to explain the business outcome of that work, not just the configuration, is what separates the consultants who get shortlisted from the ones who get screened out.
Where saas nine fits
We work across the Microsoft ecosystem in Australia and New Zealand, and Dynamics 365 ERP recruitment is where most of our F&O conversations start. We will tell you where a programme actually is before you interview, because that is the detail that decides whether a role is worth your time.
You can register your profile and preferences through our Talent Portal, which we are continuing to build out to improve matching and keep you visible to the right programmes rather than every role with F&O in the title. If you would rather have a direct conversation about what your next move should look like, get in touch and we will be straight with you about what the market is paying and who is genuinely ready to hire.