Digital SMS Solutions Development Manager, Hybrid role, MA/RI/TX/AZ options
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
First, job title: "SMS Solutions Development Manager Manager, Information Workplace Services M4 Raytheon Digital Technology – P&I Systems Design & Integration (SDI) SDI – Systems Management & Security". Not needed as heading.
We need sections:
- About the role: likely the introductory paragraph describing company and role location. The posting includes: "At RTX, the world's largest aerospace and defense company..." plus description of hybrid role location. That's about the role.
- Responsibilities: bullet list of duties under "What You Will Do". That's a list.
- Requirements: includes security clearance, US citizenship, etc. Also maybe "Position Role Type: Hybrid" etc. But we need to include only real content.
- Qualifications: There's "Qualifications You Must Have" and "Qualifications We Prefer". Could combine into Qualifications section (maybe separate Must Have and Preferred). But we need to follow instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we can have Qualifications heading and include both must have and preferred as lists.
- Skills: maybe we can extract skills from qualifications (automation, scripting, etc). But we could also have a Skills section if there is explicit skills list. The posting includes "Experience with automation and scripting technologies (PowerShell, Python, Ansible, Bash) applied to secure architectures." etc. Could be considered skills. However we need to only create Skills section if posting actually states them. It does mention skills/experience. Might be better to put them under Qualifications. But we could also create a Skills section listing technical skills: systems design, IT infrastructures, cyber compliance, automation, secure integration, RMF, NIST 800-53, PowerShell, Python, Ansible, Bash, etc. However we need to avoid inventing. The posting includes those under Qualifications We Prefer. So we could treat them as Skills.
- Benefits: The posting includes "What We Offer" describing values, relocation eligibility, benefits list: medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, holidays. Also incentive compensation. So we can create Benefits section.
- Pay: The posting includes salary range: "The salary range for this role is 107,500 USD - 204,500 USD." So we need Pay section.
- Schedule: The posting includes role type Hybrid, mention of commuting, but no explicit schedule like full-time, part-time. It says "Hybrid: Employees who are working in Hybrid roles will work regularly both onsite and offsite. Ratio of time working onsite will be determined in partnership with your leader." That's schedule info. So we can include Schedule section.
We must not include boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics.
Let's extract content.
First, About the role: The paragraph(s) after location description: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Raytheon brings the strength of more than 100 years of experience and renowned engineering expertise to meet the needs of today’s mission and stay ahead of tomorrow’s threat. We deliver solutions that help our nation and allies defend freedoms and deter aggression, creating a safer, more secure world. Join us and help shape the future of aerospace and defense. This will be a hybrid role at one of our Raytheon locations in MA or RI, North TX, or Tucson, AZ. You must be able to commute to one of the location options on a regular basis to meet with stakeholders and members of this team."
We'll put that in
under About the role. Responsibilities: Under "What You Will Do" there is a paragraph with many sentences, each describing a duty. We need to convert to
- items. Let's split by sentences (or semicolons). The text: "Manage and direct a team of experienced systems developers, setting short‑term objectives (less than one year) and guiding execution approaches for secure, automated, cyber‑compliant systems solutions. Contribute personally to solutions design, requirements analysis, and technical development activities for multiple program environments. Execute operational plans supporting SMS and DT priorities, providing measurable inputs into new processes, standards, and improvements. Oversee solution architectures, technical documentation, system requirements, and workflows that define interactions between people, processes, and technologies. Drive implementation of standardization strategies including automation, configuration management, orchestration, and policy‑driven compliance tooling. Collaborate across DT, GSS Cyber, product teams, and enterprise partners to support compliance decisions, RMF/NIST control implementation, and technical direction. Influence stakeholder understanding of policies, practices, and procedures related to secure system implementation, ensuring alignment across teams. Lead moderate to significant improvements to existing systems, infrastructures, tools, and design processes. Address difficult, multi‑variable problems across a few sites, programs, or geographies using prior experience, structured analysis, and cross‑department coordination. Provide technical consulting within the work area, helping teams understand impacts on adjacent systems and business operations. Manage team staffing, hiring, development, performance reviews, and rewards decisions, ensuring readiness and depth within the group. Mentor key technical contributors and strengthen succession pipelines within the SMS organization. Communicate operational status, progress toward objectives, and risks to leadership while maintaining collaboration across DT and enterprise partners." We'll make each a
- .
Requirements: The posting includes "Position Role Type: Hybrid U.S. Citizen, U.S. Person, or Immigration Status Requirements: Active and transferable U.S. government issued security clearance is required prior to start date. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance Security Clearance Type: Secret - Current Security Clearance Status: Active and existing security clearance required on day 1". Also earlier "Position Role Type: Hybrid". Also "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" maybe a heading. We need to capture requirements: active and transferable US govt security clearance required prior to start date; US citizenship required; security clearance type Secret; current status active and existing required on day 1. Also maybe "Hybrid" is role type but that's more schedule. We'll include requirements as list.
Qualifications: Must Have and Preferred.
Must Have: "Typically requires a University Degree or equivalent experience and minimum 8 years prior relevant experience, or An Advanced Degree in a related field and minimum 5 years' experience. Experience leading intermediate or experienced technical professionals. Experience in one or more of the following: systems design, IT infrastructures, cyber compliance, automation, and/or secure integration. Experience with U.S. Government cybersecurity standards and compliance programs (RMF, NIST 800‑53). Active and transferable U.S. government issued security clearance is required prior to start date. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance."
Preferred: list of items.
We'll combine into Qualifications section with two subheadings? But we only allowed headings from list; we could still include
or
- inside Qualifications. We could separate Must Have and Preferred as separate
- . Pay: Provide salary range. Schedule: Provide hybrid description. Now we need to ensure we don't include boilerplate like "Relocation Eligibility – available for those who meet company policy criteria." That's part of benefits? It's about relocation eligibility; could be considered benefit. We'll include it under Benefits maybe as a bullet. Also "Learn More & Apply Now!" etc is application instruction, remove. Also "Please ensure the role type defined below is appropriate for your needs before applying to this role." remove. Also "This position is classified as: Hybrid: Employees who are working in Hybrid roles will work regularly both onsite and offsite. Ratio of time working onsite will be determined in partnership with your leader. For onsite and hybrid roles, commuting to and from the assigned site is the employee’s personal responsibility." That's schedule info; we can include in Schedule. Also "As part of our commitment to maintaining a secure hiring process, candidates may be asked to attend select steps of the interview process in-person at one of our office locations, regardless of whether the role is designated as on-site, hybrid or remote." That's application instruction/boilerplate; remove. Also "The salary range provided is a good faith estimate representative of all experience levels." That's part of Pay; we can keep. Also "RTX considers several factors when extending an offer, including but not limited to, the role, function and associated responsibilities, a candidate’s work experience, location, education/training, and key skills." That's part of Pay maybe but could be omitted as it's generic. Might be considered boilerplate but it's about pay determination. Might keep? It's somewhat generic but still part of pay description. However instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not exactly those categories; it's about pay determination. Might be okay to keep but could be considered boilerplate. Safer to keep only the concrete salary range. Also "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays." That's benefits. Also "Specific benefits are dependent upon the specific business unit as well as whether or not the position is covered by a collective-bargaining agreement." That's generic; maybe we can keep as part of benefits but it's somewhat boilerplate. Might be okay. Also "Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement. Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company’s performance." That's about incentive compensation; could be part of Benefits or Pay? It's about compensation; maybe we can include under Benefits as "incentive compensation programs". But it's somewhat generic. We'll include a bullet about incentive compensation. Also "This role is a U.S.-based role. If the successful candidate resides in a U.S. territory, the appropriate pay structure and
- with preceding
maybe. But we must not create extra headings not in list. So we can just have Qualifications heading and then include two lists: one for Must Have, one for Preferred, each preceded by a
describing. Skills: Could extract from qualifications: systems design, IT infrastructures, cyber compliance, automation, secure integration, RMF, NIST 800-53, PowerShell, Python, Ansible, Bash, etc. But we already have them in Qualifications. To avoid duplication, maybe we don't create Skills section unless there is explicit skills list separate. The posting does not have a separate "Skills" heading; it's embedded. So we might omit Skills section to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine skills into Qualifications. Benefits: We'll list benefits as