ERP Business Advisor

We need to output HTML fragment only, with sections as per rules. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive information. We need to parse the posting. Key parts: - Title: Revolutionize the Construction Industry as our Next Construction ERP Business Advisor (Viewpoint Vista)! (we ignore as heading) - About Us: description of Trimble. - What Makes This Role Great: description. - Key Exciting Responsibilities: bullet list. - Essential Skills & Experience: list. - Bonus Points For: list. - Logistics: Location, Travel Requirement. - Why You'll Love Working With Us: description. - Compensation: includes hiring range, pay rate type, bonus eligible, commission eligible, benefits description. - Benefits: described. - How to Apply etc: we should remove application instructions. - EEO etc: remove. We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. "About the role": could be the "What Makes This Role Great" plus maybe "About Us"? Actually "About the role" likely describes the role itself. Could combine "What Makes This Role Great" and maybe the initial paragraph about bridging gap etc. We'll include substantive content. "Responsibilities": from "Key Exciting Responsibilities". "Requirements": maybe from "Essential Skills & Experience" (the required). Could also include "Bonus Points For" as "Qualifications" or "Skills"? The spec includes sections: Requirements, Qualifications, Skills. We need to decide distribution. We have: - Essential Skills & Experience (required): 3-5 years Vista ERP, proven background in client services, technical consulting, or field experience within construction, strong track record building relationships with contractors, exceptional communication skills, Bachelor’s degree or equivalent. - Bonus Points For: advanced degree, familiarity with broader suite, experience navigating matrixed environment. We could map: Requirements: the essential skills & experience (mandatory). Qualifications: maybe education (Bachelor's) or advanced degree? But we already have education in essential. Could treat "Qualifications" as the bonus points (preferred qualifications). Or we could split: Requirements = essential experience; Qualifications = education + bonus points; Skills = specific skills (communication, technical). But we need to avoid filler. Better: Use sections: - About the role: includes introductory paragraph and "What Makes This Role Great". - Responsibilities: list from Key Exciting Responsibilities. - Requirements: Essential Skills & Experience (mandatory). - Qualifications: Bonus Points For (preferred). - Skills: maybe we can extract specific skills like "Exceptional communication skills", "Strong track record of building influential relationships", "Deep hands-on technical expertise with Viewpoint Vista ERP". But those are already in requirements. Could combine. But we need to avoid duplication. Perhaps we can put Skills as a subsection of Requirements? But spec says we can have sections only if real content. We could omit Skills if not distinct. However we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills if not needed. Similarly Schedule: we have logistics: Location and Travel Requirement. That could be Schedule? Actually schedule refers to work schedule (in office 4 days a week, 1 day from home). Travel requirement is separate but could be placed under Schedule or maybe under Logistics not a defined section. We have a Schedule section allowed; we can put location and travel there. Pay: we have compensation range, pay rate type, bonus eligible, commission eligible. Benefits: we have benefits description. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Benefits, Schedule. We must not include empty sections. Now we need to format. Use

for each heading. Then content: use

for prose,

• for lists. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details exactly as given, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Probably we should keep the wording close but can adjust for HTML. Safer to copy sentences. We need to remove boilerplate: navigation, legal, EEO, etc. Also remove "How to Apply", "Application Deadline", EEO statements, etc. We need to keep location, travel requirement. Let's extract substantive paragraphs. Original text: "Revolutionize the Construction Industry as our Next Construction ERP Business Advisor (Viewpoint Vista)! Are you ready to transform how the world builds? As a Construction ERP Business Advisor at Trimble, you will bridge the gap between complex technology and real-world construction outcomes. You will empower General and Specialty Contractors to master Viewpoint Vista, driving digital transformation and ensuring our partners realize maximum value from their investment. Join a team where your expertise directly builds a more productive and sustainable future for global infrastructure." That's introductory. "About Us Trimble is a global technology company that connects the physical and digital worlds, transforming the ways work gets done. With relentless innovation in precise positioning, modeling and data analytics, Trimble enables essential industries including construction, geospatial and transportation. Whether it's helping customers build and maintain infrastructure, design and construct buildings, optimize global supply chains or map the world, Trimble is at the forefront, driving productivity and progress. The Trimble AECO segment provides digital construction solutions that increase precision and productivity for Architecture, Engineering, Construction, and Operations." "What Makes This Role Great In this role, you will act as a high-impact strategic consultant within the Trimble Construction One ecosystem, moving beyond standard support to shape the long-term technology roadmaps of industry-leading contractors. You will have the unique opportunity to serve as a trusted advocate and domain expert, directly influencing how the construction industry adopts SaaS solutions and making a tangible impact on the efficiency of global building projects." "Key Exciting Responsibilities Serve as a premier Vista ERP domain expert, architecting product strategies and technical best practices that empower customers to conquer complex business challenges. Enhance product value for customers through the post-sale process by evaluating existing workflows and providing optimal strategies to facilitate adoption. Spearhead strategic adoption roadmaps and executive-level business reviews, acting as a vital bridge between customer needs and Trimble’s innovative product evolution. Drive the continuous improvement of value realization practices, capturing and scaling success stories across the global Customer Success organization. Orchestrate cross-functional collaboration with Sales, Product, and Support teams to advocate for customer requirements and ensure seamless long-term success." "Essential Skills & Experience 3 to 5 years of deep, hands-on technical expertise with Viewpoint Vista ERP software. Proven background in client services, technical consulting, or field experience within the construction industry. Strong track record of building influential relationships with General, Heavy Highway, or Specialty Contractors. Exceptional communication skills with the ability to translate complex technical concepts for executive-level stakeholders. Bachelor’s degree (BA/BS) or equivalent professional experience." "Bonus Points For Advanced degree in Business, Construction Management, or a related technical field. Familiarity with the broader suite of Trimble Construction technologies and SaaS ecosystems. Experience navigating and influencing within a complex, matrixed corporate environment." "Logistics Location: Denver, CO or Portland, OR metro area - in office 4 days a week and 1 day from home. Travel Requirement: Approximately 10-25% depending on customer engagement needs." "Why You'll Love Working With Us 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." "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. Trimble reserves the right to ultimately pay more or less than the posted range and offer additional benefits and other compensation, depending on circumstances not related to an applicant’s sex or other status protected by local, state, or federal law. Hiring Range $105,600.00–$145,200.00 Pay Rate Type Salary Bonus Eligible? Yes Commission Eligible? No Benefits: Trimble offers comprehensive core benefits that include Medical, Dental, Vision, Life, Disability, Time off plans and retirement plans. Most of our businesses also offer tax savings plans for health, dependent care and commuter expenses as well as Paid Parental Leave and Employee Stock Purchase Plan. 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." We need to remove the "How to Apply" etc. Now we need to map to sections. About the role: Could combine the introductory paragraph + About Us + What Makes This Role Great? But About Us is about company, not role. Might be better to put About Us under About the role? The spec says "About the role" heading for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So About the role likely includes description of the role and maybe company context. We'll include the introductory paragraph and What Makes This Role Great. Possibly also include About Us? It's about Trimble, not role. But we could include it as part of About the role to give context. However the instruction: "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." About Us is not minor metadata; it's substantive about company. Could be placed under About the role or maybe we could create a separate section? Not allowed; only those headings. So we must fit it somewhere. Probably About the role is appropriate to include company overview. Thus About the role content: introductory paragraph + About Us + What Makes This Role Great. We'll need to ensure we don't lose any detail. Now Responsibilities: list from Key Exciting Responsibilities. Requirements: Essential Skills & Experience. Qualifications: Bonus Points For. Pay: compensation range, pay rate type, bonus eligible, commission eligible. Benefits: benefits description. Schedule: location and travel requirement (including in-office 4 days, 1 day home, travel 10-25%). We must not include filler like "commensurate with experience" etc. Not present. Now we need to output HTML only. We'll produce:

  About the role

  ...

  But we may have multiple paragraphs; we can combine into one

  with sentences separated by space. Or we can use multiple

  elements. The rule: use

  for prose. So each paragraph can be its own

  . We'll split logically. We need to preserve all substantive information; we can keep sentences as is. Let's craft About the role: Paragraph 1: "Revolutionize the Construction Industry as our Next Construction ERP Business Advisor (Viewpoint Vista)! Are you ready to transform how the world builds? As a Construction ERP Business Advisor at Trim