Core practice
API & System Integration Consulting
Integration work is where most enterprise software actually fails. Individual systems tend to be well tested in isolation; the seams between them are where assumptions diverge, error handling is thin, and nobody owns the failure.
This has been the through-line of my last seven years — at Workday supporting data integration between Adaptive Planning and external ERP and CRM systems, at LinkedIn implementing and troubleshooting customised integrations across Talent Solutions, and before that managing cloud-hosted database environments and migrations at eClinicalWorks.
Where I can help
- Diagnosing integration failures across REST APIs, webhooks and scheduled data transfers
- Designing integrations between ERPs, CRMs and third-party platforms, including the failure and retry behaviour
- Reviewing an existing integration that works most of the time and nobody fully trusts
- Payload-level analysis of XML and JSON where data is being silently dropped or transformed
- Building the integration itself where the scope suits an individual engineer rather than a team
What tends to be wrong
In my experience the root cause is rarely the API itself. It is more often an unhandled partial failure, a retry that duplicates rather than resumes, a schema change deployed on one side without the other, or an error path that logs nothing useful because it was never expected to run.
Good integration work is mostly about taking failure seriously as a first-class case rather than an afterthought.
Working with your team
I am comfortable as the engineer who does the work, or as the person who reviews and pressure-tests what your team is building. At LinkedIn a substantial part of the role was translating between customers, Engineering, Product and Operations — establishing what was actually happening before anyone committed to a fix.
Common questions
Do you build integrations or only advise on them?
Both. Where the scope suits a single engineer I will build it. Where you have a capable internal team, a review and advisory engagement usually delivers more value per rupee than adding another pair of hands.
Which platforms have you integrated?
Workday Adaptive Planning with external ERP and CRM systems, LinkedIn Talent Solutions with enterprise customer environments, MS Dynamics 365, Medallia, and cloud-hosted MSSQL environments for US medical practices.
Do you work with startups as well as enterprises?
Yes. The engineering is the same; the difference is that startups usually need the pragmatic version and enterprises usually need the documented version.
Have a problem that fits this?
Tell me what is failing and what you have already ruled out. I will tell you honestly whether I am the right person for it.
Start a conversation →