About the role
What You’ll Do
Requirements & Specification
Own end-to-end product requirements for assigned domains.
Translate business needs into:
Functional requirements
System behaviors
Business rules
Edge cases and failure scenarios
Write clear, structured documentation:
PRDs
Functional specs
Flow diagrams
State machines (where applicable)
Business Logic & System Thinking
Define and document core business logic for workflows such as:
Order lifecycle
Rider assignment
Pricing / incentives
Cancellations, retries, and exceptions
Think in terms of systems, not screens.
Anticipate downstream impacts of changes across services.
Engineering Collaboration
Work closely with backend, mobile, and infra teams during:
Requirement clarification
Technical solutioning
Sprint planning
Answer “what should happen if…” questions decisively.
Review implementations to ensure alignment with specs.
Acceptance Criteria & Testing
Define clear acceptance criteria for every feature.
Create and maintain:
Test scenarios
Happy paths and edge cases
UAT checklists
Partner with engineers and QA to validate releases.
Sign off on feature readiness for production.
Documentation & Product Hygiene
Maintain up-to-date product documentation.
Ensure assumptions, decisions, and trade-offs are recorded.
Keep requirements synchronized as systems evolve.
Stakeholder Communication
Act as the bridge between:
Business
Engineering
Operations
Present trade-offs, constraints, and decisions clearly.
Align stakeholders on scope and priorities.
Responsibilities
What We’re Looking For
Required
3-5 years of experience in:
Technical Product Management
Product Owner
Business Analyst (with strong engineering exposure)
Proven ability to write clear, unambiguous requirements.
Strong understanding of:
Backend systems
APIs and service-based architectures
Data flows and state transitions
Experience defining:
Acceptance criteria
Test cases
UAT plans
Comfortable working closely with engineers on technical details.
Background in engineering, computer science, or data.
Experience with tools like Jira, Confluence, Docusaurus.
Exposure to analytics and KPI-driven product decisions.
Strongly Preferred
Experience with system-heavy products (logistics, fintech, infra, marketplaces).
Familiarity with:
Event-driven systems
Distributed workflows
Real-time or near-real-time systems
Ability to read basic backend code or API contracts.
Experience working in fast-moving startup environments.
What Will NOT Work in This Role
Treating requirements as high-level bullet points.
Deferring all edge cases to engineering.
Writing specs without understanding system constraints.
Being disconnected from testing and validation.
Focusing only on roadmap slides instead of execution clarity.