The Role: You own the technical success of Cashfree Payment’s largest merchants from first scoping call to scaled production. You are the person, merchant CTOs call when something matters and the person internal teams trust to bring order to complex, high-stakes integrations.This role sits where engineering depth meets executive presence. You'll debug an API edge case before lunch and align a merchant's leadership on go-live readiness after it. What You'll Own: Enterprise implementations, end-to-end: Scope, plan, integrate, launch, stabilize. You own the timeline, the risks, and the outcome.Technical relationship: You're the primary point of contact for merchant engineering, product and business stakeholders. You translate payment infrastructure into solutions that fit their architecture, growth stage and risk posture, not a standard playbook.Program rigor: Project plans with real dependencies. Risks surfaced before they bite. Internal coordination across Product, Engineering, Risk, Ops and Support to keep delivery on track.Integration health, post go-live: Monitor transaction performance and success rates proactively. Spot optimization opportunities before they become incidents and own resolution when they do.Escalations: You lead the response end-to-end. Root cause, stakeholder comms and resolution. Merchants walk away with the issue fixed and their confidence intact.The merchant signal loop: Patterns you see in the field, friction points, gaps, recurring asks! They become structured inputs into the product roadmap.Launch readiness for high-stakes go-lives: Scale tests, production readiness reviews, white-glove support during peak windows.Solutioning from use case, not catalog: You start with the merchant's business model and work backwards, mapping their use case to the right mix of Cashfree products, not the full suite.SLA-grade resolution When merchant revenue is on the line, you operate to stringent SLAs, coordinating engineering and ops in real time, holding the line on both speed and fixed quality.Team leverage: Better playbooks, sharper integration guides, faster onboarding for the next merchant and the one after that. What We're Looking For: 2+ years in technical account management, implementation engineering or solutions engineering, B2B SaaS or fintech, with end-to-end ownership of complex multi-stakeholder programs.Technically credible: Strong fluency in REST APIs, webhooks, and integration patterns. You don't ship production code, but you read it, reason about it and hold your own in a technical war room.Working knowledge of at least one modern language: Go, Python or Java, with hands-on experience you can point to. Familiarity with mobile platforms (Android, iOS) is a plus, especially when integrations span SDKs.Comfortable in the tools merchants live in: Strong with SQL for slicing through transaction data and fluent with Postman (or equivalent) for testing and debugging APIs in real time.Fintech context is a strong plus: Payment flows, reconciliation, settlements or compliance frameworks, anything that lets you skip the ramp.Range of audience: You translate cleanly in both directions: technical complexity for business stakeholders, business context for engineering, without losing precision either way.Consultative by default: You ask before you prescribe. Merchants can tell the difference.High ownership: Merchant outcomes are your outcomes. You follow through without being chased and escalate with context, not noise.Built for ambiguity: Enterprise implementations rarely go to plan. You re-sequence, adapt and keep merchants confident through it.Builder's instinct: You leave the playbook, the process and the team better than you found them.