Instrumentation Manager
Association of Universities for Research in Astronomy · Boulder, CO · 1 mo ago
On-siteManagement$155k–$187k/yrFull-time
We need to produce HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Apply by September 4, 2026..." etc. Also remove "Please submit a cover letter..." etc. Also remove "Details on benefits can be found at Benefits by Location - Aura Human Resources". Also remove "Salary Range: $155,000-$187,000 per year." That is pay info, we can include Pay section. Also "AURA offers an excellent benefits package including paid time off and retirement plan contributions, competitive salary commensurate with experience, and a very attractive work environment." That's benefits but includes "competitive salary commensurate with experience" which is placeholder? It says "competitive salary commensurate with experience" which is vague; we should not include placeholder? The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The phrase "competitive salary commensurate with experience" is placeholder; we should avoid including that as content. However we have specific salary range: $155,000-$187,000 per year. That's concrete. So Pay section can include that. Benefits: we have "paid time off and retirement plan contributions". That's specific enough. Also "excellent benefits package". Might be okay. We'll include Benefits section with those specifics. Also we have Work Environment & Physical Requirements: could be under maybe "Work Environment" but not in list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. "About the role" could be introductory paragraph describing role. "Responsibilities" list essential functions. "Requirements" list degree and experience. "Qualifications" maybe preferences? Could separate. "Skills" maybe abilities. "Benefits" as described. "Pay" salary range. "Schedule" maybe work schedule? Not given explicitly; we have occasional travel, periodic work at high elevation, regular travel between Boulder and Maui. Not a schedule like full-time/part-time. Might not include Schedule if no specific schedule info. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not stated; we should omit Schedule section.
We need to avoid filler like "commensurate with experience". In benefits we have "competitive salary commensurate with experience" which is filler; we should not include that phrase. We'll extract only concrete benefits: paid time off, retirement plan contributions. Also maybe "excellent benefits package" is vague; maybe we can keep as it's not filler? It's somewhat generic but not prohibited phrase. Might be okay. Safer to include only concrete: paid time off, retirement plan contributions. Also "AURA offers an excellent benefits package including paid time off and retirement plan contributions". We'll keep that sentence.
Now we need to preserve all substantive info. Let's parse the posting.
Intro paragraph about DKIST, NSO, AURA, hiring DKIST Instrumentation Manager. That's about the role.
Essential Functions list (many bullet-like sentences). We'll turn into