Technical Product Management Specialist - Transactability
for section headings
- Use - for lists
- Use
for prose
- Don't repeat job title as heading
- Don't put Job ID/requisition numbers as headings
- Fold minor metadata into short
or drop it
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
- Remove duplicated lines and application instructions
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment, no /, no markdown code fences
The posting has:
- Application window close date: 10/26/2026 - this is minor metadata, fold into a short
or drop. I'll include as a brief note.
- Meet the Team: descriptive prose about the team
- Your Impact: descriptive prose about the role
- Responsibilities: list of duties
- Minimum Qualifications: list
- Preferred Qualifications: list
- Why Cisco?: company description, then detailed compensation and benefits
The compensation section is very detailed with salary ranges, benefits, time off, bonuses, etc. This should be split into Pay and Benefits sections.
I need to structure:
1. About the team (from Meet the Team)
2. About the role (from Your Impact)
3. Responsibilities
4. Requirements (Minimum Qualifications)
5. Preferred Qualifications
6. Pay (salary ranges, incentive details)
7. Benefits (health, 401k, time off, volunteer, etc.)
The "Why Cisco?" section contains both company mission and detailed compensation/benefits. I'll separate them.
Also note: The salary ranges are specific to locations. I should include all that detail.
The time off details are extensive - include in Benefits.
The bonus/incentive details for sales vs non-sales - include in Pay or Benefits? Probably Pay since it's compensation.
The posting mentions "Message to applicants applying to work in the U.S. and/or Canada:" - this is context for the salary range.
I'll create sections only where there's real content.
Let me draft the HTML.
First, a brief meta note about application window? The rule says fold minor metadata into short
or drop it. I'll include a
at the top or bottom. Probably at the top: "Application window closes 10/26/2026."
But the rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The application window is similar metadata. I'll include a
at the beginning.
Now, sections:
About the team
Our Transactability team powers the multi-billion dollar engine behind Cisco's services. We are a high-energy, collaborative group that demonstrates intelligent automation and AI to simplify how we quote and sell worldwide. We thrive on solving enterprise-scale challenges, focusing on accelerating deal velocity and improving the experience for our global sales teams and partners.
About the role
As a Technical Product Management Specialist, you will support the evolution of our transaction quoting, booking, and invoicing systems. Rather than just delivering requirements, you will serve as a strategic partner to our customers. You will lead the product backlog and influence the technical roadmap, bridging the gap between business vision and technical execution to ensure our systems remain scalable, automated, and user-centered.
Responsibilities
- Author comprehensive technical specifications and clear acceptance criteria within Jira to guide development teams.
- Lead the product backlog by prioritizing features based on business value, technical debt, and resource constraints.
- Drive commerce simplification by identifying ordering bottlenecks and implementing solutions to reduce quote cycle times.
- Lead the discovery phase for new features, utilizing user-centered design principles to ensure a seamless experience.
- Collaborate with cross-functional operations, legal, and finance customers to ensure configurations align with revenue recognition and pricing governance.
Requirements
- Bachelor's degree in Information Technology, Computer Science, Business Administration, or a related field.
- Minimum of 2 years of professional experience in product management, business analysis, or solution architecture in enterprise software.
- Demonstrated experience working in Agile or Scrum frameworks using tools like Jira or Rally.
- Technical expertise with enterprise commercial workflows, including pricing rules, order booking, and subscription management.
- Hands-on experience developing end-to-end test strategies, designing test cases, and leading Business Acceptance Testing (BAT/UAT) on commerce or ERP platforms.
Preferred Qualifications
- Exceptional storytelling skills with the ability to translate complex technical concepts for business customers.
- Hands-on experience in the Quote-to-Cash domain.
- Deep understanding of services lifecycle commercial models and subscription economies.
- Experience applying machine learning or intelligent automation to streamline manual business processes.
- Familiarity with API integration logic and how different systems communicate within a commerce ecosystem.
Now Pay section: The posting has detailed salary ranges and incentive compensation details. This is substantive.
Pay
The starting salary range for this position in the U.S. and/or Canada is $97,300.00 to $133,300.00, not including incentive compensation, equity, or benefits. Individual pay is determined by the candidate's hiring location, market conditions, job-related skillset, experience, qualifications, education, certifications, and/or training.
Location-specific salary ranges:
- New York City Metro Area: $112,200.00 - $186,500.00
- Non-Metro New York State & Washington State: $108,400.00 - $164,500.00
For locations not listed above, the recruiter can share more details about compensation for the role in your location during the hiring process.
For non-sales roles, employees are eligible to earn annual bonuses subject to Cisco's policies. Employees on sales plans earn performance-based incentive pay on top of their base salary, which is split between quota and non-quota components, subject to the applicable Cisco plan.
Quota-based incentive pay structure:
- 0.75% of incentive target for each 1% of revenue attainment up to 50% of quota
- 1.5% of incentive target for each 1% of attainment between 50% and 75%
- 1% of incentive target for each 1% of attainment between 75% and 100%
- Once performance exceeds 100% attainment, incentive rates are at or above 1% for each 1% of attainment with no cap on incentive compensation
For non-quota-based sales performance elements such as strategic sales objectives, Cisco may pay 0% up to 125% of target. Cisco sales plans do not have a minimum threshold of performance for sales incentive compensation to be paid.
Employees may be eligible to receive grants of Cisco restricted stock units, which vest following continued employment with Cisco for defined periods of time.
Benefits section: health, 401k, time off, volunteer, etc.
Benefits
U.S. employees are offered benefits subject to Cisco's plan eligibility rules, including:
- Medical, dental, and vision insurance
- 401(k) plan with a Cisco matching contribution
- Paid parental leave
- Short and long-term disability coverage
- Basic life insurance
Paid time away for U.S. employees (subject to Cisco's policies):
- 10 paid holidays per full calendar year, plus 1 floating holiday for non-exempt employees
- 1 paid day off for employee's birthday
- Paid year-end holiday shutdown
- 4 paid days off for personal wellness determined by Cisco
- Non-exempt employees receive 16 days of paid vacation time per full calendar year, accrued at a rate of 4.92 hours per pay period for full-time employees
- Exempt employees participate in Cisco's flexible vacation time off program, which has no defined limit on how much vacation time eligible employees may use (subject to availability and some business limitations)
- 80 hours of sick time off provided on hire date and each January 1st thereafter, and up to 80 hours of unused sick time carried forward from one calendar year to the next
- Additional paid time away may be requested to deal with critical or emergency issues for family members
- Optional 10 paid days per full calendar year to volunteer
Employees in Illinois, whether exempt or non-exempt, will participate in a unique time off program to meet local requirements.
Please see the Cisco careers site to discover more benefits and perks.
I should also include the "Why Cisco?" company mission statement? It's more of a company description. Could be part of "About Cisco" but the rule says prefer few substantive sections. The mission statement is prose, but it's not a separate section in the original. It's under "Why Cisco?" which then goes into benefits. I've already used the benefits content. The mission statement could be a brief intro before Pay/Benefits, but maybe not needed. The rule says preserve ALL substantive information. The mission statement is substantive about company culture. I could include a section "About Cisco" or fold into Benefits intro. But the rule says never create a section unless real specific content. The mission statement is generic marketing. However, it's part of the posting. I'll include a brief "About Cisco" section with that prose.
But the user said "Prefer a few substantive sections over many thin ones." So maybe skip a separate "About Cisco" and just keep the mission statement as a paragraph before Pay/Benefits? But the rule says use for section headings. If I include it, it should be a section. However, the original has "Why Cisco?" as a heading. I could use that as a section heading, but then it would contain both mission and benefits/pay. But I've split pay and benefits. The mission statement is separate. I'll create a section "Why Cisco?" with the mission statement, then Pay and Benefits separate.
But the rule: "include a section ONLY when the posting has real, specific content for it". The mission statement is real content.
for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Fold minor metadata into short
or drop it - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Remove duplicated lines and application instructions - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences The posting has: - Application window close date: 10/26/2026 - this is minor metadata, fold into a short
or drop. I'll include as a brief note. - Meet the Team: descriptive prose about the team - Your Impact: descriptive prose about the role - Responsibilities: list of duties - Minimum Qualifications: list - Preferred Qualifications: list - Why Cisco?: company description, then detailed compensation and benefits The compensation section is very detailed with salary ranges, benefits, time off, bonuses, etc. This should be split into Pay and Benefits sections. I need to structure: 1. About the team (from Meet the Team) 2. About the role (from Your Impact) 3. Responsibilities 4. Requirements (Minimum Qualifications) 5. Preferred Qualifications 6. Pay (salary ranges, incentive details) 7. Benefits (health, 401k, time off, volunteer, etc.) The "Why Cisco?" section contains both company mission and detailed compensation/benefits. I'll separate them. Also note: The salary ranges are specific to locations. I should include all that detail. The time off details are extensive - include in Benefits. The bonus/incentive details for sales vs non-sales - include in Pay or Benefits? Probably Pay since it's compensation. The posting mentions "Message to applicants applying to work in the U.S. and/or Canada:" - this is context for the salary range. I'll create sections only where there's real content. Let me draft the HTML. First, a brief meta note about application window? The rule says fold minor metadata into short
or drop it. I'll include a
at the top or bottom. Probably at the top: "Application window closes 10/26/2026." But the rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The application window is similar metadata. I'll include a
at the beginning. Now, sections:
About the team
Our Transactability team powers the multi-billion dollar engine behind Cisco's services. We are a high-energy, collaborative group that demonstrates intelligent automation and AI to simplify how we quote and sell worldwide. We thrive on solving enterprise-scale challenges, focusing on accelerating deal velocity and improving the experience for our global sales teams and partners.
About the role
As a Technical Product Management Specialist, you will support the evolution of our transaction quoting, booking, and invoicing systems. Rather than just delivering requirements, you will serve as a strategic partner to our customers. You will lead the product backlog and influence the technical roadmap, bridging the gap between business vision and technical execution to ensure our systems remain scalable, automated, and user-centered.
Responsibilities
- Author comprehensive technical specifications and clear acceptance criteria within Jira to guide development teams.
- Lead the product backlog by prioritizing features based on business value, technical debt, and resource constraints.
- Drive commerce simplification by identifying ordering bottlenecks and implementing solutions to reduce quote cycle times.
- Lead the discovery phase for new features, utilizing user-centered design principles to ensure a seamless experience.
- Collaborate with cross-functional operations, legal, and finance customers to ensure configurations align with revenue recognition and pricing governance.
Requirements
- Bachelor's degree in Information Technology, Computer Science, Business Administration, or a related field.
- Minimum of 2 years of professional experience in product management, business analysis, or solution architecture in enterprise software.
- Demonstrated experience working in Agile or Scrum frameworks using tools like Jira or Rally.
- Technical expertise with enterprise commercial workflows, including pricing rules, order booking, and subscription management.
- Hands-on experience developing end-to-end test strategies, designing test cases, and leading Business Acceptance Testing (BAT/UAT) on commerce or ERP platforms.
Preferred Qualifications
- Exceptional storytelling skills with the ability to translate complex technical concepts for business customers.
- Hands-on experience in the Quote-to-Cash domain.
- Deep understanding of services lifecycle commercial models and subscription economies.
- Experience applying machine learning or intelligent automation to streamline manual business processes.
- Familiarity with API integration logic and how different systems communicate within a commerce ecosystem.
Pay
The starting salary range for this position in the U.S. and/or Canada is $97,300.00 to $133,300.00, not including incentive compensation, equity, or benefits. Individual pay is determined by the candidate's hiring location, market conditions, job-related skillset, experience, qualifications, education, certifications, and/or training.
Location-specific salary ranges:
- New York City Metro Area: $112,200.00 - $186,500.00
- Non-Metro New York State & Washington State: $108,400.00 - $164,500.00
For locations not listed above, the recruiter can share more details about compensation for the role in your location during the hiring process.
For non-sales roles, employees are eligible to earn annual bonuses subject to Cisco's policies. Employees on sales plans earn performance-based incentive pay on top of their base salary, which is split between quota and non-quota components, subject to the applicable Cisco plan.
Quota-based incentive pay structure:
- 0.75% of incentive target for each 1% of revenue attainment up to 50% of quota
- 1.5% of incentive target for each 1% of attainment between 50% and 75%
- 1% of incentive target for each 1% of attainment between 75% and 100%
- Once performance exceeds 100% attainment, incentive rates are at or above 1% for each 1% of attainment with no cap on incentive compensation
For non-quota-based sales performance elements such as strategic sales objectives, Cisco may pay 0% up to 125% of target. Cisco sales plans do not have a minimum threshold of performance for sales incentive compensation to be paid.
Employees may be eligible to receive grants of Cisco restricted stock units, which vest following continued employment with Cisco for defined periods of time.
Benefits section: health, 401k, time off, volunteer, etc.Benefits
U.S. employees are offered benefits subject to Cisco's plan eligibility rules, including:
- Medical, dental, and vision insurance
- 401(k) plan with a Cisco matching contribution
- Paid parental leave
- Short and long-term disability coverage
- Basic life insurance
Paid time away for U.S. employees (subject to Cisco's policies):
- 10 paid holidays per full calendar year, plus 1 floating holiday for non-exempt employees
- 1 paid day off for employee's birthday
- Paid year-end holiday shutdown
- 4 paid days off for personal wellness determined by Cisco
- Non-exempt employees receive 16 days of paid vacation time per full calendar year, accrued at a rate of 4.92 hours per pay period for full-time employees
- Exempt employees participate in Cisco's flexible vacation time off program, which has no defined limit on how much vacation time eligible employees may use (subject to availability and some business limitations)
- 80 hours of sick time off provided on hire date and each January 1st thereafter, and up to 80 hours of unused sick time carried forward from one calendar year to the next
- Additional paid time away may be requested to deal with critical or emergency issues for family members
- Optional 10 paid days per full calendar year to volunteer
Employees in Illinois, whether exempt or non-exempt, will participate in a unique time off program to meet local requirements.
Please see the Cisco careers site to discover more benefits and perks.
I should also include the "Why Cisco?" company mission statement? It's more of a company description. Could be part of "About Cisco" but the rule says prefer few substantive sections. The mission statement is prose, but it's not a separate section in the original. It's under "Why Cisco?" which then goes into benefits. I've already used the benefits content. The mission statement could be a brief intro before Pay/Benefits, but maybe not needed. The rule says preserve ALL substantive information. The mission statement is substantive about company culture. I could include a section "About Cisco" or fold into Benefits intro. But the rule says never create a section unless real specific content. The mission statement is generic marketing. However, it's part of the posting. I'll include a brief "About Cisco" section with that prose. But the user said "Prefer a few substantive sections over many thin ones." So maybe skip a separate "About Cisco" and just keep the mission statement as a paragraph before Pay/Benefits? But the rule says use