What is the job of a Product Manager (Technical)?
The job of a technical product manager consists of deciding, together with other people, which digital product gets built, for whom, and in what order its parts are made. The product is software, such as an app, a platform or a tool that other companies use. It is a position that links the team that writes the code with the business, sales and customer service areas, and it differs from other product jobs because it requires a good understanding of how the technology works on the inside.
A typical day mixes meetings and individual work. The manager reviews with the development team what is being built and what problems have come up, reads feedback from users, looks at usage data on dashboards, and writes descriptions of new features so that they are clear. There are also conversations with sales or support to understand what customers are asking for, and negotiations about what gets done first when everything seems urgent.
Typical tasks
- Defining the user problems the product must solve and explaining why they matter.
- Writing requirements and feature descriptions with the level of detail the technical team needs.
- Ordering and prioritizing the backlog of work according to user value, effort and risk.
- Talking with engineers about technical options, the limits of the architecture and technical debt.
- Analyzing usage data and test results to judge whether a feature meets its goal.
- Interviewing users and customers to understand how they use the product.
- Reporting progress, changes of plan and decisions to executives and other departments.
Subjects and content usually covered
- Programming fundamentals and how an application is built.
- Databases, interfaces between programs (APIs) and software architecture, at the level of understanding.
- Agile methods and software project management.
- Data analysis, product metrics and comparative experiments.
- User-centered design and research with users.
- Product strategy, markets and digital business models.
- Written communication, presentations and negotiation.
Usual duration and type of training
There is no single training path for this job. People who arrive from a university degree in software engineering, computer systems, computer science or business administration usually study for 4 to 5 years. Technical training programs in software development generally last 2 to 3 years. There are also courses and graduate programs in product management, lasting from a few weeks to 1 or 2 years. It is usual to add several years of experience in technology teams before reaching the position. The length and the names of the programs vary by country.
How you get there and what is usually required to practice
This is a job that people reach by several paths. Many start as developers, systems analysts, business analysts, designers or in technical support, and over time move into deciding about the product. Others come from engineering or business degrees and enter through a junior or assistant product position.
No license or professional registration is required. What is usually asked for is demonstrable experience in software teams, enough technical understanding to talk with engineers, and some practice with data. The first product position can be hard to get, and sometimes it is reached by changing roles within the same company where the person already works.
Skills that help
- Explaining technical ideas to people without a technical background, and business needs to the people who write the code.
- Reading usage data and drawing conclusions without rushing.
- Prioritizing when there are more requests than time, and explaining why one thing is chosen over another.
- Listening to users and customers and telling apart what they ask for from what they actually need.
- Negotiating with departments that want different things and reaching agreements.
- Understanding technical limits well enough to question deadlines and proposals with arguments.
Career paths and job opportunities
- Software companies and cloud service providers.
- Technology start-ups.
- Banks, insurers and other financial institutions with digital products.
- E-commerce businesses and delivery or payment platforms.
- Industrial, health or education organizations that develop their own digital tools.
- Consulting firms that build products for other clients.
What you are not always told
- The person is responsible for the product's results but has little direct authority over the people who build it, so almost everything is achieved by persuading.
- A large part of the job is saying no to reasonable ideas, and that creates tension with colleagues and customers.
- Many decisions are made with incomplete information, and sometimes a feature that took months of work does not have the expected effect.
- Meetings take up a good part of the day, and time to think alone has to be protected.
- When there is a serious failure or a deadline, the pressure and the overtime can increase.
How the field is changing
Data analysis tools and user testing tools are increasingly integrated, and assistants based on artificial intelligence help summarize interviews, draft requirements and explore data. This changes the time spent on writing and analysis tasks, but it does not remove the need to decide what to build and to take responsibility for the consequences. When a product includes artificial intelligence, additional questions appear about the quality of the results, the privacy of data and rules that vary from one country to another.
Want to know if this is the right career for you?
Take the free vocational test with 5 scientific methods — CHASIDE, Holland, Big Five, MMMG and VAK — to get your personalized profile. You can also explore all university careers or learn about the scientific methodology.