Jobs · Engineering · Texas

Senior Manager, Systems Engineering

L3Harris Technologies · Greenville, TX · 3 wk ago
On-siteEngineeringFull-time
We need to output only HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. Must not repeat job title as heading. Must not include Job ID/requisition numbers as headings; can fold minor metadata into short

or drop it. Must preserve all substantive info. Remove boilerplate (EEO, legal, etc). Also remove duplicated lines, application instructions. We need to parse the posting. Key content: - Intro paragraph about L3Harris mission etc. Could be "About the role" or maybe "About the company"? The instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have: Job Title: Senior Manager, System Architects (but we should not repeat as heading). Job Code: 44939 (metadata). Job Location: Greenville, TX (metadata). Job Schedule: 9/80 - Employees work 9 out of every 14 days – totaling 80 hours worked – and have every other Friday off (this is schedule info, so we can put under Schedule heading). Job Description: We are seeking an experienced Senior Manager to lead and manage a select group of Systems Architects that serve as the senior technical authority responsible for establishing technical solutions, providing strategic design leadership, and technical governance across all platforms and systems. System Architects ensure system-of-systems coherence, interoperability, scalability, and mission alignment through disciplined architecture, integration planning, and lifecycle oversight. As their leader, you will build and mentor the team and establish relationships with senior program and functional leaders to ensure technical solutions and programs are set up for successful execution. Essential Functions: list bullet points (starting with Ability to obtain a US TS/SCI security clearance. Lead technical development of new ISR weapon systems products (aircraft, mission systems and sensors, ground support systems) that have measurable impact on business or functional results. Communicate within and outside of the organization to explain and influence changes to products and product development approaches, particularly chief engineers, project engineers, and program managers to improve mission capability and the organization’s ability to support multiple product lines. Collaborate in a multi-disciplinary, diverse, and dynamic team environment. Establish and maintain technical direction, engineering standards, and design principles. Lead technical planning, design reviews, integration, and technical decision-making, engaging in day-to-day program execution as warranted. Leadership and Communications skills. Forecast Systems Engineering Manpower needs based on Program and Potential demand forecast; responsible for creating workforce and staffing plans. Establish training requirements for continued professional development of the team to meet business goals.) Qualifications: Bachelor’s degree with twelve (12) years of leading projects and/or task teams in the integration of aerospace and defense systems and/or subsystems in airborne and/or Lab environments experience. Graduate degree with ten (10) years of leading projects and/or task teams in the integration of aerospace and defense systems and/or subsystems in airborne and/or Lab environments experience. In Lieu of a degree, a minimum of sixteen (16) years of leading projects and/or task teams in the integration of aerospace and defense systems and/or subsystems in airborne and/or Lab environments experience. Preferred Additional Skills: Coursework and/or experience in systems engineering, systems architecture, systems analysis and design, system performance modeling, integration and/or project management, and/or model-based systems engineering. Benefits: Not explicitly mentioned. There's no benefits info. So we should not create Benefits section unless posting actually states them. So we skip Benefits. Pay: Not mentioned. So skip Pay. Schedule: we have schedule info: 9/80 - Employees work 9 out of every 14 days – totaling 80 hours worked – and have every other Friday off. So we can create Schedule heading with that content. About the role: Could be the introductory paragraph about L3Harris and the job description summary. We can combine the initial paragraph about L3Harris dedication etc and the Job Description paragraph into About the role. Or we could treat the Job Description as Responsibilities. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping: - About the role: maybe a brief overview of the role (the Job Description paragraph). Could also include the company mission paragraph? The instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use About the role for a general description of the role. Responsibilities for duties. Requirements maybe for qualifications? But we have Qualifications separate. Requirements could be things like security clearance, ability to obtain TS/SCI, etc. However the posting includes "Essential Functions" which are duties/responsibilities. Also includes "Ability to obtain a US TS/SCI security clearance." That could be a requirement. We have Qualifications (education/experience). Preferred Additional Skills (skills). So we can map: - About the role: Intro paragraph about L3Harris and the role purpose (maybe first paragraph after job title). Could be: "L3Harris is dedicated to recruiting and developing high-performing talent ... L3Harris provides an inclusive, engaging environment ... L3Harris is the Trusted Disruptor in defense tech...." That's more about company. But we could still put that under About the role as context. - Responsibilities: The Essential Functions list (the bullet points). Also maybe the Job Description paragraph about leading and managing team, building relationships, etc. Could be part of responsibilities. - Requirements: Could include Ability to obtain US TS/SCI security clearance (maybe also citizenship requirement). Also maybe the job location? But location is metadata; we could fold into a short p. - Qualifications: Education/experience requirements (Bachelor's 12 years, Graduate 10 years, or 16 years in lieu). - Skills: Preferred Additional Skills (coursework/experience in systems engineering, etc.) - Schedule: the 9/80 schedule. - Benefits: none -> omit. - Pay: none -> omit. We must not create sections with filler text. So only include sections where we have real content. Thus we will output:

About the role

... (company mission + role purpose)

Responsibilities

  • ... each essential function as li

Requirements

Ability to obtain a US TS/SCI security clearance. (U.S. citizenship required for clearance.)

Qualifications

  • Bachelor’s degree with twelve (12) years of leading projects and/or task teams in the integration of aerospace and defense systems and/or subsystems in airborne and/or Lab environments.
  • Graduate degree with ten (10) years of leading projects and/or task teams in the integration of aerospace and defense systems and/or subsystems in airborne and/or Lab environments.
  • In lieu of a degree, a minimum of sixteen (16) years of leading projects and/or task teams in the integration of aerospace and defense systems and/or subsystems in airborne and/or Lab environments.

Skills

  • Coursework and/or experience in systems engineering, systems architecture, systems analysis and design, system performance modeling, integration and/or project management, and/or model-based systems engineering.

Schedule

9/80 schedule: Employees work 9 out of every 14 days, totaling 80 hours worked, and have every other Friday off.

We need to ensure we preserve all substantive info. Let's extract the exact text. From posting: Intro: "L3Harris is dedicated to recruiting and developing high-performing talent who are passionate about what they do. Our employees are unified in a shared dedication to our customers’ mission and quest for professional growth. L3Harris provides an inclusive, engaging environment designed to empower employees and promote work-life success. Fundamental to our culture is an unwavering focus on values, dedication to our communities, and commitment to excellence in everything we do. L3Harris is the Trusted Disruptor in defense tech. With customers’ mission-critical needs always in mind, our employees deliver end-to-end technology solutions connecting the space, air, land, sea and cyber domains in the interest of national security." That's the company overview. Job Description paragraph: "We are seeking an experienced Senior Manager to lead and manage a select group of Systems Architects that serve as the senior technical authority responsible for establishing technical solutions, providing strategic design leadership, and technical governance across all platforms and systems. System Architects ensure system-of-systems coherence, interoperability, scalability, and mission alignment through disciplined architecture, integration planning, and lifecycle oversight. As their leader, you will build and mentor the team and establish relationships with senior program and functional leaders to ensure technical solutions and programs are set up for successful execution." Essential Functions list: each sentence separated by periods? Let's list them: - Ability to obtain a US TS/SCI security clearance. - Lead technical development of new ISR weapon systems products (aircraft, mission systems and sensors, ground support systems) that have measurable impact on business or functional results. - Communicate within and outside of the organization to explain and influence changes to products and product development approaches, particularly chief engineers, project engineers, and program managers to improve mission capability and the organization’s ability to support multiple product lines. - Collaborate in a multi-disciplinary, diverse, and dynamic team environment. - Establish and maintain technical direction, engineering standards, and design principles. - Lead technical planning, design reviews, integration, and technical decision-making, engaging in day-to-day program execution as warranted. - Leadership and Communications skills. - Forecast Systems Engineering Manpower needs based on Program and Potential demand forecast; responsible for creating workforce and staffing plans. - Establish training requirements for continued professional development of the team to meet business goals. Note: "Leadership and Communications skills." is a bit vague but it's part of essential functions. We'll keep each as
  • . Qualifications: exactly: "Bachelor’s degree with twelve (12) years of leading projects and/or task teams in the integration of aerospace and defense systems and/or subsystems in airborne and/or Lab environments experience." "Graduate degree with ten (10) years of leading projects and/or task teams in the integration of aerospace and defense systems and/or subsystems in airborne and/or Lab environments experience." "In Lieu of a degree, a minimum of sixteen (16) years of leading projects and/or task teams in the integration of aerospace and defense systems and/or subsystems in airborne and/or Lab environments experience." We might want to trim trailing "experience" duplication but keep as is. Preferred Additional Skills: "Coursework and/or experience in systems engineering, systems architecture, systems analysis and design, system performance modeling, integration and/or project management, and/or model-based systems engineering." Schedule: "Job Schedule: 9/80 - Employees work 9 out of every 14 days – totaling 80 hours worked – and have every other Friday off" We need to preserve the dash characters? Use normal hyphen. Now, we need to avoid including boilerplate: EEO, legal, E-Verify, etc. Remove those paragraphs. Also remove duplicated lines: none. Now, ensure we don't include job title as heading. We didn't. We also need to not put Job ID/requisition numbers as headings; we can fold minor metadata into a short

    or drop it. We have Job Code and Job Location. We could include them in a short paragraph under About the role maybe, or we could drop them. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we could include a short

    with location and job code maybe under About the role or separate. But we need to preserve all substantive information.

  • Similar jobs