Development Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove application instructions (none). Keep all substantive info. We need to parse the posting. Key sections: - Overview: description of role. Could be "About the role" heading. - Essential Duties & Responsibilities: list of duties -> Responsibilities. - Knowledge & Skills Required: list of skills -> Skills. - Preferred Education And Experience: education and experience -> Qualifications (maybe also Requirements). Could split: Requirements (maybe required education/experience) and Qualifications (preferred). But we can combine. - Salary range: Pay. - Benefits: list of benefits. - Schedule: Not explicitly mentioned. There's "Maintain regular attendance during normal business hours, with on-site presence at the office and project sites as required." That's schedule info: regular business hours, on-site presence. Could be considered schedule. But we need to only include Schedule if posting actually states them. It does mention regular attendance during normal business hours, on-site presence as required. That's schedule info. So we can include Schedule section with that. - About the role: we have overview paragraph(s). Could also include the introductory paragraph about Cumming Group etc. That's about the role/company. We'll put under About the role. We must not include filler like "commensurate with experience". Not present. We need to use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we must strip the EEO paragraph and the benefits list? Wait benefits list is substantive; we keep it. The EEO paragraph is boilerplate; remove. Also remove the line about "Cumming Group reserves the right to pay more or less than the posted range..." maybe that's part of Pay section? It's about salary range; we can keep as part of Pay description. It's not boilerplate; it's about salary. Keep. Also remove the line about "Cumming Group is committed to providing Equal Employment Opportunity..." that's EEO; remove. Also remove the line about "All such decisions are based on (1) individual merit..." etc. That's EEO; remove. Also remove the line about "To this end, Cumming Group complies with all provisions..." etc. Remove. Also remove the line about "In addition to base salary, Cumming Group offers a comprehensive benefits package including:" then list benefits. Keep benefits list. Now we need to format. Let's extract content. About the role: The introductory paragraphs before "Overview". Let's capture: "At Cumming Group, you will work on some of the world's most exciting projects in a dynamic environment where your success is measured by the impact you make. We are one of the fastest-growing project and cost management consultancies in the United States, as reflected in our top 10 rankings in ENR. With over 60 offices globally, an extremely diverse project portfolio, and double-digit year-over-year revenue growth, the opportunities to make your mark are limitless! This position is with Seneca Group, a Cumming Group affiliate, who delivers top-tier real estate advisory and development management services on projects ranging from 10,000 to over 1 million square feet across corporate office, education, luxury residential, civic and cultural, healthcare, and life sciences across North America and select EMEA and APAC markets. As part of Seneca Group’s continued growth, we are seeking a skilled Development Manager based in our Seattle office in Seattle, WA. This role will play a key part in providing superior client service, delivering exceptional projects, and supporting the continued growth of the firm. If you’re looking to join a team of exceptional people working with recognized clients on high-profile, complex projects - and make a real impact - we’d love to meet you." That's substantive. We'll put under

  About the role

  with

  ...

  . Overview: The paragraph starting "Overview The Development Manager serves as the day-to-day lead..." This could be part of About the role or Responsibilities. But we already have About the role covering intro; we could treat Overview as part of About the role as well. However we might want to keep it separate? The instruction: use headings for sections like About the role, Responsibilities, etc. We can decide to put the Overview under About the role as well, or we could treat it as part of Responsibilities. But we have a separate Responsibilities section for Essential Duties & Responsibilities. So we can merge Overview into About the role or Responsibilities. Since Overview describes the role generally, it's fine to put under About the role. Thus About the role will include the intro paragraphs plus the Overview paragraph. Now Responsibilities: Essential Duties & Responsibilities list. We'll output each duty as
• . Need to preserve all duties exactly as written, but we can keep the sentences. List: - Manage the day-to-day execution of one or more real estate development projects, or multiple projects/programs, from concept through completion, under the direction of an Associate Principal and/or Principal. - Support the definition of technical and financial project scope and manage execution of approved development strategies, budgets, schedules, and delivery plans. - Prepare, maintain, and manage detailed project schedules and development budgets, including forecasting and cash flow tracking. - Oversee entitlement, permitting, and agency coordination processes. - Manage design teams, including architects, engineers, and specialty consultants. - Review and evaluate cost estimates, value engineering options, and contractor proposals. - Support the negotiation and administration of consultant and construction contracts, in coordination with the Associate Principal and/or Principal. - Provide construction management oversight, including cost, schedule, quality, and risk control. - Facilitate and lead day-to-day project meetings with clients, internal teams, and external stakeholders, escalating key decisions, risks, and issues to senior leadership as appropriate. - Serve as the primary day-to-day point of contact for the client, supporting the Associate Principal and/or Principal in overall client leadership, strategic communication, and decision-making. - Proactively identify and resolve project-level risks, conflicts, and issues. - Promote opportunities for repeat business through effective project delivery, communication, relationship management, and collaboration with senior leadership. - Achieve client objectives by aligning project execution with development goals. - Perform other duties as assigned. - Maintain regular attendance during normal business hours, with on-site presence at the office and project sites as required. - The Development Manager reports to an Associate Principal and/or Principal and collaborates closely with senior leadership to align project execution with client objectives and firm strategy. Note: The last two sentences maybe part of responsibilities; we can include. Now Knowledge & Skills Required: list of skills. We'll output as
  • each. List: - Strong ability to compile, analyze, interpret, and integrate complex project and development information. - Demonstrated leadership in managing multidisciplinary teams toward shared goals. - Ability to delegate effectively, provide clear direction, and deliver ongoing feedback. - Proven experience monitoring performance metrics and adjusting strategies as needed. - Strong problem-solving skills, including the ability to distinguish root causes from symptoms. - Excellent written and verbal communication skills, with the ability to present complex information clearly and concisely. - Ability to independently manage projects in dynamic or compressed timeframes. - Strong organizational skills with the ability to balance competing priorities and deadlines. Now Preferred Education And Experience: we can treat as Qualifications (or Requirements). We'll put under

    Qualifications

    maybe with both required and preferred. But we have also Skills section. We could put Education/Experience under Qualifications. Let's do that. List: - Bachelor’s degree required in Construction Management, Engineering, Architecture, Real Estate, Urban Planning, or a related field. - Minimum of 5+ years of demonstrated excellence in commercial real estate development management, project management, design, engineering, and/or construction. - Experience delivering large-scale, complex development projects. - Demonstrated experience managing the development and delivery of ground-up shell-and-core building projects. - Technical or sector-specific expertise in commercial office, healthcare, life sciences, education, research & development, cultural, luxury residential, and/or complex mixed-use projects. - Strong project experience and professional relationships within the assigned region is preferred. - Willingness to travel domestically (approximately 10–25%). Now Pay: we have salary range paragraph. We'll put under

    Pay

    with

    containing the salary range info. Text: "#Seneca The salary range for this full-time role is $150,000.00-$185,000.00 per year. Ranges are determined based on the position, geography, client and industry experience and level, and represent a good faith effort to provide a fair and equitable salary. This range reflects base salary only, and not the total compensation package. Cumming Group reserves the right to pay more or less than the posted range, depending on a candidate’s experience, skills, and qualifications, including client requirements." We need to remove "#Seneca" maybe it's a tag; but it's part of the posting. It's not boilerplate; it's maybe a hashtag. We can keep it as part of the paragraph? It's not substantive; but it's not boilerplate. Might be okay to keep. However we could drop the "#Seneca" as it's just a tag. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. "#Seneca" is not substantive; it's a tag. Might be considered metadata; but it's not job ID. Could drop it. Safer to keep? I'd drop it as it's not meaningful. But we need to be careful not to remove substantive info. It's not substantive; it's just a tag. I'd remove it. Thus Pay paragraph: "The salary range for this full-time role is $150,000.00-$185,000.00 per year. Ranges are determined based on the position, geography, client and industry experience and level, and represent a good faith effort to provide a fair and equitable salary. This range reflects base salary only, and not the total compensation package. Cumming Group reserves the right to pay more or less than the posted range, depending on a candidate’s experience, skills, and qualifications, including client requirements." Now Benefits: list. We have: Medical, Dental Insurance, Vision Insurance, 401(k), 401(k) Matching, Paid Time Off, Paid Holidays, Short and long-term disability, Employee Assistance Program. We need to format as

    • . Ensure each item is separate. Now Schedule: we have "Maintain regular attendance during normal business hours, with on-site presence at the office and project sites as required." That's already in Responsibilities list. But we could also create a Schedule section with that info. However we must not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put it in both Responsibilities and Schedule, we duplicate. Better to keep it only in Responsibilities (since it's a duty). Then we may not need a Schedule section. However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. If we don't have separate schedule content beyond what's already in responsibilities, we could omit Schedule section. But we could still include Schedule section with that sentence, but then we would be duplicating. The instruction does not forbid duplication explicitly, but says preserve ALL substantive information; does not forbid duplication. However better to avoid redundancy. I'd omit Schedule section because the schedule info is already captured under Responsibilities. However the instruction says "Prefer a few substantive sections over many thin ones." So we can skip Schedule. Thus sections: About the role