Jobs · Management · Alabama

Electro-Mechanical Assembly Team Leader

Leidos · Huntsville, AL · 1 mo ago
On-siteManagement$51k–$92k/yrFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content. Let's parse the description. First part: "Description Looking for an opportunity to make an impact? At Leidos, we deliver innovative solutions..." This is generic fluff; might be considered boilerplate? It's about company mission. Might be considered "About the role"? Not exactly. The posting includes "Primary Responsibilities" section with bullet-like sentences. Also "Basic Qualifications" and "Preferred Qualifications". Also "Pay Range" given. Also "Pay And Benefits" section with description. Also "About Leidos" section. We need to decide sections. We have: - About the role: maybe the initial paragraph describing the role? The description includes "Leidos’ Defense Systems Electronic Manufacturing Facility is seeking a Electro-Mechanical Assembly Lab Team Leader to join our team that does assembly and test of medium to high complexity products for various customers." Also some mission statements. Could be considered About the role. - Responsibilities: The "Primary Responsibilities" block lists many duties. - Requirements: Could be Basic Qualifications? Or "Basic Qualifications" and "Preferred Qualifications". The instruction says use headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map. We have Basic Qualifications (HS Diploma/GED with at least 3-5 years electro-mechanical assembly experience, etc.) and Preferred Qualifications (Experience leading a team, MES experience). Also there are skills like ability to multi-task, read drawings, lift, stand, US Citizen, Secret clearance. We could put Requirements as Basic Qualifications, Qualifications as Preferred Qualifications? Or combine? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include those that have content. We need to avoid filler like "commensurate with experience". Not present. We need to include Pay section because posting states Pay Range $50,700.00 - $91,650.00. Also there is a Pay And Benefits section describing benefits. So we can have Pay and Benefits separate? The instruction says we can have Benefits and Pay sections. We could combine? Better to have Pay section with the range, and Benefits section with the benefits description. Schedule: Not mentioned explicitly; no schedule info. So we should not include Schedule. Skills: Could extract from responsibilities/qualifications like ability to multi-task, read drawings, lift, stand, communication, etc. But we might not need a separate Skills section if we already have Requirements and Qualifications. However instruction says prefer a few substantive sections over many thin ones. We could omit Skills if content overlaps. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can structure them under headings. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to remove the "Securing Your Data", "Commitment to Non-Discrimination", "About Leidos" maybe? Actually "About Leidos" is company overview; might be considered boilerplate? It's not about the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "About Leidos" is not exactly that but could be considered generic company description; but it's substantive? It's about Leidos, not the role. Might be considered boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't explicitly say to remove company overview. However earlier they said "Prefer a few substantive sections over many thin ones." The "About Leidos" may be considered not directly about the role; but it's still substantive info about the employer. Might be okay to keep under "About the role"? But the heading "About the role" is for role description, not company. Could we put company overview under "About the role"? Might be stretching. Better to include a section "About Leidos" only if we have heading for it, but not in the list. The allowed headings are those listed; we shouldn't add others. So we should not include a heading for About Leidos. So we need to decide where to put that info. Perhaps we can incorporate it into "About the role" as a brief description of the company context. That seems acceptable. Thus we will have sections: - About the role: includes the introductory paragraph about Leidos, mission, the role description. - Responsibilities: list from Primary Responsibilities. - Requirements: Basic Qualifications. - Qualifications: Preferred Qualifications. - Benefits: from Pay And Benefits section (competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement). Also maybe mention "Pay and benefits are fundamental..." but we can keep the list. - Pay: Pay Range $50,700.00 - $91,650.00. We must not include Schedule. We need to use
  • for any list of duties/requirements/benefits. For prose, use

    . We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each bullet point exactly as in the posting, but we can format as list items. Let's extract details. From the posting: **Primary Responsibilities** (the block after "Primary Responsibilities"): - Responsible for overall function in Electro-Mechanical Assembly lab when lab Manager is not available. This includes normal workday hours and overtime hours to include occasional weekends. - Communication of announcements to lab team members. - Communicate with project teams and production control to provide updates on schedules. - Support solutions to technical problems including working directly with Manufacturing Engineers. - Attend meetings with management to establish new procedures and support opportunities for improvement. - Corroborate with Engineering and Management on Continuous Improvement. - Engaging with peers to share best practices. - Maintaining 5S best practices in lab. Note: Some sentences have minor grammar issues; we keep as is. **Basic Qualifications**: - HS Diploma/GED with at least 3-5 years electro-mechanical assembly experience - Applicants must have strong experience working with teams. - Ability to multi-task and handle high pressure situations - Knowledge of electro-mechanical assembly and test processes - Ability to read drawings and follow work instructions and effectively convey this information to less experienced technicians - Ability to frequently lift up to 35 pounds - Ability to stand for 4 or more hours per day - Must be a US Citizen and possess or meet the eligibility to obtain (and be able to maintain) a Secret Clearance **Preferred Qualifications**: - Experience leading a team - MES (Solumina or Aegis) Build Tracking experience **Pay Range**: - Pay Range $50,700.00 - $91,650.00 - The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered in extending an offer include (but are not limited to) responsibilities of the job, education, experience, knowledge, skills, and abilities, as well as internal equity, alignment with market data, applicable bargaining agreement (if any), or other law. **Pay And Benefits** section: - Pay and benefits are fundamental to any career decision. That's why we craft compensation packages that reflect the importance of the work we do for our customers. - Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. - More details are available at www.leidos.com/careers/pay-benefits. We need to keep the substantive info: the list of benefits: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. We also have the introductory fluff about mission etc. Let's capture that for About the role. **Description** (first paragraph): "Looking for an opportunity to make an impact? At Leidos, we deliver innovative solutions through the efforts of our diverse and talented people who are dedicated to our customers’ success. We empower our teams, contribute to our communities, and operate sustainable. Everything we do is built on a commitment to do the right thing for our customers, our people, and our community. Our Mission, Vision, and Values guide the way we do business. Your greatest work is ahead! Leidos’ Defense Systems Electronic Manufacturing Facility is seeking a Electro-Mechanical Assembly Lab Team Leader to join our team that does assembly and test of medium to high complexity products for various customers. If this sounds like the kind of environment where you can thrive, keep reading! Leidos Defense Systems Sector / Manufacturing provides a diverse portfolio of systems, solutions, and services covering land, sea, air, space, and cyberspace for customers worldwide. Solutions for Defense include enterprise and mission IT, large-scale intelligence systems, command and control, geospatial and data analytics, cybersecurity, logistics, training, and intelligence analysis and operations support. Our team is solving the world’s toughest security challenges for customers with “can’t fail” missions. To explore and learn more, click here! Are you ready to make an impact? Apply and share your resume with us today!" We need to remove application instructions like "Apply and share your resume with us today!" and "To explore and learn more, click here!" Also "Are you ready to make an impact?" maybe considered call to action. The instruction: remove application instructions. So we should remove sentences that are calls to apply. Also remove duplicated lines. Thus we keep the descriptive content about Leidos and the role, but remove the explicit apply prompts. Let's extract the substantive description: - Looking for an opportunity to make an impact? At Leidos, we deliver innovative solutions through the efforts of our diverse and talented people who are dedicated to our customers’ success. - We empower our teams, contribute to our communities, and operate sustainable. - Everything we do is built on a commitment to do the right thing for our customers, our people, and our community. - Our Mission, Vision, and Values guide the way we do business. - Your greatest work is ahead! - Leidos’ Defense Systems Electronic Manufacturing Facility is seeking a Electro-Mechanical Assembly Lab Team Leader to join our team that does assembly and test of medium to high complexity products for various customers. - If this sounds like the kind of environment where you can thrive, keep reading! (maybe remove as it's prompting to keep reading) - Leidos Defense Systems Sector / Manufacturing provides a diverse portfolio of systems, solutions, and services covering land, sea, air, space, and cyberspace for customers worldwide. - Solutions for Defense include enterprise and mission IT, large-scale intelligence systems, command and control, geospatial and data analytics, cybersecurity, logistics, training, and intelligence analysis and operations support. - Our team is solving the world’s toughest security challenges for customers with “can’t fail” missions. - To explore and learn more, click here! (remove) - Are you ready to make an impact? Apply and share your resume with us today! (remove) We can keep "If this sounds like the kind of environment where you can thrive, keep reading!" as it's still encouraging to read; but it's basically an instruction to continue reading. Might be considered application instruction? It's not exactly applying but encouraging to keep reading. Safer to remove it as it's not substantive about the role. Thus About the role paragraph will be a combination of the remaining sentences. Now we need to output HTML fragment. Structure:

    About the role

    ... (combined sentences)

    Responsibilities

    • ...
    • ...

    Requirements

    • ...
    • ...

    Qualifications

    • ...
    • ...

    Benefits

    Similar jobs