Mortgage Loan Processor III (Remote)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job description. We have: - Job Description Summary: description of role. Could be "About the role" or maybe "Job Description". We'll use

About the role

with paragraph summarizing. - Responsibilities: "What You’ll Do" bullet list. - Requirements: maybe "Sound Like You?" includes education/experience etc. Could be "Requirements" or "Qualifications". We'll decide. - Skills: maybe "Proficiently process conventional loans and government loans required" etc. Could be part of qualifications. - Benefits: "Benefits Of Working With Taylor Morrison" list. - Pay: Not mentioned. No pay info. So we should NOT include Pay section. - Schedule: Not mentioned. No schedule info. So we should NOT include Schedule. We must not repeat job title as heading. No Job ID etc. We need to remove boilerplate: EEO, legal, etc. Also remove duplicated lines. We need to preserve all substantive info. Let's extract content. Job Description Summary: "As a Client Coordinator III working for Taylor Morrison Home Funding, Inc., you will manage a residential mortgage loan pipeline and process through underwriting approval, resubmittal of approval conditions and into closing. Client Coordinators should be highly skilled in all automated underwriting systems, Desktop Originator, Loan Prospector and each investor’s automated systems. The Client Coordinator is expected to have a comprehensive knowledge of underwriting and qualifying guidelines of all FNMA & FHLMC, FHA & VA loans as well as Non-Agency or Jumbo Loans. As a Client Coordinator you are expected to follow all company policies and procedures as outlined by the company. All Client Coordinators must be customer service oriented, communicating proficiently with borrowers, title agents, builders, real estate agents and co-team members especially Loan Consultants and Closers." That's the summary. Responsibilities (What You’ll Do): List: - Responsible for loan submissions to underwriting - Prepare and deliver the Customer Commitment Letter - Review credit reports, income and assets - Ensures funds are an acceptable source of funds - Proficiently process Conventional, FHA, VA and Non-Agency or Jumbo loans: Seasoned in the requirements of government financing to include the mortgage insurance/funding fee requirements, down payment, DTI and underwriting guidelines - Familiar with and aware of the required FHA/VA application and builder disclosures - Familiar with navigating through the FHA Connection and VA Portal - Proficient with analyzing tax returns - Understanding of FHA, VA, and Conventional underwriting appraisal requirements - Ability to restructure loans - Perform other duties as assigned That's a list. Requirements / Qualifications (Sound Like You?): - Associates degree (A.A.) or equivalent from two (2) year college or technical school; or minimum two (2) years related experience and/or training; or equivalent combination of education and experience - Proficiently process conventional loans and government loans required - Must be of high integrity, technical competence and high moral character - Strong communications skills – written, verbal, and listening - Highly proficient level of computer skills, experience in mortgage loan origination software - FLSA Status: Non-Exempt (this is metadata, maybe include in a short paragraph? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. FLSA status is minor metadata; we could include in a paragraph under maybe "About the role" or separate short p. But we could drop it? It's substantive? It's about exemption status, maybe relevant. We'll include as a short paragraph after responsibilities maybe. Also: "Remote opportunities available" (maybe under schedule? but schedule not given; remote is a work arrangement. Could be part of About the role or a separate section? There's no heading for remote; we could include in About the role paragraph. Also: "Report to Division/Corporate Office/Community daily and adhere to schedule" (that's schedule info? It says report daily and adhere to schedule. That's schedule info but not specific times. Could be considered schedule content. However instruction: only create Schedule section if posting actually states them. It does state "Report to Division/Corporate Office/Community daily and adhere to schedule". That's a schedule expectation. Might be enough to include a Schedule section? But it's vague. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about schedule: "Report to Division/Corporate Office/Community daily and adhere to schedule". That's a statement about schedule. So we could include a Schedule section with that content. However it's not specific times; but it's still stating schedule expectation. I'd include a Schedule section with a paragraph: "Report to Division/Corporate Office/Community daily and adhere to schedule." But also "Remote opportunities available" could be part of schedule or about role. Might be better to include in About the role. Benefits: list given. We must not include boilerplate: EEO, equal opportunity, etc. Also remove duplicated lines: there are duplicated lines about job descriptions not intended as exhaustive lists etc. We'll drop those. Also remove "Taylor Morrison experience and/or successful completion of training program may override required education and/or experience requirement." That's a requirement note; we should keep it as part of Requirements. Also "Job descriptions are not intended as, nor should be construed to be, exhaustive lists of all responsibilities, skills, efforts, or working conditions associated with a job. They are intended to be accurate reflections of those principal job duties and responsibilities essential for making fair pay decisions about the job." appears twice; we drop. Now structure:

About the role

... summary plus remote opportunities maybe

Responsibilities

... list items
• ...

Requirements

... list items (education/experience, integrity, communication, computer skills, etc.) plus maybe "Taylor Morrison experience..." as a list item. Also include FLSA status maybe as a paragraph after requirements? Could be a short

FLSA Status: Non-Exempt

. But we could fold into Requirements as a list item? It's metadata; maybe a short p.

Skills

Maybe we could combine some skill items into Skills section: "Proficiently process conventional loans and government loans required", "Strong communications skills – written, verbal, and listening", "Highly proficient level of computer skills, experience in mortgage loan origination software", "Ability to analyze tax returns", "Ability to restructure loans", "Familiar with FHA/VA application and builder disclosures", "Familiar with navigating through the FHA Connection and VA Portal", "Understanding of FHA, VA, and Conventional underwriting appraisal requirements". However many of those already appear in Responsibilities. To avoid duplication, we could keep them in Responsibilities only. The instruction: Prefer a few substantive sections over many thin ones. So maybe we don't need a separate Skills section; we can incorporate skills into Responsibilities and Requirements. But we have to use sections only when posting has real specific content. We could omit Skills section if we feel it's covered. We have Benefits section. We have Schedule section maybe. Let's decide sections: - About the role (summary + remote opportunities) - Responsibilities (list) - Requirements (education/experience, integrity, communication, computer skills, FLSA status maybe) - Benefits (list) - Schedule (report daily and adhere to schedule) We'll not include Pay. Now craft HTML. We need to ensure we don't include any markdown fences. Just raw HTML. Let's write. About the role paragraph: "As a Client Coordinator III working for Taylor Morrison Home Funding, Inc., you will manage a residential mortgage loan pipeline and process through underwriting approval, resubmittal of approval conditions and into closing. Client Coordinators should be highly skilled in all automated underwriting systems, Desktop Originator, Loan Prospector and each investor’s automated systems. The Client Coordinator is expected to have a comprehensive knowledge of underwriting and qualifying guidelines of all FNMA & FHLMC, FHA & VA loans as well as Non-Agency or Jumbo Loans. As a Client Coordinator you are expected to follow all company policies and procedures as outlined by the company. All Client Coordinators must be customer service oriented, communicating proficiently with borrowers, title agents, builders, real estate agents and co-team members especially Loan Consultants and Closers. Remote opportunities are available." That's good. Responsibilities list items as above. Requirements list: - Associates degree (A.A.) or equivalent from two (2) year college or technical school; or minimum two (2) years related experience and/or training; or equivalent combination of education and experience - Proficiently process conventional loans and government loans required - Must be of high integrity, technical competence and high moral character - Strong communications skills – written, verbal, and listening - Highly proficient level of computer skills, experience in mortgage loan origination software - Taylor Morrison experience and/or successful completion of training program may override required education and/or experience requirement. - FLSA Status: Non-Exempt (maybe as list item) We could also include "Must be able to remain in a stationary position up to 50% of the time" under Physical Demands but that's not a requirement? It's under Physical Demands. Could be part of Requirements? Might be considered a requirement. But we have no section for Physical Demands. Could add to Requirements as a list item. However the instruction: only include sections when posting has real specific content. Physical Demands is specific content. Should we create a Physical Demands section? Not in allowed headings list; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Demands not allowed. So we must fold it into one of those sections, maybe Requirements. It's a demand, but we can include as a list item under Requirements. Thus add: "Must be able to remain in a stationary position up to 50% of the time." Also "Ability to access, input, and retrieve information from a computer and/or electronic device", "Ability to have face to face conversations with customers, co-workers and higher level manager", "Ability to sit or stand for long periods of time and move around work environment as needed", "Ability to operate a motor vehicle if applicable", "Comply with company policies and procedure". Those are also under Essential Functions/Physical Demands. Could be included in Requirements as well. But we must be careful not to make Requirements too long; but it's okay. We'll include all those as list items under Requirements. Now Benefits list: as given. We need to format benefits list items exactly as in text: "Competitive Compensation", "Health Care - Medical/Dental/Vision/Prescription Drug Coverage", "401(k) with Company Matching Contributions", "Flexible Spending Accounts", "Disability Programs", "Employee & Dependent Life Insurance", "Vacation & Company Holidays", "Tuition Reimbursement", "Employee Home Purchase Rebate Program", "Home Mortgage Program", "Employee Assistance Program (EAP)". Ensure correct spelling: "Vision" not "Visio n". The original had a line break: "Health Care - Medical/Dental/Visio n/Prescription Drug Coverage". We'll fix to "Vision". Now Schedule section: paragraph: "Report to Division/Corporate Office/Community daily and adhere to schedule." Also remote opportunities already mentioned in About the role. Now produce HTML. Check for any leftover boilerplate: we removed EEO etc.