Technical SETA SME - Imagery Science
for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content.
From posting:
- "What You Will Do": description of role. That's responsibilities. So we can have Responsibilities
with paragraphs and maybe list.
- "What You Will Need": requirements/qualifications. Could split into Requirements and Qualifications? The posting includes clearance, degree, years experience, specific experiences. Could treat as Requirements. Also "What Would Be Nice To Have": nice-to-have qualifications/skills. Could be Skills or Qualifications. We'll decide.
- Pay: salary range given. So we need Pay section.
- Benefits: list of benefits given. So Benefits section.
- Schedule: mentions "This role requires 5-days a week on client site in Bethesda, MD." That's schedule info (on-site 5 days). So Schedule section.
- About the role? Could be a brief overview; we have "What You Will Do" which is responsibilities. Could also have an "About the role" summarizing. But we can avoid duplication. The instruction: use headings for section headings (e.g. About the role, Responsibilities, etc). We need to include a section only when posting has real specific content. We have content for Responsibilities, Requirements, Qualifications? Might combine Requirements and Qualifications into one? But we have both "What You Will Need" (requirements) and "What Would Be Nice To Have" (preferred qualifications). Could map "What You Will Need" to Requirements, and "What Would Be Nice To Have" to Qualifications or Skills. Also we have Skills maybe from nice-to-have (programming languages, etc). Could put those under Skills.
Thus sections:
- Responsibilities (Responsibilities
) with paragraph(s) describing tasks.
- Requirements (Requirements
) with list of mandatory items: clearance, degree, years experience, specific experiences.
- Qualifications (Qualifications
) maybe for nice-to-have? Or we could put nice-to-have under Skills. But we have both Qualifications and Skills headings allowed. Let's assign:
- Qualifications: nice-to-have education/experience (Master's/PhD, 4+ years experience, etc.)
- Skills: specific technical skills (programming languages, tools, IC experience, supply chain awareness).
- Benefits (Benefits
) with list.
- Pay (Pay
) with paragraph stating salary range.
- Schedule (Schedule
) with paragraph about 5 days onsite.
We should not repeat job title. No metadata like Job Family, Travel Required, Clearance Required as headings; but we need to preserve that info. Those are part of requirements (clearance, travel). So include them in Requirements list.
We must not include boilerplate like EEO, legal, accommodation, etc. Remove those.
We must preserve all substantive information. So include details: Travel Required Up to 10%, Clearance Required Active Top Secret SCI with Polygraph. Also mention "Job Family Communications Engineering (COE)" maybe not needed but it's substantive? It's a job family; could be considered metadata but maybe we should keep? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Job Family is minor metadata; we could include in a short p at top? But they said we can fold minor metadata into a short
or drop it. Since we are not outputting a heading for it, we could include a short paragraph before sections? But they said output ONLY the HTML fragment, no extra markup besides sections. We could include a
at the beginning containing that minor metadata. However they said "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short p for Job Family, Travel Required, Clearance Required. But we also have those details in Requirements; maybe we can drop them as minor metadata. Safer to drop them? But we must preserve ALL substantive information. Travel Required and Clearance Required are substantive. So we need to include them somewhere. We can include them in Requirements list. Thus Requirements list includes: Active Top Secret SCI clearance with polygraph, Travel up to 10%, etc. Now let's extract details. From posting: Job Family Communications Engineering (COE) Travel Required Up to 10% Clearance Required Active Top Secret SCI with Polygraph What You Will Do: - The Technical SETA will provide support in the execution of the lifecycle of a research program from development, source selection, execution, closeout, and transition. - The Technical SETA will be responsible for attending meetings, workshops, conferences, and testing events as the Subject Matter Expert. - In this role, the Technical SETA will serve as the Subject Matter Expert in Image Science, with specialization in EO/IR systems, advanced sensing modalities, and associated image processing, spectral analysis, and evaluation. - This role requires 5-days a week on client site in Bethesda, MD. What You Will Need: - An ACTIVE and MAINTAINED TS/SCI Federal or DoD security clearance with a polygraph - Bachelor’s degree in computer science, applied physics, electrical engineering, systems engineering, or a related technical field. A Master’s degree may be used in lieu of TWO (2) years of relevant work experience. - SIX (6) or more years of working experience. Experiences should include, but not be limited to: * Comprehensive understanding of EO/IR systems standards, procedures, and practices * Expertise with microwave, VHF, UHF, or infrared wavelength systems * Experience developing, implementing, testing, or analyzing signal processing, optimization, or machine learning algorithms * Experience or equivalent education using test and measurement equipment relevant to advanced sensing technologies, such as spectrum analyzers, oscilloscopes, RF test platforms, wireless communications testbeds, biometric sensor test systems, or commercial off‑the‑shelf sensing devices * Experience or equivalent education involving telecommunications systems, radio frequency (RF) sensing, signal processing, biometric sensing modalities, and/or advanced sensor system design and evaluation * Experience managing a multi-disciplinary research and development (R&D) or Test and Evaluation (T&E) team * Experience creating program plans, work breakdown structures, and milestone schedules What Would Be Nice To Have: - Master’s degree or PhD in computer science, applied physics, electrical engineering, systems engineering, or related fields, with FOUR (4) or more years of work experience - FOUR (4) years of experience with programming languages or tools commonly used in sensing, data analysis, or experimental automation, such as LabVIEW, Python, MATLAB, C/C++, or embedded systems software - TWO (2) years of experience in the Intelligence Community (IC), including experience with requirements, CONOPS, and transition - Awareness of supply chain, security, and integration considerations for commercial off‑the‑shelf sensing technologies, telecommunications hardware, and RF component Pay: The annual salary range for this position is $115,200.00-$172,800.00. Compensation decisions depend on a wide range of factors, including but not limited to skill sets, experience and training, security clearances, licensure and certifications, and other business and organizational needs. Benefits: Guidehouse offers a comprehensive, total rewards package that includes competitive compensation and a flexible benefits package that reflects our commitment to creating a diverse and supportive workplace. Benefits Include: - Medical, Rx, Dental & Vision Insurance - Personal and Family Sick Time & Company Paid Holidays - Position may be eligible for a discretionary variable incentive bonus - Parental Leave and Adoption Assistance - 401(k) Retirement Plan - Basic Life & Supplemental Life - Health Savings Account, Dental/Vision & Dependent Care Flexible Spending Accounts - Short-Term & Long-Term Disability - Student Loan PayDown - Tuition Reimbursement, Personal Development & Learning Opportunities - Skills Development & Certifications - Employee Referral Program - Corporate Sponsored Events & Community Outreach - Emergency Back-Up Childcare Program - Mobility Stipend We should not include the EEO etc. Now produce HTML. We'll have:
Responsibilities
The Technical SETA will provide support in the execution of the lifecycle of a research program from development, source selection, execution, closeout, and transition. The Technical SETA will be responsible for attending meetings, workshops, conferences, and testing events as the Subject Matter Expert. In this role, the Technical SETA will serve as the Subject Matter Expert in Image Science, with specialization in EO/IR systems, advanced sensing modalities, and associated image processing, spectral analysis, and evaluation. This role requires 5-days a week on client site in Bethesda, MD.
But schedule is separate; we might move the schedule sentence to Schedule section. However responsibilities currently includes that sentence; we could keep it there but also have Schedule section. To avoid duplication, we could keep responsibilities without schedule line, and put schedule in its own section. Let's split: responsibilities paragraph without the schedule sentence; schedule section with that sentence. Thus responsibilities paragraph: "The Technical SETA will provide support in the execution of the lifecycle of a research program from development, source selection, execution, closeout, and transition. The Technical SETA will be responsible for attending meetings, workshops, conferences, and testing events as the Subject Matter Expert. In this role, the Technical SETA will serve as the Subject Matter Expert in Image Science, with specialization in EO/IR systems, advanced sensing modalities, and associated image processing, spectral analysis, and evaluation." Schedule section:This role requires 5-days a week on client site in Bethesda, MD.
Now Requirements: include clearance, travel, degree, years experience, and the bullet list. We'll make- items. Requirements list: - Active Top Secret SCI clearance with polygraph (maintained) - Travel required up to 10% - Bachelor’s degree in computer science, applied physics, electrical engineering, systems engineering, or a related technical field. A Master’s degree may be used in lieu of two (2) years of relevant work experience. - Six (6) or more years of working experience. - Comprehensive understanding of EO/IR systems standards, procedures, and practices - Expertise with microwave, VHF, UHF, or infrared wavelength systems - Experience developing, implementing, testing, or analyzing signal processing, optimization, or machine learning algorithms - Experience or equivalent education using test and measurement equipment relevant to advanced sensing technologies, such as spectrum analyzers, oscilloscopes, RF test platforms, wireless communications testbeds, biometric sensor test systems, or commercial off‑the‑shelf sensing devices - Experience or equivalent education involving telecommunications systems, radio frequency (RF) sensing, signal processing, biometric sensing modalities, and/or advanced sensor system design and evaluation - Experience managing a multi-disciplinary research and development (R&D) or Test and Evaluation (T&E) team - Experience creating program plans, work breakdown structures, and milestone schedules We could combine some items into paragraphs but list is fine. Qualifications (nice-to-have): - Master’s degree or PhD in computer science, applied physics, electrical engineering, systems engineering, or related fields, with four (4) or more years of work experience - Four (4) years of experience with programming languages or tools commonly used in sensing, data analysis, or experimental automation, such as LabVIEW, Python, MATLAB, C/C++, or embedded systems software - Two (2) years of experience in the Intelligence Community (IC), including experience with requirements, CONOPS, and transition - Awareness of supply chain, security, and integration considerations for commercial off‑the‑shelf sensing technologies, telecommunications hardware, and