MxU Success Manager I

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title. Remove boilerplate: EEO, legal, accommodation, etc. Also remove application instructions (none). Keep substantive info. Let's parse content. First paragraph: description of GFiber, mission, etc. Could be "About the role"? Actually that's about company. Could be "About the role" or maybe "About GFiber". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" containing description of role and company? The role description paragraph: "Role Description As a GFiber Multifamily Success Manager, you will be responsible for increasing the number of active residential customers within an assigned portfolio of multi-dwelling/multi-family properties (apartments, condos, etc). You will own and cultivate strong relationships with property owners, managers, and building staff to promote the growth and retention of Google Fiber’s residential internet. You will maximize impact by acting as a single point of contact for staff, and leverage strong relationships to drive penetration growth through customer acquisition programming and events, and successful customer care." Then bullet list: "In this role, you'll:" followed by items. Thus we can put responsibilities under

Responsibilities

with

• items. Then "At a minimum we'd like you to have:" list of minimum qualifications. That's Requirements? Could be "Requirements". Then "It's preferred if you have:" list of preferred qualifications. Could be "Qualifications" or "Skills". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (minimum) and Qualifications (preferred) or Skills (preferred). Let's decide: Requirements = minimum qualifications. Qualifications = preferred qualifications. Skills maybe separate but we can combine. We also have Pay: "The US base hourly range for this full-time position is between $30.77 + bonus + benefits." That's pay info. So we need a Pay section with that sentence. Schedule: "Need to have the ability to work some nights and weekends." Also "Need to have the ability to lift up to 45 lbs on occasion." That's physical requirement maybe part of Requirements? Could be part of Requirements. But schedule info about nights and weekends is schedule. So we can include Schedule section with that sentence. Benefits: Not explicitly listed besides "+ bonus + benefits" in pay line. No explicit benefits description. So we should not create Benefits section unless posting actually states them. It only mentions "+ bonus + benefits" but not detail. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, we have only mention of benefits generically but not specifics. Probably we should not create Benefits section because no specific benefits listed. Pay we have specific hourly range plus bonus + benefits, that's enough to state Pay. Schedule we have ability to work some nights and weekends, that's schedule info. So include Pay and Schedule. Now About the role: Could include introductory paragraph about GFiber mission and team. That's not exactly role description but could be "About the role". We'll include that. Now we must not repeat job title as heading. So no heading for "GFiber Multifamily Success Manager". Good. We must not put Job ID/requisition numbers as headings; none present. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO paragraph, accommodation request, etc. Also remove duplicated lines: there may be duplicate sentences? Not seeing. Now produce HTML fragment. Structure:

  About the role

  At GFiber, we believe that great internet has the power to drive innovation, strengthen communities, enable the impossible, and do all the everyday things that make all of our world go round. And the job of creating better internet is never done - so we’re growing! Our team is committed to building a place where people who want to make a difference can grow their careers and find their spot to belong. GFiber is an Alphabet company that brings Google Fiber and Google Fiber Webpass internet services to homes and businesses across the United States. Our teams are expanding as we connect more cities and people to exceptional internet.

  Then Responsibilities:

  Responsibilities

  • Increase the number of active residential customers within an assigned portfolio of multi-dwelling/multi-family properties (apartments, condos, etc).
  • Own and cultivate strong relationships with property owners, managers, and building staff to promote the growth and retention of Google Fiber’s residential internet.
  • Act as a single point of contact for staff, and leverage strong relationships to drive penetration growth through customer acquisition programming and events, and successful customer care.
  • Meet or exceed quarterly portfolio pen growth sales quota by promoting Google Fiber's internet.
  • Drive pen growth through customer acquisition programming and events, and successful customer care retention management.
  • Own relationships with property owners, managers, and building staff within an assigned portfolio of multi-dwelling properties.
  • Act as the main point of contact for the property.
  • Obtain a robust knowledge of Google Fiber’s network and technical deployment, and communicate the Google Fiber value proposition to property management, staff, and tenants.
  • Consider the impact of all cross-functional teams on portfolio pen (including sales, marketing, installation, churn, customer service, etc) and make recommendations to drive growth.
  • Display solid communication skills internally and externally, and partner with other Google Fiber team members to ensure a seamless, end-to-end customer and partner experience.
  But note some items duplicate earlier sentences. We need to preserve all substantive information but not repeat duplicated lines. The bullet list includes some repeats of earlier sentences. We should deduplicate. Let's extract unique responsibilities. From role description paragraph: responsibilities: increase number of active residential customers within assigned portfolio; own and cultivate relationships with property owners, managers, building staff; act as single point of contact for staff; leverage relationships to drive penetration growth through customer acquisition programming and events, and successful customer care. Then bullet list items: - Meet or exceed quarterly portfolio pen growth sales quota by promoting Google Fiber's internet. - Drive pen growth through customer acquisition programming and events, and successful customer care retention management. - Own relationships with property owners, managers, and building staff within an assigned portfolio of multi-dwelling properties. - Act as the main point of contact for the property. - Obtain a robust knowledge of Google Fiber’s network and technical deployment, and communicate the Google Fiber value proposition to property management, staff, and tenants. - Consider the impact of all cross-functional teams on portfolio pen (including sales, marketing, installation, churn, customer service, etc) and make recommendations to drive growth. - Display solid communication skills internally and externally, and partner with other Google Fiber team members to ensure a seamless, end-to-end customer and partner experience. Now we see some overlap: "Own relationships with property owners..." similar to earlier "own and cultivate strong relationships". Slight difference but we can keep both? Might be considered duplicate. To avoid duplication, we can combine or keep one. The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So if two sentences are substantively same, we should keep only one. Let's see: Earlier: "You will own and cultivate strong relationships with property owners, managers, and building staff to promote the growth and retention of Google Fiber’s residential internet." Bullet: "Own relationships with property owners, managers, and building staff within an assigned portfolio of multi-dwelling properties." The bullet lacks "to promote growth and retention" and "within an assigned portfolio". The earlier includes purpose. They are not identical; bullet is more generic. Both provide info: one mentions purpose, the other mentions portfolio. Could keep both as they add nuance. However they are similar; but not exact duplicate. We'll keep both. "Act as the main point of contact for the property." vs earlier "Act as the single point of contact for staff". Slight difference: staff vs property. Keep both. Now "Meet or exceed quarterly portfolio pen growth sales quota by promoting Google Fiber's internet." is new. "Drive pen growth through customer acquisition programming and events, and successful customer care retention management." similar to earlier "leverage strong relationships to drive penetration growth through customer acquisition programming and events, and successful customer care." Slight nuance: retention management vs customer care. Keep both. Now "Obtain a robust knowledge of Google Fiber’s network and technical deployment, and communicate the Google Fiber value proposition to property management, staff, and tenants." new. "Consider the impact of all cross-functional teams on portfolio pen (including sales, marketing, installation, churn, customer service, etc) and make recommendations to drive growth." new. "Display solid communication skills internally and externally, and partner with other Google Fiber team members to ensure a seamless, end-to-end customer and partner experience." new. Now also need to include physical requirement: "Need to have the ability to lift up to 45 lbs on occasion." and "Need to have the ability to work some nights and weekends." These could go under Requirements (minimum) or Schedule. We'll put lift ability under Requirements (physical requirement). Nights/weekends under Schedule. Now Requirements (minimum) list: - High school diploma or GED. - 1 year of experience in sales and/or customer service. - Ability to exert yourself physically over extended periods of time, including frequent walking and climbing stairs. - Ability to lift up to 45 lbs on occasion. - Valid driver’s license and access to reliable transportation during working hours. - Ability to pass a motor vehicle record check that meets company standards. We could also include "Ability to exert yourself physically over extended periods of time, including frequent walking and climbing stairs." That's from minimum. Now Qualifications (preferred) list: - 2 years of experience in sales or strategic account management, carrying a quota, in the ISP or telecom industry. - Property Management experience. - Proficiency in SalesForce or other CRM. - Experience with effective sales relationship-building or partnership development. - Excellent work ethic, communication, navigating ambiguity and time management skills. - Ability to speak Spanish. Now Skills maybe not needed; we could treat Qualifications as skills. But we have both headings; we could omit Skills if no specific content beyond qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section called Qualifications (or Skills). But we have both minimum and preferred; we could have Requirements (minimum) and Qualifications (preferred). That's two sections. That's fine. Now Pay section:

  Pay

  The US base hourly range for this full-time position is between $30.77 + bonus + benefits.

  Schedule section:

  Schedule

  Need to have the ability to work some nights and weekends.

  We could also include lift ability under Requirements; we already did. Now About the role section: we included introductory paragraph. Could also add the application window date? The posting includes: "The application window will be open until at least September 21st, 2026. This opportunity will remain online based on business needs which may be before or after the specified date." That's metadata about application timing. According to rules, we should remove application instructions, but this is not instruction; it's about timing. Should we keep? It's substantive info about when to apply. The instruction says remove application instructions. This is not instruction but a date. Might be considered metadata like Job ID. The instruction says: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could fold