Commercial Lending Analyst

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: EEO, disclaimer about equal opportunity, etc. Also remove application instructions (none). Remove duplicated lines. Must not create sections with filler like "commensurate with experience". We have Starting Salary: $55,000-$60,000. Also later "PM22 Compensation details: 55000-60000 Yearly Salary". So we have pay info. No explicit benefits or schedule. So we should not create Benefits or Schedule sections unless posting actually states them. It does not mention benefits or schedule. So omit those sections. We need sections: About the role (maybe from first paragraph). Responsibilities (Essential Functions and Responsibilities). Requirements (Position Requirements and Qualifications). Qualifications (maybe Preferred Qualifications). Skills (maybe computer proficiency etc). Pay (Starting Salary). Could also combine Requirements and Qualifications? The instruction says use headings for those categories if content exists. We have both "Position Requirements and Qualifications:" and "Preferred Qualifications:" separate. Could treat Requirements as required qualifications, Qualifications as preferred. Skills could be computer proficiency etc. But we must not invent. Let's extract. About the role: first sentences: "The Commercial Lending Analyst is vital to the department’s loan origination and underwriting function. The Lending Analyst position is responsible for the execution of URA financing programs including sourcing clients, underwriting loans, and portfolio management. An ideal candidate will have excellent communication skills, be passionate, driven, collaborative, and dedicated to furthering Pittsburgh’s economic vitality." That's about role. Responsibilities: list under "Essential Functions and Responsibilities:" each bullet after colon. We'll need to convert to

• . Ensure we keep all items. Let's list them: - Work with URA Business Services and partner organizations to widely promote loan programs across the city. - Create connections and source deal flow throughout the City of Pittsburgh. - Originate applications for financing, collect applicable information and documentation; analyze and underwrite the application; prepare and present loan proposals for internal and loan review committee review; close approved loans; and service the loan. - Coordinate teamwork among URA staff, entrepreneurs and small businesses, private funders, and others. - Work with the Manager of Business Lending and the URA’s Legal and Compliance staff to ensure that commercial loans and grants are originated in accordance with federal tax law, applicable underwriting guidelines, the Urban Redevelopment Authority’s program guidelines and all other applicable local/state and federal regulations and guidelines. - Monitor the financial performance of borrowers and as necessary recommend technical assistance and loan restructuring. - Facilitate URA façade program promotion, underwriting, and execution. - Prepare professional correspondence, credit memos, and other documentation. - Work with businesses to connect with resources and tools (both URA and non URA) including technical assistance. - Represent the Commercial and Business Lending Department and its programs to external partners and the public, as requested. - Work independently with general direction from the manager and director. - Perform other duties as assigned. Now Requirements: "Position Requirements and Qualifications:" then list: - Bachelor’s Degree in business administration, economics, or entrepreneurship - One (1) or more years of experience underwriting and presenting credit and risk analysis for direct lending and investment preferred. - Excellent organizational skills and communication skills, including verbal, written and public speaking. - Computer proficiency in Microsoft Office suite products such as word, excel, and publisher. Note: "preferred" appears in second bullet; but it's still a requirement? It says "preferred". We'll keep as is. Preferred Qualifications: separate list: - Commercial underwriting experience in businesses and commercial real estate is preferred. - Experience using Salesforce, WordPress, or similar software a plus. Skills: Could be computer proficiency etc. But we already have computer proficiency under Requirements. Could also list communication skills etc. Might be redundant. Perhaps we create a Skills section for "Excellent organizational skills and communication skills, including verbal, written and public speaking." and "Computer proficiency in Microsoft Office suite products such as word, excel, and publisher." But those are already in Requirements. The instruction: Prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one section? But headings are prescribed; we can omit sections if no content. We have content for Requirements, Qualifications, Skills, Pay. We could decide to not have Skills separate if its content overlaps with Requirements; but we must preserve all substantive info. If we put computer proficiency under Requirements, that's fine. Communication skills also under Requirements. So Skills section may be redundant; we could omit Skills if we feel it's thin. But we have to include sections only when posting has real specific content for it. The posting does have specific content about skills (communication, organizational, computer proficiency). So we could include Skills section with those items. However we already have them under Requirements; duplicating would repeat info, which is allowed? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. We could move skills to Skills section and keep Requirements focused on education/experience. Let's parse: Position Requirements and Qualifications: includes education, experience, organizational/communication skills, computer proficiency. Preferred Qualifications: commercial underwriting experience, Salesforce/WordPress experience. We could treat: - Requirements: education and experience (Bachelor's degree, 1+ years experience). - Qualifications: preferred qualifications (commercial underwriting experience, Salesforce/WordPress). - Skills: organizational skills, communication skills, computer proficiency. That seems reasonable and avoids duplication. Now Pay: Starting Salary: $55,000-$60,000. Also later "PM22 Compensation details: 55000-60000 Yearly Salary". We'll include Pay section with that salary range. Now Benefits and Schedule: none, omit. Now we need to output HTML fragment with

  headings and

  • for lists,

    for prose. We must not include any markdown fences. Let's craft:

    About the role

    The Commercial Lending Analyst is vital to the department’s loan origination and underwriting function. The Lending Analyst position is responsible for the execution of URA financing programs including sourcing clients, underwriting loans, and portfolio management. An ideal candidate will have excellent communication skills, be passionate, driven, collaborative, and dedicated to furthering Pittsburgh’s economic vitality.

    Responsibilities

    • Work with URA Business Services and partner organizations to widely promote loan programs across the city.
    • Create connections and source deal flow throughout the City of Pittsburgh.
    • Originate applications for financing, collect applicable information and documentation; analyze and underwrite the application; prepare and present loan proposals for internal and loan review committee review; close approved loans; and service the loan.
    • Coordinate teamwork among URA staff, entrepreneurs and small businesses, private funders, and others.
    • Work with the Manager of Business Lending and the URA’s Legal and Compliance staff to ensure that commercial loans and grants are originated in accordance with federal tax law, applicable underwriting guidelines, the Urban Redevelopment Authority’s program guidelines and all other applicable local/state and federal regulations and guidelines.
    • Monitor the financial performance of borrowers and as necessary recommend technical assistance and loan restructuring.
    • Facilitate URA façade program promotion, underwriting, and execution.
    • Prepare professional correspondence, credit memos, and other documentation.
    • Work with businesses to connect with resources and tools (both URA and non URA) including technical assistance.
    • Represent the Commercial and Business Lending Department and its programs to external partners and the public, as requested.
    • Work independently with general direction from the manager and director.
    • Perform other duties as assigned.

    Requirements

    • Bachelor’s Degree in business administration, economics, or entrepreneurship
    • One (1) or more years of experience underwriting and presenting credit and risk analysis for direct lending and investment preferred.

    Qualifications

    • Commercial underwriting experience in businesses and commercial real estate is preferred.
    • Experience using Salesforce, WordPress, or similar software a plus.

    Skills

    • Excellent organizational skills and communication skills, including verbal, written and public speaking.
    • Computer proficiency in Microsoft Office suite products such as word, excel, and publisher.

    Pay

    Starting Salary: $55,000-$60,000 yearly.

    Check: Did we preserve all substantive info? We omitted the line "Reports to: Commercial and Business Lending Manager" and "Department: Commercial and Business Lending Divisional Unit: Lending and Investments". Those are substantive metadata. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we could include those as a short paragraph maybe under About the role or separate. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can include Department, Divisional Unit, Reports to as a short paragraph. Let's add a

    after About the role maybe. We also omitted "Job title: Commercial Lending Analyst" (we shouldn't repeat as heading). That's fine. We omitted "Starting Salary: $55,000-$60,000" we used in Pay. We omitted "PM22 Compensation details: 55000-60000 Yearly Salary PI000dd3538860-25448-41600333" - the latter part looks like a job ID; we drop it. We omitted "Physical Requirements" section. That's substantive info about ability to lift etc. Should we include? The instruction: include a section ONLY when the posting has real, specific content for it. Physical Requirements is specific content. Should we create a section? There's no predefined heading for Physical Requirements; we could fold into a

    maybe under Requirements or Skills? But it's not a standard heading. The instruction says 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

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for those categories; other info can be folded into paragraphs. So we can include Physical Requirements as a paragraph under maybe Requirements or a separate

    titled? But we cannot create a heading like Physical Requirements unless we want to, but the instruction suggests we should prefer those headings. However we could still add a

    Physical Requirements

    if we want, but it's not in the list; but the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it