Contract or permanent? Two very different Salesforce CVs

The Salesforce ecosystem runs on two hiring tracks, and they judge a CV by different rules. A contract role wants proof you can land in an unfamiliar org and deliver now, at a day rate that has to pay for itself. A permanent role wants proof you will grow, take ownership, and still be there in three years. The same career can serve both — but not with the same document. Send a contractor's punchy, deliverable-first CV into a permanent hiring manager's inbox and it can read as rootless; send a permanent CV of steady five-year tenures to a contract recruiter and it can read as slow and unproven at parachuting in.

A recruiter builds a mental timeline of your career in the first six to eight seconds. What that timeline should say is different for each track.

Why the rate changes the reading

Salesforce contractors command real money — often £300–£950+ a day in the UK, or roughly $50–$300+ an hour in the US, depending on seniority and stack. A day rate is a promise: this person justifies the premium by being productive almost immediately, with little onboarding. So a contract CV is read as a risk assessment — can you de-risk a delivery? A permanent salary, by contrast, buys potential and continuity, so a permanent CV is read as an investment case.

The contract CV: lead with delivery

Foreground evidence that you drop in and ship:

• Specialise loudly. Name the exact clouds, tools, and problem you solve — "Service Cloud + Omni-Channel implementation specialist," not "Salesforce professional." Contracts are bought for a specific gap.
• Organise around engagements and outcomes. Each entry: client (or anonymised "Financial-services org, 800 users"), the mandate, and 3–6 delivered results. Quantify them — the same discipline we cover in putting numbers on your resume.
• Show fast ramp and breadth. Multiple orgs, industries, and go-lives signal you adapt quickly — a feature for contractors, where it might read as restlessness for a permie.
• Tame the job-hop optics. Six three-month contracts listed as six jobs looks alarming. Group them under one umbrella — "Independent Salesforce Consultant, 2022–present" — with sub-engagements beneath, and label each Contract. That reframes churn as a deliberate portfolio.

The permanent CV: lead with trajectory

Foreground growth, ownership, and staying power:

• Show progression. Promotions, expanding scope, and increasing org size tell the investment story a permanent employer is buying.
• Emphasise ownership over breadth. Depth in one org — "grew and governed a 2,000-user org over four years" — beats a scatter of short stints here.
• Signal continuity and fit. Tenure, mentoring, cross-team work, and platform stewardship say you will stick and lift the team, not just clear a backlog.
• Frame long-arc impact. Not just what you shipped, but what it still does — adoption that held, technical debt retired, a release process that outlasted you.

Switching lanes without looking wrong

The lane you are leaving colours how you read, so reframe deliberately:

• Contractor → permanent. Recruiters may fear you will bolt at the next day rate. Group your contracts (as above), then add a line about why now — you want ownership and long-term impact, not just delivery. Lead with the longest, deepest engagement.
• Permanent → contract. The worry is that you have never had to ramp fast. Reframe internal roles as delivery: the projects you led, the go-lives you owned, the speed you brought — evidence you can hit the ground running for a rate.

Details both tracks get wrong

• Dates: month and year on every role. Contractors especially cannot hide behind year-only dates — a timeline with visible gaps reads worse than honest short engagements.
• Titles: append "(Contract)" or "Consultant" so the reader isn't guessing which roles were temporary.
• Gaps: a deliberate bench period between contracts is normal — a one-line note beats an unexplained hole.
• Role targeting: whichever lane, the specific posting still sets the keywords — the same principle as covering the right ATS terms and knowing whether the role wants an admin or a developer.

Keep both versions ready

Most Salesforce careers touch both tracks eventually, and rebuilding a CV from scratch each time is what pushes people toward one do-everything document that lands nowhere. In the SFCV builder your history lives in one place, so a contract-leaning and a permanent-leaning version derive from the same source instead of drifting — and when you spot a role on the jobs board, you can point the right version at it in minutes.

Same skills, two arguments. Decide whether the role is buying delivery now or growth over time, lead with that, and let the other track's version wait its turn.