[Spring 2027] Technology Services Intern

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract relevant content. Let's parse the posting. Key info: - Whitney’s Academic Year Internship program offers a semester-long paid internship for rising Juniors and above (including Graduate students) enrolled in an accredited academic program. Internship is in person and onsite. For spring 2027, interns commit between 16–21 hours per week over 10–12 weeks for a total of 176 hours. Official program dates: Jan 18-Apr 26, 2027. Interns assigned to a specific department at the Museum for duration. - Application window for Spring 2027 Ostrover Family Academic Internship is now open through November 9. Rolling basis, some opportunities may close before deadline. For more info, visit internships page. (We can drop application instructions.) - The Whitney seeks a Technology Services Intern for the spring 2027 semester. - One or two solutions built properly, plus documentation, is the whole job. Museum gets solutions actually in use. Intern leaves with portfolio of work that real people depend on. - Expected Projects & Assignments: Build Solutions from the Idea List (review list with Director, select one or two ideas, scope, build, test with staff, hand over solution, documentation, walkthrough). Knowledge Base Documentation: Write staff-facing KB articles for solutions built and existing fixes, follow format, submit through repo, version control fundamentals taught, target 4-6 published articles. Working with AI: Use Claude for drafting, code, troubleshooting, documentation, explain approach, write prompts, verify, test code, check facts, read before publishing, report where AI got it wrong. Team Participation: Attend weekly team meeting, give short update, keep ideas current in Asana, flag anything discovered that should become its own idea or ticket. - Skills & Qualifications: Currently enrolled undergraduate junior or senior. Computer science, information systems, digital humanities, museum studies with a technology focus, or related field. Coursework matters less than being able to show something built. Required: Hands-on experience using an AI assistant such as Claude to write code or documentation, with examples to show and ability to explain approach taken. Required: Clear written English, able to explain a technical step to a non-technical reader. Required: Comfortable finishing something small rather than starting something large. Desired: Able to write and debug a script in at least one language, PowerShell or Python. Desired: Interest in museums, cultural institutions, or nonprofit technology. No prior professional experience required. This is entry-level internship. Coursework, personal projects, hackathons, open source contributions count as evidence. Prior IT support or help desk experience not required. Certifications not required. - Outcomes: Portfolio of solutions in active use at museum, with name attached; published documentation used daily by staff; practice applying AI to real problems under real constraints, reviewed by someone who does it daily; working view of how technology runs inside a cultural institution. - Compensation: Interns are provided a stipend of $3000. Generous support for Ostrover Family Academic Year Interns is provided by Julie and Doug Ostrover. - About The Whitney: description of museum. We need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must decide which sections have real content. - About the role: Could include description of internship, what it is, department assignment, etc. We have content: Whitney’s Academic Year Internship program offers a semester-long paid internship for rising Juniors and above... assigned to a specific department... The Whitney seeks a Technology Services Intern... One or two solutions built properly... etc. So we can put that in About the role. - Responsibilities: Expected Projects & Assignments, Knowledge Base Documentation, Working with AI, Team Participation. Those are duties/responsibilities. So we can list them as bullet list. - Requirements: Could be required qualifications: currently enrolled undergraduate junior or senior; hands-on experience using AI assistant such as Claude; clear written English; comfortable finishing something small; etc. Also maybe "Currently enrolled undergraduate junior or senior." That is a requirement. Also "Coursework matters less than being able to show something built." That's more of a qualification? We'll treat as requirement. - Qualifications: Could be desired qualifications: able to write and debug a script in PowerShell or Python; interest in museums, cultural institutions, nonprofit technology; etc. Also maybe "Computer science, information systems, digital humanities, museum studies with a technology focus, or a related field." That could be qualification. - Skills: Could be skills like using AI assistant, clear written English, finishing small tasks, scripting, etc. But we already used some in requirements/qualifications. Might need to differentiate but we can still include a Skills section with bullet list of skills like "AI-assisted coding (Claude)", "Technical communication", "Scripting (PowerShell/Python)", "Documentation", "Asana tracking", etc. - Benefits: Could include "Portfolio of solutions in active use", "Published documentation used daily", "Experience applying AI", "Insight into museum tech operations", maybe also "Stipend"? But stipend is Pay. Benefits could be non-monetary: portfolio, documentation, AI practice, view of tech inside cultural institution. Also maybe "Generous support for Ostrover Family Academic Year Interns". That's more about funding. - Pay: Stipend of $3000. - Schedule: Hours per week 16-21 over 10-12 weeks, total 176 hours, program dates Jan 18-Apr 26, 2027. Also mention in-person onsite. We must not include filler like "commensurate with experience". Not present. We must not include application instructions, EEO, etc. Remove those. We must not repeat job title as heading. The job title is "Technology Services Intern". We must not use that as heading. We must not include Job ID/requisition numbers. We must output only HTML fragment, no /, no markdown fences. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits, and

    for prose. Thus each section will have

    Section Name

    then either

    prose or

    • list. We need to decide which sections get lists vs prose. - About the role: prose describing internship. - Responsibilities: list of duties. - Requirements: list of required items. - Qualifications: list of desired/qualifications. - Skills: list of skills. - Benefits: list of benefits. - Pay: maybe prose with stipend amount. - Schedule: prose with hours and dates. We must ensure we only include sections that have real content. All sections have content. Now extract precise content. About the role: From posting: "The Whitney’s Academic Year Internship program offers a semester-long paid internship for rising Juniors and above (to include Graduate students) enrolled in an accredited academic program. The internship is in person and onsite. For spring 2027, interns commit between 16–21 hours per week over 10–12 weeks for a total of 176 hours. The official program dates will span from January 18-April 26, 2027. Interns are assigned to a specific department at the Museum for the duration of the internship. The application window for our Spring 2027 Ostrover Family Academic Internship is now open through November 9. Please note that all candidates will be considered on a rolling basis, and as such, some opportunities may close before the deadline. For more information, including information on eligibility requirements, please visit our internships page. The Whitney seeks a Technology Services Intern for the spring 2027 semester. One or two solutions built properly, plus the documentation that goes with them, is the whole job. The museum gets solutions that are actually in use. The intern leaves with a portfolio of work that real people depend on." We should remove application window and rolling basis lines (application instructions). Also remove "For more information, including information on eligibility requirements, please visit our internships page." That's application instruction. So we keep core description. Thus About the role prose: combine: "The Whitney’s Academic Year Internship program offers a semester-long paid internship for rising Juniors and above (including graduate students) enrolled in an accredited academic program. The internship is in person and onsite. For spring 2027, interns commit between 16–21 hours per week over 10–12 weeks for a total of 176 hours, with official program dates from January 18 to April 26, 2027. Interns are assigned to a specific department at the Museum for the duration of the internship. The Whitney seeks a Technology Services Intern for the spring 2027 semester. One or two solutions built properly, plus accompanying documentation, constitute the role; the museum receives solutions that are actually in use, and the intern leaves with a portfolio of work that real people depend on." That seems good. Responsibilities: list from Expected Projects & Assignments, Knowledge Base Documentation, Working with AI, Team Participation. We need to capture each bullet. Let's extract: - Build Solutions from the Idea List: * Review the Technology Services Idea Management list with the Director and select one or two ideas to take on for the term * Scope each one down to something that can be finished in the time available: what it does, what it does not do, and who uses it * Build it. Depending on the idea, this means a PowerShell or Python script, a Power Automate flow, a SharePoint page, a Freshservice workflow, or a small web page * Test it with a staff member who actually has the problem before calling it done * Hand it over at the end of the term: working solution, documentation, and a walkthrough for whoever runs it next - Knowledge Base Documentation: * Write staff-facing knowledge base articles for the solutions built, and for existing fixes the team has never written down * Follow the department’s established article format: structured metadata, plain language, numbered steps, and screenshots where they help * Submit articles through the department’s documentation repository and review process. Version control fundamentals are taught on the job * Target for the term: four to six published articles - Working with AI: * Use Claude for drafting, code, troubleshooting, and documentation, and be able to explain the approach taken * Write prompts that carry enough context to produce a usable result * Verify what comes back. Test the code, check the facts, and read anything going to staff line by line before it publishes * Report back where the AI got it wrong. This informs both the team’s practice and the museum’s wider AI enablement work - Team Participation: * Attend the Technology Services weekly team meeting and give a short update on what is built and what is blocked * Keep assigned ideas current in Asana so the team can see status without asking * Flag anything discovered along the way that should become its own idea or ticket We'll make a
      with
      • items; each bullet can be a sentence or multiple sentences. Could break into multiple
      • for each subpoint, but we can keep each main bullet as
      • containing multiple sentences. That's fine. Requirements: list required items. From Skills