Software Product Manager III

Candescent is the leading cloud-based digital banking solutions provider for financial institutions. We are transforming digital banking with intelligent, cloud-powered solutions that connect account opening, digital banking, and branch experiences for financial institutions. Our advanced technology and developer tools enable seamless, differentiated customer journeys that elevate trust, service, and innovation. Success here requires flexibility in a fast-paced environment, a client-first mindset, and a commitment to delivering consistent, reliable results as part of a performance-driven, values-led team. With team members around the world, Candescent is an equal opportunity employer.

Role: Software Product Manager III

Product Manager Developer Tooling & SDK Platform
Location: Bangalore Org: Developer Experience

Candescent is looking for a highly technical Product Manager to lead our Developer Tooling & SDK Platform team within the Developer Interfaces vertical. You ll own the strategy and execution for SDKs (web, mobile, server), CLI tools, code extensions, and our public GitHub ecosystem including sample apps and reference integrations. Your north star: reduce developer integration time from weeks to hours through intuitive, high-quality tools.What You ll Do Drive the roadmap for SDKs, CLIs, code extensions, and developer utilities. Build interactive SDK playgrounds, toolkits, and sample apps to accelerate TTFX. Maintain and evolve Candescent s public GitHub presence and developer resources. Collaborate closely with engineering, documentation, and design to deliver cohesive developer experiences. Define metrics that reduce friction and improve integration speed, reliability, and adoption. Champion developer empathy and modern API-first workflows across the organization.About You Background as a developer, SDET, QA engineer, or similar technical role. Hands-on experience with SDKs, developer tooling, or integration workflows. Strong understanding of API design, developer workflows, and rapid iteration cycles. Excellent technical writing and documentation skills. Passion for solving developer pain points and building delightful, frictionless experiences.About the Developer Experience OrgWe aim to enable effortless and extensible integration for Financial Institutions, Fintechs, and AI developers through world-class APIs, SDKs, a unified console, and an open marketplace. Our mission is to position Candescent as the leading extensible and intelligent fintech developer platform, delivering frictionless onboarding, AI-augmented productivity, and ecosystem network effects.Interview rubric1. Technical Depth & Developer EmpathyWhat we re assessing: Ability to understand APIs, SDKs, CLIs, extensions Experience working as a developer/SDET/QA Ability to reason about developer workflows, debugging, integration paths Ability to empathize with developer pain pointsPositive Signals: Can read and reason about code (not necessarily write production code) Understands API versioning, SDK semantics, dependency management Explains why developers do what they do Provides examples of reducing developer frictionRed Flags: Superficial understanding of core developer tools Cannot articulate how developers think or debug Focuses only on features, not developer outcomesSample Questions: Tell me about a time you built or improved a developer tool. What insights guided your decisions Explain the difference between a high-quality SDK and a poor one. How would you diagnose why developers are struggling to complete integration2. Experience with SDKs, Tooling, and GitHub EcosystemsWhat we re assessing: Prior experience with SDKs (web/mobile/server), CLIs, sample apps, code playgrounds Ability to maintain a public GitHub repo with strong community hygiene Understanding of testing frameworks, code samples, documentation pipelinesPositive Signals: Has built or shipped SDKs or CLIs Familiar with playground environments (e.g., CodeSandbox, Snack, Postman, Swagger, custom sandboxes) Experience writing or maintaining sample apps or integrations Understands GitHub workflows, issue triage, PR reviews, versioningRed Flags: Has never worked with developer-facing assets No familiarity with GitHub as a product surfaceSample Questions: Walk me through an SDK or toolkit you ve built or owned. What made it successful How would you improve our public GitHub developer experience Tell me about a time you created a sample app or reference implementation.3. Product Strategy & RoadmappingWhat we re assessing: Ability to define a cohesive strategy across SDKs, tools, docs, and insights Ability to prioritize based on outcomes (TTFX, developer cycle time, adoption) Ability to articulate trade-offs and decision frameworksPositive Signals: Writes clear product requirements Designs with outcomes, not features Understands metrics like TTFX, onboarding funnel, support ticket volume, SDK adoptionRed Flags: Vague or reactive thinking Cannot define success metrics Talks only about outputs (features) not outcomesSample Questions: If you joined tomorrow, what would you prioritize in your first 90 days and why How would you measure whether our SDKs are making developers faster Describe a time you drove a product strategy that reduced friction for users.4. Documentation & Communication SkillsWhat we re assessing: Ability to write concise, clear developer-facing documentation Ability to explain complex concepts simply Ability to collaborate effectively across engineering, DevRel, design, and docs teamsPositive Signals: Communicates clearly with both technical and non-technical audiences Knows best practices for API/SDK documentation Can empathize with learners and beginnersRed Flags: Overly verbose or unclear explanations Cannot structure complex ideasSample Questions: Show me how you would explain one of our SDK features to a new developer. Tell me about a time your writing clarified something complex for developers.5. Execution & DeliveryWhat we re assessing: Ability to move ideas into shipped, high-quality artifacts Cross-functional collaboration and leadership Comfort in fast-paced environments Strong ownership mindsetPositive Signals: Gives examples of shipping complex, multi-stakeholder products Demonstrates urgency and bias for action Breaks work down into incremental deliverables Manages engineering partnerships wellRed Flags: Struggles to articulate delivery methodology Passes responsibility instead of owning outcomes Overly theoretical; lacks shipping historySample Questions: Tell me about a complex project you shipped end-to-end. How did you unblock challenges Describe a conflict where engineering and product were misaligned. How did you resolve it6. Problem Solving & Systems ThinkingWhat we re assessing: Ability to diagnose friction in developer workflows Ability to think in systems: APIs SDKs Docs Errors Tooling Support Ability to design holistic developer experiencesPositive Signals: Uses data, logs, feedback, telemetry Thinks of developer journey as an end-to-end funnel Shows clarity in structuring ambiguous problemsRed Flags: Jumps straight to feature ideas Lacks a framework for diagnosing developer problemsSample Questions: Developers report integrations still take weeks. How do you troubleshoot Explain how you would redesign our SDK onboarding journey end-to-en

Statement to Third Party Agencies
To ALL recruitment agencies: Candescent only accepts resumes from agencies on the preferred supplier list. Please do not forward resumes to our applicant tracking system, Candescent employees, or any Candescent facility. Candescent is not responsible for any fees or charges associated with unsolicited resumes.