Is your D365 job spec asking for too much?
What overloaded D365 job specs get wrong.
I read a "D365 CE Consultant" ad this week that wanted a developer, an architect, a BI lead and a PM. Plus the actual consultant job. One salary.
Here's the full list it asked for:
Sales and Customer Service, expert level.
Power Apps and Power Automate.
Copilot Studio and agent building.
Power BI.
Solution architecture.
Project management.
C-level stakeholder management.
And "ideally, some Azure integration."
That's not a greedy employer trying to get five hires for one fee. It's usually one who hasn't worked out what they actually need yet.
When the role isn't clear in your own head, you list everything.
And you reach for the words everyone's posting about. Copilot. Agents. AI. Because they feel current, and you're hoping they pull stronger applicants.
The trouble is what it does to the people you actually want.
The strong CE consultants read a list like that and quietly move on. They could do the core job standing on their head. They just recognise a role that hasn't been thought through, because they've been burned by one before.
What you're left with is a pile of applications that don't fit, and you sitting there wondering why.
The fix is simpler than people expect. Work out the two or three things this person has to be great at on day one, and build the role around those. Everything else is trainable, or it's a second hire.
And if you're a consultant who's felt boxed out by ads like this: it isn't you. The role just hasn't been defined yet.
Specialists win the work that matters. Deep beats wide, every time.
CE folks, which one skill on that list actually matters most, and which is just noise?
I work with Microsoft Partners, ISVs and end users across the US, helping them build permanent and freelance teams across the Dynamics 365 ecosystem.
If you'd like to compare notes on the market or discuss your hiring plans, I'd be delighted to connect.
