As of March 01, 2025, the average annual salary for a Technical Product Manager VI in Yakima, WA is $216,790. According to Salary.com, salaries can range from a low of $191,190 to a high of $245,447, with most professionals earning between $203,390 and $231,790.
| Annual Salary |
Monthly Pay |
Weekly Pay |
Hourly Wage |
|
| 75th Percentile | $231,790 | $19,316 | $4,458 | $111 |
| Average | $216,790 | $18,066 | $4,169 | $104 |
| 25th Percentile | $203,390 | $16,949 | $3,911 | $98 |
An entry-level Technical Product Manager VI with under 1 year experience makes about $210,642. With less than 2 years of experience, a mid-level Technical Product Manager VI makes around $211,660. After 2-4 years, the Technical Product Manager VI pay rises to about $212,068. Those senior Technical Product Manager VI with 5-8 years of experience earn roughly $213,697, and those Technical Product Manager VI having 8 years or more experience are expected to earn about $215,123 on average.
| Levels | Salary |
|---|---|
| Entry Level Technical Product Manager VI | $210,642 |
| Intermediate Level Technical Product Manager VI | $211,660 |
| Senior Level Technical Product Manager VI | $212,068 |
| Specialist Level Technical Product Manager VI | $213,697 |
| Expert Level Technical Product Manager VI | $215,123 |
| Entry Level | 3% |
| Mid Level | 2% |
| Senior Level | 2% |
| Top Level | 1% |
| Experienced | 1% |
Not the salary data you are looking for? Choose the city salary you want to see.
Salary.com job board provides millions of Technical Product Manager VI information for you to search for. Click on search button below to see Technical Product Manager VI 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.
Computer Science: Computer science is the study of computation, automation, and information. Computer science spans theoretical disciplines (such as algorithms, theory of computation, information theory, and automation) to practical disciplines.
| Skill | Salary | Demand |
|---|---|---|
|
Products and Services
|
$244,973 |
13%
|
|
Verbal Communication
|
$236,301 |
9%
|
|
KPI
|
$234,133 |
8%
|
|
Initiative
|
$227,630 |
5%
|
|
Leadership
|
$225,462 |
4%
|
|
Insight
|
$225,462 |
4%
|
