Before You Accept a Specialist Tech Role, Ask About the Roadmap
By Tony Kvatch
Before accepting a Salesforce, CRM, marketing automation, data or AI role, ask about the platform's current state, investment and scheduled projects across ANZ and Southeast Asia.
Understand the platform's current state and the work planned for it before you accept the role. Illustration generated with AI for FutureHero.
A job description tells you what a company wants. It doesn’t always tell you what the job will actually be.
A role may name Salesforce, a marketing automation platform, a data stack or AI. That list does not tell you whether the platform is in good shape, whether the business is investing in it, or what projects are actually planned.
Before you accept, try to understand the work behind the job title. You do not need confidential plans or a detailed technical audit. You do need a clear account of the platform’s current state and the direction the company intends to take it.
Start with the platform’s current state
Ask how the platform is being used today. Who relies on it? What is working well? Where are the gaps? Is the team maintaining an established system, improving it, replacing parts of it, or building something new?
The answers help you distinguish a defined role from a vague expectation to “fix the platform”. For a Salesforce or CRM role, that might mean understanding adoption, data quality, integrations and ownership. In marketing automation, it might mean whether the team is refining campaigns or rebuilding journeys and customer data. For data and AI roles, ask what foundations, products or use cases already exist.
Ask what investment is happening
Find out what the business is committing to the platform. Investment can mean more than a licence. It may involve people, time, leadership attention, implementation support or a funded programme of work.
Ask what has been approved and resourced, and what is still an idea. A company can have an ambitious strategy without the people or authority to deliver it. That is useful context for deciding whether the opportunity matches your expectations.
Find out which projects are scheduled
Ask what projects are planned, who owns them and when they are expected to begin. Where appropriate, clarify whether work is approved, funded and scheduled, or still being considered.
A specific project gives you a better sense of the role than a general promise of “transformation”. You can understand whether you will be configuring and supporting existing tools, leading a new implementation, improving data flows, or helping move an AI use case into production.
Connect the roadmap to your role
The final question is what you will be responsible for delivering. Will you own a project, contribute technical expertise, advise stakeholders or focus on ongoing operations? Who makes platform decisions? What resources and colleagues will you work with?
The roadmap matters because it sets the context for your work. A platform can have significant investment planned, but a role may not give you the remit to influence the projects. Be clear about the connection between the company’s plans and your responsibilities.
Listen for clarity, not perfect answers
Not every role needs a major programme or a long list of projects. A maintenance role can be a good opportunity when that is what the business needs and the expectations are honest.
Listen for whether people can explain the platform’s condition, the work ahead and how your role fits. If those answers are still developing, that is not automatically a reason to walk away. It is a reason to ask how priorities will be set and when decisions will be made.
These questions apply across Salesforce, CRM, marketing automation, data and AI roles. For specialists considering opportunities in Australia, New Zealand or Southeast Asia, the central issue is the same: understand what the organisation is investing in and what it expects you to do with it.
What should I ask before accepting a Salesforce or CRM role?
Ask about the current state of the platform, approved investment, scheduled projects and what you will personally own. Clarify the difference between committed work and future ideas.
How can I tell whether a platform roadmap is real?
Ask what has been approved, resourced and scheduled, who owns the work, and how your role connects to it. A clear plan does not need to reveal confidential details.
Does every specialist role need a major transformation project?
No. Some roles focus on stable operations, support or incremental improvement. The important thing is to know the real purpose of the role before accepting it.