Software Engineer Sr - Clearance Required
Lockheed Martin · Colorado Springs, CO · 4 wk ago
OTHR$98k–$182k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each section heading. Only include sections when posting has real specific content. We need to preserve all substantive info, remove boilerplate.
We need to parse the job description.
Content:
- Who We Are: description of Lockheed Martin values, benefits, etc. Could be "About the role"? Actually "Who We Are" is about company. Could be "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly.
We have:
- "What We’re Doing Our Team, the Command and Control, Battle Management and Communications (C2BMC) Regional team, is constantly engineering, developing and integrating new capabilities for the U.S. Missile Defense System. protecting both the United States and its allies. This large, fast paced team, is composed of many small agile teams working together dynamic environment with a common mission to develop and deploy leading-edge missile defense technologies."
That's about the team/mission. Could be "About the role" or maybe "Responsibilities"? Actually responsibilities are later.
- "The Work The C2BMC-Regional Application Agile Release Train is seeking a Software Engineer that will thrive in a fast paced team environment in the design, development, and testing of the C2BMC applications. Common responsibilities of a software engineer on the RA ART team include: ..."
Then list of responsibilities (bulleted). So we can have a Responsibilities section with
for each section heading. Only include sections when posting has real specific content. We need to preserve all substantive info, remove boilerplate.
We need to parse the job description.
Content:
- Who We Are: description of Lockheed Martin values, benefits, etc. Could be "About the role"? Actually "Who We Are" is about company. Could be "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly.
We have:
- "What We’re Doing Our Team, the Command and Control, Battle Management and Communications (C2BMC) Regional team, is constantly engineering, developing and integrating new capabilities for the U.S. Missile Defense System. protecting both the United States and its allies. This large, fast paced team, is composed of many small agile teams working together dynamic environment with a common mission to develop and deploy leading-edge missile defense technologies."
That's about the team/mission. Could be "About the role" or maybe "Responsibilities"? Actually responsibilities are later.
- "The Work The C2BMC-Regional Application Agile Release Train is seeking a Software Engineer that will thrive in a fast paced team environment in the design, development, and testing of the C2BMC applications. Common responsibilities of a software engineer on the RA ART team include: ..."
Then list of responsibilities (bulleted). So we can have a Responsibilities section with - .
- Then "Why Join Us Excellent benefits and amenities Ongoing career development and support Rewards and recognition for your hard work Medical and dental coverage 401k retirement savings plan Paid time off for work/life balance Mentorship opportunities" This seems like benefits. Also later there is a Benefits offered list.
- Then "Plans, conducts, and coordinates software development activities. Designs, develops, documents, tests, and debugs software that contains logical and mathematical solutions to business/mission problems or questions in computer language for solutions by means of data processing equipment. Applies the appropriate standards, processes, procedures, and tools throughout the development life cycle. Applies knowledge of computer hardware and software, subject matter to be programmed in business/mission applications, information processing techniques used, and information gathered from system users to develop software. Corrects program errors, prepares operating instructions, compiles documentation of program development, and analyzes system capabilities to resolve questions of program intent, output requirements, input data acquisition, programming techniques, and controls. Ensures software standards are met."
That seems like more detailed responsibilities or qualifications? Might be generic description of software engineer role. Could be part of Responsibilities or maybe "Qualifications"? Actually it's more like a generic job description of software engineer duties. Could be considered responsibilities.
- Then "Basic Qualifications Bachelor's degree from an accredited college in software engineering, or related discipline, or equivalent experience/combined education with 3+ years of related experience Experience and knowledge of software practices such as coding standards, automated testing, automated build pipelines and configuration.Understanding of software engineering and software development with Java/J2EE experience or alternate OO development experience (additional experience with C++ also desired).Must have excellent oral and written communication skills and an ability to work effectively in a rapid paced, team environment.Must currently hold an ACTIVE DOD Secret Security Clearance to be considered for this positon."
That's qualifications.
- Then "Desired Skills Experience developing enterprise applications on Linux (Windows experience also desired).Strong problem solving skills, including the ability to review performance and operational issues, identify root cause, recommend, design and implement a solution.Use of common software development and management tools such as maven, git/GitHub, nexus and Eclipse.Experience with agile development methodologies.Understanding of standard system engineering design artifacts such as Use Cases and SysML diagrams.Command and control system application development.Experience with Software Integration and formal testing.Knowledge and experience implementing Cyber Security/RMF requirements.Ability to present advanced concepts to non-software engineers, including senior program and military leaders.Experience with DevSecOps and/or build management.Flexibility and willingness to take on unanticipated tasking.Strong verbal and written communication skills, have the ability to work independently and in a highly dynamic environment."
That's desired skills (Skills section).
- Then "Pay Information Full-Time Salary Range: $98100.00 - $182100.00 At Lockheed Martin, we know mission success starts with taking care of our people. Our Total Rewards program is designed to attract top talent, support your well-being, and help you grow—both professionally and personally. The salary range for this position is as listed on the requisition. Please note that the salary information listed is a general guideline only. Lockheed Martin considers factors such as (but not limited to) scope and responsibilities of the position, candidate's work experience, education/ training, key skills as well as market(work location) and business considerations when extending an offer. Benefits offered: Medical, Dental, Vision, Flexible work arrangements and schedules (e.g., 4x10), 401(k) match, Paid time off, Holidays, Parental Leave, EAP, Flexible Spending Accounts, Education Assistance, Life Insurance, Short-Term Disability, and Long-Term Disability. Annual short-term and/or long-term incentive compensation programs may be offered depending on the position. Payments under these annual programs are not guaranteed and can vary from year to year and are tied to a range of performance metrics.For (Washington state applicants only) Non-represented full-time employees: accrue at least 10 hours per month of Paid Time Off (PTO) to be used for incidental absences and other reasons; receive at least 90 hours for holidays. Represented full time employees accrue 6.67 hours of Vacation per month; accrue up to 52 hours of sick leave annually; receive at least 96 hours for holidays. PTO, Vacation, sick leave, and holiday hours are prorated based on start date during the calendar year."
So we have Pay (salary range) and Benefits (detailed list). Also schedule? Not explicit schedule aside from flexible work arrangements mentioned in benefits. No explicit schedule like shift, etc. So we may not include Schedule section because no specific schedule info.
We need to avoid boilerplate like EEO etc. Already removed.
We need to output only HTML fragment, no markdown fences.
We need to include sections only when there is real specific content. So we can have:
About the Role
maybe containing the "Who We Are" and "What We’re Doing" paragraphs.
But "About the role" maybe should contain description of role and team. Could combine Who We Are and What We’re Doing.
Alternatively we could have separate sections: About the Role (company overview), Responsibilities, Qualifications, Skills, Benefits, Pay.
We must not repeat job title as heading.
We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep the details as given, but we can format into paragraphs and lists.
We need to use for prose,
- for any list of duties/requirements/benefits.
Thus:
- About the Role: combine Who We Are and What We’re Doing into prose paragraphs.
- Responsibilities: list from "Common responsibilities of a software engineer on the RA ART team include:" plus the subsequent bullet-like sentences (they are separated by periods). Also the later paragraph "Plans, conducts, and coordinates software development activities..." could also be responsibilities. We'll include all responsibility-like sentences as list items.
We need to parse the responsibilities list:
After "Common responsibilities of a software engineer on the RA ART team include:" we have:
"Software development in the Java language for one of the Regional Applications teams in Colorado Springs, CO (User Interface, Enterprise Services, Sys Architecture)."
"Under minimal direction, provides specialized expertise within multiple systems, software disciplines, as well as general knowledge of related disciplines, applications implications, and customer areas."
"Perform in-depth analysis and technical support of systems software products, including complex problem resolution, design, development, testing, operational integration, and user support."
"Work from specifications to develop or modify operating systems applications."
"Assists with design, coding, benchmark testing, debugging and documentation of programs."
"Interfaces with other system support groups to resolve problems, setting standards and improving overall efficiency of the operating system."
"Designs, codes, tests and implements tools for operations automation."
"Works on most phases of software systems programming applications, and may require minor instruction and guidance in other phases."
Then later paragraph: "Plans, conducts, and coordinates software development activities. Designs, develops, documents, tests, and debugs software that contains logical and mathematical solutions to business/mission problems or questions in computer language for solutions by means of data processing equipment. Applies the appropriate standards, processes, procedures, and tools throughout the development life cycle. Applies knowledge of computer hardware and software, subject matter to be programmed in business/mission applications, information processing techniques used, and information gathered from system users to develop software. Corrects program errors, prepares operating instructions, compiles documentation of program development, and analyzes system capabilities to resolve questions of program intent, output requirements, input data acquisition, programming techniques, and controls. Ensures software standards are met."
We could split that into separate list items as well, but it's long sentences. Could keep as a paragraph under Responsibilities? The instruction: Use
- for any list of duties/requirements/benefits. So if we have a list, we should use list. The responsibilities are clearly a list. The later paragraph could be considered additional responsibilities but not explicitly a list; we could still make them list items for consistency. However we must not invent detail; we can break sentences into list items as they are separate statements. That seems okay.
Thus Responsibilities
with many - .
- Requirements: maybe we treat Basic Qualifications as Requirements? Actually they have Basic Qualifications and Desired Skills. Could map Basic Qualifications to Requirements section, and Desired Skills to Skills section. Or we could have Requirements (Basic Qualifications) and Skills (Desired Skills). The instruction includes Requirements and Skills as possible headings. So we can do:
Requirements
with Basic Qualifications content (maybe as - for each bullet). The Basic Qualifications text is a run-on sentence; we can split into logical items: Bachelor's degree..., 3+ years experience, experience with software practices..., understanding of software engineering with Java/J2EE..., excellent communication skills, ability to work in rapid paced team, active DOD Secret clearance.
We need to preserve all detail; we can keep as a paragraph but better as list.
- Skills: Desired Skills content as list.
- Benefits: from "Why Join Us" and later Benefits offered list. Combine.
- Pay: salary range and explanation.
We should not include Schedule.
We need to ensure we don't include filler like "commensurate with experience" etc. Not present.
Now produce HTML.
Let's craft.
First, About the Role:
Paragraph 1: Who We Are: "At Lockheed Martin, we believe that by applying the highest standards of business ethics and forward-thinking, everything is within our reach – and yours as a Lockheed Martin employee. We value your unique skills and expertise, and we aim to give back continuously by offering a wide variety of benefits and amenities to help our employees live flexible, balanced, and fulfilling lives at, and outside of, work."
Paragraph 2: What We’re Doing: "Our Team, the Command and Control, Battle Management and Communications (C2BMC) Regional team, is constantly engineering, developing and integrating new capabilities for the U.S. Missile Defense System, protecting both the United States and its allies. This large, fast‑paced team is composed of many small agile teams working together in a dynamic environment with a common mission to develop and deploy leading‑edge missile defense technologies."
We need to preserve punctuation.
Now
About the Role
maybe containing the "Who We Are" and "What We’re Doing" paragraphs. But "About the role" maybe should contain description of role and team. Could combine Who We Are and What We’re Doing. Alternatively we could have separate sections: About the Role (company overview), Responsibilities, Qualifications, Skills, Benefits, Pay. We must not repeat job title as heading. We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep the details as given, but we can format into paragraphs and lists. We need to usefor prose,
- for any list of duties/requirements/benefits.
Thus:
- About the Role: combine Who We Are and What We’re Doing into prose paragraphs.
- Responsibilities: list from "Common responsibilities of a software engineer on the RA ART team include:" plus the subsequent bullet-like sentences (they are separated by periods). Also the later paragraph "Plans, conducts, and coordinates software development activities..." could also be responsibilities. We'll include all responsibility-like sentences as list items.
We need to parse the responsibilities list:
After "Common responsibilities of a software engineer on the RA ART team include:" we have:
"Software development in the Java language for one of the Regional Applications teams in Colorado Springs, CO (User Interface, Enterprise Services, Sys Architecture)."
"Under minimal direction, provides specialized expertise within multiple systems, software disciplines, as well as general knowledge of related disciplines, applications implications, and customer areas."
"Perform in-depth analysis and technical support of systems software products, including complex problem resolution, design, development, testing, operational integration, and user support."
"Work from specifications to develop or modify operating systems applications."
"Assists with design, coding, benchmark testing, debugging and documentation of programs."
"Interfaces with other system support groups to resolve problems, setting standards and improving overall efficiency of the operating system."
"Designs, codes, tests and implements tools for operations automation."
"Works on most phases of software systems programming applications, and may require minor instruction and guidance in other phases."
Then later paragraph: "Plans, conducts, and coordinates software development activities. Designs, develops, documents, tests, and debugs software that contains logical and mathematical solutions to business/mission problems or questions in computer language for solutions by means of data processing equipment. Applies the appropriate standards, processes, procedures, and tools throughout the development life cycle. Applies knowledge of computer hardware and software, subject matter to be programmed in business/mission applications, information processing techniques used, and information gathered from system users to develop software. Corrects program errors, prepares operating instructions, compiles documentation of program development, and analyzes system capabilities to resolve questions of program intent, output requirements, input data acquisition, programming techniques, and controls. Ensures software standards are met."
We could split that into separate list items as well, but it's long sentences. Could keep as a paragraph under Responsibilities? The instruction: Use
- for any list of duties/requirements/benefits. So if we have a list, we should use list. The responsibilities are clearly a list. The later paragraph could be considered additional responsibilities but not explicitly a list; we could still make them list items for consistency. However we must not invent detail; we can break sentences into list items as they are separate statements. That seems okay.
Thus Responsibilities
- with many
- .
- Requirements: maybe we treat Basic Qualifications as Requirements? Actually they have Basic Qualifications and Desired Skills. Could map Basic Qualifications to Requirements section, and Desired Skills to Skills section. Or we could have Requirements (Basic Qualifications) and Skills (Desired Skills). The instruction includes Requirements and Skills as possible headings. So we can do:
Requirements
with Basic Qualifications content (maybe as- for each bullet). The Basic Qualifications text is a run-on sentence; we can split into logical items: Bachelor's degree..., 3+ years experience, experience with software practices..., understanding of software engineering with Java/J2EE..., excellent communication skills, ability to work in rapid paced team, active DOD Secret clearance. We need to preserve all detail; we can keep as a paragraph but better as list. - Skills: Desired Skills content as list. - Benefits: from "Why Join Us" and later Benefits offered list. Combine. - Pay: salary range and explanation. We should not include Schedule. We need to ensure we don't include filler like "commensurate with experience" etc. Not present. Now produce HTML. Let's craft. First, About the Role: Paragraph 1: Who We Are: "At Lockheed Martin, we believe that by applying the highest standards of business ethics and forward-thinking, everything is within our reach – and yours as a Lockheed Martin employee. We value your unique skills and expertise, and we aim to give back continuously by offering a wide variety of benefits and amenities to help our employees live flexible, balanced, and fulfilling lives at, and outside of, work." Paragraph 2: What We’re Doing: "Our Team, the Command and Control, Battle Management and Communications (C2BMC) Regional team, is constantly engineering, developing and integrating new capabilities for the U.S. Missile Defense System, protecting both the United States and its allies. This large, fast‑paced team is composed of many small agile teams working together in a dynamic environment with a common mission to develop and deploy leading‑edge missile defense technologies." We need to preserve punctuation. Now
- .
- Requirements: maybe we treat Basic Qualifications as Requirements? Actually they have Basic Qualifications and Desired Skills. Could map Basic Qualifications to Requirements section, and Desired Skills to Skills section. Or we could have Requirements (Basic Qualifications) and Skills (Desired Skills). The instruction includes Requirements and Skills as possible headings. So we can do:
- for any list of duties/requirements/benefits. So if we have a list, we should use list. The responsibilities are clearly a list. The later paragraph could be considered additional responsibilities but not explicitly a list; we could still make them list items for consistency. However we must not invent detail; we can break sentences into list items as they are separate statements. That seems okay.
Thus Responsibilities