lendable - Technical Product Manager (Superapp)
Requirements
• Deep, hands-on engineering background - this role must be staffed by someone who has shipped production systems, not someone who has only managed backlogs. • Strong commercial instinct: can build a business case, speak to P&L impact, and hold a line on ROI. • Exceptional stakeholder management across product, engineering, and finance without direct line authority over all of them. • Comfortable with ambiguity - platform value is often indirect and long-horizon. • Track record of contributing as an IC while operating at a senior, cross-team level. • Proactive, low-ego, and clear communicator - able to hold a line with leadership and pod leads alike. • Experience in platform, infrastructure, or developer tooling contexts. • Familiarity with SLA/SLO frameworks and incident management at scale. • Experience enforcing CI/CD standards across multiple teams or pods. • Prior work making "invisible" infrastructure legible to non-technical leadership. • Platform & backend: Kotlin, AWS, Postgres, RabbitMQ, Docker, Kubernetes. • Gateway & clients: Node GraphQL gateway, React Native / TypeScript mobile app, Relay. • Tooling & observability: GitHub, GitHub Actions, Jira, Confluence, Datadog, Sentry, Grafana.
Responsibilities
• Own platform stability • Own platform stability as a primary accountability - SLA/SLO metrics, incident rates, release quality. • Hold release gating authority: block features from production that don't meet testing standards or introduce unacceptable regression risk. • Enforce CI/CD standards centrally so pods don't fragment into one-off solutions. • Track and report stability metrics alongside commercial outcomes - stability is the foundation that makes the rest possible. • Be commercially accountable • Own the business case for platform investment and answer "why are we spending six engineers on this for three months?" in terms leadership understands. • Track platform impact in business terms: developer velocity, incident cost, time-to-market, reliability, capacity - e.g. "CXO rollout removes a 3-second API fan-out, reducing session abandonment" or "we can now handle 20k simultaneous logins". • Input into headcount and investment decisions for the platform team. • Own the platform roadmap • Own the platform backlog, prioritised by business value and sequenced to unblock the highest-value product teams first - not driven by technical debt or engineer preference alone. • Make trade-offs explicit: "if we do X now, we defer Y by Z weeks - here's what that means for products depending on us". • Ensure every initiative has a defined success metric that non-engineers can track. • Be the stakeholder interface • Act as the single point of contact for Pod Leads: business requirements coming from pods and engineering/developer requirements flowing to pods; prioritise both in service of platform stability. • Make platform work visible to leadership - regular forums with product MDs and PMs to capture upcoming dependencies before they become blockers; represent platform work in leadership reviews; translate technical milestones into business milestones. • Drive cross-team collaboration and buy-in with other PMs; engage architecture in technical design. • Escalate when product teams make requests that would create unsustainable platform load or technical debt. • Contribute as an engineer • Write code, review PR's, and participate in architecture design as a core part of the role - not a side project. • Bring a strong technical voice to roadmap decisions without owning final architecture calls (that's Architecture and Tech Leads).
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT