Software Engineering Co-op (Cloud)

We need to output HTML fragment with sections only if there is real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove application instructions. Keep substantive info. Let's parse the posting: Intro paragraph: "At Sonos we want to create the ultimate listening experience..." That's about the role/company. Could be "About the role" or maybe "About Sonos". Use "About the role". We'll put that paragraph in

. Then: "We’re seeking talented students to join Sonos’s Co-Op Program and explore what it means to blend creativity, technology, and sound. Our co-ops are an essential part of our team, bringing fresh ideas, learning from experts, and helping us push the boundaries of what’s possible. Come broaden your skills, share your input and pursue your passion with our 6 month co-op experience." That's also about the role. Then: "Work Period: January 2027 - June 2027 Location & Schedule: This is a full-time, 40-hour-per-week position with a minimum 4 days per week onsite in our Boston, MA office. There is no relocation or housing assistance for this position." This includes schedule and location. We have Schedule section maybe. Also location could be part of About the role? But we have a Schedule heading if we have specific schedule info. It says full-time, 40-hour-per-week, minimum 4 days per week onsite in Boston. That's schedule info. So we can create a

Schedule

with

Full-time, 40‑hour‑per‑week position; minimum 4 days per week onsite in Boston, MA office.

. Also note no relocation/housing assistance - could be included. Then "What You’ll Do" list: bullet points. That's Responsibilities. So

Responsibilities

with

• ... each bullet. List items: - Dive into our cloud services, learning through first hand experience - Monitor, debug, and be responsible for improving our automated & analytics infrastructure - Add and democratize new forms of telemetry, data, and metrics to allow the team to measure, debug, and make decisions based on data analytics and dashboards - Own and update the development experience via automated pipelines that includes timely feedback and a seamless path to release-level quality - Engineer new automated testing methodologies - Own services from end-to-end by being part of the on-call rotation - Collaborate with other cross-functional teams when issues are found in deployed/production features Now "Skills And Attributes" then subheadings Basic Qualifications, Preferred Qualifications, Program Qualifications. We need to decide sections: Could have Requirements (basic qualifications), Qualifications (preferred?), Skills (maybe combine). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: - About the role: intro paragraphs. - Responsibilities: the "What You’ll Do" list. - Requirements: Basic Qualifications. - Qualifications: Preferred Qualifications? Or maybe Program Qualifications? Actually "Qualifications" could cover both basic and preferred? But we have separate headings: Requirements and Qualifications. Usually Requirements = basic qualifications, Qualifications = preferred qualifications. We'll do that. - Skills: maybe combine Skills And Attributes? But we already used Requirements and Qualifications for qualifications. Skills could be the list of skills/attributes (like object-oriented design, etc.) but those are already in Basic Qualifications. However we could still have Skills section for the list of skills and attributes (like "Ability to break down complex problems..." etc.) but that overlaps. Better to follow the headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Benefits described later: comprehensive benefits program with details. So Benefits section. Pay: No specific pay mentioned. So we should NOT create Pay section because no real specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule we have. Benefits we have. Pay we do not have, so omit. Now we need to extract Benefits content: "We also offer a comprehensive benefits program with choice and flexibility in mind to help support the health, wealth, and overall well-being of our employees. Interns and Coops in the US are eligible for benefits on day one, unless otherwise noted, including: Medical, Dental and Vision Insurance after 90 days of continuous employment Eligibility for our 401(k) plan, with company matching, after 1000 hours of service or 3 years averaging 500 hours of service per year, whichever comes first 80 hours of sick time upon hire, refreshed annually Up to 12 paid holidays per calendar year A generous employee discount program & Sonos Radio HD - on us! Note: No amount of pay is considered to be wages or compensation until such amount is earned, vested, and determinable. The amount and availability of any bonus, benefits, or any other form of compensation and benefits that are allocable to a particular employee remains in the Company's sole discretion unless and until paid and may be modified at the Company’s sole discretion, consistent with the law." We should keep substantive info: benefits list. The note about pay etc maybe considered boilerplate? It's legal disclaimer. Might be considered boilerplate; but it's about benefits. However instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This note is legal disclaimer about benefits; could be considered boilerplate. Safer to omit that note. Keep the benefit items. Thus Benefits section:
  • Medical, Dental and Vision Insurance after 90 days of continuous employment
  • Eligibility for our 401(k) plan, with company matching, after 1000 hours of service or 3 years averaging 500 hours of service per year, whichever comes first
  • 80 hours of sick time upon hire, refreshed annually
  • Up to 12 paid holidays per calendar year
  • A generous employee discount program & Sonos Radio HD – on us!
  Now Requirements (Basic Qualifications): list: - Experience with backend or cloud technologies - Knowledge of QA methodology and tools, software testing processes, and best practices - Object-oriented design and coding skills (JavaScript, Java & Python preferred) with knowledge of JSON and API development - Ability to break down complex problems into elegant, testable pieces - Demonstrated knowledge in: AWS compute, database, and networking services, RESTful API testing - Building out and using automated test frameworks: Spring, JUnit, TestNG, Mocha, Jest - Code repositories - Github/Jira We need to preserve all substantive info. Could combine some lines. Now Qualifications (Preferred Qualifications): list: - Demonstrated knowledge with: CI/CD pipelines - Apigee, API gateway solutions - Configuration management tools (Ansible, Terraform) - Code quality tools (Sonarqube) - Data Analytics skills (CloudWatch, DataDog, Tableau, Kibana, Grafana, LOKI) - Proficiency in Performance Engineering/Testing tools such as JMeter, Gatling - Kubernetes and Docker - Jenkins (or other CI build systems) - Ability to thrive in a fast paced environment, challenge yourself, ask questions, and learn from failure Now Program Qualifications: Could be considered part of Qualifications? But we already have Qualifications for preferred. Program Qualifications maybe separate but we have no heading for Program Qualifications. Could we put them under Qualifications as well? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could treat Program Qualifications as part of Qualifications (maybe combine). But we already have Qualifications for preferred. Could we add another heading like "Program Qualifications"? Not in the list; but we could still use Qualifications heading and include both preferred and program qualifications. However we must not invent headings not in the list? The list is examples, not exclusive? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings; we could also use other headings if needed? Safer to stick to those. So we need to fit Program Qualifications into one of those headings. Perhaps under Qualifications we can include both preferred and program qualifications. Or we could treat Program Qualifications as Requirements? But they are about enrollment etc. Might be better to put them under Qualifications as well. Alternatively we could create a "Requirements" section for basic qualifications, and a "Qualifications" section for preferred + program qualifications. That seems fine. Now Skills: we haven't used Skills heading yet. What content left? The "Skills And Attributes" heading includes both basic and preferred qualifications; we already used those. Maybe there is no separate skills content beyond those. Could we still create a Skills section with something like "Ability to break down complex problems..." etc? But that's already in Requirements. To avoid duplication, maybe we skip Skills section if no distinct content. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills if no unique content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Check if we missed any substantive info: The "Work Period: January 2027 - June 2027" we placed in Schedule? Actually schedule includes work period. Could also be part of About the role. But we have Schedule section with full-time etc. We should include the work period there as well. So Schedule: Full-time, 40‑hour‑per‑week position; minimum 4 days per week onsite in Boston, MA office; Work period: January 2027 – June 2027. Also note no relocation/housing assistance. Now About the role: combine intro paragraphs and maybe the "We’re seeking talented students..." etc. Let's craft a concise paragraph(s). We'll keep all substantive info: At Sonos we want to create the ultimate listening experience... As part of the Sonos team, you’ll collaborate... We’re seeking talented students to join Sonos’s Co-Op Program... Our co-ops are an essential part of our team... Come broaden your skills, share your input and pursue your passion with our 6 month co-op experience. We should not repeat job title. That's fine. Now ensure we removed boilerplate: EEO, legal, accommodation, etc. Also removed "Note: No amount of pay is considered..." etc. Also removed "Your profile will be reviewed and you'll hear from us once we have an update. At Sonos we take the time to hire right and appreciate your patience." That's maybe application instruction? It's not exactly instruction but could be considered boilerplate. Safer to remove. Also removed "2027 Co-op Program Overview The Co-op Program includes the following elements..." That's substantive? It describes program elements: Multi-day orientation, Speaker Series, Social Activities, Real meaningful projects, Mentorship. That is substantive and could be part of About the role or maybe a separate section like "Program Overview". But we don't have a heading for that. Could we include it under About the role? Yes, we can add that as part of About the role description. So we should incorporate those bullet points into About the role maybe as a list? But we have no heading for that; we could add a

  under About the role? The instruction: Use
  • for any list of duties/requirements/benefits. So if we have a list of program elements, we should use
    . Where to place? Could be under About the role as a