Director, Fastpath Growth Marketing
Delinea · United States · 3 wk ago
RemoteRemoteMarketingFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Delinea" (company description) then "Position Summary", "Key Responsibilities", "What We’re Looking For", "Success in This Role", "Why work at Delinea?" etc.
We must use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we should only include sections when posting has real specific content. We need to map content to appropriate headings.
We have:
- About Delinea (company description) maybe "About the role"? Actually "About Delinea" is about company, not role. Could be "About the role" but we have Position Summary. The instruction: use
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we should only include sections when posting has real specific content. We need to map content to appropriate headings.
We have:
- About Delinea (company description) maybe "About the role"? Actually "About Delinea" is about company, not role. Could be "About the role" but we have Position Summary. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to decide which sections to include based on content.
We have:
- Position Summary: could be under "About the role" (summary of role). Or we could have a separate heading "Position Summary" but not in list; but instruction says use those example headings, but not strictly limited? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. So we should map content to those.
Thus:
- About the role: include Position Summary and maybe About Delinea? Actually About Delinea is company overview; could be part of About the role? Might be better to include a short paragraph about company under About the role? But they said do NOT repeat the job title as a heading. They didn't forbid including company description. We'll include About the role containing Position Summary and maybe a brief about Delinea? But we have separate "About Delinea" paragraph; we could incorporate it into About the role.
- Responsibilities: Key Responsibilities list.
- Requirements / Qualifications / Skills: The "What We’re Looking For" includes experience, knowledge, etc. Could be split into Requirements (experience) and Skills (knowledge). But we can combine into Requirements or Qualifications. Since we prefer few substantive sections, we could have Requirements (includes experience, knowledge, abilities). Could also have Skills separate but not needed.
- Benefits: The "Why work at Delinea?" includes benefits: competitive salaries, meaningful bonus program, excellent benefits including healthcare insurance, pension/retirement matching, comprehensive life insurance, employee assistance program, time off plans, paid company holidays. Also core values etc. So we can include Benefits section.
- Pay: Not specified (no salary range). So we should NOT include Pay section because no specific content.
- Schedule: Not specified. So omit.
Thus we will output:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. So we should map content to those.
Thus:
- About the role: include Position Summary and maybe About Delinea? Actually About Delinea is company overview; could be part of About the role? Might be better to include a short paragraph about company under About the role? But they said do NOT repeat the job title as a heading. They didn't forbid including company description. We'll include About the role containing Position Summary and maybe a brief about Delinea? But we have separate "About Delinea" paragraph; we could incorporate it into About the role.
- Responsibilities: Key Responsibilities list.
- Requirements / Qualifications / Skills: The "What We’re Looking For" includes experience, knowledge, etc. Could be split into Requirements (experience) and Skills (knowledge). But we can combine into Requirements or Qualifications. Since we prefer few substantive sections, we could have Requirements (includes experience, knowledge, abilities). Could also have Skills separate but not needed.
- Benefits: The "Why work at Delinea?" includes benefits: competitive salaries, meaningful bonus program, excellent benefits including healthcare insurance, pension/retirement matching, comprehensive life insurance, employee assistance program, time off plans, paid company holidays. Also core values etc. So we can include Benefits section.
- Pay: Not specified (no salary range). So we should NOT include Pay section because no specific content.
- Schedule: Not specified. So omit.
Thus we will output:
About the role
... (position summary + about Delinea)
Responsibilities
- ... each responsibility
Requirements
- ... each requirement/skill Benefits
- ... each benefit