Business Systems Analysis Management

We need to output HTML fragment with sections: About the role? Actually the posting includes "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 use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The instruction says: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. 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. Thus we need to decide which sections to include based on content. We have: - About Us (company description) -> could be "About the role"? Actually "About Us" is about company, not role. But we could treat as "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. We have: - What Makes This Role Great -> could be "About the role" (description of role). We'll put that under

About the role

. - Key Exciting Responsibilities ->

Responsibilities

with list. - Essential Skills & Experience -> could be

Requirements

or

Qualifications

or

Skills

. The instruction says we can use Skills, Qualifications, Requirements. We need to decide. Probably combine skills and experience into Requirements or Qualifications. Since they list "Essential Skills & Experience" and "Bonus Points For". We could have

Requirements

for essential skills, and maybe

Preferred Qualifications

but not in list. However instruction says we should only include sections when posting has real specific content. We have essential skills and bonus points. Could combine both into one

Skills

with sublists? But better to follow instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can pick a few. We have compensation details: Pay range $99,600–$137,000, bonus eligible yes, commission no. So we should include Pay section. We have Benefits: comprehensive core benefits list. So include Benefits section. We have Schedule? Not mentioned besides full time schedule implied. No explicit schedule details. So we should not create Schedule section unless posting actually states them. It mentions "This compensation range is based on a full time schedule." That's not a schedule description like "Monday-Friday, 9-5". Probably not enough to create Schedule section. So skip. We have Location: Westminster, CO or Dayton, OH (In Office). Travel 0-10%. That's logistics. Could be part of "About the role" or maybe a separate section like "Location". But instruction only lists those headings; we could fold location into a short

under About the role or maybe under Responsibilities? Better to include a short paragraph after About the role maybe as part of same section? The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Location is minor metadata; we can fold into a short

within About the role or maybe after. We also have "Why You'll Love Working With Us" which is culture/benefits narrative. Could be part of Benefits or maybe a separate section like "About the role"? But we already have Benefits section for tangible benefits. The culture narrative could be included under Benefits? Might be better to include under "About the role" as description of role environment. However we already have About the role describing what makes role great. Could combine "What Makes This Role Great" and "Why You'll Love Working With Us" into About the role section. That seems reasonable. We need to preserve all substantive information; not invent or summarize away detail. So we need to include all details from those sections. Thus plan:

About the role

Include description from "What Makes This Role Great" and "Why You'll Love Working With Us" plus location and travel maybe.

Then

Responsibilities

with

• list each responsibility. Then

  Requirements

  (or Skills) with essential skills & experience list. Then

  Benefits

  with list of benefits. Then

  Pay

  with compensation range and bonus eligibility. We must not include sections like Qualifications if we already have Requirements; but we could also include Qualifications separate. However instruction says prefer a few substantive sections over many thin ones. So we can combine essential skills and bonus points into Requirements. We need to ensure we don't create sections with filler text. All sections have real content. Now we need to strip boilerplate: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to remove the "How to Apply", "Application Deadline", EEO statements, etc. Also remove the "Compensation: Trimble provides the following compensation range..." but we need to keep the compensation range and bonus eligible info. However the paragraph includes some legal disclaimer: "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." That's boilerplate? It's part of compensation description but maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal disclaimer about compensation; might be considered legal boilerplate. However we need to preserve ALL substantive information; does that disclaimer count as substantive? It's a standard disclaimer; maybe we can drop it as legal boilerplate. The substantive info is the range, bonus eligible yes, commission eligible no. So we can keep that. Similarly benefits paragraph includes some legal disclaimer: "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 also boilerplate; we can drop. We also need to remove duplicated lines. Now craft HTML. Let's extract content. About Us description: "Corporate: 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. For more information about Trimble (Nasdaq:TRMB), visit: www.trimble.com." What Makes This Role Great: "In this role, you will be at the center of our digital evolution, acting as the ultimate technical authority for enterprise Oracle systems while spearheading operational readiness and knowledge transfer for our ongoing migration to Oracle Fusion Financials." Why You'll Love Working With Us: paragraphs about real-world impact, collaborative culture, owner mindset. We'll combine. Location: "Logistics Location: Westminster, CO or Dayton, OH (In Office) Travel Requirement: 0-10%" We'll include location and travel in About the role paragraph. Now Responsibilities list: - Spearhead global Tier 2/3 support and resolve high-impact technical and functional challenges across SCM, Inventory, WMS, O2C, and Financials. - Drive operational readiness, seamless knowledge transfer, and system stability during our major ERP transformation from Oracle EBS 12.2 to Oracle Fusion. - Champion IT service management excellence using Jira to ensure ticket SLAs are consistently met and clear support metrics are delivered to leadership. - Master advanced backend troubleshooting by writing, reading, and executing complex PL/SQL scripts to analyze data and implement critical fixes. - Lead, mentor, and empower a high-performing, globally distributed IT support team to foster continuous improvement and professional growth. Now Essential Skills & Experience: - 8-12+ years of hands-on technical and functional experience with Oracle E-Business Suite, including extensive exposure to version 12.2. - Deep functional expertise across Oracle SCM, Inventory, Shipping, WMS, Order to Cash (O2C), and Financials modules. - Proven track record leading, managing, and mentoring globally distributed IT support teams. - Advanced proficiency writing, debugging, and troubleshooting complex PL/SQL queries and scripts. - Practical experience utilizing Jira for ITSM workflow tracking, SLA monitoring, and issue resolution. Bonus Points For: - Hands-on implementation or support experience with Oracle Fusion Financials. - Strong familiarity with SOX compliance controls, ERP security architectures, and enterprise job scheduling management. We'll combine these into Requirements list. Now Benefits list: - Medical, Dental, Vision, Life, Disability, Time off plans and retirement plans. - Tax savings plans for health, dependent care and commuter expenses. - Paid Parental Leave. - Employee Stock Purchase Plan. We can also mention "comprehensive core benefits". We'll list as items. Now Pay: - Hiring Range $99,600.00–$137,000.00 - Pay Rate Type Salary - Bonus Eligible? Yes - Commission Eligible? No We'll present as

  or

  . Probably
  • for each. Now ensure no markdown fences, just HTML. Let's craft. We'll start with

    About the role

    then

    containing combined paragraphs. We need to avoid duplication: The About Us description is about company; we can include it as part of About the role? Might be okay. The instruction says About the role heading; we can include company description there. Let's write:

    About the role

    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. In this role, you will be at the center of our digital evolution, acting as the ultimate technical authority for enterprise Oracle systems while spearheading operational readiness and knowledge transfer for our ongoing migration to Oracle Fusion Financials. 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