Back to Career Explorer
💻
IT, AI & Software

Product Manager — Tech

Define what gets built, why it gets built, and for whom — leading cross-functional teams of engineers, designers, and data analysts to ship digital products that solve real user problems and achieve business goals.

Highly CompetitiveHigh demand Global career EntrepreneurialCan work remotely

A Product Manager (PM) in technology is the person responsible for the strategy, roadmap, and success of a digital product. They sit at the intersection of business, technology, and user experience — defining what the product should be, prioritising what gets built, and making sure the team builds the right thing. PMs do not manage engineers directly (they have no formal authority over their team) but they lead through influence — by having better insight into user needs, market context, and business strategy than anyone else on the team. The role requires breadth rather than depth: enough technical understanding to work credibly with engineers, enough design sensibility to work with UX designers, enough commercial awareness to align with business stakeholders, and enough data literacy to make evidence-based decisions. Product management is one of the highest-paid roles in the global technology industry. At companies like Google, Meta, and Amazon, Senior PMs earn USD 200k–400k in total compensation. In Sri Lanka, the role is growing rapidly — PickMe, Daraz, Dialog Digital, IFS, WSO2, and BOC PayMedia all have product management functions. The career is almost always entered laterally from another discipline: engineers who develop product instincts become Technical PMs; UX designers who develop business acumen become UX-focused PMs; business analysts who develop technical understanding become data-driven PMs. It is very rare to enter product management directly from university without prior experience in an adjacent role. Sri Lanka's product management community is small but active — the PM community on LinkedIn and the ProductHive Sri Lanka group are the primary local networking resources.

What a Product Manager — Tech does daily

  • Define the product vision and strategy — articulating what the product is for, who it serves, and how it will create value; aligning the team around a clear direction; the most important and least tangible part of the role
  • Prioritise the product roadmap — deciding which features to build, which problems to solve, and in what order; balancing user needs, business goals, technical constraints, and market timing; writing product roadmaps that communicate priorities to all stakeholders
  • Write product requirements — Product Requirement Documents (PRDs), user stories, and acceptance criteria; translating user needs and business goals into precise specifications that engineers and designers can act on
  • Conduct user research and discovery — customer interviews, surveys, usability tests; understanding the problems users face and validating whether proposed solutions will actually work; the best PMs conduct more research than their design and research teams expect
  • Define and track product metrics — identifying the key metrics that indicate whether the product is delivering value (DAU, MAU, retention rate, conversion rate, NPS, ARPU); building dashboards; analysing metric movements; making data-informed decisions
  • Manage the product backlog — maintaining an ordered list of user stories and features; grooming backlog items; running sprint planning with the engineering team; ensuring the backlog is always ready for the next sprint
  • Coordinate cross-functional delivery — aligning engineering, design, QA, data, marketing, and sales around the product roadmap; removing blockers; communicating status; managing dependencies between teams
  • Conduct competitive and market analysis — researching competitor products; identifying market gaps; understanding industry trends; informing product strategy with external context
  • Define go-to-market strategy — working with marketing and sales on how to launch features; writing release notes; coordinating customer communication; measuring adoption of new features
  • Review and improve based on data — analysing user behaviour data (Mixpanel, Amplitude, Google Analytics), A/B test results, and customer feedback after launch; iterating the product toward better outcomes
Why this matters: Product managers determine whether an organisation's technology investment creates real value. A technically excellent product built for the wrong users, solving the wrong problems, with the wrong priorities, fails in the market regardless of its engineering quality. Sri Lanka's digital economy — mobile banking, e-commerce, ride-hailing, telemedicine, e-government — depends on product managers who can translate user needs and business goals into products that people actually use. Internationally, the PM role is one of the clearest paths from a technical background to high-earning, high-influence roles in the technology industry without moving into pure management.

Step-by-Step Career Roadmap

What to do
  • Develop product intuition by using and critiquing apps — pick apps you use daily and ask: what problem does this solve? who is it for? what would make it better? what is missing? this critical usage habit is the foundation of product thinking
  • Learn basic business concepts — what revenue is, what a business model is, how companies make money from apps; "How does WhatsApp make money?" and "How does YouTube make money?" are great starting questions; Khan Academy Economics (free) covers fundamentals
  • Read "The Design of Everyday Things" by Don Norman (chapters 1–2) — the foundational book on why products succeed or fail; develops the habit of asking "why did the designer make this decision?" about every product interaction
  • Develop Excel / Google Sheets proficiency — product managers live in spreadsheets; building and manipulating data tables, using SUMIF/VLOOKUP/COUNTIF, creating charts; these skills are the data analysis foundation
  • Write and communicate clearly in English — product management is 50% clear writing; practice writing short essays that explain complex ideas simply; the skill of explaining technical ideas to non-technical people starts here
Key subjects
MathematicsICT / ComputingEnglishCommerce / Business Studies
Skills to build
Product critique — articulating what works and fails about digital productsBasic business concepts (revenue, profit, business model)Excel / Google Sheets (VLOOKUP, SUMIF, charts)Clear written communication in EnglishCritical thinking about technology
Suggested activities
  • Weekly product critique: analyse one app per week — problem, users, what works, what fails, what you would change
  • Khan Academy: Intro to Economics (free)
  • "The Design of Everyday Things" by Don Norman — Chapters 1–2
  • Google Sheets: build a product metrics dashboard tracking a favourite app's features
  • "How I built this" podcast (NPR) — stories of product and company building (free)
Important notes
  • Product management is a role for generalists who are excellent at one or two things — developing depth in software engineering, UX design, or data analysis during school makes the eventual PM transition far more credible; do not try to learn "product management" in isolation without first building expertise in a foundation discipline
💡 Backup / alternative options
Software EngineeringData ScienceUI/UX DesignBusiness Analysis
⚠️ Important: Career paths and admission requirements change. Always verify the latest university entrance criteria, professional body requirements, and A/L subject combinations with official sources before making final decisions.