Mechanic I

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

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only if posting has real specific content. We need to parse the posting. The posting includes: - Intro: "Your Impact at Lowe's As a maintenance Mechanic I, you play an important role..." This is about role, could be "About the role". We'll put that in

About the role

with

. - "How We Support You" includes safety, culture, financial future, bonus potential, health and wellbeing. That's benefits. So we can have

Benefits

with

• items. - "Your Day at Lowe's" describes duties; could be part of responsibilities. We'll include responsibilities. - "Key Responsibilities" list bullet points. - "Minimum Qualifications" list. - "Preferred Qualifications" list. - "Schedule Requirements" list. - "Working Conditions" maybe part of responsibilities or qualifications? Could be part of responsibilities or maybe not a separate heading; but we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have content for: - About the role (intro + impact + how we support you? Actually "How We Support You" is benefits; but we can treat that as Benefits.) - Responsibilities: includes "Your Day at Lowe's" and "Key Responsibilities". Could combine. - Requirements: maybe Minimum Qualifications. - Qualifications: maybe Preferred Qualifications. - Skills: maybe not explicit; but we could extract skills from responsibilities (electrical/mechanical ability, trade skills, etc.) but we might not need a Skills section if not explicit. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But we have separate headings allowed. We need to include a section only when posting has real specific content for it. We have content for Minimum Qualifications and Preferred Qualifications. Could treat them as Requirements and Qualifications respectively. - Benefits: we have content. - Schedule: we have Schedule Requirements. - Pay: posting mentions "Starting rate of pay may vary based on factors..." but no specific pay amount. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have only a vague statement that starting rate may vary; that's not specific pay info. Should we include Pay? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state schedule requirements (specific). It does state benefits (specific). For Pay, it only says starting rate may vary based on factors... that's not a specific pay figure or range. Likely we should NOT include Pay section because it's not specific pay info. So omit Pay. - Skills: we could extract from responsibilities but not explicit heading; maybe we can omit Skills section. Thus sections: About the role, Responsibilities, Requirements (Minimum Qualifications), Qualifications (Preferred Qualifications), Benefits, Schedule. We need to use

  for each heading. Use

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

    for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove duplicated "About Lowe's" repeated twice; we need to keep only one? The posting includes two "About Lowe's" paragraphs with slightly different content (one says FORTUNE® 50, another says FORTUNE® 100 and includes more details). Both are about the company; we need to preserve ALL substantive information, but we should remove duplicated lines? The duplicated lines are the repeated "About Lowe's" heading and similar content but not exactly same; they are two separate paragraphs with some overlapping but also some differences (e.g., first says FORTUNE® 50, second says FORTUNE® 100, includes branches and distribution centers). We should keep both? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines: if identical lines appear twice, remove duplicates. Here they are not identical but similar; they are both substantive info about the company. Should we keep both? Probably we should keep the combined info, but not duplicate identical sentences. Since they are not identical, we could keep both but maybe combine to avoid redundancy. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot omit any substantive info. If we combine, we might lose some nuance (like FORTUNE® 50 vs 100). Both are different; we need to keep both. So we need to include both paragraphs under About the role? Actually "About Lowe's" is company overview, not necessarily role. Could be part of About the role or maybe a separate section like "About the company". But allowed headings list does not include "About the company". We could put it under About the role as prose. That would preserve all info. Thus About the role section will contain: - Impact paragraph: "Your Impact at Lowe's As a maintenance Mechanic I, you play an important role..." etc. - How We Support You paragraph (benefits) but we moved that to Benefits section. Actually we should not duplicate. So About the role will contain the impact paragraph only? The "How We Support You" is benefits; we will put that in Benefits section. - Then the two "About Lowe's" paragraphs. We need to ensure we don't include boilerplate like "Lowe’s is an equal opportunity employer..." that's EEO boilerplate; remove. Also remove "For information about our benefit programs and eligibility, please visit https://talent.lowes.com/us/en/benefits." That's a link; but it's part of benefits description? It's a reference; we could keep as part of benefits? It's not boilerplate? It's a link for more info; maybe we keep it as part of benefits. However it's a repeated line later also appears. We'll keep one instance. Also remove "Starting rate of pay may vary based on factors including, but not limited to, position offered, location, education, training, and/or experience." That's pay info but vague; we decided not to include Pay section; but we could still include that sentence somewhere? If we don't have Pay section, where to put? Could be omitted as it's not specific pay; but it's substantive? It's about pay but vague. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that starting rate may vary; that's a statement about pay. But we are not making a Pay section; we could include that sentence in Benefits? Probably not appropriate. Safer to omit it entirely as it's not specific pay and we are not making Pay section. The instruction: "Prefer a few substantive sections over many thin ones." Omitting that vague pay statement may be okay; but we risk losing substantive info. However it's not specific pay; it's a disclaimer. Might be considered boilerplate? Not exactly. But we can keep it in Benefits? Not really. Perhaps we can include a short

    under Benefits about pay variability? But the instruction says never create Pay section unless posting actually states them. It does state something about pay, but it's not a specific pay rate or range. The rule may intend to avoid empty Pay sections like "Pay: not specified". Since they gave a statement about variability, we could include a Pay section with that statement. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state something about pay (starting rate may vary). So we could include a Pay section with that statement. But we need to avoid filler like "commensurate with experience". This statement is not filler; it's actual info about pay variability. So we could include Pay section. Similarly, Schedule we have specific schedule requirements; we will include Schedule section. Benefits we have specifics. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We need to avoid duplication. Let's extract content. **About the role** (impact paragraph): "Your Impact at Lowe's As a maintenance Mechanic I, you play an important role in keeping our distribution center running smoothly. By quickly and independently fixing equipment issues in different areas, you'll help maintain a seamless flow of goods and keep our supply chain running. Your adaptable skills, combined with the ability to guide others, directly contribute to the overall efficiency of our distribution center teams. Your impact is not just about repairs – it's about creating a safe and productive environment for your fellow team members." We could also include the first sentence of "How We Support You"? No, that's benefits. **Benefits** (from How We Support You): - Safety: Our commitment to safety is a key factor that attracts skilled mechanics to our team. We encourage our mechanics to take their time with their work, prioritize their physical health and safety, and take pride in keeping our facilities clean, well-maintained, and adhering to safety regulations. - Culture of Belonging: Our teams enjoy a positive work environment where leaders support and respect you, and associates genuinely appreciate each other. - Financial Future: We invest in you – own part of the company with our optional Employee Stock Purchase Plan, or participate in our matching 401k plan. - Bonus Potential: When we win, you win. We award front line workers discretionary and profit-sharing bonuses when we succeed. - Health and Wellbeing: We offer paid time off for vacations, holidays and sick time, as well as access to top-tier medical, dental and vision insurance. For information about our benefit programs and eligibility, please visit https://talent.lowes.com/us/en/benefits. We should keep the link. **Responsibilities**: From "Your Day at Lowe's" paragraph: "As a maintenance Mechanic I, you'll use your specialized expertise in conveyors, rolling stock, or building components to handle complex repairs in your area of focus. Armed with sufficient electrical and mechanical knowledge, you will independently diagnose, prioritize, plan, and execute repairs. You will also be expected to collaborate with colleagues in management or leadership when needed." Plus the Key Responsibilities list: - Work in a distribution/warehouse environment, handling physical and environmental aspects typical to such settings. - Utilize tools for maintenance tasks requiring fine motor skills and hand-eye coordination. - Perform specialized repairs in conveyors, rolling stock, or building components within the Regional Distribution Center (RDC). - Demonstrate electrical and mechanical ability for safe, independent equipment repairs in the Regional Distribution Center (RDC). - Use trade skills, classroom knowledge, and systems experience to diagnose equipment issues and make necessary repairs. - Obtain or order the proper parts necessary for equipment repairs - Maintain accurate and detailed records of repairs, replacements, and maintenance activities. - Adhere to safety protocols and ensure a safe working environment for oneself and others. - Stay updated on new technologies, equipment, and maintenance procedures through ongoing training and education. We need to preserve all; combine into a

    • list. Also include the prose paragraph before list as

      . **Requirements** (Minimum Qualifications): List: - Possess a valid state driver's license - 2 years of experience in your specialty area - Combination of experience and/or technical training in electrical/electronic theory ranging up to 600 volts systems (or willingness to obtain proper training within 1 year of employment) - Minimally must be able to lift 25 pounds; up to 70 pounds. - Must be able to work safely with corrosive materials and at heights of 20+ feet. - If required by local regulations, certified to perform work at the Maintenance Mechanic level (such as electrical work in