Copy of Copy of Copy of Software Engineer II (Hybrid - 2x/week)

before sections? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading. So we can have a leading

  for the "Why join Avery Dennison:" paragraph. Then sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Possibly also "Additional Information" but that's mostly salary range and legal stuff; we already captured salary. The rest is boilerplate (EEO, accommodations, identity verification, pre-employment screening) which we should remove. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the details from "Why join Avery Dennison" paragraph: global materials science..., locations over 50 countries, approx 35k employees, diverse teams stronger, culture of curiosity and courage, open collaborative culture, diversity of thought encouraged, hear from employees, learn more at website. That's substantive; we keep as prose. Also "Benefits:" section: we need to keep each bullet exactly as described. "About the role:" paragraph: we keep. "Key Responsibilities:" list items: we need to turn each bullet into

• under a
  . The responsibilities are given as headings with colon then description. We should treat each as a list item. Eg: "Full-Stack Feature Development: Design, build, test, and maintain scalable microservices using .NET Core for backend web APIs and modern Angular for front-end web interfaces." That's one item. Similarly for others. "Qualifications:" we have bullet points? Actually it's a paragraph with multiple sentences. We can treat as a
  with each qualification as list item? The instruction: Use
  • for any list of duties/requirements/benefits. Qualifications is a list of requirements. So we should break into list items. The qualifications text: "BS in Computer Science, Engineering, or related technical field with 4+ years of software development experience (or MS with 1+ years). Proven experience building enterprise web applications using .NET Core, C#, Angular, and RESTful Web APIs within a microservices architecture. Strong proficiency in MS SQL / T-SQL development, schema design, query optimization, and working with managed database instances. Practical experience with Azure cloud components (AKS, Azure Service Bus, Blob Storage, Application Insights) and continuous integration/deployment using GitHub Actions. Strong debugging, analytical, and communication skills to resolve complex technical issues escalated from support teams and articulate designs to engineering leadership." We can split each sentence into a list item. "Additional Information" includes salary range and legal disclaimer. We already captured salary range in Pay section. The rest is boilerplate (legal disclaimer about salary may vary etc). That's still substantive? It's about salary variability; but it's more detail about pay. Could include in Pay section as prose after the range. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the disclaimer about actual salaries may vary etc. That's part of Pay. So Pay section can have

    with the range and then a

    with the disclaimer? Or combine into one

    . Probably better to keep as one

    containing both sentences. Schedule: we have hybrid position requiring 2 days/week in-office. Also location restriction: "Currently we are only considering candidates within a commutable distance to our offices in Little Rock, AR; Dallas, TX; Mentor, OH; Miamisburg, OH; and New Century, KS." That's location info, not schedule. Could be part of Schedule? Might be better to include as a separate section? There's no heading for Location. But we could include location info under Schedule or maybe under a separate "Location" but not in allowed headings. The instruction says use headings only for those listed; we should not create other headings. So we need to fold location info into a short

    or drop it. It's substantive; we should not drop. So we can include it as a

    after the Schedule section maybe, or incorporate into Schedule

    . Probably best to add a

    after Schedule that mentions location restriction. We must not include boilerplate like EEO, accommodations, identity verification, pre-employment screening. Remove those. Now construct HTML. Start with a

    for the "Why join Avery Dennison:" paragraph. Then

    About the role

    ...

    Then

    Responsibilities

    • ...
    ...
    Then

    Qualifications

    • ...
    ...
    Then

    Benefits

    • ...
    ...
    Then

    Pay

    ...

    Then

    Schedule

    ...

    Then maybe a

    for location restriction. Check that we didn't repeat job title. Now ensure we keep all specifics. Let's extract exact text. Why join Avery Dennison paragraph: "Why join Avery Dennison: We are a global materials science and digital identification solutions company with locations in over 50 countries, and approximately 35,000 employees worldwide. As a science and innovation company, we believe that diverse teams are stronger teams. We are committed to fostering a culture of curiosity and courage, where you can grow your career with a company that has innovation in its DNA. Founded on creating real-world impact to enable a better future, we strive to provide an open, collaborative culture where diversity of thought is encouraged and respected. Hear from our employees about what it's like working at Avery Dennison. Learn more at www.averydennison.com." Note there is a colon after "Why join Avery Dennison". We'll keep as is. Now About the role paragraph: "About the role: As a Software Engineer II on the storeLink engineering team, you will design, develop, and support key features for our cloud-native retail management platform. storeLink empowers grocery and drug retailers across three core operational capabilities: in-store price tag printing, Electronic Shelf Label (ESL) device management, and digital video screen display management. Operating within an Azure-hosted microservices architecture, you will work closely with dedicated feature sprint teams, our Principal Architect, and L2 Technical Support Engineers to deliver reliable, high-performance web applications and API integrations. This is a hybrid position that requires 2 days/week in-office. Currently we are only considering candidates within a commutable distance to our offices in Little Rock, AR; Dallas, TX; Mentor, OH; Miamisburg, OH; and New Century, KS." Note that the hybrid position sentence and location sentence are part of About the role paragraph. But we also need Schedule section separate. However the instruction says to use Schedule section only when posting has real specific content for it. The posting does have hybrid position requiring 2 days/week in-office. That's schedule info. The location info is separate. We could keep location info in About the role paragraph (makes sense) and then Schedule section just about the 2 days/week. But the About the role paragraph currently includes both hybrid and location. If we move the hybrid sentence to Schedule, we need to adjust About the role paragraph to remove that sentence. But we must preserve all substantive information; we can split sentences across sections. That's okay as long as we don't lose info. So we can keep About the role paragraph without the hybrid sentence, and then Schedule section with that sentence. Location sentence can stay in About the role paragraph (or we could make a separate location note but we don't have heading). Let's keep location sentence in About the role paragraph. Thus About the role paragraph: "As a Software Engineer II on the storeLink engineering team, you will design, develop, and support key features for our cloud-native retail management platform. storeLink empowers grocery and drug retailers across three core operational capabilities: in-store price tag printing, Electronic Shelf Label (ESL) device management, and digital video screen display management. Operating within an Azure-hosted microservices architecture, you will work closely with dedicated feature sprint teams, our Principal Architect, and L2 Technical Support Engineers to deliver reliable, high-performance web applications and API integrations. Currently we are only considering candidates within a commutable distance to our offices in Little Rock, AR; Dallas, TX; Mentor, OH; Miamisburg, OH; and New Century, KS." Now Schedule section: "This is a hybrid position that requires 2 days/week in-office." Now Responsibilities list items: need to extract each bullet. From text: "Key Responsibilities: Full-Stack Feature Development: Design, build, test, and maintain scalable microservices using .NET Core for backend web APIs and modern Angular for front-end web interfaces. Database & Cloud Infrastructure: Maintain and optimize MS SQL data structures, leverage Azure AI Search, and support applications hosted on Azure Kubernetes Service (AKS), Azure Service Bus, Blob Storage, Azure Front Door, and Application Insights. API Integration & Services: Integrate storeLink microservices with external systems via REST APIs, including custom rendering engines (such as UE2) for PDF and PNG media generation. CI/CD & Production Support: Manage GitHub version control, build/release pipelines using GitHub Actions, and partner with L2 support to triage and resolve escalated production issues. Quality, Compliance & Agile Methods: Implement unit/automated integration tests, adhere to internal security and SOX 404 controls, and participate in Agile code reviews and task estimation." We'll make each a

  • . Now Qualifications list items: split sentences. Sentences: 1. "BS in Computer Science, Engineering, or related technical field with 4+ years of software development experience (or MS with 1+ years)." 2. "Proven experience building enterprise web applications using .NET Core, C#, Angular, and RESTful Web APIs within a microservices architecture." 3. "Strong proficiency in MS SQL / T-SQL development, schema design, query optimization, and working with managed database instances." 4. "Practical experience with Azure cloud components (AKS, Azure Service Bus, Blob Storage, Application Insights) and continuous integration/deployment using GitHub Actions." 5. "Strong debugging, analytical, and communication skills to resolve complex technical issues escalated from support teams and articulate designs to engineering leadership." Now Benefits list items: from text: "Benefits: At Avery Dennison, some of the great benefits we provide are: Inclusive Care Program: Specially trained service team with increased knowledge and understanding of LGBTQ+ concerns to help find quality care, behavioral health professionals, and community support resources. 4