Business Systems Analyst – Refining Digital Operations

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include only sections with real specific content. We need to parse the posting. First, there is an introductory paragraph: "An exciting career awaits you At MPC, we’re committed to being a great place to work – one that welcomes new ideas, encourages diverse perspectives, develops our people, and fosters a collaborative team environment." Then "Position Summary Join the Refining Digital team..." etc. That's about the role. So we can have an

About the role

with paragraphs summarizing the position summary. We must not repeat job title as heading. The job title is Business Systems Analyst (implied). Not to repeat. We need to include Responsibilities: list of key responsibilities bullet points. We need Education and Experience: maybe under Requirements or Qualifications. The posting has "Education and Experience" section. We can treat as Requirements (or Qualifications). We need to decide which headings to use. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content exists. But we should avoid thin sections. Likely we can combine Education and Experience into Requirements, and maybe Skills separate. We have Skills list: Adaptability, AI Fundamentals, Change Management, Agile Methodologies, Analytical Thinking, Authentic Communicator, Business Analysis, Business Partner Relations. That's a list. We have Benefits: "Marathon Petroleum offers a total rewards program which includes, but is not limited to, access to health, vision, and dental insurance, paid time off, 401k matching program, paid parental leave, and educational reimbursement. Detailed benefit information is available at mympcbenefits.com. The hired candidate will also be eligible for a discretionary company-sponsored annual bonus program." That's benefits content. Pay: "Pay Min/Max: $80,800.00 - $139,500.00 Salary Grade: 9 - 10". That's pay specifics. Schedule: Not mentioned explicitly. There's location and maybe full-time. It says "Employee Group: Full time Employee Subgroup: Regular". That indicates schedule: full-time. So we can include Schedule section with "Full-time". However we need to check if we should include Schedule only if posting actually states them. It does state Employee Group: Full time. So we can include Schedule. Location: Not a heading we need to output; we can fold location into a short paragraph maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and maybe job ID in a short paragraph. We must remove boilerplate: EEO, legal, accommodation, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all substantive content from the posting, but we can reformat. Let's extract substantive content: - Intro: "An exciting career awaits you At MPC, we’re committed to being a great place to work – one that welcomes new ideas, encourages diverse perspectives, develops our people, and fosters a collaborative team environment." - Position Summary: "Join the Refining Digital team and play a key role in shaping technology solutions that drive safety, reliability, efficiency, and business value across 15 refineries. As a Business Systems Analyst, you will partner with end users across the Refining landscape and particularly operators to deliver innovative digital capabilities that solve real-world challenges for frontline workers and operators. This role offers the opportunity to work with cutting-edge technologies including Digital Twins, connected worker solutions, industrial data platforms, and advanced analytics. If you are energized by transforming complex operational needs into impactful digital solutions, this is your chance to help define the digital future of MPC Refining. This position belongs to a family of jobs with increasing responsibility, competency, and skill level. Actual position title and pay grade will be based on the selected candidate’s experience and qualifications." - Key Responsibilities: list bullet points (we need to preserve each). Let's extract them exactly as given: 1. Manages the definition of business processes in order to measure, analyze, improve and control the process being reviewed. 2. Drive results by leading initiatives from concept through implementation, maintaining focus on business outcomes, value realization, and user adoption. 3. Communicates effectively with stakeholders, aligning the understanding of requirements, and identifying cross functional changes/impacts of the specifications for solution delivery. 4. Collaborate across highly cross-functional teams to align priorities, resolve challenges, and ensure successful delivery of strategic digital initiatives. 5. Develops recommendations for appropriate systems alternatives and/or enhancements to current systems. 6. Investigates business performance and other measures to gain insight and drive business planning; applies continuous iterative processes. 7. Performs cost benefit and return on investment analyses for proposed systems to aid management in making implementation decisions. 8. Supports implementation of ways to improve working processes in the team. 9. Supports monitoring the execution of IT service management practices around incident, Change, Problem and Solution Development Lifecycle (SDLC) delivery methodologies for improvement and collaboration, including more advanced configuration tasks. 10. Coordinates test case development, execution and support of strategy creation for technology delivery. 11. Plans, executes, and documents user stories, user feedback to support the development of prototypes and wireframes. - Education and Experience: "Bachelor’s Degree in Information Systems preferred, related field or equivalent experience. 2+ years of relevant experience required Experience with Data Contextualization or Industrial Digital Twin technologies is preferred. Experience supporting refining, manufacturing, industrial, or operational technology (OT) environments is preferred. Experience developing or supporting digital tools for rounds, logbooks, task tracking, or digital permitting capabilities is preferred. Proven ability to drive efforts across diverse teams and drive successful outcomes in complex environments preferred." We need to keep each bullet? It's a paragraph with sentences. We can keep as

or break into

• . The instruction: Use
  • for any list of duties/requirements/benefits. So for Education and Experience, it's a list of requirements. We can make a
    • for each requirement. - Skills: list of skills with descriptions. We can make
      • each skill with its description. - Benefits: paragraph as above. - Pay: "Pay Min/Max: $80,800.00 - $139,500.00 Salary Grade: 9 - 10". We'll put in

        maybe under Pay heading. - Schedule: "Employee Group: Full time Employee Subgroup: Regular". So schedule: Full-time. - Location: "Location: Findlay, Ohio Job Requisition ID: 00024294 Pay Min/Max: $80,800.00 - $139,500.00 Salary Grade: 9 - 10 Location Address: 539 S Main St Additional locations: ..." We need to include location info but not as heading. We can fold location and maybe job ID into a short

        after About the role or separate. Since we already have Pay heading, we should not duplicate Pay Min/Max there. We'll put location info in a

        maybe under About the role or separate "Details". But we should not create a heading for location unless we have a specific heading like "Location". Not in the list of allowed headings. So we can just include a paragraph after About the role: "

        Location: Findlay, Ohio (with additional sites in Anacortes, Washington; Canton, Ohio; Carson, California; Catlettsburg, Kentucky; Denver CO; Detroit, Michigan; Dickinson, North Dakota; El Paso, Texas; Garyville, Louisiana; Houston TX One Allen Center; Kenai, Alaska; Mandan, North Dakota; Martinez, California; Robinson, Illinois; Salt Lake City, Utah; San Antonio, Texas; St Paul Park, Minnesota; Texas City, Texas; Wilmington, California). Job Requisition ID: 00024294.

        " However we need to avoid duplicating Pay Min/Max again; we already have Pay heading. So we should not repeat Pay Min/Max there. We'll omit that. We need to ensure we preserve all substantive information: The location address: "Location Address: 539 S Main St". Additional locations list. We'll include that. We also have "Education: Employee Group: Full time Employee Subgroup: Regular". Actually that appears after location list: "Education: Employee Group: Full time Employee Subgroup: Regular". Wait the text: "Location Address: 539 S Main St Additional locations: ... Education: Employee Group: Full time Employee Subgroup: Regular". It seems "Education:" maybe a label for employee group? Actually it's weird: after location list, they wrote "Education: Employee Group: Full time Employee Subgroup: Regular". Probably they meant "Employee Group: Full time Employee Subgroup: Regular". So we have schedule info there. We also have "Marathon Petroleum Company LP is an Equal Opportunity Employer..." which we must remove as boilerplate. We also have the accommodation paragraph, remove. We also have the total rewards program paragraph (benefits) we keep. We also have "Detailed benefit information is available at mympcbenefits.com." keep as part of benefits. We also have "The hired candidate will also be eligible for a discretionary company-sponsored annual bonus program." keep. We also have the EEO Veteran/Disability paragraph, remove. Now we need to decide headings. We have: - About the role: combine intro and position summary. - Responsibilities: list of key responsibilities. - Requirements: maybe Education and Experience. - Qualifications: maybe we could also have a separate Qualifications section for preferred qualifications? But we already have requirements includes preferred. To avoid thin sections, we could combine Education and Experience and maybe also Skills? But Skills is separate heading allowed. We'll keep Skills separate. - Benefits: as described. - Pay: as described. - Schedule: as described. We should not create a heading if content is thin. Let's evaluate each: About the role: we have substantive paragraphs. Responsibilities: we have list of 11 items -> good. Requirements: we have education and experience list (Bachelor's, 2+ years, experience with Data Contextualization, etc.) -> good. Skills: we have list of 8 skills with descriptions -> good. Benefits: we have paragraph about health, vision, dental, PTO, 401k, parental leave, educational reimbursement, bonus program -> good. Pay: we have specific numbers -> good. Schedule: we have "Full time" -> maybe thin but it's substantive (states full-time). Could be considered thin but it's actual info. The instruction: Prefer a few substantive sections over many thin ones. But schedule is a real piece of info; we could include it. It's not filler like "commensurate with experience". It's specific. So we include Schedule. We also need to include location info somewhere. Could be part of About the role or a separate short paragraph without heading. Since we cannot create a heading for location (not in list), we just add a

        after About the role maybe. We must not repeat job title as heading. We are not. We must not put Job ID/requisition numbers as headings; we will fold into a short

        . Now produce HTML fragment. Structure:

        About the role

        An exciting career awaits you At MPC, we’re committed to being a great place to work – one that welcomes new ideas, encourages diverse perspectives, develops our people, and fosters a collaborative team environment.

        Join the Refining Digital team and