Databricks Platform and DevSecOps Engineer
Peregrine Advisors · United States · 3 wk ago
RemoteRemoteEngineering$120k–$140k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Peregrine" description, then details about role. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We have Pay: salary range $120k-$140k per year. Schedule: remote position (full-time). Benefits: described. Responsibilities: list of tasks (Your first project...). Requirements: list of requirements. Qualifications? Might be overlapping with requirements; but we can treat Requirements as qualifications. Skills maybe separate? The posting includes "Preferred" and "Who you are" and "What you bring". Could map to Skills or Qualifications. We need to avoid filler headings. We'll include sections: About the role (maybe a brief description), Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Qualifications? But we can combine Requirements and Qualifications. The instruction: use headings for those specific labels if content exists. We'll include About the role (summary of role). Responsibilities (list of duties). Requirements (list). Benefits (list). Pay (salary). Schedule (remote full-time). Avoid duplication.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, equal opportunity, application instructions, etc. Also remove navigation, cookie, legal. The posting includes "Peregrine Advisors is an equal opportunity employer." and "Peregrine exclusively works with OPEN Data Jobs..." That's boilerplate; remove.
We need to preserve all substantive information. So include details about Peregrine, mission, culture maybe in About the role? The "About Peregrine" is company description; could be part of About the role? Probably we can put that in About the role section.
Let's extract:
About Peregrine: description of company, mission, values, awards, etc.
Role description: At Peregrine Advisors, you will own the environments, the deployment path, and the platform operations beneath production data products for a federal agency... etc.
Your first project: list of tasks.
Requirements: bullet list.
Preferred: bullet list.
Who you are: description.
What you bring: bullet list.
When we talk: instruction.
Benefits: list.
What we offer: description.
What we commit to: description.
We need to output only HTML fragment.
We'll create sections:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We have Pay: salary range $120k-$140k per year. Schedule: remote position (full-time). Benefits: described. Responsibilities: list of tasks (Your first project...). Requirements: list of requirements. Qualifications? Might be overlapping with requirements; but we can treat Requirements as qualifications. Skills maybe separate? The posting includes "Preferred" and "Who you are" and "What you bring". Could map to Skills or Qualifications. We need to avoid filler headings. We'll include sections: About the role (maybe a brief description), Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Qualifications? But we can combine Requirements and Qualifications. The instruction: use headings for those specific labels if content exists. We'll include About the role (summary of role). Responsibilities (list of duties). Requirements (list). Benefits (list). Pay (salary). Schedule (remote full-time). Avoid duplication.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, equal opportunity, application instructions, etc. Also remove navigation, cookie, legal. The posting includes "Peregrine Advisors is an equal opportunity employer." and "Peregrine exclusively works with OPEN Data Jobs..." That's boilerplate; remove.
We need to preserve all substantive information. So include details about Peregrine, mission, culture maybe in About the role? The "About Peregrine" is company description; could be part of About the role? Probably we can put that in About the role section.
Let's extract:
About Peregrine: description of company, mission, values, awards, etc.
Role description: At Peregrine Advisors, you will own the environments, the deployment path, and the platform operations beneath production data products for a federal agency... etc.
Your first project: list of tasks.
Requirements: bullet list.
Preferred: bullet list.
Who you are: description.
What you bring: bullet list.
When we talk: instruction.
Benefits: list.
What we offer: description.
What we commit to: description.
We need to output only HTML fragment.
We'll create sections:
About the role
... combine Peregrine description and role overview.
Responsibilities
- ... list of duties from "Your first project" and maybe other duties.
Requirements
- ... list of required qualifications.
Preferred qualifications
maybe but heading "Qualifications" is allowed. We could use "Qualifications" for preferred? But we already have Requirements. Could add "Preferred qualifications" but not in allowed list; only allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put preferred under Qualifications or Skills. Let's put under Qualifications.Qualifications
- ... preferred items. maybe also include "Who you are" and "What you bring" as skills? Could put under Skills. Better: Use Skills for "Who you are" and "What you bring". But those are more traits. We'll put them under Skills. Thus:
- ... items from Who you are and What you bring.