Jobs · Oregon

ERP Business Advisor

Trimble Inc. · Lake Oswego, OR · 1 mo ago
Full-time
We need to output HTML fragment with sections: About the role? Actually we have sections: About Us, What Makes This Role Great, Key Exciting Responsibilities, Essential Skills & Experience, Bonus Points For, Logistics, Why You'll Love Working With Us, Compensation, Benefits, etc. Need to follow rules: Use

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. We need to decide which sections to include based on content. We have: - About Us (company description) - What Makes This Role Great (role description) - Key Exciting Responsibilities (list) - Essential Skills & Experience (list) - Bonus Points For (list) - Logistics (Location, Travel Requirement) - Why You'll Love Working With Us (company culture, impact) - Compensation (range, pay rate type, bonus eligible, commission eligible) - Benefits (list) - Possibly also "How to Apply" etc but we need to remove application instructions. We need to avoid boilerplate like EEO, diversity statement, privacy notices, etc. Remove those. We need to keep substantive info. We need to use

    for section headings. Use
    • for any list of duties/requirements/benefits. Use

      for prose. We need to not repeat job title as heading. We need to not include Job ID etc. We need to include Pay and Benefits sections only if posting actually states them. Yes compensation and benefits are present. We need to include Schedule? Not present; we have logistics location and travel requirement but not schedule (like work hours). Could include Logistics as a section maybe with heading "Logistics". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? It says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples; we can use those headings if appropriate. But we can also use other headings? Probably better to stick to those examples. However we have sections like About Us, What Makes This Role Great, Key Exciting Responsibilities, Essential Skills & Experience, Bonus Points For, Logistics, Why You'll Love Working With Us, Compensation, Benefits. We could map: - About Us -> About the role? Actually About Us is about company, not role. Could use "About the role" for role description? But we have "What Makes This Role Great" which is about role. Could use "About the role" heading for that. But we also have "Key Exciting Responsibilities" which could be "Responsibilities". "Essential Skills & Experience" could be "Requirements" or "Skills". "Bonus Points For" could be "Qualifications". "Logistics" maybe not in list but could be omitted or placed under a short p? However instruction says include a section ONLY when posting has real, specific content for it. Logistics has location and travel requirement, that's specific. Could we put that under a heading like "Logistics"? Not in examples but maybe allowed. The instruction says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. Safer to map to those headings. Thus we could produce sections: - About the role (combining What Makes This Role Great and maybe About Us? Actually About Us is company description; could be separate but not in list. Could omit About Us? But we need to preserve ALL substantive information. So we need to include company description somewhere. Could put it under a heading like "About the company" but not in list. However we could incorporate it into "About the role" maybe? But that would mix company description with role description; still substantive. Might be okay. Alternatively we could create a section "About Us" as heading, even though not in examples; but instruction says use h3 for section headings (e.g. ...). It doesn't say you cannot use other headings, just gives examples. Likely acceptable to use other headings as long as they are h3. To be safe, we could use the examples but also add others if needed. However risk: they might check for only those headings? Not sure. The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies we should use those headings where applicable, but we can also use other headings if needed? The examples are just examples; they didn't say "only these". I'd assume we can use other headings as long as they are h3. Thus we can keep headings: About Us, What Makes This Role Great, Key Exciting Responsibilities, Essential Skills & Experience, Bonus Points For, Logistics, Why You'll Love Working With Us, Compensation, Benefits. We need to ensure we don't include filler sections. Now we need to convert content into appropriate HTML. We need to remove boilerplate: EEO statements, diversity, privacy notices, application instructions (How to Apply, Application Deadline, etc). Also remove duplicated lines. We need to preserve all substantive info: company description, role description, responsibilities list, skills/experience list, bonus points, logistics (location, travel), why you'll love working with us (impact, culture), compensation (range, pay rate type, bonus eligible, commission eligible), benefits list. We need to format lists as
      • . We need to use

        for prose paragraphs. We need to not include job title heading. We need to not include Job ID etc. Now let's extract content. Original posting: "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 prose; could be part of About the role or What Makes This Role Great. Then "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." That's About Us. "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." That's role great. "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." That's responsibilities list; each sentence could be a bullet. "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." That's skills/experience list. "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." That's bonus points. "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." That's logistics. "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." That's why you'll love working with us. "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" That's compensation. "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." That's benefits

Similar jobs

ERP Advisory

Dynatrum Canada IncVendor, AR· 2 mo ago
Salesapply on dynatrum.com

ERP Specialist Advisor

NTT DATA North AmericaPlano, TX· Yesterday
Information Technology$107k–$198k/yrapply on careers.nttdata.com

ERP Specialist Advisor

NTT DATA North AmericaOakbrook Terrace, IL· 2 mo ago
Information Technology$175k–$198k/yrapply on careers.services.global.ntt

Business Advisor

Hunt RemotelyProvo, UT· 3 mo ago
Consultingapply on huntremotely.com

Business Advisor

CapgeminiBridgewater, NJ· 3 mo ago
Consultingapply on capgemini.com