An implementation specialist is the person who takes a customer from signed contract to actually using the software. You're usually carrying several accounts at once, each at a different stage, and most of your day is spent moving one of them a step closer to go-live. It's hands-on work: you do the configuration, the imports and the training yourself.
The title sounds close to implementation consultant, and some companies use them interchangeably. Where they differ, the specialist runs more accounts that are smaller and more alike, and follows a playbook the team already built. You're not usually designing a custom rollout for a hospital network. You're getting a dental group, a property manager or a mid-sized manufacturer onto a product that works the same way for most customers, and doing it fast and cleanly. That means less time in discovery workshops and more time inside the admin panel, the import tool and the project tracker. The day below describes a specialist at a software company that sells to small and mid-sized businesses, working from home with a book of accounts in Rocketlane and tickets in Jira.
You open your project tracker and look at every account you own. Two are waiting on the customer for data, one is mid-configuration, one goes live tomorrow and one kicked off last week. You scan overnight emails and the shared Slack channel with the customer who goes live tomorrow, then reorder your day around them. Anything that's gone quiet for a few days gets a short nudge before it turns into a stalled project.
The account executive joins for the first few minutes, introduces you, then drops off. You walk the customer through the plan: what data you need from them, who their admin will be, what training looks like and roughly when they'll be live. The real work of the call is finding out what they were promised in the sale. You write down anything that sounds like a feature the product doesn't have, and you flag it to sales before the customer finds out the hard way.
A customer sent their contact list and open orders as a spreadsheet. The phone numbers come in different formats, the dates came out of their old system as text, and the state column mixes abbreviations with full names. You fix it in Excel, map each column to a field in your import template, run a test import into a sandbox and check a handful of records by hand. Only then do you load it into their live account.
You were supposed to spend the afternoon on an admin training session. Instead, tomorrow's go-live customer emails that nobody can log in through Okta. You get on a call with their IT person, compare the SAML settings on both sides and find a mismatched entity ID. It isn't fixed by the end of the call, so you open a Jira ticket for your engineering team with screenshots and the error text, then push the training to the next morning and tell the customer why.
You write a short status note on each project: what moved today, what's blocked and who owns the next step. Your manager reads these in the weekly pipeline review, and so does the customer success manager who'll inherit each account after go-live. A clean handoff note is how they know what the customer was told. You end by confirming the sign-on ticket has an owner on the engineering side.
The hardest part isn't the technical work. It's that your deadlines depend on customers who have their own jobs to do and don't send their data on time. You'll chase the same spreadsheet every way you can think of and still get blamed when the go-live slips. Specialists who last in the role learn to write down every commitment, send recaps after every call and escalate early. The ones who burn out try to absorb every delay quietly.
This is the most common route. Support agents already know the product inside out, have seen every import error and know which settings customers get wrong. Ask to shadow an onboarding, then volunteer to take the smaller ones.
A former office manager at a clinic, a payroll administrator or a restaurant manager brings something the product team can't teach: how the customer's day actually runs. Software companies that sell into healthcare, construction or hospitality hire this way often, then teach the tool.
If you've been the person at your company who ran the Salesforce, NetSuite or HR system rollout, you've done implementation from the other side of the table. Put the rollout on your résumé as a project, with what you configured, what you migrated and how many people you trained.
30% of openings are fully remote.
$79,400 – $102,000
Typical range in the 28 of the newest 60 postings that list pay.
Usually not. You'll need to be comfortable with spreadsheets, settings pages and reading error messages. Some roles ask for basic SQL to check imported data, or for testing an API call in Postman, and those skills will set you apart. Writing software isn't part of the job at most companies.
They work next to each other but own different stretches of the customer's life. You own the setup, up to go-live and a little after. The customer success manager owns the relationship from there, including renewals and whether the customer keeps paying. Many specialists move into customer success later.
The common next steps are senior specialist, implementation consultant on larger and more custom projects, or implementation manager running a team. Some specialists move sideways into solutions engineering, product or customer success, because they've seen exactly where customers get stuck.
HeroApply applies to them for you, so you can keep doing the job you have.