Property Administrator (Downtown Houston)

We need to output only HTML fragment, no /, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse the posting: - "ABOUT STREAM REALTY PARTNERS" is about company, not role. We can maybe treat as "About the role"? Actually the instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - Position Overview: description of role. Could be "About the role". We'll put that under

About the role

with

. - Primary Responsibilities: list of duties. Use

• . - Qualifications: there is a "QUALIFICATIONS" heading with bullet-like list (but not bullet). We'll treat as Requirements? Actually they have "Qualifications" section. Could map to "Requirements" or "Qualifications". Since they have both headings possible, we need to decide. The posting includes "Qualifications" with list of attributes. Also there is "Additional Information" about Culture Index survey etc. That's not needed? It's application instruction; we should remove application instructions. Also there is EEO boilerplate and benefits statement: "Stream Realty Partners offers competitive salaries, bonuses, medical/dental/vision insurance, pharmacy benefits, health savings account, flexible spending accounts, 401(k) plan with company matching, PTO, and holiday pay. Individual compensation packages are based on various factors..." That's benefits and pay info. We need to include Benefits and Pay sections only if posting actually states them. It does state benefits and mentions competitive salaries but not specific pay. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (list). It does not state specific pay numbers or schedule. So we can include Benefits section with the list. Pay section: they mention "competitive salaries, bonuses" but that's still part of compensation; but it's vague. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive salaries, bonuses" is somewhat vague but still a statement. Might be acceptable? However they said "Individual compensation packages are based on various factors..." That's also vague. I'd say we should not create a Pay section because it's not specific. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (list). So we can include Benefits. For Pay, it's not specific; better to omit. Schedule: not mentioned, omit. Skills: we could extract from qualifications: "Proficient with Microsoft Excel and Word; Yardi experience a plus; Attention to Detail; Basic accounting skills and knowledge; Mathematical aptitude; Strong verbal and written communication skills; Excellent customer service skills; Good organizational skills; Desire and ambition to learn and grow..." That's skills. Could put under Skills heading. Requirements: maybe education: "Bachelor’s Degree preferred". Could be under Requirements. Qualifications: maybe the core values alignment? Actually they have "Attributes which align with Stream’s core values of Smart, Honest, Nice, and Passionate." That's more like Qualifications. But we already used Qualifications for skills? Let's think: The posting has a section titled "QUALIFICATIONS" with bullet list. That's likely the qualifications. So we should map that to

  Qualifications

  . Then we might have a separate

  Skills

  for the skills list? But the qualifications list includes skills already. To avoid duplication, we could treat the qualifications list as Requirements (education, experience) and Skills as separate. However the qualifications list includes both education and skills. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine into one Qualifications section that includes education and skills. But we have headings for Requirements, Qualifications, Skills. We need to decide which to use. We have content: "Bachelor’s Degree preferred" (education). "Proficient with Microsoft Excel and Word; Yardi experience a plus" (skill). "Attention to Detail" (skill). "Basic accounting skills and knowledge" (skill). "Mathematical aptitude" (skill). "Strong verbal and written communication skills" (skill). "Excellent customer service skills" (skill). "Good organizational skills" (skill). "Desire and ambition to learn and grow in Stream’s property management department" (attribute). "Attributes which align with Stream’s core values of Smart, Honest, Nice, and Passionate." (attribute). So we could put all under Qualifications. Requirements could be empty if we don't have separate. Better to omit Requirements heading if no specific content distinct from Qualifications. Skills heading could be omitted if we put skills in Qualifications. Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits. Check if we need to include "About the role" from Position Overview. Yes. Responsibilities: Primary Responsibilities list. Qualifications: the QUALIFICATIONS list. Benefits: the benefits statement. We must not include company description about Stream Realty Partners (the "ABOUT STREAM REALTY PARTNERS") as it's not about the role. Should we include it? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "About the role" heading is for role overview, not company. So we should not include the company description. However we might include a brief "About Stream Realty Partners" as part of About the role? Probably not; we should keep only role-related content. The company description is not about the role, but could be considered background. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. But also says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not boilerplate; it's substantive info about the company. Should we keep it? The instruction about headings is about structuring the job posting. It didn't say to exclude company description. It said to reformat a job posting into clean, well-structured semantic HTML. So we likely need to include all substantive information, including company overview. However we need to map it to a heading. There's no heading like "About the company". The allowed headings list does not include that. But we could still include a

  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 suggests using those for sections. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections; we could still have other headings but they'd deviate. Safer to stick to those headings only. But we need to place company info somewhere. Could put it under About the role? That would be mixing role overview with company info, but still substantive. Might be acceptable. Alternatively, we could create a

  About the company

  but not in the list; risk of violating instruction. Better to incorporate into About the role paragraph. Thus About the role paragraph will include both position overview and company description. Let's craft:

  About the role

  Founded in 1996, Stream Realty Partners (Stream) began with a vision focused on people, not bricks and mortar. Headquartered in Dallas, TX and operating in core markets coast to coast, Stream completes billions in annual transactions across office, industrial, retail, healthcare, land, and data center properties, managing millions of square feet. As one of the fastest‑growing full‑service commercial real estate services organizations, Stream’s team lives by the core values smart, honest, nice, and passionate. The Property Administrator position provides first‑class property management services and assists the Property Management team with day‑to‑day responsibilities of operating a commercial property.

  That preserves company info and role overview. Now Responsibilities:

  Responsibilities

  • Accounts Payable – accurately input, verify proper backup, and code all invoices according to the approved budget into the payables system and then forward to the Property Manager for approval.
  • Accounts Receivable – monthly review of accounts receivable in the system and assist with the preparation of late notices and default notices.
  • Assist Property Manager with the preparation of monthly/quarterly financial reports.
  • Assist Property Manager with day‑to‑day operation of assigned portfolio.
  • Assist with answering the main telephone line and screen calls to forward to the appropriate personnel; deliver messages to personnel and/or forward messages to voicemail; greet guests and notify personnel of incoming visitors; accept deliveries/packages.
  • Receive and enter work order requests into the system.
  • Maintain, track, and input into the system all Certificates of Insurance for vendors/tenants/clients.
  • Prepare, compile, and facilitate the creation and execution of Service Contracts for vendor services.
  • Schedule building activity, including move‑ins / move‑outs; verify insurance.
  • Assist in planning and executing tenant events with the management team.
  Now Qualifications:

  Qualifications

  • Bachelor’s Degree preferred
  • Proficient with Microsoft Excel and Word; Yardi experience a plus
  • Attention to Detail
  • Basic accounting skills and knowledge
  • Mathematical aptitude
  • Strong verbal and written communication skills
  • Excellent customer service skills
  • Good organizational skills
  • Desire and ambition to learn and grow in Stream’s property management department
  • Attributes which align with Stream’s core values of Smart, Honest, Nice, and Passionate
  Now Benefits:

  Benefits

  • Competitive salaries
  • Bonuses
  • Medical/dental/vision insurance
  • Pharmacy benefits
  • Health savings account
  • Flexible spending accounts
  • 401(k) plan with company matching
  • Paid time off (PTO)
  • Holiday pay
  We should not include Pay or Schedule sections. Check for any duplicated lines: we have not included application instructions, EEO boilerplate, Culture Index survey, etc. We removed those. We must ensure we preserve all substantive information: Did we miss anything? The posting also mentions "Once you have completed your application, you will receive an email from notifications@smartrecruiters.com with a link to the Culture Index survey..." That's application instruction, remove. Also "Please search for the 'Property Administrator - All Locations' position in the Culture Index portal." Remove. "We kindly request that you set aside 10 uninterrupted minutes within 48 hours of submitting your application." Remove. Also the line "Stream is an equal-opportunity employer..." remove EEO. Also "To apply for a position, please visit our website at www.streamrealty.com" remove. We kept benefits list. Did we preserve the phrase "Individual compensation packages are based on various factors unique to each candidate, including skill set, experience, qualifications, location, and other job-related reasons." That's somewhat about pay but vague. We omitted Pay section; but maybe we should include