Loan Scanner, Multiple Locations
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - Locations list: multiple addresses. Could be considered "Locations" but not a required heading; we can embed in a paragraph. - Essential duties and responsibilities: list of duties. - Requirements: list. - Preferred skills and qualifications: bilingual Spanish a plus. - Physical requirements: list. - Hours: Full Time M-F. - Benefits: mention "Employees enjoy excellent benefits" but not specific. Not specific enough to create Benefits section? The rule: never create Benefits section unless posting actually states them. It says "Employees enjoy excellent benefits" but no specifics. Likely not enough to create Benefits section. So we skip Benefits. - Pay: not mentioned. - Schedule: "Full Time M-F" is schedule info. So we can create Schedule section with that. - About the role: maybe we can have a brief paragraph summarizing role? The posting includes "Loan Scanner" and locations. Could create About the role paragraph describing the job: scanning loan documents, compliance, communication, etc. But we already have Responsibilities. The About the role could be a short summary: "The Loan Scanner position involves scanning and indexing loan documents, ensuring compliance, communicating with customers, preparing correspondence, and performing related duties." That's derived from duties. It's not invented; it's summarizing but we must not summarize away detail? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing may be okay if we keep all details? But we already have Responsibilities list with details. About the role could be a brief overview but might be considered summarizing. Safer to not include About the role if we already have Responsibilities covering details. However we need to decide which sections to include: Responsibilities, Requirements, Qualifications (maybe Preferred skills), Skills (maybe physical requirements?), Schedule. We have: - Responsibilities: list of duties. - Requirements: list of qualifications (high school, MS Office, communication, etc.) - Preferred skills: bilingual Spanish a plus. - Physical requirements: could be under Qualifications or Skills. Could create a Skills section for physical requirements? But physical requirements are not skills. Could create a Qualifications section that includes both requirements and physical requirements? The instruction: Use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (mandatory) and Qualifications (preferred). Skills could be for physical requirements? Or we could put physical requirements under Skills? Might be okay. Better: Use Requirements for mandatory qualifications, Qualifications for preferred skills (bilingual), Skills for physical requirements? But physical requirements are not skills. However we can still put them under Skills as they are abilities. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one Requirements section? But we have both mandatory and preferred. Could create Requirements (mandatory) and Qualifications (preferred). Skills maybe not needed. We also have Hours: Full Time M-F -> Schedule. We also have Locations: could be a short paragraph under About the role? Or we could include a Locations paragraph but no heading for Locations (not in allowed headings). Could embed in a paragraph under About the role or as a separate
without heading. We must not include boilerplate like EEO, etc. Thus output HTML:
Responsibilities
- Scan and index loan documents ... etc.
- High School Graduate or High School equivalency ... etc.
- Bilingual (Spanish) a plus
- Constant use of computer screens and reading of reports ... etc (physical requirements). Might be too detailed but okay.
- Scan and index loan documents
- Ensure compliance with regulations and BancFirst policies and procedures
- Customer communication on the phone and in person
- Clear loan exceptions
- Prepare written correspondence
- Perform other duties and projects as assigned
- High School Graduate or High School equivalency
- Proficient in Microsoft Office and knowledge of, or the ability to quickly learn, banking software applications
- Excellent communication skills, both written and verbal
- Strong organizational skills and an ability to multitask with accuracy
- Critical thinking skills
- Must work well under stress and deadlines
- Work well individually and with team members while maintaining a positive attitude
- Must demonstrate a business professional image and demeanor
- Excellent work ethic
- Must be flexible and able to work additional hours when crucial to the branch environments
- Regular attendance and punctuality is an essential function of the job
- Bilingual (Spanish) a plus
- Constant use of computer screens and reading of reports
- Ability to operate a computer keyboard, multi-line telephone, photocopier, scanner and facsimile
- Regularly required to sit, use hand to finger, handle or feel, reach with hands and arms, and talk, see or hear
- Intermittently standing, stooping, bending at the waist, walking, kneeling or crouching to file materials
- Regularly lift and/or move and carry up to 10 pounds
- BancFirst, Prague – 902 W Main St., Prague, OK 74864
- BancFirst, Okemah – 402 W Broadway St., Okemah, OK 74859
- BancFirst, Chandler – 1001 Manvel Ave., Chandler, OK 74834
- BancFirst, Kingfisher – 124 S Main St., Kingfisher, OK 73750
- BancFirst, Prague – 902 W Main St., Prague, OK 74864
- BancFirst, Okemah – 402 W Broadway St., Okemah, OK 74859
- BancFirst, Chandler – 1001 Manvel Ave., Chandler, OK 74834
- BancFirst, Kingfisher – 124 S Main St., Kingfisher, OK 73750
- Scan and index loan documents
- Ensure compliance with regulations and BancFirst policies and procedures
- Customer communication on the phone and in person
- Clear loan exceptions
- Prepare written correspondence
- Perform other duties
Requirements
Qualifications
Skills
Schedule
Full Time, Monday‑Friday
We might also include an introductory paragraph about the role and locations before sections. Could add adescribing the role and locations. But we must not repeat job title as heading. The job title is "Loan Scanner". Not needed. Let's craft:
Loan Scanner positions are available at BancFirst branches in Prague, Okemah, Chandler, and Kingfisher, Oklahoma.
Then sections. Check for any other specifics: "Hometown service, statewide strength. BancFirst is a $13 billion bank offering personal and commercial products, trust, insurance, and investment services in sixty Oklahoma communities. Employees enjoy excellent benefits and a learning environment that allows them to continuously improve their skills to deliver highly personalized service to customers." This is boilerplate-ish but could be considered About the role? It's generic. Might be considered boilerplate; we should remove. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those but could be considered fluff. Better to omit. Thus final HTML:Loan Scanner positions are available at BancFirst branches in Prague, Okemah, Chandler, and Kingfisher, Oklahoma.
Responsibilities
Requirements
Qualifications
Skills
Schedule
Full Time, Monday‑Friday
Check for any duplicated lines: none. We omitted locations list details? We included a short sentence referencing locations. Could also include the addresses in abut that might be too detailed but we can include as a paragraph. The instruction: Preserve ALL substantive information. The addresses are substantive. Should we include them? Yes, we should preserve all substantive information. The locations list is substantive. So we should include them. We can put them in a
after the intro. Thus:
Locations:
introducing and then a
- list.
Thus final HTML includes that list.
Check for any other substantive info: "While the position is regional, regular and routine bank to bank travel is not anticipated." That's substantive about travel. Should we include? Could add a
under Responsibilities maybe? Or a separate paragraph after Responsibilities. Since we have no heading for Travel, we can add a
after Responsibilities: "While the position is regional, regular and routine bank to bank travel is not anticipated." Also "Hometown service, statewide strength..." is fluff; we can omit. Also "BancFirst is a $13 billion bank offering personal and commercial products, trust, insurance, and investment services in sixty Oklahoma communities." That's generic; could be omitted as boilerplate? It's not exactly boilerplate but could be considered company description. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. It's company info. Might be considered substantive? It's about the bank. Could be included in an About the role paragraph. But we already have intro. Might be okay to include a short
about BancFirst. However we risk adding fluff. The instruction says prefer a few substantive sections over many thin ones. This is not a section but a paragraph. Might be okay to include as part of About the role. But we don't have About the role heading. Could add a
after the locations: "BancFirst is a $13 billion bank offering personal and commercial products, trust, insurance, and investment services in sixty Oklahoma communities." That's substantive. But we must not invent or summarize away detail. It's fine. Also "Employees enjoy excellent benefits and a learning environment that allows them to continuously improve their skills to deliver highly personalized service to customers." That's benefits but vague; we already decided not to create Benefits section. Could include as a
under maybe a generic paragraph. But we risk adding fluff. The instruction: "Prefer a few substantive sections over many thin ones." Adding many small paragraphs may be thin. Better to keep only essential: locations, responsibilities, requirements, qualifications, skills, schedule. The company description may be considered fluff. I'd omit. Travel note: "While the position is regional, regular and routine bank to bank travel is not anticipated." That's substantive about travel expectations. Could add as a
after Responsibilities. Thus final HTML:
Loan Scanner positions are available at BancFirst branches in Prague, Okemah, Chandler, and Kingfisher, Oklahoma.