A European utilities firm in the middle of an S/4HANA migration needed an SAP BASIS Lead for a 12-month engagement to own the cutover and post-cutover stabilization. Their internal team had two BASIS engineers, both already at capacity on the existing ECC environment. The migration was scoped for a 14-month timeline, of which 9 months had already passed; the cutover was 4 months away and the prior external lead had quit. They needed a senior BASIS engineer with multiple prior S/4HANA cutovers and prior energy/utilities domain exposure — a thin intersection.
SAP BASIS Leads who have done multiple S/4HANA cutovers in utilities are extraordinarily rare. The talent pool worldwide is probably in the low hundreds. Most senior SAP BASIS engineers have done one or two cutovers and built career narratives around them — they're not actively seeking new roles, they're being courted by SAP partners. The client's previous external lead had quit after 7 months because of friction with the internal team, and the prior engagement had been with a multinational consultancy that had used the engagement as a training ground for junior BASIS engineers — a common pattern that the client didn't want to repeat. They needed an individual contributor with cutover experience, not a consultancy that would staff up juniors under their senior name. The 12-month commitment also narrowed the pool: most senior BASIS engineers were on consulting day rates and wouldn't switch to a 12-month engagement without significant premium.
The search had to be narrow and high-trust. We started with SAP's own certified-consultant registry — a public database of certified BASIS consultants — and cross-referenced against our internal database for candidates who had verifiable cutover history. The 785 applicants who reached our funnel were the result of three weeks of active outreach to candidates who hadn't applied themselves; we approached them because their profiles matched. Of 785, 220 passed the AI scoring (which heavily weighted SAP-cert verification through the official registry). Senior recruiter screen took that to 68, then a 4-hour written assignment cut to 28. The assignment was deliberately specific: critique the client's existing migration plan (which we had permission to share under NDA) and identify the three highest-risk areas. Most submissions missed the regulatory archive requirement (European utilities have specific data-retention obligations on energy-trading records); the 14 candidates who flagged it cleared. Live discussion (90-minute, run by our senior BASIS recruiter) focused on past cutover war stories — specific dates, specific failure modes, specific recovery actions. The top 5 went to the client. The client's IT director and the two internal BASIS engineers ran 2-hour final rounds focused on cultural fit and the IC-vs-consultancy distinction (would the candidate roll up their sleeves and do the work themselves, or try to bring in a team?). The winning candidate (Pune-based, 11 years experience, three prior S/4HANA cutovers including one for a Spanish utility) walked through the client's migration plan with specific risk callouts and a personal commitment to do the work himself, not subcontract.
Offer day 18 at top-of-band ($14,500/month). Accepted within a week. Started day 25 with onboarding compressed by pre-provisioning SAP system access during the offer-acceptance window. The cutover ran on schedule four months later (week 18 of the engagement) with zero unplanned downtime; the regulatory archive integration that the prior lead had missed got built in time. Post-cutover stabilization (the next eight months of the engagement) handled three production incidents, all resolved within SLA. The client's regulatory audit at month 11 passed cleanly. The 12-month engagement extended into a 24-month engagement at the original day rate. The engineer's reference letter from the client became one of our strongest credibility signals for future SAP BASIS searches; two more SAP BASIS Lead placements followed in the next year on the back of it.
Three-hour call with the client's IT director + their existing two BASIS engineers. Reviewed the existing migration plan, the gaps the previous lead had left, and the regulatory audit requirements specific to European utilities.
SAP-cert verification done through SAP's own certified-consultant registry. Migration-cutover signal verified through reference calls with prior clients (not just prior employers).
28 candidates critiqued the client's existing migration plan in writing. 14 cleared (most missed the regulatory archive requirements). Live discussion focused on past cutover war stories with specific dates and failure modes.
Client's IT director ran 2-hour final rounds with the top 5. Picked the engineer who'd led three prior S/4HANA cutovers, two in utilities. Offer day 18. Started day 25. Cutover ran on schedule.
For ultra-niche searches (SAP BASIS + S/4HANA + utilities, payments-domain Go, reactive Kotlin), the right search is narrow and outbound, not wide and inbound. We approached most of the 785 candidates ourselves; only ~80 had applied to a public posting. The active-market pool for these niches is too thin to be the entire funnel. Second lesson: for migration-cutover roles where the deliverable is binary (the cutover works or it doesn't), the IC-vs-consultancy distinction matters enormously. Consultancy-backed candidates often promise senior delivery but staff up juniors under the senior's name. Asking the candidate to commit to personally doing the work — and then verifying through references that they have a history of doing so — surfaces the right signal.