Arnav Dasgupta
Backend engineer · Amsterdam · Available now
I build backend systems other teams depend on, and lately the AI agents that run on top of them. Six years at SAP, most recently on the OpenTelemetry platform that 300+ cloud services report into.
I moved to Amsterdam in November 2026 on a Dutch partner permit, so I have full right to work and need no sponsorship. I'm looking for a backend team here to grow with.
Work
Telemetry platform
SAP Labs India · Software Engineer II · 2020 to 2026
I built the core of SAP Cloud ALM's OpenTelemetry routing platform and the Java and Node.js client library every connected service uses: nearest-datacentre routing, automatic mTLS certificates, and failover across 17 datacentres. Kafka-driven onboarding took new tenants from two days to near-instant, and the HTTP/2 migration I led added 45% throughput.
- Telemetry a day
- ~6 TB
- Uptime
- 99.9%
- Fewer data-loss incidents
- 90%
SAP Labs India · Built and owned alone · In production
Onboarding was eating four days of every twelve-day sprint. I built a prototype over a weekend, hardened it, and shipped it to SAP's cloud service teams a week later. How it works.
- Users in week one
- 180
- Questions a day
- ~400
- Person-days a quarter
- 31 → 3
Open source · Merged Feb 2026
The SDK quietly turned every "+" in resource attributes into a space, because it decoded them like form data. I replaced the decoder with one that follows the W3C Baggage spec, with tests.
The onboarding agent, in more detail
Start from the data. Jira showed where my team's time went: onboarding services, troubleshooting, and fixing onboardings that went wrong took around 31 person-days a quarter. That decided what the agent had to do first.
Earn trust in stages. Service teams onboard their dev and test landscapes through the agent's chat, with help instrumenting our client library. Once they've checked that monitoring works and approved it, the agent pulls all their production tenants and onboards them on its own. People verify where mistakes are cheap; the agent takes over the expensive, repetitive part.
Corrections become fixes. An admin UI captures live conversations. When someone corrects an answer, the correction goes back into the prompt or the knowledge base. Retrieval misses users reported were fixed by tuning chunking, embeddings and a glossary of internal jargon.
Keep it debuggable. Every run is traced with OpenTelemetry and Langfuse, and every config change the agent makes is a commit to version-controlled YAML in GitHub, so it can be audited and reverted. Built on Claude Opus with the Anthropic SDK on SAP AI Core.
How I work
- Measure the pain first. The agent started with Jira data, not an idea.
- Prototype in a weekend, harden in a week. A working thing in front of users beats a proposal.
- Earn trust in stages. Let people check results where mistakes are cheap, then automate the rest.
- Corrections become tests. A mistake a user has fixed shouldn't come back.
Background
M.Tech. (Master of Technology) in Software Engineering from BITS Pilani, studied part-time while working, on a full scholarship. Dissertation on efficient resilience in distributed cloud systems. Before that, a BCA from MIT World Peace University, Pune. I mentored three interns at SAP, and outside work I play guitar.