Jobs · Engineering · Tennessee

Lead Tester

Hyve Solutions · Memphis, TN · 2 days ago
EngineeringFull-time
The user wants me to convert this job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - Company Overview (but this is more of an intro/about the company) - Responsibilities - Requirements - Benefits/Perks (there are two lists: "Hyve Perks" and "What's in it for you") Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use
  • for lists - Use

    for prose - Don't repeat job title as heading (not provided anyway) - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, equal opportunity, etc.) - Include section ONLY when real specific content exists - No Pay/Schedule/Benefits unless actually stated - Output ONLY HTML fragment Looking at the content: 1. There's a long company overview paragraph(s) - this could be "About the company" or "About the role" but the rules say "About the role" for section headings. However, the company overview is about the company, not the role. The posting starts with "Hyve Company Overview" then describes the company. Then "Hyve Solutions is looking for a detail-oriented..." which is about the role. I think I should have an "About the role" section with that paragraph, and maybe "About the company" but the rules only list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the company" isn't listed, but "About the role" is. The first paragraph after company overview is about the role: "Hyve Solutions is looking for a detail-oriented, hands-on, results-driven individual..." That's a good "About the role" section. 2. Responsibilities: clearly listed with bullet points (though in text they're separated by periods). I'll make a list. 3. Requirements: listed with bullet points. 4. Benefits: two sections "Hyve Perks" and "What's in it for you" - both are benefits. I'll combine into a Benefits section. 5. EEO statement at the end - remove as boilerplate. No Pay or Schedule mentioned specifically, so no sections for those. Now, I need to parse the responsibilities and requirements into list items. They are written as sentences separated by periods. I'll split them into individual duties. Responsibilities text: "Performs the set-up, calibration, testing and troubleshooting of complex circuits, components, instruments and mechanical assemblies. Tests and troubleshoots assemblies and/or final systems. May perform other tasks including but not limited to unpacking, packaging, placing labels and crating. May complete rework on assemblies and/or systems as a result of testing. Determines and may develop test specifications, methods and procedures from blueprints, drawings and diagrams. Prepare technical reports summarizing findings and recommending solutions to technical problems. Assigns and coordinates daily production requirements in the test area. Prepare daily productivity reports. May assist in the selection and set-up of specialized test equipment. May be required to interface with vendors for technical support." I'll make each sentence a list item. Requirements text: "Advanced understanding and adherence to manufacturing documentation. Advanced computer skills. Works on assignments that are primarily complex in nature. Considerable judgment and initiative are required in resolving problems and making recommendations. Determines methods and procedures on new assignments. Must be able to effectively work within a team environment. May lead/provide guidance to lower-level non-exempt associates. Viewed as an expert in job assignments and related tasks. Typically requires 4-6 years of related experience. High School diploma or GED equivalent. Ability to regularly lift and/or move up to 50 pounds Ability to stand for a prolonged period of time Ability to work on ladders or stools" Note: some lines are not separated by periods but line breaks. I'll treat each as a separate requirement. Benefits: two lists. I'll combine into one list. Now, structure:

    About the role

    Hyve Solutions is looking for a detail-oriented, hands-on, results-driven individual with proven communication skills and a strong work ethic to work in a challenging, fast-paced, energetic environment.

    Responsibilities

    • Performs the set-up, calibration, testing and troubleshooting of complex circuits, components, instruments and mechanical assemblies.
    • Tests and troubleshoots assemblies and/or final systems.
    • May perform other tasks including but not limited to unpacking, packaging, placing labels and crating.
    • May complete rework on assemblies and/or systems as a result of testing.
    • Determines and may develop test specifications, methods and procedures from blueprints, drawings and diagrams.
    • Prepare technical reports summarizing findings and recommending solutions to technical problems.
    • Assigns and coordinates daily production requirements in the test area.
    • Prepare daily productivity reports.
    • May assist in the selection and set-up of specialized test equipment.
    • May be required to interface with vendors for technical support.

    Requirements

    • Advanced understanding and adherence to manufacturing documentation.
    • Advanced computer skills.
    • Works on assignments that are primarily complex in nature.
    • Considerable judgment and initiative are required in resolving problems and making recommendations.
    • Determines methods and procedures on new assignments.
    • Must be able to effectively work within a team environment.
    • May lead/provide guidance to lower-level non-exempt associates.
    • Viewed as an expert in job assignments and related tasks.
    • Typically requires 4-6 years of related experience.
    • High School diploma or GED equivalent.
    • Ability to regularly lift and/or move up to 50 pounds.
    • Ability to stand for a prolonged period of time.
    • Ability to work on ladders or stools.

    Benefits

    • Every Day is Casual Day
    • Company Discounts
    • Community Involvement Opportunities
    • Profit Sharing
    • Medical, Dental & Vision Insurance
    • 401k
    • FSA & HSA
    • Paid Vacation, Holiday & Sick Days
    • Employee Stock Purchase Plan
    • Tuition Reimbursement
    • Live Well Work Well Program
    • Benefit Insurance
    • Flexible Spending Account (FSA)
    • Health Savings Account (HSA)
    • Mental Health Care
    • 401K with match
    • Paid Holidays, Vacation & Sick Days
    • Tuition Reimbursement
    • Perks at Work
    • LEAP Program
    • MyFlexPay
    Note: There are duplicates (FSA, HSA, Tuition Reimbursement, Paid Vacation/Holiday/Sick Days appear twice). I'll keep them as they appear in the source? The rule says preserve ALL substantive information. But duplicates might be considered boilerplate? However, they are listed in two separate sections. I'll include all items as they appear, but maybe deduplicate? The rule says "Remove duplicated lines". So I should remove duplicates. But they are in two different lists. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So duplicated lines should be removed. I'll deduplicate the benefits list. Let me list unique benefits: From Hyve Perks: - Every Day is Casual Day - Company Discounts - Community Involvement Opportunities - Profit Sharing - Medical, Dental & Vision Insurance - 401k - FSA & HSA - Paid Vacation, Holiday & Sick Days - Employee Stock Purchase Plan - Tuition Reimbursement - Live Well Work Well Program - And More (this is vague, maybe omit? "And More" is not substantive. I'll omit.) From What's in it for you: - Benefit Insurance (maybe same as Medical, Dental & Vision? But different phrasing) - Flexible Spending Account (FSA) (duplicate of FSA & HSA) - Health Savings Account (HSA) (duplicate) - Mental Health Care (new) - 401K with match (similar to 401k but with match detail) - Paid Holidays, Vacation & Sick Days (duplicate) - Tuition Reimbursement (duplicate) - Perks at Work (new) - LEAP Program (new) - MyFlexPay (new) I'll combine and deduplicate, but keep distinct items. For example, "401k" and "401K with match" - I'll keep "401K with match" as more specific. "FSA & HSA" vs separate FSA and HSA - I'll keep both? Actually "FSA & HSA" is one line, then separate lines for FSA and HSA. I'll keep the separate ones as they are more detailed. "Paid Vacation, Holiday & Sick Days" vs "Paid Holidays, Vacation & Sick Days" - same. Keep one. "Tuition Reimbursement" appears twice. Keep one. "Medical, Dental & Vision Insurance" vs "Benefit Insurance" - maybe different. I'll keep both. I'll create a combined list with unique items. But the rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should not summarize away detail. However, duplicates are not substantive. I'll include each unique benefit once. Let me craft the final HTML. Also, the company overview at the top is quite long. Should I include it? The rules say "include a section ONLY when the posting has real, specific content for it". The company overview is about the company, not the role. The heading "About the role" is for the role. The company overview could be "About the company" but that's not in the allowed headings. The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So I could put the company overview under "About the role"? But it's about the company. The posting starts with "Hyve Company Overview" then describes the company. Then "Hyve Solutions is looking for a detail-oriented..." That second paragraph is about the role. I think I should include the company overview as a paragraph before sections? But the output should be only the HTML fragment with sections. The rules don't forbid a company overview section, but they say use

    for section headings (e.g. About the role, Responsibilities...). The "e.g." suggests those are examples, but we should only use those? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but "Prefer a few substantive sections over many thin ones." The company overview is substantive. However, the job title is not given, but the page already shows it. The company overview is part of the posting. I think I'll include an "About the company" section? But the allowed list doesn't include it. The user might expect only those headings. I'll include the company overview as a paragraph under "About the role"? That would be weird. Alternatively, I could create an "About the company" heading, but the rule says "use

    for section headings (e.g. About the role, Respons

Similar jobs

Lead Tester

Hyve SolutionsCarson City, NV· 1 mo ago
Engineeringapply on synnex.wd5.myworkdayjobs.com

Lead Tester

Yulista Holding LLCFalls Church, VA· 1 mo ago
Engineeringapply on calistacorp.wd1.myworkdayjobs.com

Lead Tester

Hyve SolutionsOlive Branch, MS· 3 mo ago
Engineeringapply on synnex.wd5.myworkdayjobs.com

Lead Checker

Pyramid FoodsParsons, KS· 18 mo ago
Managementapply on jobboard.timeforge.com

Lead Penetration Tester

GunnisonWashington, DC· 3 days ago
RemoteInformation Technology$160k–$180k/yrapply on recruiting.paylocity.com