Sr. P2P Engineer

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must not create sections with filler like "commensurate with experience". Must include Pay and Schedule only if posting actually states them. Pay: we have "Competitive salary of $111,000 - $142,000/annual". So Pay section can be included. Schedule: not explicitly stated; maybe "Flexible work arrangement in a fully remote working environment" but schedule not given. So we should not include Schedule unless there is explicit schedule info. Benefits: we have many benefits listed: Health, dental, vision and a retirement plan with a 6% employer match, Unlimited Paid Time Off Plan, Flexible work arrangement in a fully remote working environment, Bi-weekly work from home stipend, Parental leave, Tuition Reimbursement, A culture of learning and development, and so much more! Also remote work environment details. So Benefits section. We need sections: About the role (maybe a brief description of role). Responsibilities (list of duties). Requirements (maybe education and experience). Qualifications (maybe similar). Skills (maybe technical skills). But we must avoid duplication. The posting includes many bullet-like sentences. We need to parse. We need to output only HTML fragment, no /, no markdown fences. We must use

for section headings. Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from posting, but we can group them logically. We must remove boilerplate: "Brief Description The physical location for the candidate selected must be within the contiguous United States WHO WE ARE! Susan G. Komen brings a 100% virtual working environment, and you can work anywhere within the U.S. We are a force united by a promise to end breast cancer forever..." etc. Also "SORRY, NO AGENCIES" etc. Also EEO statements. Also "Komen provides a remote and/or home-based working environment for all active employees." etc. Also "Komen defines remote..." etc. Also "Susan G. Komen is fair and equal..." etc. Also "Additionally, we embrace diverse teams..." etc. Also "SORRY, NO AGENCIES". Also "The physical location for the candidate selected must remain within the contiguous United States. In the event a move is expected to occur by the candidate selected, it must be approved by Komen's HR team prior to the move." This is location requirement, maybe we can include in About the role or Requirements? It's a requirement: location within contiguous US. We should preserve that info. We need to avoid duplication: there are repeated lines like "At least seven years of relevant experience with JavaScript/CSS, databases, and data modelling." appears twice. We should include once. We need to decide sections. Potential sections: - About the role: maybe a brief overview: "Senior Peer-to-Peer Engineer role: leads cloud native applications and integrations, manages platforms powering community-based experiential programs (3-Day, Race For The Cure, MORE THAN PINK Walk, DIY, BigWigs, Pink Tie Guys). Works with product managers, etc." This is prose. - Responsibilities: list of duties: lead both cloud native applications and integrations, requirements gathering, architecture, infrastructure, data modeling, development, full scale testing, maintenance; lead and collaborate on projects with other dev and technical resources, product managers, project managers, business SMEs; manage all P2P platform integrations and data flows; serve as technical & architectural thought leader; collaborate w/ Product Management & business groups to develop technology roadmap; design, plan, execute P2P platform enhancements; design, plan, execute implementation and use of P2P platforms to support experiential programs (including data model, registration workflow, event-specific pages, payment integrations, constituent management and communication systems); ensure stakeholders kept abreast; own P2P platform integrations (with web, CRM, email, BI, other reporting); understand and own data models, define and ensure adherence to data hygiene rules; develop, execute, maintain systems for data cleansing, data loads, data syncing, report preparation and list generation, data and gift entry and relationship management; create customized reports and dashboards; serve as primary organizational contact to troubleshoot customer support issues with P2P platforms and connected third-party apps; design, develop, deploy data storage and data connectors (database & table schema, stored procedures, SQL jobs); design, develop, deploy integration connectors with various homegrown & 3rd party on-prem and cloud-based solutions; manage projects from inception to implementation and beyond; develop, maintain, ensure adherence of SDLC; design, develop, deploy front-end (HTML, JavaScript, Angular) and back-end modules and integration connectors; report to senior management and business project management on P2P platform’s design, development, testing, and deployment processes; budget management, project prioritization, research, and recommendation of new systems/software products and services; oversee day-to-day activities and operations for the P2P platform; other duties as assigned. That's a lot; we can bullet them. - Requirements: maybe education and experience: Bachelor’s degree in Computer Science, Information Technology or Engineering or other STEM degree, or equivalent professional software engineer experience and expertise in information systems, business administration or related discipline. At least 7 years of hands-on technical experience P2P Platforms (Blackbaud’s Luminate Online, Donor Drive, Funraisin, etc.), and relevant experience with JavaScript/CSS, databases, and data modelling. Strong working experience in ETL, experience working with dynamic content using session variables. Ability and passion to debug solve problems collaboratively with a small team, but also be able to execute independently and make strong recommendations. Requires strong ability to listen and synthesize, develop frameworks, and create clear and compelling project planning, communication, and presentation materials including business cases, teamwork plans, implementation roadmaps, etc. Proven track record of managing P2P Fundraising platforms. Strong experience with Microsoft SQL Server and working experience with No-SQL databases. Experience working with JIRA. Experience troubleshooting and resolving database integrity, integration, and performance issues. Ability to lead, prioritize, and multi-task in a fast-paced agile environment with high standards and tight deadlines. Ability to translate business requirements into technical deliverables. Detail-oriented with strong planning skills, good judgment, and consistent follow through. Highly organized, responsible, and attentive to timelines and details. Strong communication skills, fluent in both verbal and written English with the ability to communicate complex topics in simplified terms. Ability to self-manage and work in a fully remote environment. Excellent project management, meeting management, and organizational skills required. Excellent analytical and problem-solving skills. Experience with WordPress and Asana are a plus. Personal qualities like integrity, credibility, and commitment to Susan G Komen’s mission. Physical location must be within the contiguous United States; any move must be approved by HR. - Qualifications: maybe overlapping with Requirements; but we can treat Requirements as qualifications. However we need to avoid duplication. Could combine Requirements and Qualifications into one section? But the instruction says use headings only when posting has real specific content for it. We could have both Requirements and Qualifications if they have distinct content. The posting lumps education/experience under "What You Will Bring To The Table" and then later "We know you will have and be able to..." which is basically qualifications. Could treat "What You Will Bring To The Table" as Responsibilities? Actually that section lists responsibilities. Then "We know you will have and be able to..." is qualifications. Then "We would love if you also have and are able to..." is additional qualifications/skills. Then "So, what’s in it for you?" is benefits. Then pay. Then remote work description. Thus we can have sections: - About the role (maybe a brief summary from "Brief Description" and "WHO WE ARE!" but we need to avoid boilerplate. Could summarize: "Senior Peer-to-Peer Engineer role within Susan G. Komen's IT team, focusing on P2P platforms supporting community-based experiential programs." That's okay. - Responsibilities: from "What you will be doing in the role..." and "What You Will Bring To The Table" (the bullet list). We'll combine. - Qualifications: from "We know you will have and be able to..." and "We would love if you also have and are able to..." plus location requirement. - Skills: maybe we can extract technical skills: JavaScript/CSS, databases, data modelling, ETL, session variables, Microsoft SQL Server, No-SQL, JIRA, WordPress, Asana, front-end (HTML, JavaScript, Angular), back-end, SDLC, etc. But we might avoid duplication; maybe we can put skills under Qualifications. However we need to include a Skills section only if there is real specific content. The posting does list many skills; we could create a Skills section enumerating them. But we must avoid duplication with Qualifications. Could treat Qualifications as education/experience, and Skills as technical abilities. That seems reasonable. - Benefits: list of benefits. - Pay: salary range. - Schedule: not present; skip. We must not include sections with filler like "commensurate with experience". Not present. Now we need to ensure we preserve all substantive information. Let's extract all substantive info from posting, removing boilerplate. Let's copy the posting and manually extract. Original text: "Brief Description The physical location for the candidate selected must be within the contiguous United States WHO WE ARE! Susan G. Komen brings a 100% virtual working environment, and you can work anywhere within the U.S. We are a force united by a promise to end breast cancer forever. For over 40 years, we've led the way funding groundbreaking research, community health initiatives and advocacy programs in local communities across the U.S. Susan G. Komen is the ONLY organization that addresses breast cancer on multiple fronts such as research, community health, global outreach, and public policy initiatives to make the biggest impact against this disease. Komen strives to have a culture of passionate, growth-minded professionals who thrive in a team environment and work collaboratively to inspire greatness in others! We take an ongoing approach to ensure open communication from all levels throughout the organization. It’s encouraged to give and receive feedback to ensure two-way accountability with a focus on continual improvement both personally and professionally! What you will be doing in the role of a Senior Peer-to-Peer Engineer Komen’s IT team seeks a Senior Peer to Peer Engineer to leverage a variety of business solutions, across our organization, to acquire, engage, and retain fundraisers to support our mission. Komen runs a variety of community-based experiential programs including the 3-Day, Race For The Cure, MORE THAN PINK Walk, DIY, BigWigs, and Pink Tie Guys to raise funds for Komen’s mission. This resource will lead both cloud native applications and integrations, including requirements gathering, architecture, infrastructure, data modeling, development, full scale testing, and maintenance. The Senior Peer to Peer Engineer will play an important hands-on role in managing the platforms that power these programs. This role will both lead and collaborate on projects with other development and technical resources, product managers, project managers, business subject matter experts, and others to design, develop, deploy, enhance, maintain integration assets and their ancillary components. Interfacing with the Product Manager and other resources as the technical resources, this candidate will be responsible for managing all the Peer-to-Peer (P2P) platform integrations and data flows. The candidate must have a strong attention to detail and serve as both a leader and team player fostering a constructive attitude towards delivering business solutions. The ideal candidate will be able to handle projects from conception to finished product and