Senior Software Engineer (Golang)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, application instructions, etc. We need to parse the posting. Key info: Location: Boston, MA | Hybrid, 3 days per week in our Boston office About the role: "Build the technology behind elite sporting performance. At Catapult, we are building the future of sports performance technology, with a mission to Unleash the Potential of every athlete and team on earth. Since 2006, our technology has helped shape the world of sports performance software, science and data. Today, our solutions are used by more than 5,000 teams around the world, including organisations across the NFL, NBA, NHL, MLS, EPL, AFL, NRL, NCAA and many more. Our technology brings together wearable data, digital video and athlete information to help coaches, sports scientists, performance staff and athletes understand what is happening, make better decisions and improve performance. We are looking for a Senior Software Engineer with strong Golang experience to join our engineering team in Boston and help build the next generation of our cloud platform. This is a hands-on engineering role where you will work with Golang, distributed systems, AWS, APIs and data to build scalable services used by some of the world's leading sporting organisations. If you enjoy solving complex engineering problems, taking ownership of systems and seeing your work have a real impact, this is an opportunity to do that while working alongside a great engineering team in Boston." Then "The opportunity" section: description of responsibilities. Then "What you'll do:" list bullet points. Then "What you'll bring:" list bullet points. Then "It would be great if you also have:" list bullet points. Then "You do not need to be a sports expert..." (maybe part of qualifications). Then "What success looks like" (maybe not needed as separate section? Could be part of responsibilities or qualifications? Might be considered "Responsibilities"? But we can treat as part of responsibilities or maybe separate "Expectations"? Not required to include if not matching headings. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. About the role: introductory paragraph about company and role. Responsibilities: The "What you'll do:" list. Requirements: maybe "What you'll bring:" (mandatory) plus maybe "Strong professional experience with Golang..." etc. Qualifications: maybe "It would be great if you also have:" (nice-to-have) plus maybe "You do not need to be a sports expert..." (not a qualification). Could also include "Strong understanding of software engineering fundamentals" etc. Skills: maybe list of specific technologies: Golang, AWS, distributed systems, etc. Could be part of Requirements. But we need to avoid duplication. We can combine. We need to include Pay section: compensation range given: $112,934 to $225,868 per year, inclusive of base salary and target incentive plan, includes equity etc. Also mention benefits: generous paid leave, health/dental/vision insurance, 401(k) with match, comprehensive benefits package. Schedule: Hybrid, 3 days per week in Boston office. We must not include filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, legal, application instructions. Remove lines like "All offers of employment are subject to Catapult's positive prehire check." That's boilerplate; remove. Also "For further information about the role or hiring process, please contact the Talent Partner for this position." Remove. Also remove "We'd love to hear from you ..." maybe that's application instruction; remove. Also remove "Whether you are interested in sports or not, you will have the opportunity to build software that supports some of the world's best teams and athletes." Might be considered fluff but still substantive? It's more marketing; but we can keep if not boilerplate. However it's somewhat generic; but we can keep as part of About the role maybe. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep details like "Since 2006", "more than 5,000 teams", list of leagues, etc. We need to keep bullet points exactly as given? We can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the content but can reformat into HTML lists. We should not omit any bullet points. Must include all bullet points from "What you'll do:", "What you'll bring:", "It would be great if you also have:". Also need to include the "Why Catapult?" section? That's not a heading we have; but we could incorporate into About the role or maybe as separate section like "Why Catapult?" but not in allowed headings. Since we only allowed those headings, we should not create extra headings. We could fold that content into About the role or Responsibilities? It's about why work there; could be part of About the role. But we must not lose substantive info. So we can include that content within About the role paragraph(s). That's okay. Similarly "What success looks like" could be part of Responsibilities or maybe a separate section like "Expectations". Not in allowed headings; we could incorporate into Responsibilities or maybe into About the role. But we need to preserve details: 6 months and 12 months expectations. That's substantive. We could add a subsection under Responsibilities as a paragraph describing success metrics. Or we could create a separate section "Expectations" but not allowed. So we need to embed within existing allowed sections. Probably best to add a paragraph under Responsibilities after the bullet list, describing success expectations. Similarly "Why Catapult?" can be part of About the role. Now we need to decide which sections to include. We definitely have About the role (intro). Responsibilities (What you'll do list + success expectations). Requirements (What you'll bring mandatory). Qualifications (nice-to-have). Skills maybe we can combine with Requirements; but we have separate heading for Skills. Could we put technical skills list under Skills? The posting includes many specific technologies under Requirements and nice-to-have. We could separate: Requirements: years of experience, Golang, etc. Skills: specific technologies (AWS, containers, CI/CD, REST/GraphQL/gRPC, Postgres/MongoDB, etc). Qualifications: nice-to-have items. But we must not create thin sections; better to have few substantive sections. However we have to follow instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Skills into one section maybe "Requirements". But we have headings list; we can omit Skills if not needed. However we need to include all substantive info; we can put skills within Requirements. Similarly Qualifications could be separate section for nice-to-have. Pay and Benefits separate sections. Schedule separate. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include empty sections. Now craft HTML. We'll use

for each heading. Inside each, we can have

for prose,

• for lists. We need to ensure we don't repeat job title. Let's draft. About the role: combine introductory paragraphs plus why catapult. Paragraph 1: "Build the technology behind elite sporting performance. At Catapult, we are building the future of sports performance technology, with a mission to Unleash the Potential of every athlete and team on earth. Since 2006, our technology has helped shape the world of sports performance software, science and data. Today, our solutions are used by more than 5,000 teams around the world, including organisations across the NFL, NBA, NHL, MLS, EPL, AFL, NRL, NCAA and many more. Our technology brings together wearable data, digital video and athlete information to help coaches, sports scientists, performance staff and athletes understand what is happening, make better decisions and improve performance." Paragraph 2: "We are looking for a Senior Software Engineer with strong Golang experience to join our engineering team in Boston and help build the next generation of our cloud platform. This is a hands-on engineering role where you will work with Golang, distributed systems, AWS, APIs and data to build scalable services used by some of the world's leading sporting organisations. If you enjoy solving complex engineering problems, taking ownership of systems and seeing your work have a real impact, this is an opportunity to do that while working alongside a great engineering team in Boston." Paragraph 3 (Why Catapult): "Work on technology that has an impact: The systems you build will be used by some of the world's leading sporting organisations, helping teams understand athlete performance, monitor workload and readiness, analyse video and make better decisions. Work on interesting engineering problems: We are bringing together video, wearable data, athlete information and analytics into a platform used by thousands of teams around the world, solving challenging problems across distributed systems, cloud architecture, data, APIs, performance and reliability. Work with a great team in Boston: This role is based in our Boston office, with the team working together in person three days per week. You will work alongside an experienced and collaborative engineering team where you can share ideas, solve problems together and learn from the people around you, and also collaborate with colleagues across a global organisation spanning more than 20 countries. Grow your career: As a senior engineer, you will have the opportunity to take increasing ownership of technical decisions, contribute to architecture and help shape the direction of our platform. We encourage open communication, constructive challenge and a practical approach to continuous improvement. Whether you are passionate about sport or simply enjoy building great software, you will have the opportunity to work on technology that is used by some of the most successful teams and athletes in the world." That covers a lot. Now Responsibilities: include "What you'll do:" bullet list plus success expectations. Bullet list from posting: - Design, build and maintain scalable, reliable and maintainable services in Golang - Contribute to the architecture and technical direction of our cloud platform - Take ownership of services and features from planning and design through to production - Solve complex engineering problems across distributed systems, APIs, data and cloud infrastructure - Help drive code quality, engineering standards and best practices across the development lifecycle - Participate in technical design discussions, architecture reviews and code reviews - Contribute to our test strategy and write high-quality automated tests - Improve automation and engineering processes to support reliable and efficient delivery - Work closely with engineers and other teams to understand customer needs and develop effective technical solutions - Identify opportunities to improve our systems, processes and developer productivity - Share knowledge and contribute to the development of the wider engineering team - Take ownership of problems and outcomes while working collaboratively with colleagues across our global organisation Now success expectations (6 months and 12 months). We'll add as prose after list. "Success looks like: In 6 months, you will have a strong understanding of our platform, architecture and engineering practices and will be confidently owning one or more Go microservices, shipping production changes across backend services and contributing to areas such as our unified entitlement and licensing system, distributed data platform and authentication systems, while building strong relationships with the Boston engineering team and global colleagues. In 12 months, you will be leading the architectural design of a significant subsystem, taking a problem from initial design through to production across our Go service estate, contributing to how we evolve our federation patterns, offline-first edge architecture, data and entitlement models, as well as the APIs and services that support client applications and third-party integrations, and will be a trusted senior technical contributor delivering high-quality software, taking ownership of complex problems and helping raise the engineering capability of the wider team." Now Requirements: "What you'll bring:" bullet list. List: - Strong professional experience with Golang - 5+ years' recent experience delivering multiple scalable services into production - Experience designing, building and operating production-grade backend services