Part-Time Audio/Video Recording Assistant, UMKC Conservatory
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Application Deadline", "Sponsorship Information", "Community Information", "Benefit Eligibility", "Equal Employment Opportunity", etc. Keep substantive info: description of role, duties, shift, qualifications, preferred qualifications, anticipated hiring range (pay), maybe grade etc. Also note "Benefit Eligibility" says not eligible for benefits, but we should not create Benefits section unless posting actually states them. It does state benefit eligibility (not eligible). Should we include Benefits section? The instruction: "Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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 posting does state benefit eligibility: "This position is not eligible for University benefits." That's specific content. So we can include a Benefits section with that info. However we need to consider if that is considered "real, specific content". Yes. So include Benefits section.
Pay: "Anticipated Hiring Range The anticipated hiring range for this position has been established as $15.10/hourly." That's specific. So include Pay section.
Schedule: "Shift This position must be available to work evening and weekend hours. The time commitment varies widely depending on departmental workload; many weeks there will be no work at all, while during our busiest season there may be up to 20 hours available per week. Applicants for this opening will be expected to work on average 10 hours per week." That's schedule info. So include Schedule section.
About the role: The first paragraph describing role. Could be About the role.
Responsibilities: list of duties: "Other Duties Include, But Are Not Limited To Live sound reinforcement (system engineering and operation)Audio masteringVideo recording (camera setup and operation)Video post-production (editing, audio layback, and media exporting)Audio/Video archiving (preparation, digitization/transfer, and metadata entry)". Also earlier: "assist the Conservatory’s Recording Studio in capturing a variety of events, including ensemble concerts, student/faculty/guest artist recitals, dance performances, special events, and recording sessions. These events occur both on and off campus and frequently take place in the evening and/or during the weekend." That could be responsibilities too. We'll combine.
Requirements: Minimum Qualifications: "A high school diploma and at least 2 years of experience from which comparable knowledge and skills can be acquired is necessary."
Qualifications: Preferred Qualifications list.
Skills: maybe we can extract from preferred qualifications: hands-on experience with recording and editing of classical music, prior experience with Pro Tools, Davinci Resolve, and Dante audio networking, interest in acoustic music, thorough understanding of stereo microphone techniques. Could be Skills section.
But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one? But the instruction says use headings for those categories if we have content. We can have Requirements (minimum), Qualifications (preferred), Skills (maybe derived). However we might avoid duplication. Let's see: Minimum Qualifications is a requirement. Preferred Qualifications could be Qualifications. Skills could be derived from preferred qualifications but could be separate. Might be okay to have Requirements, Qualifications, Skills.
But we need to ensure we don't create sections with filler. All have content.
We'll produce:
About the role
... description ...
Responsibilities
- ... items ...
Requirements
Minimum Qualifications: A high school diploma and at least 2 years of experience from which comparable knowledge and skills can be acquired is necessary.
Qualifications
- Bachelor’s Degree in audio engineering or a related field
- Hands-on experience with the recording and editing of classical music
- Prior experience with Pro Tools, Davinci Resolve, and Dante audio networking
- An interest in acoustic music, including classical and jazz
- A thorough understanding of stereo microphone techniques
Skills
... maybe we can combine with Qualifications? But we already have Qualifications as list. Skills could be things like: Live sound reinforcement, Audio mastering, Video recording, Video post-production, Audio/Video archiving. But those are responsibilities. Better to keep Skills as technical skills: Pro Tools, Davinci Resolve, Dante, stereo mic techniques, etc. But that duplicates Qualifications. Might be okay to omit Skills section and just have Qualifications. However the instruction says we can use those headings if we have content. It's not required to use all. We can choose to omit Skills if it would be thin. Let's see if we have enough distinct content for Skills beyond Qualifications. Could list: Live sound reinforcement system engineering and operation, Audio mastering, Video recording (camera setup and operation), Video post-production (editing, audio layback, media exporting), Audio/Video archiving (preparation, digitization/transfer, metadata entry). Those are more duties/responsibilities. So maybe we skip Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule, Benefits. Check each for real content. About the role: we have paragraph describing role. Responsibilities: list of duties. Requirements: minimum qualifications. Qualifications: preferred qualifications list. Pay: anticipated hiring range $15.10/hourly. Schedule: shift details. Benefits: not eligible for University benefits; may participate in Tax Deferred Annuity Plan (403b). Provide that. We must not include boilerplate like "Application Deadline", "Sponsorship Information", "Community Information", "Equal Employment Opportunity", etc. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting that are not boilerplate. Let's extract all substantive info: - Hiring Department UMKC Conservatory Job Description - Part-time Audio/Video Recording Assistant - Assist Conservatory’s Recording Studio in capturing events: ensemble concerts, student/faculty/guest artist recitals, dance performances, special events, recording sessions. Events on/off campus, frequently evening/weekend. - Other Duties Include, But Are Not Limited To: Live sound reinforcement (system engineering and operation) Audio mastering Video recording (camera setup and operation) Video post-production (editing, audio layback, and media exporting) Audio/Video archiving (preparation, digitization/transfer, and metadata entry) - Shift: must be available to work evening and weekend hours. Time commitment varies widely depending on departmental workload; many weeks no work; busiest season up to 20 hours per week. Expected average 10 hours per week. - Minimum Qualifications: high school diploma and at least 2 years of experience from which comparable knowledge and skills can be acquired. - Preferred Qualifications: Bachelor’s Degree in audio engineering or related field Hands-on experience with recording and editing of classical music Prior experience with Pro Tools, Davinci Resolve, and Dante audio networking Interest in acoustic music, including classical and jazz Thorough understanding of stereo microphone techniques - Anticipated Hiring Range: $15.10/hourly. - Grade: Salary Plan # 006 - University Title: Senior Operations Support Technician - To review the University of Missouri’s Staff Compensation Structure you can view the Job Code detail page. - Internal applicants can determine their university title by accessing the Talent Profile tile in myHR. - Application Deadline: 9/29/2026. (boilerplate? It's a date; but it's application instruction; we should remove application instructions per rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So remove Application Deadline.) - Sponsorship Information: Employment visa sponsorship is not available for this position. (This is sponsorship info; likely considered boilerplate? Not exactly EEO but it's about visa sponsorship. Might be considered metadata; but rule says remove application instructions, not necessarily sponsorship. However it's not substantive to role? It's a condition. Might be considered relevant. But the instruction says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Sponsorship info is not explicitly listed, but it's similar to legal. Might be considered boilerplate. Safer to remove it. - Community Information: description of Kansas City etc. That's likely boilerplate/community info, remove. - Benefit Eligibility: This position is not eligible for University benefits. Individuals in non benefit eligible positions may choose to participate in the Tax Deferred Annuity Plan (403b). For information about this plan, please visit the Faculty & Staff Benefits website at https://www.umsystem.edu/departments-staff/human-resources/benefits-retirement/retirement/core-voluntary-plans This is substantive about benefits; we keep but maybe trim the URL? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep the sentence about not eligible and may participate in TDA plan, and maybe the URL? The URL is a reference for more info; it's still substantive. We'll keep it. - Equal Employment Opportunity: boilerplate, remove. Also we have "Grade: Salary Plan # 006" and "University Title: Senior Operations Support Technician" and lines about reviewing compensation structure and internal applicants. Those are metadata but maybe substantive? They are about grade and title. Could be considered part of Pay/Qualifications? The instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include grade and title in a short paragraph maybe under Pay or About the role. But we already have Pay section with hourly rate. Could add a note about grade and title. However the instruction says prefer a few substantive sections over many thin ones. So we could incorporate grade and title into Pay section as additional detail. Similarly "To review the University of Missouri’s Staff Compensation Structure you can view the Job Code detail page." and "Internal applicants can determine their university title by accessing the Talent Profile tile in myHR." are instructions/internal info; could be considered boilerplate/internal instructions; maybe remove. We need to decide what to keep. The rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep grade and university title as they are substantive about the position. However they might be considered metadata but still substantive. We'll include them in a short paragraph maybe under Pay or a separate "Details" section but we don't have a heading for that. Could add a
after Pay section. But we must not create headings without real content. We could add a
under Pay section that includes grade and title. Let's structure:
About the role
The UMKC Conservatory is accepting applications for a part-time Audio/Video Recording Assistant. In this role, you will assist the Conservatory’s Recording Studio in capturing a variety of events, including ensemble concerts, student/faculty/guest artist recitals, dance performances, special events, and recording sessions. These events occur both on and off campus and frequently take place in the evening and