Software Engineer I (.Net)

We need to output HTML fragment with sections: About the role? The posting includes description of company, but we need to follow rules: use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if real content. We have: - About the role: maybe the "HOW YOU WILL MAKE AN IMPACT:" and "Impact of the Role" etc. Could be considered About the role. - Responsibilities: "WHAT YOU WILL DO:" list. - Requirements: maybe "QUALIFICATIONS:" includes Knowledge, Skills, Abilities and Education, Certification And Experience. - Skills: could be part of qualifications. - Benefits: "Our Benefits" list. - Pay: not present, so omit. - Schedule: not present, omit. We must not repeat job title as heading. Also no metadata like location as heading; we can fold location into a short

maybe. We need to preserve all substantive information, remove boilerplate: cookie/navigation/legal/EEO etc. At end there is EEO statement; remove. Also remove "Physical Requirements" maybe? It's substantive? It's about physical demands; maybe keep? It's not in prescribed headings; but we could include as a

under maybe "About the role"? But we should not invent sections. Could keep as a

after qualifications? The instruction: "Prefer a few substantive sections over many thin ones." We could include Physical Requirements as a

under maybe "About the role" or separate? But we only have prescribed headings; we can still include other content as

not under headings? 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." It doesn't forbid other headings, but says use those for those sections. Likely we should stick to those headings only. Other info can be in

  without heading. Thus we can have:

  About the role

  with paragraphs describing impact, etc.

  Responsibilities

  with
  of duties.

  Qualifications

  with maybe subpoints? Could split into Knowledge, Skills, Abilities, Education etc as
  or

  . Use

  for list.

  Skills

  maybe separate? But qualifications already includes skills; we could combine. But we need to avoid thin sections. Maybe combine Qualifications and Skills into one section? But we have both headings possible. The instruction: "Prefer a few substantive sections over many thin ones." So better to have one Qualifications section that includes knowledge, skills, abilities, education. So we will not create separate Skills heading. Benefits:

  Benefits

  with
  . We must not include Pay or Schedule. Location: we can include a short

  after the heading maybe before About the role: "Location: Memphis TN Varsity Spirit HQ". Not a heading. Now ensure we preserve all substantive information: company overview, commitment to safety, etc. Should we include that? It's substantive but not under headings; we could include as a

  before About the role. The instruction: "Preserve ALL substantive information". So we need to keep the company overview and safety commitment. We'll put them in

  paragraphs. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement; remove. Also "Learn more at Our Commitment to Safety - Varsity.com." maybe keep as part of safety commitment? It's a link; we can keep as plain text. Also "Physical Requirements" section: we should keep that info as substantive. It's not under headings; we can include as a

  after Qualifications maybe. Also "OUR VALUES" list: keep as

  or

  ? It's a list of values; we could make
  . But we have no heading for values; we could just put as

  with commas or

  . Since it's a list, better
  . But we need to decide if we want to add a heading? Not required; we can just output
  directly. The instruction: Use
  • for any list of duties/requirements/benefits. Values is not duties/requirements/benefits, but still a list; we could still use
    . It's okay. Now produce HTML fragment. Let's draft:

    Varsity Spirit, a Varsity Brands company, has been the leading global source for all things spirit for over 50 years, including cheerleading, dance team, performing arts and yearbook. With 5,000+ employees, they celebrate school spirit, focusing on safety, entertainment and traditional school leadership, impacting over a million athletes each year.

    Our Commitment to Safety: At Varsity Spirit, the safety and wellbeing of the young people we serve is of the utmost importance. Since inception 50 years ago, we have been – and remain – steadfastly committed to creating a safe and positive environment for participants’ physical, emotional, and social development, promoting an environment free from abuse and misconduct. Varsity has a zero tolerance for abuse in its programs, events, and associated business activities, and is committed to reporting all suspicions, allegations, and incidents of abuse in full accordance with local laws and reporting requirements. Learn more at Our Commitment to Safety - Varsity.com.

    Location: Memphis TN Varsity Spirit HQ

    About the role

    Varsity Spirit supports a portfolio of modern applications and digital services that power key parts of the spirit experience, from product configuration and ordering to delivery and customer engagement. These applications work together through scalable, API-driven integrations and shared capabilities, enabling faster innovation, improved user experiences, and more efficient business operations. The Full Stack Developer I role is an entry-level engineering position responsible for contributing to the development of these various platforms. This high-growth role applies foundational software engineering knowledge and exercises independent judgment in executing assigned work, including selecting appropriate approaches within established guidelines to build, test, and maintain software components.

    Impact of the Role:

    • Contributes to delivery of platform features and backend services that power critical business and customer experiences
    • Builds foundational capability to support scalable, cloud-based engineering environments
    • Establishes a pipeline of engineering talent aligned to Varsity Spirit’s long-term platform strategy

    Responsibilities

    • Write, test, and debug code for applications, backend services, and APIs
    • Contribute to development of features and services within established architecture and engineering standards
    • Participate in code reviews and incorporate feedback to improve code quality
    • Troubleshoot and resolve development and lower-environment issues, applying sound judgment to determine appropriate solutions
    • Collaborate with engineering, product, and QA teams to deliver functional and reliable software
    • Follow established development workflows, security practices, and engineering standards
    • Contribute to documentation and knowledge sharing to support team effectiveness
    • Continuously build understanding of platform architecture, service interactions, and system design principles
    • Develop working knowledge of platform services, system interactions, and engineering patterns to support future growth into independent ownership

    Qualifications

    Knowledge, Skills, Abilities

    • Technical Knowledge: Foundational knowledge of software engineering principles, including object-oriented programming and data structures; basic understanding of APIs, application architecture, and databases; familiarity with modern development environments and tools
    • Technical Skills: Ability to write, test, and debug code in at least one programming language (.Net preferred); foundational understanding of RESTful APIs, SQL and data handling, version control systems (Git-based tools)
    • Cognitive & Problem-Solving Abilities: Applies logical reasoning to solve defined technical problems; exercises independent judgment in selecting approaches within established guidelines; identifies issues and escalates appropriately when needed
    • Collaboration & Communication: Communicates effectively within team environments; actively participates in team collaboration and development processes; incorporates feedback to improve performance and output
    • Learning Agility: Demonstrates ability to quickly learn new technologies and tools; adapts to evolving engineering practices and environments

    Education, Certification And Experience: Bachelor’s degree in Computer Science, Engineering, or related technical discipline; or equivalent combination of education and experience. 0‑2 years of relevant experience (internships, academic projects, or early career roles).

    Benefits

    • Comprehensive Health Care Benefits
    • HSA Employer Contribution / FSA Opportunities
    • Wellbeing Program
    • 401(k) plan with company matching
    • Company paid Life, AD&D, and Short-Term Disability
    • Generous My Time Off & Paid Holidays
    • Varsity Brands Ownership Program
    • Employee Resource Groups
    • Access to Financial Coaching and member-owned Credit Union
    • St. Jude Partnership & Volunteer Opportunities
    • Employee Perks including discounts on personal apparel and equipment

    Physical Requirements: The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodation may be made to enable individuals with disabilities to perform the essential functions. Please note this job description is not designed to cover or contain a comprehensive listing of activities, duties or responsibilities required of the employee for this job.

    OUR VALUES

    • Service – We lead with heart. We champion community.
    • Passion – We love what we do. It fuels our purpose.
    • Integrity – We do what we promise. We own our actions and decisions.
    • Respect – We earn it by giving it. Because everyone deserves it.
    • Innovation – We never stop striving to be better. For ourselves and our community.
    • Transparency – We are committed to openness and honesty in everything we do.
    We must ensure no markdown fences, just HTML. Also ensure we didn't include any heading for Pay or Schedule. Good. Check for any leftover boilerplate: removed EEO, removed "Varsity Brands companies are equal opportunity employers..." etc. Also removed "Eligibility for company-sponsored benefits is determined by scheduled work hours..." maybe part of benefits? It's about benefits eligibility; could be considered part of benefits but it's generic; we could keep as a

    under Benefits? It's not a list item but could be prose. However it's somewhat boilerplate; but it's about benefits eligibility. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly EEO but it's about benefits eligibility; might be considered boilerplate but it's substantive? It's describing eligibility; maybe keep as a

    under Benefits. However we already have Benefits list; we could add a

    after list: "Eligibility for company-sponsored benefits is determined by scheduled work hours, and the terms of the applicable benefit plans. Benefit offerings and eligibility requirements may vary by position and are subject to change in accordance with plan documents and applicable law." That's not duplicated; it's explanatory. Keep. Also "Our Benefits We are committed to putting you and your families first..." we already captured. Now ensure