Sr. Real Estate Development Manager, Multifamily
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which headings to use based on content. The posting has "Job Description" (maybe treat as About the role). Then "Responsibilities". Then "Qualifications". Also "About Us". Could map "About Us" to "About the role" or maybe separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when we have content. For "Job Description" we could use About the role. For "Qualifications" we could use Requirements or Qualifications. Probably use Qualifications heading. For "About Us" maybe also About the role? But we already have About the role from Job Description. Could combine? Better to have About the role (Job Description) and maybe another section like About Us could be omitted or merged? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide which sections to include. We have content for: - About the role: could be the Job Description paragraph(s) that describe role and company. That's substantive. - Responsibilities: list. - Qualifications: list. - About Us: could be considered "About the role"? But we already used that. Could also treat as "About the role" again? Might be redundant. Perhaps we can include "About the role" covering both Job Description and About Us? But they are distinct: Job Description describes role; About Us describes company. Could we have two sections: About the role (Job Description) and About Us (maybe not in list). The allowed headings list does not include "About Us". So we cannot create a heading not in the list. So we must either omit About Us or incorporate its content into an allowed heading like About the role or maybe Requirements? Not appropriate. Probably we omit About Us content? But instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot drop About Us content. We need to include it somewhere. Since only allowed headings are those listed, we could put About Us content under About the role heading (makes sense as it's about the organization). Or we could create a generic
without heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to have other headings, but better to stick to those. We could embed About Us content in a
after the About the role heading without a new heading. That would preserve info. Thus structure:
About the role
Job Description paragraph(s) + About Us paragraph(s) combined? Might be long but okay. Then
Responsibilities
- ... each responsibility
Qualifications
- ... each qualification
or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short
with location and schedule maybe. But we already have About the role section; we could add a
after heading for metadata. However we must not create Pay/Benefits/Schedule sections unless posting actually states them. The posting does state Job Schedule Full time Regular. That's a schedule info. Should we include a Schedule section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The posting does state schedule: Full time Regular. That's specific. So we could create a
Schedule
withFull time Regular
. But we need to see if we should treat schedule as minor metadata to fold into a shortor drop it. The instruction says: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Schedule might be considered minor metadata? Not sure. It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." So if posting states them, we can create them. So we can create Schedule section. Similarly Benefits: not stated. Pay: not stated. So we omit those. Thus we will have sections: About the role, Responsibilities, Qualifications, Schedule. We need to include location maybe in About the role or separate? Could add a short
after About the role heading for location: "Located at 51 S Main St, Salt Lake City, UT, 84111, US." That's minor metadata but okay. We must preserve all substantive information: include the details about the role, responsibilities, qualifications, about us, schedule, location. Let's extract content. Job Description paragraphs: "At Property Reserve, our people, values, and work come together to build something greater. Property Reserve is the real estate investment arm of the reserve funds for The Church of Jesus Christ of Latter-day Saints. In the spirit of time-tested self-reliance principles, Property Reserve creates sustainable cashflow for future needs. As caretakers of sacred funds, we invest in income-generating properties and land to support the Church’s mission. Our focus is on the acquisition, build-to-hold development, and portfolio level management of office, industrial, multi-family, build-to-rent, hospitality, and retail properties. Property Reserve provides a diverse range of investment experiences, interacting with a seasoned leadership team. Working in a highly collaborative environment, each Property Reserve team member has the chance to contribute meaningfully and frequently to the company culture. Headquartered in downtown Salt Lake City, we offer a locale with a unique blend of world-class outdoor recreation, a thriving culture & arts scene, and diverse housing options with convenient commutes" Then role description: "The Senior Development Manager, Multifamily leads the successful execution of multifamily, build-to-rent, and other residential development projects from initial feasibility through stabilization. This role is responsible for coordinating market analysis, site selection, due diligence, underwriting, entitlements, design, budgeting, scheduling, construction oversight, risk management, and project reporting to ensure projects are delivered consistent with approved business plans, investment objectives, scheduled turn over projections, and owner expectations. The Senior Development Manager contributes to residential investment strategy and creates value through disciplined execution, clear decision-making, risk management, and leadership of internal teams, development partners, consultants, contractors, municipalities, and other stakeholders." That's the job description. About Us paragraph: "Church employees find joy and satisfaction in using their unique talents and abilities to further the Lord’s work. From the IT professional who develops an app that sends the gospel message worldwide, to the facilities manager who maintains our buildings— giving Church members places to worship, teach, learn, and receive sacred ordinances—our employees seek innovative ways to share the gospel of Jesus Christ with the world. They are literally working in His kingdom. Only members of the Church who are worthy of a temple recommend qualify for employment. Apart from this, the Church is an equal opportunity employer and does not discriminate in its employment decisions on any basis that would violate U.S. or local law. Qualified applicants will be considered for employment without regard to race, national origin, color, gender, pregnancy, marital status, age, disability, genetic information, veteran status, or other legally protected categories that apply to the Church. The Church will make reasonable accommodations for qualified individuals with known disabilities." We can include that under About the role as well. Responsibilities list (each bullet): - In collaboration with senior leadership, help define and implement the Company's residential development strategy, with particular focus on multifamily and build-to-rent investment opportunities. - Evaluate and support the pursuit and execution of new residential development opportunities through market research, financial analysis, site feasibility, and due diligence. - Lead projects from acquisition through stabilization, maintaining clear accountability for budget, schedule, scope, risk, quality, investment performance, and alignment with approved business plans. - Coordinate land planning, architecture, engineering, permitting, entitlements, utility coordination, municipal approvals, and community engagement while resolving key entitlement, design, construction, and financial risks. - Manage development partners, consultants, architects, engineers, contractors, and internal project teams to protect owner interests, coordinate execution, and deliver projects on time and to quality expectations. - Review and evaluate project budgets, change orders, contingency use, pay applications, project schedules, and major project risks. - Prepare and review financial models, budgets, return analyses, investment recommendations, and executive updates, reports, and review board-level materials that clearly identify key decisions, risks, costs, schedule impacts, and recommended next steps. - Monitor market trends, demographic shifts, competitive developments, construction costs, and economic conditions impacting residential investment opportunities. - Negotiate development agreements, consultant contracts, and other project-related documents. - Support portfolio-level initiatives, strategic projects, process improvements, including standardized reporting, consultant management, budget controls, project risk tracking, and by establishing development best practices, process improvements, and operational efficiencies. - Provide mentorship, guidance, and work direction to other members of the development team as assigned. - Perform other essential duties as assigned. Qualifications list: - Member of The Church of Jesus Christ of Latter-day Saints and currently temple worthy. - Bachelor's degree in Real Estate, Finance, Business, Construction Management, Engineering, Architecture, Urban Planning, or related field required. - MBA, MRED, MSRE, or other related advanced degree preferred. - Minimum of 8 years of progressively responsible commercial real estate development experience with significant exposure to multifamily, build-to-rent, single-family rental, or residential land development projects. - Experience managing institutional-quality multifamily or build-to-rent projects across multiple jurisdictions preferred. - Demonstrated experience managing projects through acquisition, entitlement, design, construction, and delivery. - Strong understanding of residential development economics, real estate finance, capital markets, market analysis, financial modeling, investment underwriting, project pro formas, development budgeting, construction practices, and entitlement processes. - Proven ability to identify, evaluate, and execute profitable development opportunities. - Strong analytical, quantitative, problem-solving, negotiation, communication, presentation, leadership, collaboration, relationship-building, and prioritization skills. - Strong work ethic, entrepreneurial mindset, attention to detail, sound judgment, ability to influence across teams, and commitment to excellence. - Ability and willingness to travel as required. (PR/IP) Also there is "Qualificação de dignidade Must be a member of The Church of Jesus Christ of Latter-day Saints and currently temple worthy." That's duplicate; we can ignore duplicate. Schedule: "Job Schedule Full time Regular or Temporary Regular". Actually says: "Job Schedule Full time Regular or Temporary Regular". So schedule: Full time Regular (or Temporary Regular). We'll note "Full time Regular". Location: "Locations 51 S Main St, Salt Lake City, UT, 84111, US (No Local)". We'll include location. Now produce HTML. We'll start with
About the role
Job Description paragraphs + About Us paragraph + location maybe.
But we might want to separate location into its ownafter About the role? It's okay. We'll embed location in a
after the About the role content. Then