Engineering Manager, Transfer Explorer

We need to output HTML fragment with sections: About the role? The posting includes mission description at top, then "The Role" paragraph. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should strip out things like "Work Authorization and Sponsorship", "Compensation And Benefits", "Work for ITHAKA", "Apply Now", etc unless they contain specific content for sections like Benefits, Pay, etc. We need to preserve substantive info. Let's parse content: Mission paragraph: "ITHAKA’s mission is to expand access to knowledge and education around the world. Our services — JSTOR, Portico, and Ithaka S+R — enable people everywhere to learn, to grow, and to overcome barriers to education. In carrying out our mission, as employees we feel a deep responsibility to members of our community and to each other, and we are committed to building and sustaining a culture where everyone can thrive." That's about the organization; could be "About the role"? Actually "About the role" heading is for description of role. The mission is more about company. Could be placed under "About the role"? But we have a separate "About the role" section maybe we can put mission and role description there. The posting includes "The Role ITHAKA Labs is seeking an Engineering Manager for its Transfer Explorer team." Then description of Transfer Explorer, etc. So we can combine mission and role description under About the role. Responsibilities: bullet list under "Key responsibilities include:" with subpoints: Team supervision, Technical leadership, Vendor and partner management, Project leadership. Each has description. Experience And Skills Required: list of required experience and skills (10+ years..., 3+ years..., etc). Also "Preferred Experience working with data from higher educational institutions..." That's preferred, could be under Skills or Qualifications. Work Authorization and Sponsorship: statement about not considering candidates who require immigration sponsorship. That's a requirement; could be under Qualifications or Requirements. But we need to decide sections. Compensation And Benefits: salary range $138,000 to $173,000 per year, plus benefits list. So we have Pay and Benefits sections. Work for ITHAKA: values etc. Could be omitted as boilerplate? It's about culture; maybe not needed. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Work for ITHAKA" section is not exactly boilerplate but could be considered fluff. Might be okay to keep as part of About the role? But we need to avoid filler. It's somewhat generic but still substantive about culture. Might keep as part of About the role. Apply Now etc: application instructions, we should remove. Thus sections we will include: - About the role (contains mission + role description) - Responsibilities (list) - Requirements (maybe combine required experience and skills, plus work authorization) - Qualifications (maybe preferred experience) - Skills (maybe list of skills like collaboration, communication, agile, etc) - Benefits (list of benefits) - Pay (salary range) - Schedule? Not mentioned; no schedule info, so omit. We must not create sections with filler like "commensurate with experience". We have specific salary range, so Pay section is valid. Benefits: we have specific list: medical, dental, vision plans, employer-paid 10% retirement contribution, paid parental and caregiver leave, 22 days of paid time off, 11 paid holidays, up to 12 paid sick days, wellness benefits, and more. That's specific enough. Now we need to format using

for each section heading, then content:

for prose,

• for lists. We must not include markdown fences. Let's craft. About the role: combine mission paragraph and role description. Mission paragraph: "ITHAKA’s mission is to expand access to knowledge and education around the world. Our services — JSTOR, Portico, and Ithaka S+R — enable people everywhere to learn, to grow, and to overcome barriers to education. In carrying out our mission, as employees we feel a deep responsibility to members of our community and to each other, and we are committed to building and sustaining a culture where everyone can thrive." Role description: "ITHAKA Labs is seeking an Engineering Manager for its Transfer Explorer team. Transfer Explorer is a growing platform which aims to make it easy for students, school administrators, and advisors to see how earned credits and prior learning experiences will transfer and count toward a degree at a new institution. Building on a concept initially piloted at the City University of New York, the team has created a national version of the tool that strives to help students across multiple states. Transfer Explorer is managed as a startup within the ITHAKA Labs team, whose mission is to discover opportunities, design solutions, and incubate and scale services that change people’s lives through learning. The Engineering Manager will direct the technical aspects of the Transfer Explorer effort, ensuring that the platform provides the best possible experience for data providers and student users alike, and that the engineering team is empowered and productive. As one of the leaders of the Transfer Explorer team, the Engineering Manager will play an active role in scaling this startup towards impact and sustainability." We can combine into a few paragraphs. Responsibilities: list items: - Team supervision: Manage a talented and growing team of engineers, including goal setting and review, time and expense management, mentorship, and, as needed, staff development, performance management and recruitment of new staff. Set the team up for success as they collaborate with a multifunctional team of designers, researchers, and product and project managers. - Technical leadership: Create the conditions needed for a dynamic and creative team of engineers to deliver a Transfer Explorer platform that features scalable and sustainable data processing pipelines and best-in-class user experience for students and administrators, all with security and observability in mind. - Vendor and partner management: Own the relationships with multiple technical vendors, including our relationship with data integration partners DXtera, managing contracts, deliverables, and integration with the team. Work with project leadership to explore and cultivate partnerships and collaborations that enhance Transfer Explorer’s position in the community. - Project leadership: Participate actively in Transfer Explorer and ITHAKA Labs leadership teams, conducting business and contingency planning, roadmapping, contributing to grant application and management, and exploring new partnerships. We can keep each as
• with the description. Requirements: required experience and skills: - 10+ years experience developing and managing web-based software applications, including experience with cloud computing environments (such as AWS) - 3+ years experience and a proven affinity for managing and developing software engineers - Demonstrated ability to create technology driven solutions that are both innovative and feasible - Experience scaling solutions from prototype to scalable, sustainable infrastructure, and an understanding of when and how to invest varying levels of resilience and structure - Experience using agile development approaches: for example, lean-startup and design-thinking inspired methods incorporating short product development, business-hypothesis-driven experimentation, iterative product releases, and validated learning - Experience developing and architecting software that spans multiple components, including data pipelines - Excellent collaboration and communication skills - Work Authorization: ITHAKA is not currently considering candidates who require any type of immigration sponsorship (additional work authorization or permanent work authorization) to work in the United States. We could put work authorization under Requirements as well. Qualifications: preferred experience: - Preferred Experience working with data from higher educational institutions, including student information systems, degree audit systems, transfer articulation, or student records operations Skills: maybe we can list specific skills like collaboration, communication, agile, etc but those are already in requirements. Could combine. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section "Requirements" that includes both required and preferred. Or we could have separate sections if they have substantive content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we have About the role, Responsibilities, Requirements (including required and preferred), Benefits, Pay. That's 5 sections. We need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can omit sections lacking content. So we can have About the role, Responsibilities, Requirements, Benefits, Pay. We could also include Qualifications if we separate preferred experience. But to avoid many thin sections, we could put preferred experience under Requirements as well. So we omit Qualifications and Skills. Thus final HTML:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  The starting salary for this position ranges from $138,000 to $173,000 per year. Starting pay may vary with job-related knowledge, skills, and experience.

  We need to ensure we preserve all substantive information. Let's verify we didn't miss any important details: - Mission paragraph included. - Role description included. - Responsibilities covered all four bullet points. - Requirements: we included all required experience/skills plus work authorization. - Preferred experience: we need to include that somewhere. If we put under Requirements, we need to include it. So add a bullet: "Preferred experience working with data from higher educational institutions, including student information systems, degree audit systems, transfer articulation, or student records operations." - Benefits: we included list. - Pay: included salary range. - No schedule. Check for any other substantive info: "At ITHAKA we believe in openness and fair pay..." we captured salary range. Also "At present, our total compensation package for benefits-eligible employees includes medical, dental, and vision plans, an employer-paid 10% retirement contribution, paid parental and caregiver leave, 22 days of paid time off, 11 paid holidays, up to 12 paid sick days, wellness benefits, and more." That's benefits. Also "Please note that ITHAKA, at its discretion, may make changes to its benefits programs from time to time." That's a note; could be included as a sentence in benefits. Also "We are committed to our organizational values of belonging, evidence, speed, teamwork, and trust." That's culture; maybe we could include in About the role as part of mission? Could add a sentence. Also "We take seriously the need for everyone to feel welcome. Belonging is one of our core values, and it shows in our vibrant culture. People from a wide range of backgrounds work at ITHAKA, and we believe that unique perspectives help us realize new insights and build better solutions. We want to work with people who are passionate about ideas like these and who wish to contribute their perspectives and talents to ITHAKA’s mission. We enthusiastically welcome applications from people of all backgrounds and credentials. We want to hear your story and include your perspective in the transformative work we aim to do." This is more about inclusion; could be considered boilerplate EEO? It's about values, but might be considered fluff. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is about belonging and inclusion; could be considered EEO-related. Safer to remove. Also "Learn more about Working at ITHAKA." and "Apply Now" etc are application instructions, remove. Also "Although ITHAKA has physical offices in New York and Ann Arbor, Michigan, our employees are distributed across the continental United States. At this time, we’re not considering candidates who are unable to work and reside in the continental U.S." That's a location requirement; could