Senior Home Lending Advisor - New York NY - Times Square

We need to output HTML fragment with sections: headings

for sections present: About the role? The description includes "Job Description" then responsibilities, qualifications, etc. We need to parse content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove NMLS registration details? That's part of qualifications? It's about compliance; maybe keep as part of responsibilities? It's more legal requirement; but it's substantive? It's about employment contingency; maybe keep as part of "Requirements" or "Qualifications". The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The NMLS registration is not exactly EEO; it's a requirement. Might be considered legal but it's substantive to the job. Probably keep. We need sections: About the role (maybe from first paragraph). Responsibilities (list). Requirements (maybe combine Required Qualifications, Capabilities And Skills). Benefits (maybe from About Us: competitive total rewards package, benefits). Pay? Not specified exact numbers; we should not create Pay section unless posting actually states them. It says "competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation". That's vague but still mentions pay. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state base salary etc. So we can include Pay section with that info. Benefits: they list benefits. Schedule: not mentioned, so omit. We need to avoid filler like "commensurate with experience". Not present. We need to use

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

  for prose. We must not repeat job title as heading. So headings: About the role, Responsibilities, Requirements, Benefits, Pay maybe. We need to ensure we don't include sections with no content. Let's extract content. Job Description paragraph: "Join our fun, high-energy team as a Senior Home Lending Advisor in Chase Home Lending and put your exceptional knowledge and understanding of home lending products to good use by serving as your customers' chief point of contact throughout the life of the loan while the Home Lending team supports you by sharing demonstrated knowledge in this area of specialization. You will adhere to all regulatory requirements while marketing and promoting the financial products offered by Chase. You will have a unique opportunity to grow your career while making a significant impact on our business. As a Senior Home Lending Advisor in Chase Home Lending, you will take your clients on a first-class journey to home ownership and deliver strong sales results. You will put your exceptional knowledge and understanding of home lending products to good use by serving as your customers' chief point of contact throughout the life of the loan. You will adhere to all regulatory requirements while marketing and promoting the financial products offered by Chase." That's repetitive; we need to preserve all substantive info but can we deduplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must keep duplicates; but we should not remove substantive info. Duplicates are same info repeated; we could keep one instance. Probably okay to deduplicate to avoid redundancy but not lose info. Safer to keep as is? Might be considered duplicated lines which we should remove: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to deduplicate repeated sentences. Thus we can combine: "Join our fun, high-energy team as a Senior Home Lending Advisor in Chase Home Lending and put your exceptional knowledge and understanding of home lending products to good use by serving as your customers' chief point of contact throughout the life of the loan while the Home Lending team supports you by sharing demonstrated knowledge in this area of specialization. You will adhere to all regulatory requirements while marketing and promoting the financial products offered by Chase. You will have a unique opportunity to grow your career while making a significant impact on our business. As a Senior Home Lending Advisor in Chase Home Lending, you will take your clients on a first-class journey to home ownership and deliver strong sales results." That covers. Now Responsibilities: list bullet points from "Job Responsibilities". Let's extract: - Coaches and mentors the branch team by providing training on products and services. - Works together with bankers, meeting with their customers and introducing new clients to bankers for additional products and services - Partners with your team to create an outstanding customer experience by utilizing centrally managed direct mail, media advertisements, cross-sell efforts, relocation programs, statement programs, Chase.com, electronic newsletters, outbound lead sourcing, and other marketing efforts - Develops a strong partnership with the assigned retail branches to promote mortgage loan originations (in footprint territories), and can function well within formal and dotted-line reporting relationships - Builds role as the internal and external mortgage expert; builds and maintains good relationships with customers; and exhibits consultative skills to provide recommendations based on financial analysis and expertise, product knowledge, and knowledge of the customer's financial needs, goals, and circumstances We need to ensure each bullet is a

• . Now Required Qualifications, Capabilities And Skills: - Minimum three years of mortgage lending and proven sales experience in retail banking - Knowledge of real estate market in local area - Excellent written and oral communication skills - Knowledge of FHA, VA, FNMA, and FHLMC guidelines Preferred Qualifications, Capabilities And Skills: - FHA/VA sales experience - Marketing, promoting, relationship building, and consulting skills - Intermediate PC skills in a Windows environment - Bachelor's degree or equivalent work experience in sales and/or real estate Also compliance requirements: Dodd Frank/Truth in Lending Act qualification requirements for Loan Originators; employment offer contingent on JPMC's review of criminal conviction history, credit report, NMLS, etc. Felony conviction within last seven years disqualifies. Continued employment contingent upon compliance with TILA/Dodd Frank Loan Originator requirements. Position requires NMLS registration under SAFE Act of 2008; upon active employment, must register or update NMLS registration; continued employment contingent upon compliance with SAFE Act, including successful registration immediately after start date, timely completion of annual renewal and required updates. Any info obtained may impact employment. Info provided in Chase online application may be transferred to NMLS. Advise to review info for accuracy. We could include these under Requirements or maybe a separate "Compliance" section but not required heading. Since we have Requirements section, we can include these as part of Requirements (maybe as sub-bullets). However the instruction: Use
  • for any list of duties/requirements/benefits. So we can have a list for Required Qualifications, another for Preferred Qualifications, and maybe another for Compliance Requirements. But we must not create thin sections; we can combine Required and Preferred into one Requirements section with subheadings? But we only allowed

    for section headings; we cannot have subheadings other than

    . Could we embed paragraphs? We could have a

    describing required qualifications then a

    for list. For preferred, another

    and

    . That's okay. Now Benefits: from About Us: "We offer a competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions. We also offer a range of benefits and programs to meet employee needs, based on eligibility. These benefits include comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more." We need Benefits section with list of benefits. Also Pay section: we could separate base salary and commission info. But the rule: prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one "Compensation and Benefits" section? But headings must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include Benefits and Pay separately if they have content. However we might avoid too many sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Pay and Benefits into one section called "Benefits" that includes both pay and benefits info. But the heading must be exactly one of the allowed headings. We could use "Benefits" heading and include both pay and benefits details. That seems acceptable. Thus we will have sections: About the role, Responsibilities, Requirements, Benefits. We need to ensure we don't include empty sections. Now craft HTML. Start with

    About the role

    then

    with the deduplicated description. Then

    Responsibilities

    then
    • ... etc. Then

      Requirements

      then maybe

      Required qualifications:

      then
      for required; then

      Preferred qualifications:

      then
      for preferred; then maybe

      Compliance requirements:

      then
      for compliance items. But we need to avoid too many headings; but we can keep paragraphs inside Requirements section. Now Benefits:

      Benefits

      then

      describing total rewards package etc. Then

      for list of benefits. Let's list benefits: comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more. We could also mention commission-based pay etc. We'll include in the

      . Now ensure we removed duplicated lines, boilerplate like EEO, etc. The About Us includes EEO statements; we should remove those. The About Us paragraph includes: "We recognize that our people are our strength and the diverse talents they bring to our global workforce are directly linked to our success. We are an equal opportunity employer and place a high value on diversity and inclusion at our company. We do not discriminate on the basis of any protected attribute, including race, religion, color, national origin, gender, sexual orientation, gender identity, gender expression, age, marital or veteran status, pregnancy or disability, or any other basis protected under applicable law. We also make reasonable accommodations for applicants' and employees' religious practices and beliefs, as well as mental health or physical disability needs. Visit our FAQs for more information about requesting an accommodation. Equal Opportunity Employer/Disability/Veterans". That's boilerplate EEO; we should remove. Also "About The Team" section maybe not needed? It's descriptive but could be considered substantive about team. However it's not under allowed headings; we could incorporate into About the role? But it's about the team; maybe we can include as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The About The Team paragraph describes Consumer & Community Banking division etc. That's substantive about the company/team. Should we keep? It's not under a specific heading but we could include in About the role paragraph as extra info. However the About the role currently is about the job; adding team info may be okay. But we must not create new headings. We could add a

      after About the role describing the team. That's still within About the role section? Actually we already used About the role heading; we can have multiple

      under that heading. So we can add another

      describing the team. Thus About the role section will have two paragraphs: job description and team description. Now ensure we removed duplicated lines and boilerplate. Now produce HTML. Let's craft. About the role paragraph 1: combine as earlier. Paragraph 2: "Our Consumer & Community Banking division serves our