Program Coordinator, Entrepreneurship Education & Programs

We need to produce 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 as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, application instructions, etc. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay Range $65,628.00 - $68,000.00 Annual Rate. So we can include Pay section with that. Benefits: there is a "University Benefits" section describing benefits. So we can include Benefits section with that content. Schedule: posting mentions "This position is hybrid-eligible depending on business needs and evaluation of several factors. Student or alumni facing roles will require more in-person work some weeks than others." That's schedule info (hybrid eligibility). So we can include Schedule section with that. Now we need sections: About the role (maybe overview), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. The posting includes: University Overview (general about Penn). Then Wharton School Overview. Then Program Coordinator responsibilities description. Then Required Qualifications (list). Then Preferred Qualifications (list). Then Job Location, Department/School, Pay Range, etc. Then Benefits description. We need to extract substantive info and place into appropriate sections. We must not repeat job title as heading. So no heading for "Program Coordinator, Entrepreneurship Education & Programs". We'll just have sections. We need to 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 keep details like specific duties, qualifications, etc. We must not omit any detail. However we can combine similar items? The instruction: "Prefer a few substantive sections over many thin ones." But we must preserve all substantive information; we can group items under appropriate headings. We need to decide what goes into each section. About the role: Could include overview of the role, maybe from Wharton School Overview and role summary. Could include description of what the role does generally. Responsibilities: list of duties (day-to-day execution, develop work plans, coordinate engagement, supervise student leadership teams, serve as primary operational contact, support financial administration, maintain records, collect/analyze/report data, support donor stewardship, assess performance, implement improvements, support portfolio-wide reporting, coordinate shared resources, support coordination between Programming and Marketing, serve as central point for marketing requests, communicate priorities, facilitate collaboration, provide hands-on support for routine program marketing needs, coordinate with Operations, IT, other partners, contribute to development of shared processes, etc.) Requirements: Could be the Required Qualifications list (bullet points). Qualifications: maybe Preferred Qualifications? Or we could treat Required Qualifications as Requirements, and Preferred Qualifications as Qualifications. Skills: maybe combine skills from both? But we have separate sections for Skills. Could list skills like communication, organizational, proficiency with MS Office, etc. However those are also in Required Qualifications. Might be redundant. But we need to follow instruction: Use sections only when posting has real specific content for it. The posting includes Required Qualifications (list) and Preferred Qualifications (list). It also includes skills like "Strong written, verbal, and interpersonal communication skills", "Strong organizational and administrative skills", "Proficiency with Microsoft Office". Those are part of Required Qualifications. So we could put those under Skills section. But we also have Requirements section for required qualifications (education/experience). Qualifications section for preferred qualifications? Might be okay. But we must not create thin sections. Let's think: We could have: - About the role (overview) - Responsibilities (duties) - Requirements (required qualifications: education/experience, interest, ability to coordinate multiple programs, experience coordinating programs, experience coordinating program marketing, ability to build relationships, experience collecting/maintaining/analyzing/reporting data, strong communication skills, strong organizational skills, proficiency with MS Office and tech) - Qualifications (preferred qualifications: experience in entrepreneurship, experience mentoring student employees, experience supporting program assessment, commitment to exceptional service, experience monitoring budgets, experience using technology to coordinate programs) - Skills (maybe we could merge some but we already have communication/organizational/tech skills in Requirements; maybe we can keep Skills separate for those specific skill items: communication, organizational, proficiency with MS Office, etc. But that would duplicate content. Better to incorporate those skill items into Requirements or Qualifications. Since we have both Required and Preferred qualifications, we can put skill items under Requirements (as they are required). Then Qualifications for preferred qualifications. Then we might not need a separate Skills section. However the instruction says we can include Skills section if there is real specific content. The posting does mention skills explicitly, but they are already in Required Qualifications. We could still create a Skills section pulling out those skill statements, but that would be duplicating content, which might be okay as long as we preserve all info (not lose any). Duplication is not prohibited, but we should avoid unnecessary repetition? Not explicitly prohibited. However we should aim to preserve all substantive information; duplication is okay as long as we don't lose info. But we might want to avoid redundancy to keep concise. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe better to not create a Skills section if its content is already covered elsewhere. But we need to decide. We also need Benefits section: include the benefits description. Pay section: include pay range. Schedule section: include hybrid eligibility statement. Now we need to ensure we don't include boilerplate like EEO, legal, application instructions, etc. So we must remove Equal Opportunity Statement, Special Requirements background checks, etc. Also remove "A cover letter is preferred." That's application instruction; remove. Also remove "Job Location - City, State Philadelphia, Pennsylvania Department / School Wharton School" maybe we can keep location as part of About the role? But location is not a heading; we can include it in a paragraph maybe under About the role or as a separate short p. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Location is minor metadata; we can fold into a short p. Probably include location in About the role paragraph. Now we need to output only HTML fragment, no /, no markdown. Let's draft. First, About the role: combine University Overview, Wharton School Overview, role summary. We need to preserve all substantive information: So we need to include details about Penn being largest private employer, Ivy League, top 10, 12 schools, interdisciplinary approach, Forbes award, working environment, urban campus, Philadelphia attractions, competitive benefits package (but that's also in Benefits section). We might mention benefits in About the role? But we have separate Benefits section; we can still mention but maybe we should not duplicate. However we need to preserve all substantive information; if we mention benefits in About the role and also in Benefits section, we are preserving but duplicating. That's okay. But we might want to avoid duplication to keep concise. However the instruction says preserve ALL substantive information; does not forbid duplication. It says do NOT invent or summarize away detail. Duplication is not inventing or summarizing away; it's repeating. It's allowed but maybe not ideal. However we can choose to include location and maybe brief overview without repeating benefits. Let's include in About the role: University of Penn overview, Wharton School overview, role purpose. We'll write a paragraph(s). Use

  for prose. Now Responsibilities: we need to list duties as

  • . We'll extract each duty from the description. Let's list them: - Responsible for the day-to-day execution of assigned educational programs and provides operational coordination that strengthens the effectiveness of Venture Lab's Philadelphia-based programming portfolio. - Supports assigned Philadelphia-based programs supporting students and engaging alumni, and will be the primary Coordinator to assume responsibility for new Philadelphia-based programs, supporting the successful implementation, assessment, and continuous improvement of strategically important co-curricular initiatives. - Following established processes for assigned programs, the Program Coordinator develops annual work plans and timelines aligned with program goals. - Coordinates student and stakeholder engagement. - Supervises student leadership teams. - Serves as the primary operational contact for students, alumni, faculty, reviewers, and external partners. - Supports program financial administration, including expense tracking, policy-aligned budget stewardship, and coordinating with Finance & Administration. - Maintains program records and CRM data integrity. - Collects, analyzes, and reports program data and key performance indicators. - Supports donor stewardship through data and participant materials collection, and preparing reports. - Assesses program performance and recommends improvements. - Implements approved operational improvements that enhance program quality, participant experience, and educational outcomes. - In addition to assigned program responsibilities, the Program Coordinator strengthens the operational capacity and visibility of Venture Lab's Philadelphia-based programming portfolio by supporting portfolio-wide reporting and data management. - Coordinating shared operational resources. - Supporting coordination between Programming and Marketing. - Supporting the Senior Director, the Coordinator serves as a central point of coordination for program marketing requests, activities, timelines, and routine communications. - Communicates program priorities and audience needs. - Facilitates effective collaboration. - Provides hands-on support for routine program marketing needs as appropriate. - Coordinates with Operations, IT, and other functional partners. - Contributes to the development and improvement of shared processes, organizational initiatives, and special projects that improve the effectiveness and consistency of Venture Lab's Philadelphia-based programming. That's a lot; we need to keep all. We'll put each as
  • . Now Requirements: Required Qualifications list. Let's extract each bullet from Required Qualifications: - Bachelor's degree and 3-5 years in higher education, non-profit, or a similar environment with progressively responsible professional experience in program coordination, program administration, project coordination, or a related field, or an equivalent combination of education and experience. - Interest in entrepreneurship and innovation and demonstrated ability to quickly develop knowledge of new subject areas, programs, and stakeholder communities. - Demonstrated ability to independently coordinate multiple programs, projects, and priorities, manage competing deadlines, exercise sound judgment, troubleshoot routine issues, maintain strong attention to detail, and consistently follow through on deliverables in a fast-paced environment. - Experience coordinating programs, projects, events, or initiatives involving multiple stakeholders, including managing timelines, logistics, communications, materials, scheduling, and follow-up to support successful execution. - Experience coordinating program marketing, communications, or audience engagement activities, such as email communications, website content, newsletters, event promotion, or promotional materials; familiarity with marketing principles and best practices and ability to work effectively with marketing and communications partners. - Demonstrated ability to build and maintain collaborative working relationships with students, faculty, staff, alumni, volunteers, external partners, and other stakeholders and to coordinate activities and information across multiple departments or functional areas. - Experience collecting, maintaining, analyzing, and reporting program and operational data, including tracking participation, outcomes, or other key program metrics; maintaining accurate records and documentation; and using information to support program assessment, planning, and continuous improvement. - Strong written, verbal, and interpersonal communication skills, including the ability to independently prepare clear and professional correspondence, reports, presentations, program materials, and stakeholder communications for a variety of audiences. - Strong organizational and administrative skills, with demonstrated ability to establish and maintain effective processes, documentation, calendars, and workflows that support efficient program operations. - Proficiency with Microsoft Office and experience using or learning enterprise technology platforms, databases, CRM systems, event or project management tools, and other business applications used to support program administration and operations. We'll put each as
  • under Requirements. Now Qualifications: Preferred Qualifications list. Extract: - Experience working in entrepreneurship, innovation, venture capital, startup ecosystems, experiential education, or a similarly dynamic participant-focused environment. - Experience providing day-to-day guidance, mentorship, or coordination to