As of March 01, 2025, the average annual salary for a Product Manager IV in Lawrence, KS is $137,139. Salary.com reports that pay typically ranges from $125,199 to $145,871, with most professionals earning between $114,328 and $153,821.
| Annual Salary |
Monthly Pay |
Weekly Pay |
Hourly Wage |
|
| 75th Percentile | $154,524 | $12,877 | $2,972 | $74 |
| Average | $145,274 | $12,106 | $2,794 | $70 |
| 25th Percentile | $132,626 | $11,052 | $2,551 | $64 |
An entry-level Product Manager IV with under 1 year experience makes about $132,684. With less than 2 years of experience, a mid-level Product Manager IV makes around $133,218. After 2-4 years, the Product Manager IV pay rises to about $134,109. Those senior Product Manager IV with 5-8 years of experience earn roughly $135,357, and those Product Manager IV having 8 years or more experience are expected to earn about $139,354 on average.
| Levels | Salary |
|---|---|
| Entry Level Product Manager IV | $132,684 |
| Intermediate Level Product Manager IV | $133,218 |
| Senior Level Product Manager IV | $134,109 |
| Specialist Level Product Manager IV | $135,357 |
| Expert Level Product Manager IV | $139,354 |
| Entry Level | 9% |
| Mid Level | 8% |
| Senior Level | 8% |
| Top Level | 7% |
| Experienced | 4% |
Not the salary data you are looking for? Choose the city salary you want to see.
Salary.com job board provides millions of Product Manager IV information for you to search for. Click on search button below to see Product Manager IV job openings or enter a new job title here.
Each competency has five to ten behavioral assertions that can be observed, each with a corresponding performance level (from one to five) that is required for a particular job.
Analysis: Analysis is the process of considering something carefully or using statistical methods in order to understand it or explain it.
User Stories: In software development and product management, a user story is an informal, natural language description of one or more features of a software system. User stories are often written from the perspective of an end user or user of a system. They are often recorded on index cards, on Post-it notes, or in project management software. Depending on the project, user stories may be written by various stakeholders including clients, users, managers or development team members. User stories are a type of boundary object. They facilitate sensemaking and communication; that is, they help software teams organize their understanding of the system and its context. User stories are often confused with system requirements. A requirement is a formal description of need; a user story is an informal description of a feature.
B2B: B2B (business-to-business), a type of electronic commerce (e-commerce), is the exchange of products, services or information between businesses, rather than between businesses and consumers (B2C).
| Skill | Salary | Demand |
|---|---|---|
|
Design Engineering
|
$149,481 |
9%
|
|
Partnering
|
$146,738 |
7%
|
|
Decision Making
|
$145,367 |
6%
|
|
Data Science
|
$143,996 |
5%
|
|
Influencing
|
$143,996 |
5%
|
|
Empathy
|
$142,624 |
4%
|
