Software Engineer III

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must not create sections with placeholder text like "commensurate with experience", "not specified", etc. So we need to parse the job posting. Let's extract content: Job Details Description: - MELE Associates, Inc. is seeking to add an experienced Software Engineer to support the Office of Personnel and Facility Clearances and Classification (OPFCC), NA-74. - The OPFCC is responsible for implementing all Department of Energy (DOE) personnel security and facility clearance requirements for all National Nuclear Security Administration (NNSA) field sites. - This full-time position is contingent upon contract award. Essential Functions (these are responsibilities): - Interpret requirements and create technical solutions with programming code, databases and user interfaces - Abide by NA-IM security and process requirements - Ensure requirements and acceptance criteria are well known to the team - Preparation of business requirement documents as directed Minimum Qualifications: - Bachelor's degree in computer science - Three (3) years of experience in a software engineering role. Experience may be substituted for education on a year for year basis. - Experience working in the Agile methodology - Knowledge of Capability Maturity Model Integration (CMMI) processes and best practices - Superior communication, organizational, interpersonal, and writing skills. - Strong aptitude for critical thinking - Current and active DOE Q Clearance/Top Secret Clearance with ability to acquire an SCI. Preferred Qualifications: - Master’s degree in computer science or CSM certification - Experience with DOE/NNSA Location: This is a full-time position in Albuquerque, NM 87123 USA #OPT Salary: Salaries are determined based on several factors including external market data, internal equity, and the candidate’s related knowledge, skills, and abilities for the position. Benefits: - MELE Offers Employer-paid employee Medical, Dental and Vision Care. - Low-Cost Family Health Care offered. - Federal Holidays and three (3) weeks’ vacation - 401(k) with Employer Match - Cross-training opportunities About MELE Associates, Inc. (company description) - could be "About the role"? Actually "About MELE Associates, Inc." is company overview. Could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About the role: maybe the description of the role (first paragraph about supporting OPFCC, responsibilities? Actually "About the role" could be a brief summary of the position. We have description: "MELE Associates, Inc. is seeking to add an experienced Software Engineer to support the Office of Personnel and Facility Clearances and Classification (OPFCC), NA-74. The OPFCC is responsible for implementing all Department of Energy (DOE) personnel security and facility clearance requirements for all National Nuclear Security Administration (NNSA) field sites. This full-time position is contingent upon contract award." That's about the role. - Responsibilities: Essential Functions list. - Requirements: Minimum Qualifications? Or Requirements could be same as Minimum Qualifications. We'll treat Minimum Qualifications as Requirements. - Qualifications: Preferred Qualifications. - Skills: maybe we can extract skills from Minimum Qualifications: communication, organizational, interpersonal, writing, critical thinking, Agile, CMMI, etc. But we already have them in Requirements. Could combine? The instruction: prefer a few substantive sections over many thin ones. So we could combine Skills into Requirements or Qualifications. But we need to follow headings only if we have real specific content. We have content for About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred), Benefits, Pay (salary info). Schedule? Not mentioned besides full-time. Could we infer schedule? It says full-time position. That's schedule info: full-time. But is that specific enough? It says "This full-time position is contingent upon contract award." So we could include Schedule: Full-time. However, the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state full-time, so we can include Schedule with "Full-time". But we need to check if that's considered substantive. It's a statement. Probably okay. Pay: The posting says "Salaries are determined based on several factors including external market data, internal equity, and the candidate’s related knowledge, skills, and abilities for the position." That's not a specific number or range. It's vague. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is similar to "Salaries are determined based on several factors..." which is vague but not exactly placeholder like "commensurate with experience". It's still not a specific number. Might be considered filler. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about salary determination, but not a specific figure. Is that considered stating them? It states that salaries are determined based on factors. That's still some info. However, the instruction about filler text includes "commensurate with experience", "not specified", etc. This is not exactly those but still vague. I'd lean to include Pay section with that sentence, as it's the only salary info. But we need to see if it's considered filler. The instruction says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The given sentence is not exactly those, but it's still vague. However, it's not a placeholder like "TBD". It's a statement of how salary is determined. I'd include it. Benefits: we have specific benefits. Schedule: we have full-time. Now we need to output HTML fragment with

headings and appropriate content:

for prose,

• for lists. We must not include boilerplate like EEO, E-Verify, etc. Also remove duplicated lines. Also remove "About MELE Associates, Inc."? That's company description; maybe we can include under "About the role"? Actually "About the role" is about the role, not company. The company description could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep company description somewhere. Where could it fit? Possibly under "About the role"? But that's about the role, not company. Could we create a section "About the company"? Not in allowed headings list. The allowed headings are only those listed. So we must fit company description into one of those headings. Perhaps "About the role" can include both role and company? But that seems off. However, we could treat "About the role" as a summary of the position and include company description as part of that? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It implies we should use those headings when appropriate. It doesn't say we cannot add other headings, but we should follow the examples. Safer to stick to those headings. Where to put company description? Maybe under "About the role" we can include a brief description of the role and the company? Might be acceptable. Alternatively, we could treat company description as part of "About the role" because it's about the role at MELE. I'll include a paragraph describing MELE under About the role. Now we need to remove duplicated lines: The phrase "This full-time position is contingent upon contract award." appears twice (once in job details, once later). We'll include only once. Also "Preferred Qualifications" includes Master’s degree in computer science or CSM certification, Experience with DOE/NNSA. Now we need to decide which content goes where. Let's outline:

  About the role

  MELE Associates, Inc. is seeking to add an experienced Software Engineer to support the Office of Personnel and Facility Clearances and Classification (OPFCC), NA-74. The OPFCC is responsible for implementing all Department of Energy (DOE) personnel security and facility clearance requirements for all National Nuclear Security Administration (NNSA) field sites. This full-time position is contingent upon contract award. MELE Associates, Inc. is a veteran and minority-owned government contractor with over 300 employees and offices in Rockville, MD, Washington, DC, and Albuquerque, NM, providing technical, engineering, and programmatic support expertise to U.S. federal and international agencies.

  But we need to ensure we don't invent details. The company description includes over 300 employees, offices, veteran/minority-owned, etc. That's from the "About MELE Associates, Inc." paragraph. We can include that. Now Responsibilities:

  Responsibilities

  • Interpret requirements and create technical solutions with programming code, databases and user interfaces
  • Abide by NA-IM security and process requirements
  • Ensure requirements and acceptance criteria are well known to the team
  • Preparation of business requirement documents as directed
  Requirements (Minimum Qualifications):

  Requirements

  • Bachelor's degree in computer science
  • Three (3) years of experience in a software engineering role (experience may be substituted for education on a year-for-year basis)
  • Experience working in the Agile methodology
  • Knowledge of Capability Maturity Model Integration (CMMI) processes and best practices
  • Superior communication, organizational, interpersonal, and writing skills
  • Strong aptitude for critical thinking
  • Current and active DOE Q Clearance/Top Secret Clearance with ability to acquire an SCI
  Qualifications (Preferred):

  Qualifications

  • Master’s degree in computer science or CSM certification
  • Experience with DOE/NNSA
  Skills: We could combine some skills but we already have communication etc in Requirements. Could we create a Skills section for things like Agile, CMMI, etc? But that would be thin. Better to omit Skills section if we don't have distinct skills not already covered. However, we have "Superior communication, organizational, interpersonal, and writing skills." and "Strong aptitude for critical thinking". Those are skills. Could we put them under Skills? But then Requirements would be just education/experience/clearance. Might be better to split: Requirements = education/experience/clearance; Skills = communication, critical thinking, Agile, CMMI. But the instruction says prefer a few substantive sections over many thin ones. So maybe we keep them together under Requirements. We'll not create a separate Skills section. Benefits:

  Benefits

  • Employer-paid employee Medical, Dental and Vision Care
  • Low-Cost Family Health Care offered
  • Federal Holidays and three (3) weeks’ vacation
  • 401(k) with Employer Match
  • Cross-training opportunities
  Pay:

  Pay

  Salaries are determined based on several factors including external market data, internal equity, and the candidate’s related knowledge, skills, and abilities for the position.