Professional Services Project Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to produce sections only where there is real content.
Let's parse the posting:
- Title: "Transform Software Implementations as Our Next Professional Services Project Manager!" (we ignore as heading not needed)
- About Us: paragraph about Trimble.
- What Makes This Role Great: paragraph describing role.
- Key Exciting Responsibilities: list of bullet points (starting with "Spearhead end-to-end..." etc). Should be
- .
- Essential Skills & Experience: list of bullet points (starting with "Bachelor's degree..." etc). Should be
- .
- Bonus Points For: list of bullet points (starting with "Prior consulting experience..." etc). Should be
- .
- Logistics: Location and Travel Requirement. Could be a short paragraph or list. The posting says: "Logistics Location: Lake Oswego, OR, Westminister, CO, Alpharetta, GA (In Office) Travel Requirement: Up to 10%". That's specific content. Should we make a section "Logistics"? The allowed headings include "Schedule" but not "Logistics". However we can use any heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. Likely we should stick to those headings where applicable. For location and travel, maybe we can incorporate into a short
without a heading? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location and travel might be considered minor metadata, but they are substantive. Could embed in a
without heading. However they said "include a section ONLY when the posting has real, specific content for it". Could we make a section "Logistics"? Not in examples but maybe acceptable. Safer to not create a heading for logistics; just include a
with that info.
- Why You'll Love Working With Us: paragraph(s) about culture, impact, etc. Should be a section maybe "About the role"? Actually "Why You'll Love Working With Us" is like a benefits/culture section. Could map to "Benefits"? But Benefits section is separate. Could treat as "About the role"? Not exactly. Perhaps we can create a heading "Why You'll Love Working With Us" as
. The instruction didn't forbid other headings, just gave examples. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we can also use others if they match content? The examples are just examples; likely they expect us to use those headings for the standard sections. For "Why You'll Love Working With Us", maybe we can treat as part of "Benefits" or "About the role". But there is already a Benefits section later. The "Why You'll Love Working With Us" includes culture, impact, collaborative team, ownership spirit. That's more about company culture and benefits beyond compensation. Could be part of "Benefits" but Benefits already defined as medical etc. Might be better to create a heading "Why You'll Love Working With Us". The instruction didn't forbid; it just gave examples. I'd include it as a section.
- Benefits: paragraph about medical, dental, etc. Should be a section with heading Benefits.
- Compensation: includes hiring range, pay rate type, bonus eligible, commission eligible. Should be a section with heading Pay (or Compensation). The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use "Pay" heading for compensation.
- Schedule: Not mentioned; there is no schedule info besides full time schedule mentioned in compensation description. Not specific schedule like hours. So we should not create a Schedule section.
- Also there is a line: "Compensation: Trimble provides the following compensation range and general description of other compensation and benefits that it in good faith believes it might pay and/or offer for this position. This compensation range is based on a full time schedule." That's the compensation.
- Also there is a line: "If this position is identified above as commission- or bonus-eligible, the terms of the commission plan or discretionary bonus plan for which you are eligible will be provided following the employee start date." That's part of compensation.
- Also there is a line: "How to Apply: ..." which is application instructions, we must remove.
- Also EEO boilerplate etc remove.
- Also duplicated lines: maybe some repeated sentences? We'll just keep unique.
Now produce HTML fragment.
Structure:
About Us
...
What Makes This Role Great
...
Responsibilities
- Spearhead end-to-end software implementation projects, establishing unified project designs that align customer goals with strategic implementation methodology.
- Direct multi-organizational project tasks into single, cohesive plans while actively forecasting efforts, milestones, and deliverables.
- Cultivate strong client relationships through proactive account management, education on operational data flow, and swift issue resolution.
- Lead remote, matrixed project teams to consistently meet delivery deadlines, maintain project scopes, and ensure resource alignment.
- Execute robust risk identification and mitigation strategies to keep complex, parallel projects running on schedule and within budget.
Requirements
- Bachelor's degree in business or a related field with 4+ years of project management experience (or 7+ years of relevant project management experience in lieu of a degree).
- Proven expertise with industry-standard project management methodologies such as PMBOK or Agile.
- Strong track record of driving multiple parallel projects while successfully leading remote teams within a matrix environment.
- Demonstrated excellence in client management, relationship building, requirement gathering, and negotiation.
- Expert capability in identifying project risks and executing effective mitigation strategies.
// Wait need exact text: "Expert capability in identifying project risks and executing effective mitigation strategies."
But the instruction says use headings like Requirements, Qualifications, Skills. We have Essential Skills & Experience. Could map to Requirements or Skills. Let's use "Requirements" for the essential skills & experience.
Skills
maybe for Bonus Points? Actually Bonus Points For could be "Skills" or "Qualifications". Let's treat Bonus Points For as "Skills" or "Qualifications". The instruction includes Skills as a possible heading. We'll put Bonus Points For under Skills
with list.
Alternatively we could have both Requirements and Skills. Let's do:
Requirements
for Essential Skills & Experience.
Skills
for Bonus Points For.
Now Logistics: we can include a without heading: maybe after Skills.
Location: Lake Oswego, OR; Westminster, CO; Alpharetta, GA (In Office). Travel: Up to 10%.
But we should not invent tags like ? The instruction didn't forbid using other HTML tags; just said use for headings, - for lists,
for prose. Using is okay as part of prose. But maybe better to just plain text: "Location: Lake Oswego, OR; Westminster, CO; Alpharetta, GA (In Office). Travel Requirement: Up to 10%." That's fine.
Now Why You'll Love Working With Us
with paragraphs.
Then Benefits
with paragraph.
Then Pay
with paragraph about compensation range, pay rate type, bonus eligible, commission eligible.
Make sure not to include filler like "commensurate with experience". Not present.
Check for any duplicated lines: we should avoid repeating same sentence.
Now ensure we removed application instructions, EEO, etc.
Let's extract the exact text for each section.
About Us:
"Trimble is an industrial technology company transforming the way the world works by delivering solutions that enable our customers to thrive. We create technologies that connect the digital and physical worlds, helping our customers increase productivity, quality, safety, and sustainability. From purpose-built products to enterprise-level solutions, our technology empowers professionals in construction, geospatial, government, transportation, and more."
What Makes This Role Great:
"In this role, you will sit at the center of client success, serving as the strategic liaison between cross-functional teams, external stakeholders, and key customer accounts. You will directly influence how businesses optimize their operational data flows while driving complex software implementation projects from concept through final delivery."
Key Exciting Responsibilities: list as given.
Essential Skills & Experience: list as given.
Bonus Points For: list as given.
Logistics: "Location: Lake Oswego, OR, Westminster, CO, Alpharetta, GA (In Office). Travel Requirement: Up to 10%."
Why You'll Love Working With Us: multiple paragraphs:
"At Trimble, we're not just a company that "does good"—we are a team dedicated to making a tangible, positive Real-World Impact. We build innovative solutions designed to solve the world's most critical challenges. From construction sites to transportation hubs, our work tangibly improves how people live, build, move, and grow. You'll work on projects that truly matter: Our purpose-driven culture means you'll be helping to build and deliver solutions that make work faster, safer, and more sustainable for millions of people worldwide. Our impact is tangible, from connected machines that save fuel to data-driven insights that reduce waste.
Collaborate with like-minded people: Our strong internal culture is a "hidden gem." You will work with a collaborative, supportive team that shares your purpose and fosters a genuine sense of belonging. We're a company of "visionary pragmatists" who think boldly and build things that work. Be an owner: Trimble thrives on individuals who take initiative and embrace ownership. You'll find an entrepreneurial spirit where success is often "self-authored," empowering proactive "doers.""
Benefits:
"Trimble offers comprehensive core benefits that include Medical, Dental, Vision, Life, Disability, Time off plans and retirement plans. Most of our businesses
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to produce sections only where there is real content. Let's parse the posting: - Title: "Transform Software Implementations as Our Next Professional Services Project Manager!" (we ignore as heading not needed) - About Us: paragraph about Trimble. - What Makes This Role Great: paragraph describing role. - Key Exciting Responsibilities: list of bullet points (starting with "Spearhead end-to-end..." etc). Should be
- .
- Essential Skills & Experience: list of bullet points (starting with "Bachelor's degree..." etc). Should be
- .
- Bonus Points For: list of bullet points (starting with "Prior consulting experience..." etc). Should be
- .
- Logistics: Location and Travel Requirement. Could be a short paragraph or list. The posting says: "Logistics Location: Lake Oswego, OR, Westminister, CO, Alpharetta, GA (In Office) Travel Requirement: Up to 10%". That's specific content. Should we make a section "Logistics"? The allowed headings include "Schedule" but not "Logistics". However we can use any heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. Likely we should stick to those headings where applicable. For location and travel, maybe we can incorporate into a short
without a heading? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location and travel might be considered minor metadata, but they are substantive. Could embed in a
without heading. However they said "include a section ONLY when the posting has real, specific content for it". Could we make a section "Logistics"? Not in examples but maybe acceptable. Safer to not create a heading for logistics; just include a
with that info. - Why You'll Love Working With Us: paragraph(s) about culture, impact, etc. Should be a section maybe "About the role"? Actually "Why You'll Love Working With Us" is like a benefits/culture section. Could map to "Benefits"? But Benefits section is separate. Could treat as "About the role"? Not exactly. Perhaps we can create a heading "Why You'll Love Working With Us" as
. The instruction didn't forbid other headings, just gave examples. It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we can also use others if they match content? The examples are just examples; likely they expect us to use those headings for the standard sections. For "Why You'll Love Working With Us", maybe we can treat as part of "Benefits" or "About the role". But there is already a Benefits section later. The "Why You'll Love Working With Us" includes culture, impact, collaborative team, ownership spirit. That's more about company culture and benefits beyond compensation. Could be part of "Benefits" but Benefits already defined as medical etc. Might be better to create a heading "Why You'll Love Working With Us". The instruction didn't forbid; it just gave examples. I'd include it as a section. - Benefits: paragraph about medical, dental, etc. Should be a section with heading Benefits. - Compensation: includes hiring range, pay rate type, bonus eligible, commission eligible. Should be a section with heading Pay (or Compensation). The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use "Pay" heading for compensation. - Schedule: Not mentioned; there is no schedule info besides full time schedule mentioned in compensation description. Not specific schedule like hours. So we should not create a Schedule section. - Also there is a line: "Compensation: Trimble provides the following compensation range and general description of other compensation and benefits that it in good faith believes it might pay and/or offer for this position. This compensation range is based on a full time schedule." That's the compensation. - Also there is a line: "If this position is identified above as commission- or bonus-eligible, the terms of the commission plan or discretionary bonus plan for which you are eligible will be provided following the employee start date." That's part of compensation. - Also there is a line: "How to Apply: ..." which is application instructions, we must remove. - Also EEO boilerplate etc remove. - Also duplicated lines: maybe some repeated sentences? We'll just keep unique. Now produce HTML fragment. Structure:
About Us
...
What Makes This Role Great
...
Responsibilities
- Spearhead end-to-end software implementation projects, establishing unified project designs that align customer goals with strategic implementation methodology.
- Direct multi-organizational project tasks into single, cohesive plans while actively forecasting efforts, milestones, and deliverables.
- Cultivate strong client relationships through proactive account management, education on operational data flow, and swift issue resolution.
- Lead remote, matrixed project teams to consistently meet delivery deadlines, maintain project scopes, and ensure resource alignment.
- Execute robust risk identification and mitigation strategies to keep complex, parallel projects running on schedule and within budget.
Requirements
- Bachelor's degree in business or a related field with 4+ years of project management experience (or 7+ years of relevant project management experience in lieu of a degree).
- Proven expertise with industry-standard project management methodologies such as PMBOK or Agile.
- Strong track record of driving multiple parallel projects while successfully leading remote teams within a matrix environment.
- Demonstrated excellence in client management, relationship building, requirement gathering, and negotiation.
- Expert capability in identifying project risks and executing effective mitigation strategies. // Wait need exact text: "Expert capability in identifying project risks and executing effective mitigation strategies."
Skills
maybe for Bonus Points? Actually Bonus Points For could be "Skills" or "Qualifications". Let's treat Bonus Points For as "Skills" or "Qualifications". The instruction includes Skills as a possible heading. We'll put Bonus Points For underSkills
with list. Alternatively we could have both Requirements and Skills. Let's do:Requirements
for Essential Skills & Experience.Skills
for Bonus Points For. Now Logistics: we can include awithout heading: maybe after Skills.
Location: Lake Oswego, OR; Westminster, CO; Alpharetta, GA (In Office). Travel: Up to 10%.
But we should not invent tags like ? The instruction didn't forbid using other HTML tags; just said usefor headings,
- for lists,
for prose. Using is okay as part of prose. But maybe better to just plain text: "Location: Lake Oswego, OR; Westminster, CO; Alpharetta, GA (In Office). Travel Requirement: Up to 10%." That's fine. Now
Why You'll Love Working With Us
with paragraphs. ThenBenefits
with paragraph. ThenPay
with paragraph about compensation range, pay rate type, bonus eligible, commission eligible. Make sure not to include filler like "commensurate with experience". Not present. Check for any duplicated lines: we should avoid repeating same sentence. Now ensure we removed application instructions, EEO, etc. Let's extract the exact text for each section. About Us: "Trimble is an industrial technology company transforming the way the world works by delivering solutions that enable our customers to thrive. We create technologies that connect the digital and physical worlds, helping our customers increase productivity, quality, safety, and sustainability. From purpose-built products to enterprise-level solutions, our technology empowers professionals in construction, geospatial, government, transportation, and more." What Makes This Role Great: "In this role, you will sit at the center of client success, serving as the strategic liaison between cross-functional teams, external stakeholders, and key customer accounts. You will directly influence how businesses optimize their operational data flows while driving complex software implementation projects from concept through final delivery." Key Exciting Responsibilities: list as given. Essential Skills & Experience: list as given. Bonus Points For: list as given. Logistics: "Location: Lake Oswego, OR, Westminster, CO, Alpharetta, GA (In Office). Travel Requirement: Up to 10%." Why You'll Love Working With Us: multiple paragraphs: "At Trimble, we're not just a company that "does good"—we are a team dedicated to making a tangible, positive Real-World Impact. We build innovative solutions designed to solve the world's most critical challenges. From construction sites to transportation hubs, our work tangibly improves how people live, build, move, and grow. You'll work on projects that truly matter: Our purpose-driven culture means you'll be helping to build and deliver solutions that make work faster, safer, and more sustainable for millions of people worldwide. Our impact is tangible, from connected machines that save fuel to data-driven insights that reduce waste. Collaborate with like-minded people: Our strong internal culture is a "hidden gem." You will work with a collaborative, supportive team that shares your purpose and fosters a genuine sense of belonging. We're a company of "visionary pragmatists" who think boldly and build things that work. Be an owner: Trimble thrives on individuals who take initiative and embrace ownership. You'll find an entrepreneurial spirit where success is often "self-authored," empowering proactive "doers."" Benefits: "Trimble offers comprehensive core benefits that include Medical, Dental, Vision, Life, Disability, Time off plans and retirement plans. Most of our businesses
- .
- Logistics: Location and Travel Requirement. Could be a short paragraph or list. The posting says: "Logistics Location: Lake Oswego, OR, Westminister, CO, Alpharetta, GA (In Office) Travel Requirement: Up to 10%". That's specific content. Should we make a section "Logistics"? The allowed headings include "Schedule" but not "Logistics". However we can use any heading? The instruction says use
- .
- Bonus Points For: list of bullet points (starting with "Prior consulting experience..." etc). Should be