Development Manager

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have content: "Being part of the team" (maybe About the role?), "Our story" (maybe About the company?), "How you’ll contribute" (maybe Responsibilities?), "The day-to-day:" (Responsibilities), "What you’ll bring:" (Requirements/Qualifications/Skills), "What you’ll bring" includes education, experience, skills). "Total Rewards:" (Benefits). Pay: we have compensation: "$115,000 - $140,000 base salary USD and eligible for discretionary bonus plan". So we need a Pay section. Schedule: not specified. So we should not include Schedule. Also we need to include maybe "About the role" or "About the team"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose appropriate headings based on content. We have "Being part of the team" and "Our story" which are more about company/role context. Could combine into About the role? Probably "About the role" could include description of team and mission. We'll put that content under

About the role

. Then Responsibilities: from "How you’ll contribute" and "The day-to-day:" (list). We'll combine into a

• list. Requirements/Qualifications/Skills: "What you’ll bring:" includes education, experience, knowledge, abilities. Could split into Requirements (education+experience), Qualifications (knowledge), Skills (abilities). But we can also combine into one section if we want fewer sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements, Qualifications, Skills into one section? But they said use headings for those categories; we can still include them if we have content. We have content for each: education/degree (Requirements), experience (Requirements), knowledge of building design and construction processes (Qualifications), understanding of real estate finance fundamentals (Qualifications), ability to manage multiple projects (Skills), understanding of project management tools (Skills), ability to take direction (Skills), thrive in high-volume (Skills), reliable/trustworthy (Skills), previous success in team management (Skills), experience coaching (Skills). So we could have separate headings but that would be many thin sections. Better to combine into one section like "Requirements & Qualifications" but they only allow those specific headings. Could we use "Requirements" heading and put all content there? That would be acceptable as we are not violating rule: we only emit heading when posting has real specific content for it. We have content for Requirements. We could also add "Qualifications" and "Skills" but they'd be thin if we split. Better to just have one heading "Requirements" and include all. However they gave example list includes Requirements, Qualifications, Skills as separate possible headings. It's not mandatory to use all; we just must not create empty sections. So we can choose to use only Requirements heading and put all under it. Similarly Benefits: we have Total Rewards list. Pay: we have compensation. So sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to output only HTML fragment, no /. Use

  for each heading. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: EEO, etc. Also remove duplicated lines. Also remove navigation/cookie etc. Not present. We need to include all substantive info from posting. Let's extract content: Being part of the team paragraph: "Our business is a team sport that began on a field with baseballs and bats and has evolved into one of the most recognizable brands in sports and entertainment through Cubs baseball and live events. Our success is driven by our people, who work to create and inspire change in an engaging, collaborative and inclusive environment. As a team, we continue to build a culture on and off the field that delivers unforgettable experiences for one another, our fans and community. In support of that effort, we expect associates to work primarily in our office. Are you ready to be part of it?" Our story paragraph: "MARQUEE DEVELOPMENT is a full-service real estate firm that specializes in mixed-use sports and entertainment districts. We strategically manage every aspect of a sports-adjacent mixed-use development with a best-in-class ability to curate the experience for a team, fans and community. By bringing bring a sports-operational mindset to traditional real estate development, we focus on the critical integration of team operations and real estate to ensure the experience amplifies the brand of the district, while complementing and protecting the team brand to maximize long-term franchise value." How you’ll contribute paragraph: "We are looking for an experienced and versatile Development Manager to contribute to Marquee Development’s growth and help us innovate and expand our business processes. Our ideal candidate has a strong background in architectural design, urban planning, construction, real estate finance, and/or other aspects of development. A demonstrated ability to build critical relationships with our external development partners and consultants is required. They will be expected to coordinate with external development partners and consultants to achieve critical project execution. If you are passionate about driving results, have an entrepreneurial spirit, and love the rewarding challenge of turning concept into built reality, we want to hear from you." The day-to-day: list of duties (many bullet-like sentences). We need to turn each into

  • . Let's extract each sentence separated by line breaks? The posting shows each duty separated by line breaks but not bullet. We'll treat each line as a duty. List: - Coordinate and facilitate external design activities, directing architects, engineers, general contractors, and related subconsultants - Manage design and construction schedule and status for an assigned development, coordinating closely with ownership and other project team members to ensure critical project execution - Work with sub-contractors and assist in drawing and specification preparation, as well as review pricing and consultant contracts. Review working drawings. - Lead the development of detailed project budgets and schedules - Monitor and review contractors’ work as it relates to budget, schedule, and owner’s program - Support project executive and project manager in managing bid process and executing contracts - Assist owner and/or tenants in space planning, budget preparation, material selection, cost estimating, construction contracts, and cost monitoring - Prepare construction updates for the development group. Prepare and monitor cost estimates, budget updates, change order reports - Maintain and monitor the progress of punch lists - Control project documentation and historical data regarding construction - Assist in the development of project deliverables, research, and collateral - Work in concert with project managers to organize and monitor project status, schedule, and deliverables - Demonstrate commitment to stakeholder needs and on-time project delivery - Report project outcomes and/or risks to the appropriate management channels as needed - Communicate clearly and effectively with project stakeholders and team members - Complete necessary administrative tasks, such as data gathering, email, PowerPoint, and project organization Note some sentences have two sentences combined; we can keep as one
  • each. What you’ll bring: list: - Undergraduate degree in urban planning, architecture, construction, engineering, real estate, and/or business. MBA or MRED a plus - Highly organized, with minimum five years of experience in oversight of development projects within architecture, urban planning, construction management, or a related field - Demonstrated knowledge of building design and construction processes - General understanding of real estate finance fundamentals including, hard and soft cost budgeting, components of revenue/leasing, return on cost, and levered/unlevered internal rate of return - Ability to manage multiple projects at once - Thorough understanding of project management tools - Ability to take direction and execute tasks and projects accordingly - Ability to thrive in a high-volume, deadline-driven work environment - Reliable, trustworthy, and committed to the team’s success - Previous success in team management and project delivery - Experience coaching and educating project teams to strengthen team members’ capabilities and skill sets Total Rewards: list: - On-site parking - Transit benefits - Paid time off: Personal, Sick, Vacation Time, Office Holidays & Winter Break - Flexible work arrangement - Casual work attire environment - Complimentary Meal & beverage plan - Access to campus wide Wrigley Field events & pre-sales - 401K Plan Employee Contribution & Employer Match - Benefit Plans: Medical, Dental, Vision & Life Insurance - Health & Wellness engagement & programming - Variety of associate special events, volunteer opportunities and partnership discounts - Monthly allotment for internal rewards & recognition platform - Complimentary access to EV charging stations Pay: "$115,000 - $140,000 base salary USD and eligible for discretionary bonus plan" We also have location: Chicago, IL. Could be included in About the role? Not required but we can include as prose maybe. The instruction: do not repeat job title as heading. We can include location in a short

    maybe under About the role or separate? Not required to have a section for location. We'll include it in About the role paragraph maybe after the story. We must not include boilerplate: EEO, equal opportunity, etc. Remove. Now construct HTML. We'll have:

    About the role

    Being part of the team: ...

    Our story: ...

    Location: Chicago, IL

    But we need to preserve all substantive info; we can combine being part of the team and our story into one or two paragraphs. We'll keep two

    elements. Then Responsibilities:

    Responsibilities

    • ...
    ...
    Then Requirements:

    Requirements

    • ...
    ...
    Then Benefits:

    Benefits

    • ...
    ...
    Then Pay:

    Pay

    $115,000 - $140,000 base salary USD and eligible for discretionary bonus plan

    We should not include Schedule. Check for any duplicated lines: none. Make sure we didn't miss any substantive info: The "How you’ll contribute" paragraph we haven't used yet. It contains description of ideal candidate etc. That could be part of Responsibilities or Requirements? It's more about role expectations. Could be included under About the role or Responsibilities. Since we already have About the role with team and story, we could add How you’ll contribute as another paragraph under About the role. That would preserve that info. Thus About the role will have three paragraphs: Being part of the team, Our story, How you’ll contribute. Let's extract How you’ll contribute paragraph exactly: "We are looking for an experienced and versatile Development Manager to contribute to Marquee Development’s growth and help us innovate and expand our business processes. Our ideal candidate has a strong background in architectural design, urban planning, construction, real estate finance, and/or other aspects of development. A demonstrated ability to build critical relationships with our external development partners and consultants is required. They will be expected to coordinate with external development partners and consultants to achieve critical project execution. If you are passionate about driving results, have an entrepreneurial spirit, and love the rewarding challenge of turning concept into built reality, we want to hear from you." We'll include that as a

    . Now ensure we didn't miss any other info: The "FLSA STATUS: Exempt" maybe not needed; it's metadata but could be included in About the role as short line? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short <