kamron.clark.carpenter@gmail.com

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract content from posting. We have: - About The Role: paragraph(s). We'll put under

About the role

with

content. - Key Responsibilities: list of duties. Use

• . - What Success Looks Like: maybe could be considered part of responsibilities? But we can treat as separate? The instruction: prefer few substantive sections over many thin ones. Could combine Success expectations into Responsibilities or maybe a separate "Expectations" but not listed as allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. - Required Qualifications: under Requirements or Qualifications? Both headings allowed. We need to decide. Probably "Requirements" for required qualifications, and "Qualifications" for preferred? But we have both required and preferred. Could put required under "Requirements" and preferred under "Qualifications". Or combine both under "Requirements". The instruction: prefer few substantive sections. Might combine required and preferred into one "Requirements" section. But we have also "Preferred Qualifications" separate. Could still combine. - Benefits: we have Benefits Highlights section. So include

  Benefits

  with list. - Pay: we have compensation range: $65,000 to $80,000 annually. So include

  Pay

  with

  . - Schedule: we have location and work arrangement details: hybrid days, remote options. That's schedule info. So include

  Schedule

  with

  . - Skills: maybe we could include technical skills from required qualifications? But we already have responsibilities and qualifications. Could omit Skills if not distinct. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: navigation, legal, EEO, etc. Also remove "Our Hiring Process", "Diversity, Equity & Inclusion", "The Pay Range For This Role Is ..."? Actually pay range we need to keep. The line "The Pay Range For This Role Is 65,000 - 80,000 USD per year(United States)" is duplicate of compensation earlier; we can keep one. We need to preserve all substantive information. Let's extract: About The Role paragraph: "As a .NET Developer on our Lottery Solutions team, you’ll build and maintain the reliable web-based solutions our lottery clients and the people who use their digital platforms depend on. You’ll own application modules end to end, from technical definition through development, testing and release, working alongside back-end, front-end, mobile, QA, business analysis, architecture and IT teammates to turn client needs into secure, maintainable and scalable applications. This is an individual contributor role. It’s a strong fit if you like solving practical business problems, learning from senior technical teammates, and shipping production-quality work in a collaborative agency environment. You’ll deepen your .NET expertise, strengthen your understanding of modern delivery practices, and contribute to solutions running in highly visible, regulated client environments where reliability and security really matter." Key Responsibilities list (bullet points): - Implement application modules based on provided specifications, and contribute to maintaining product quality through code reviews and self-assessment. - Analyze and estimate small technical tasks, and perform updates and maintenance on existing code. - Support nontechnical staff in understanding straightforward client requirements, and help them see what is and is not feasible. - Develop, integrate and consume APIs, and build against relational databases with an eye on performance. - Build technical expertise through work experience and training, collaborating with senior team members to deliver reliable and efficient solutions. - Work within a multidisciplinary team made up of technical and nontechnical members. - Participate in solution brainstorming and help identify the best approach to delivering against client needs and requirements. - Support DevOps and deployment work, including GitLab repositories, merge requests, CI/CD pipelines and controlled production releases. - Write and maintain technical documentation, including solution specifications, API documentation, deployment procedures and code documentation that supports long-term maintainability. - Assist with project estimation, planning and milestone tracking, providing accurate effort estimates so projects are delivered on time and within scope. - Research emerging technologies, AI-assisted development techniques and industry trends, sharing what you learn and recommending improvements to our development practices. What Success Looks Like: we could incorporate into Responsibilities or maybe a separate section but not allowed headings. Could add as a paragraph under About the role? Might be redundant. Probably we can omit as it's somewhat repetitive; but we must preserve ALL substantive information. So we need to include it somewhere. Could add a

  Expectations

  but not allowed. Could add as a

  under About the role? Might be okay to add after About the role paragraph as additional detail. The instruction: use headings only for those specific section names. It didn't forbid adding extra paragraphs without heading. So we can include the success expectations as a paragraph after About the role, maybe under same heading? But that would be mixing content under About the role heading; still okay. We'll put About the role heading, then include the About the role paragraph, then a paragraph for Success expectations (maybe combine 30-day, six-month, 12-month expectations). We'll keep them as a paragraph. Required Qualifications: list: - Experience and Education: Three or more years of hands-on development experience building digital, web, online or mobile solutions in a professional environment - Bachelor’s degree in computer science, software engineering or a related field. Equivalent professional experience is fully accepted. What matters most is demonstrated depth, judgment and growth, not the specific path that produced it. - .NET and Web Development: Strong working knowledge of C#, ASP.NET, .NET Core, MVC and the .NET Framework, with the ability to build and maintain production web applications - Experience developing, integrating and consuming APIs, including RESTful services, HTTP fundamentals and structured data formats such as JSON. - Experience with relational databases, including SQL querying, data modeling fundamentals, stored procedures and performance-aware application development - Security, Quality and Collaboration: Working knowledge of web application security fundamentals, including authentication, authorization, secure data handling and common web vulnerabilities - Experience using version control systems, preferably Git, including branching, merging, pull or merge requests, and collaborative code review workflows - Commitment to clean, maintainable, well-documented code that follows established standards, design patterns and team best practices - Working Style: Ability to stay organized, communicate trade-offs, and adapt when requirements, priorities or deadlines change. Preferred Qualifications: list: - Technical Experience working in cloud-based environments such as Azure, AWS or Google Cloud Platform, including common deployment and hosting patterns - Experience with modern front-end frameworks, especially Vue.js, and comfort collaborating with front-end developers on integrated web applications - Experience working with .NET-based CMS or DXP platforms, including implementation, customization, integration or ongoing support - Exposure to containerized application environments using Docker and/or Kubernetes - Delivery and Process Experience contributing across the software development life cycle, from discovery and technical definition through design, development, testing, release and support - Familiarity with Agile delivery practices, including sprint planning, estimation, backlog refinement, demos, retrospectives and cross-disciplinary collaboration - Experience using AI-assisted development tools responsibly to accelerate research, prototyping, debugging, documentation or code quality improvements - Industry and Environment Experience in a marketing or digital agency, or in finance, lottery, gaming or consulting - Experience working in regulated, high-visibility or transaction-oriented digital environments where reliability, security and maintainability are important We could combine required and preferred into a single "Requirements" section, but we have a lot. Could split: "Requirements" for required, "Qualifications" for preferred. That seems reasonable. Benefits: list: - Time Off: A flexible time-off policy, with most employees taking approximately four to six weeks annually. - Family Support: Twelve weeks of fully paid parental leave. - Health and Wellness: Medical, dental and vision coverage, plus telemedicine, behavioral health resources. - Lifestyle Support: Wellness and creative stipends, phone plan support and partner discounts. - Financial Benefits: A 401(k) with company contributions, student loan repayment support and college savings options. - Career paths: Defined career paths for every department, so you can see how to progress and what it takes to get there. Pay: Compensation: $65,000 to $80,000 annually, depending on experience. Schedule/Location: Location and Work Arrangement: - Local candidates are preferred for this role. - Cleveland: Employees in the Cleveland area work from the Cleveland office each Wednesday and one additional day per week based on team needs. - Cincinnati: Employees in the Cincinnati area work from the Cincinnati office each Wednesday and one additional day per week based on team needs. - Remote: Employees elsewhere in Ohio or in an approved state may work remotely. - Candidates must have an established primary residence in an approved state before an offer can be issued. We can’t issue an offer based on a planned future move without a valid address. - Employment Eligibility: Candidates must be legally authorized to work in the United States. Marcus Thomas is unable to provide employment visa sponsorship for this position now or in the future. We could include that as Schedule section. We must not include boilerplate like "Community of Practice: Digital Delivery Primary Solution Group: Lottery Solutions Reports To: Senior Back-End Development Lead Location: Cleveland or Cincinnati, Ohio (hybrid), or remote in an approved state (see below) Employment Type: Full time, regular". That's metadata; we can fold minor metadata into a short

  or drop it. The location and work arrangement we already captured. The "Reports To" and "Employment Type" maybe minor; we could drop or include in a short p. Probably drop. We need to output only HTML fragment. Let's construct:

  About the role

  As a .NET Developer on our Lottery Solutions team, you’ll build and maintain the reliable web-based solutions our lottery clients and the people who use their digital platforms depend on. You’ll own application modules end to end, from technical definition through development, testing and release, working alongside back-end, front-end, mobile, QA, business analysis, architecture and IT teammates to turn client needs into secure, maintainable and scalable applications. This is an individual contributor role. It’s a strong fit if you like solving practical business problems, learning from senior technical teammates, and shipping production-quality work in a collaborative agency environment. You’ll deepen your .NET expertise, strengthen your understanding of modern delivery practices, and contribute to solutions running in highly visible, regulated client environments where reliability and security really matter.

  Success expectations: 30‑day: Learn the lottery business domain, product ecosystem and team processes; become comfortable with the development environment and team workflows; deliver initial bug fixes or small enhancements while meeting coding and quality standards. Six‑month: Independently deliver features and enhancements of moderate complexity; demonstrate a solid understanding of the lottery platform and business requirements; collaborate effectively with Product, QA, DevOps and other engineering teams while consistently delivering high‑quality code. 12‑month: Be a fully productive and trusted member of the Lottery Solutions team; own assigned work from requirements through implementation with minimal supervision; demonstrate strong business domain knowledge and consistently deliver reliable, maintainable and high‑quality solutions; support new team members through knowledge sharing and collaboration.

  But we used which is okay but not required. Could just plain text. Better to keep as plain paragraph. Now Responsibilities:

  Responsibilities

  • Implement application modules based on provided specifications, and contribute to maintaining product quality through code reviews and self‑assessment.
  • Analyze and estimate small technical tasks, and perform updates and maintenance on existing code.
  • Support nontechnical staff in understanding straightforward client requirements