HF Analyst
Radiance Technologies · Ohio, United States · 1 mo ago
Business DevelopmentFull-time
We need to output HTML fragment with sections only if content present. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to extract sections.
Job description includes:
- Intro: Radiance Technologies is an employee-owned company... benefits... (this is about the company, could be "About the role" or maybe "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have:
- About the role: maybe the description of role: "Radiance is seeking a highly qualified and motivated HF Analyst to support the production of critical intelligence pertaining to regional threat systems supporting the National Air and Space Intelligence Center (NASIC) mission. They will be working collaboratively with other analysts to solve complex exploitation issues."
- Responsibilities: list of duties: bullet points under Job Duties.
- Requirements: maybe "Active Top Secret Clearance with SCI eligibility", "Strong technical writing and briefing skills", "Willingness to work various shifts". Those are required skills and qualifications.
- Qualifications: maybe "Desired Skills And Qualifications" list: excellent analytical and time management skills, communicates effectively, thrives in dynamic team-oriented environment, experience in additional NASIC mission areas (SAR, EO, TIR, FMV, GMT, LIDAR). Could be considered Qualifications.
- Skills: maybe combine required and desired? But we have separate sections for Skills. Could put required skills under Requirements, desired under Skills? Or we could put Skills as a separate section for both required and desired? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections.
We need to decide mapping:
- About the role: intro paragraph about role.
- Responsibilities: Job Duties list.
- Requirements: Required Skills And Qualifications (active TS/SCI, technical writing, willingness to work various shifts). Could also include "Active Top Secret Clearance with SCI eligibility" as requirement.
- Qualifications: Desired Skills And Qualifications (analytical, time management, communication, team-oriented, experience in additional NASIC mission areas).
- Skills: maybe we could combine both have required and desired; but we already used Requirements and Qualifications. Could still have Skills section for technical writing and briefing skills? But that's already in Requirements. Might be redundant. Better to not create Skills if content overlaps; but we can still have Skills if we have distinct content not covered elsewhere. However we have technical writing and briefing skills already in Requirements; we could move that to Skills and keep Requirements just for clearance and shift willingness. But the instruction: Preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all info. We can split as we like as long as we keep all info.
We also have Benefits: The intro mentions employee ownership, generous 401K, full health/dental/life/vision insurance benefits, educational reimbursement, competitive salaries, interesting assignments, pleasant work environment. That's benefits. So we should have a Benefits section with those items as list.
Pay: Not specified explicitly; only "competitive salaries" but that's vague. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive salaries" is a statement about pay, but it's not a specific number or range. Is that enough to create a Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "states them" meaning actual content about pay, schedule, benefits. "competitive salaries" is a statement about pay, albeit vague. I'd argue we can include a Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." So maybe we can incorporate pay into Benefits or About the role. But they said Benefits section for benefits; Pay separate if stated. Since we have "competitive salaries" we could include a Pay section with that phrase. But we also have "generous 401K" etc under benefits. So we can have Benefits section listing those, and Pay section with "competitive salaries". However they said never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive salaries, so we can.
Schedule: Not mentioned except "Willingness to work various shifts" which is a requirement, not schedule details. So we should not create a Schedule section because no schedule info given.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce sections in order: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly Skills could be omitted if we already covered skills elsewhere. But we have technical writing and briefing skills (requirements) and analytical, time management, communication, team-oriented, experience (desired). Those are skills. Could put all under Skills section and then Requirements just clearance and shift willingness? But then we lose distinction between required and desired. However we can still keep both.
Let's decide:
- About the role: paragraph describing role.
- Responsibilities: ul list of duties.
- Requirements: ul list: Active Top Secret Clearance with SCI eligibility, Willingness to work various shifts.
- Qualifications: ul list: Strong technical writing and briefing skills (maybe this is skill but we can put here), Excellent analytical and time management skills, Communicates effectively through briefings and written reports, Thrives in a dynamic, team-oriented environment, Experience in additional NASIC mission areas (SAR, EO, TIR, FMV, GMT, LIDAR).
But then we have duplicated technical writing etc. Actually technical writing is in Required Skills And Qualifications. So we could put that under Requirements as well. But we already have clearance and shift willingness. Could add technical writing there. However the instruction: "Required Skills And Qualifications" includes technical writing and briefing skills, willingness to work various shifts. So we can put all three under Requirements.
Then Desired Skills And Qualifications go under Qualifications.
Thus we have:
Requirements:
- Active Top Secret Clearance with SCI eligibility
- Strong technical writing and briefing skills
- Willingness to work various shifts
Qualifications:
- Possession of excellent analytical and time management skills
- Communicates effectively through briefings and written reports
- Thrives in a dynamic, team-oriented environment
- Experience in additional NASIC mission areas (SAR, EO, TIR, FMV, GMT, LIDAR)
Now Benefits: list:
- Employee ownership
- Generous 401K
- Full health/dental/life/vision insurance benefits
- Educational reimbursement
- Competitive salaries (maybe this goes to Pay)
- Interesting assignments
- Pleasant work environment
But we said competitive salaries maybe Pay. Let's separate: Benefits list without competitive salaries; Pay section with "Competitive salaries". However the intro also mentions "competitive salaries" as part of benefits list. We'll put it in Pay.
Thus Benefits:
- Employee ownership
- Generous 401K
- Full health/dental/life/vision insurance benefits
- Educational reimbursement
- Interesting assignments
- Pleasant work environment
Pay:
- Competitive salaries
Now About the role: paragraph: "Radiance is seeking a highly qualified and motivated HF Analyst to support the production of critical intelligence pertaining to regional threat systems supporting the National Air and Space Intelligence Center (NASIC) mission. They will be working collaboratively with other analysts to solve complex exploitation issues."
Also maybe include the first sentence about Radiance Technologies being employee-owned etc. That is more about company benefits; but we already captured benefits. Could include a brief about company in About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So About the role should describe the role, not company. So we keep the role description.
Now Responsibilities: list from Job Duties:
- Perform data extraction, analysis, and quality control of HF data
- Coordinate with multiple production teams
- Work with customers to produce requirements for new intelligence taskings
- Develop and enhance new and existing intelligence products
- Participate in Government required training activities
Now we need to ensure we don't include boilerplate like EEO etc. Remove that.
Now produce HTML:
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to extract sections.
Job description includes:
- Intro: Radiance Technologies is an employee-owned company... benefits... (this is about the company, could be "About the role" or maybe "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have:
- About the role: maybe the description of role: "Radiance is seeking a highly qualified and motivated HF Analyst to support the production of critical intelligence pertaining to regional threat systems supporting the National Air and Space Intelligence Center (NASIC) mission. They will be working collaboratively with other analysts to solve complex exploitation issues."
- Responsibilities: list of duties: bullet points under Job Duties.
- Requirements: maybe "Active Top Secret Clearance with SCI eligibility", "Strong technical writing and briefing skills", "Willingness to work various shifts". Those are required skills and qualifications.
- Qualifications: maybe "Desired Skills And Qualifications" list: excellent analytical and time management skills, communicates effectively, thrives in dynamic team-oriented environment, experience in additional NASIC mission areas (SAR, EO, TIR, FMV, GMT, LIDAR). Could be considered Qualifications.
- Skills: maybe combine required and desired? But we have separate sections for Skills. Could put required skills under Requirements, desired under Skills? Or we could put Skills as a separate section for both required and desired? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections.
We need to decide mapping:
- About the role: intro paragraph about role.
- Responsibilities: Job Duties list.
- Requirements: Required Skills And Qualifications (active TS/SCI, technical writing, willingness to work various shifts). Could also include "Active Top Secret Clearance with SCI eligibility" as requirement.
- Qualifications: Desired Skills And Qualifications (analytical, time management, communication, team-oriented, experience in additional NASIC mission areas).
- Skills: maybe we could combine both have required and desired; but we already used Requirements and Qualifications. Could still have Skills section for technical writing and briefing skills? But that's already in Requirements. Might be redundant. Better to not create Skills if content overlaps; but we can still have Skills if we have distinct content not covered elsewhere. However we have technical writing and briefing skills already in Requirements; we could move that to Skills and keep Requirements just for clearance and shift willingness. But the instruction: Preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all info. We can split as we like as long as we keep all info.
We also have Benefits: The intro mentions employee ownership, generous 401K, full health/dental/life/vision insurance benefits, educational reimbursement, competitive salaries, interesting assignments, pleasant work environment. That's benefits. So we should have a Benefits section with those items as list.
Pay: Not specified explicitly; only "competitive salaries" but that's vague. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive salaries" is a statement about pay, but it's not a specific number or range. Is that enough to create a Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "states them" meaning actual content about pay, schedule, benefits. "competitive salaries" is a statement about pay, albeit vague. I'd argue we can include a Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." So maybe we can incorporate pay into Benefits or About the role. But they said Benefits section for benefits; Pay separate if stated. Since we have "competitive salaries" we could include a Pay section with that phrase. But we also have "generous 401K" etc under benefits. So we can have Benefits section listing those, and Pay section with "competitive salaries". However they said never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive salaries, so we can.
Schedule: Not mentioned except "Willingness to work various shifts" which is a requirement, not schedule details. So we should not create a Schedule section because no schedule info given.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce sections in order: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly Skills could be omitted if we already covered skills elsewhere. But we have technical writing and briefing skills (requirements) and analytical, time management, communication, team-oriented, experience (desired). Those are skills. Could put all under Skills section and then Requirements just clearance and shift willingness? But then we lose distinction between required and desired. However we can still keep both.
Let's decide:
- About the role: paragraph describing role.
- Responsibilities: ul list of duties.
- Requirements: ul list: Active Top Secret Clearance with SCI eligibility, Willingness to work various shifts.
- Qualifications: ul list: Strong technical writing and briefing skills (maybe this is skill but we can put here), Excellent analytical and time management skills, Communicates effectively through briefings and written reports, Thrives in a dynamic, team-oriented environment, Experience in additional NASIC mission areas (SAR, EO, TIR, FMV, GMT, LIDAR).
But then we have duplicated technical writing etc. Actually technical writing is in Required Skills And Qualifications. So we could put that under Requirements as well. But we already have clearance and shift willingness. Could add technical writing there. However the instruction: "Required Skills And Qualifications" includes technical writing and briefing skills, willingness to work various shifts. So we can put all three under Requirements.
Then Desired Skills And Qualifications go under Qualifications.
Thus we have:
Requirements:
- Active Top Secret Clearance with SCI eligibility
- Strong technical writing and briefing skills
- Willingness to work various shifts
Qualifications:
- Possession of excellent analytical and time management skills
- Communicates effectively through briefings and written reports
- Thrives in a dynamic, team-oriented environment
- Experience in additional NASIC mission areas (SAR, EO, TIR, FMV, GMT, LIDAR)
Now Benefits: list:
- Employee ownership
- Generous 401K
- Full health/dental/life/vision insurance benefits
- Educational reimbursement
- Competitive salaries (maybe this goes to Pay)
- Interesting assignments
- Pleasant work environment
But we said competitive salaries maybe Pay. Let's separate: Benefits list without competitive salaries; Pay section with "Competitive salaries". However the intro also mentions "competitive salaries" as part of benefits list. We'll put it in Pay.
Thus Benefits:
- Employee ownership
- Generous 401K
- Full health/dental/life/vision insurance benefits
- Educational reimbursement
- Interesting assignments
- Pleasant work environment
Pay:
- Competitive salaries
Now About the role: paragraph: "Radiance is seeking a highly qualified and motivated HF Analyst to support the production of critical intelligence pertaining to regional threat systems supporting the National Air and Space Intelligence Center (NASIC) mission. They will be working collaboratively with other analysts to solve complex exploitation issues."
Also maybe include the first sentence about Radiance Technologies being employee-owned etc. That is more about company benefits; but we already captured benefits. Could include a brief about company in About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So About the role should describe the role, not company. So we keep the role description.
Now Responsibilities: list from Job Duties:
- Perform data extraction, analysis, and quality control of HF data
- Coordinate with multiple production teams
- Work with customers to produce requirements for new intelligence taskings
- Develop and enhance new and existing intelligence products
- Participate in Government required training activities
Now we need to ensure we don't include boilerplate like EEO etc. Remove that.
Now produce HTML:
About the role
Radiance is seeking a highly qualified and motivated HF Analyst to support the production of critical intelligence pertaining to regional threat systems supporting the National Air and Space Intelligence Center (NASIC) mission. They will be working collaboratively with other analysts to solve complex exploitation issues.
Responsibilities
- Perform data extraction, analysis, and quality control of HF data
- Coordinate with multiple production teams
- Work with customers to produce requirements for new intelligence taskings
- Develop and enhance new and existing intelligence products
- Participate in Government required training activities
Requirements
- Active Top Secret Clearance with SCI eligibility
- Strong technical writing and briefing skills
- Willingness to work various shifts
Qualifications
- Possession of excellent analytical and time management skills
- Communicates effectively through briefings and written reports
- Thrives in a dynamic, team-oriented environment
- Experience in additional NASIC mission areas (SAR, EO, TIR, FMV, GMT, LIDAR)
Benefits
- Employee ownership
- Generous 401K
- Full health/dental/life/vision insurance benefits
- Educational reimbursement
- Interesting assignments
- Pleasant work environment
Pay
Competitive salaries
We should not include Schedule section. Check that we haven't repeated job title. Good. Check that we preserved all substantive information: we have role description, duties, required clearance, technical writing, shift willingness, desired analytical, time management, communication, team-oriented, experience in mission areas, benefits list, competitive salaries. We omitted the EEO line and the duplicated lines about Radiance Technologies being employee-owned etc (we captured benefits). The first sentence about Radiance Technologies being employee-owned company with benefits that are unmatched... we captured benefits but not the phrase "unmatched by most companies in the Dayton, OH area." That's a substantive detail about benefits being unmatched. Should we preserve that? It's a statement about benefits being unmatched. It's part of benefits description. We could incorporate into Benefits section as a note. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that detail. We could add aunder Benefits: "Benefits are unmatched by most companies in the Dayton, OH area." Or we could add as a list item. Better to add a paragraph. Thus Benefits section could have a
describing that benefits are unmatched, plus a
- list of specific benefits.
Similarly, the first sentence also mentions "employee-owned company". That's a benefit (employee ownership) we already have as list item. Good.
Thus adjust Benefits:
- Employee ownership
- Generous 401K
- Full health/dental/life/vision insurance benefits
- Educational reimbursement
- Interesting assignments
- Pleasant work environment
Benefits
Benefits are unmatched by most companies in the Dayton, OH area.