SAP functional consultants
FI, CO, MM, SD, PP, QM, PM, EWM and the industry variants. Configuration depth matters more than certification count.
Careers
Small teams, senior work, no bench time.
Recognize is around 150 people working only on SAP. That means no adjacent practice pulling you onto something unrelated, and no long stretches waiting to be staffed. It also means the work is visible: on a team this size, what you build is attributed to you.
SAP only
Every project is SAP. Depth compounds instead of scattering.
Senior on delivery
Consultants sit on the critical path, not behind a delivery manager.
Pune based
With travel to client sites in India and further markets.
Why people join
The reasons are usually the same three.
People who move to a firm this size are rarely chasing a title. They are usually leaving one of three things behind.
You want the whole problem
On large programmes, most people own a slice. Here you see the assessment, the design, the build and the first period close.
You are tired of waiting to be staffed
Bench time is expensive for a firm this size, so we do not carry it. Between projects usually means days, not months.
You want to be in the room
Consultants present their own work to the client. Nobody translates your design into someone else's slide.
The people in the room at the pitch are the people on the build. That is a promise to clients and a working condition for everyone here.
How we staff every project
Where we hire
The skills we are usually looking for.
We do not always have a posting open. We are always interested in people in these areas, and we would rather keep a good CV on file than let a conversation wait for a vacancy.
SAP Basis and cloud
System administration, HANA, migration tooling, and operating landscapes on RISE, private cloud and hyperscalers.
Data management specialists
Archiving, DVM, ILM, decommissioning and carve-outs. This is our deepest practice and the hardest to hire for.
ABAP and extension developers
Clean Core thinking, RAP, CDS and BTP extensions, alongside the remediation work that migrations always need.
Integration engineers
SAP Integration Suite on BTP and existing PI/PO landscapes, including the migration between them.
Solution architects and leads
People who can hold a design in their head, defend it to a CIO, and still be on the floor during cutover.
How we hire
Four steps, and you will know where you stand after each one.
We keep the process short because good SAP people are usually in the middle of a project and do not have four weeks to spend on interviews.
- 1
A first call
Thirty minutes on what you have worked on, what you want next, and whether the work we have coming up matches it.
- 2
A technical conversation
With people who do the job. Real scenarios from real landscapes rather than a quiz on menu paths.
- 3
Meet the team
You meet whoever you would actually work with, and you get to ask them what the last project was really like.
- 4
Offer
Made quickly once we decide, with the role, the level and the first project named rather than left vague.
What we look for
Beyond the modules on your CV.
- You can explain a design to someone who does not work in SAP.
- You say when something will not work, early, rather than at the retrospective.
- You have gone live and stayed through the first period close.
- You are comfortable being the most senior person in the room on your area.
- You would rather fix the cause than close the ticket.
What this is not
This is client-facing consulting. It means travel to client sites, periods of intensity around cutovers, and being accountable to someone outside the company for what you deliver.
If you are looking for a purely remote product role with fixed hours and no client contact, this will not suit you, and it is better we both know that now.
No posting that fits? Send it anyway.
We keep good CVs on file and come back to them when work lands. Tell us what you have worked on and what you want to do next.