Part-Time Float Teller (Tu/Th/F/S) - Hudsonville
maybe. Who we are: paragraph. About this position: paragraph. What you’ll do: list of duties; we can break into sections: Member Experience, Transaction Processing and Cash Handling, Product Promotion/Growth, Learning & Development. Could be under Responsibilities. What you’ll bring: requirements: experience, education. What you’ll get: benefits: weekly pay and retirement savings options for all employees; full-time employees get comprehensive health coverage etc. Since this is part-time position, but they still list benefits. We need to include Benefits section if there is real specific content. There is: weekly pay and retirement savings options for all employees; full-time employees get health coverage etc. Since the role is part-time, but still mention benefits. We can include Benefits section with that info. Pay: weekly pay mentioned. Schedule: Part-Time (Tu/Th/F/S) given. So we can include Schedule section. We must not include sections with filler like "commensurate with experience". Not present. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. The job title is Teller. Not to put as heading.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reorganize.
We need to remove boilerplate: "General Information Primary Location: Hudsonville Employee Status: Part-Time (Tu/Th/F/S) Workplace Type: Fully On-Site". We can fold into a short
maybe: "Location: Hudsonville. Employment type: Part-Time (Tuesday, Thursday, Friday, Saturday). Workplace: Fully on-site."
We need to keep "Who we are:" paragraph.
"About this position:" paragraph.
"What you’ll do:" we need to break into sub-sections? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings exactly if we have content. So we need to map content to those headings.
Thus we need sections: About the role (maybe corresponds to "About this position:" and "Who we are:"? Actually "About the role" could be the description of the position. We'll put the "About this position:" paragraph there.
Responsibilities: combine "What you’ll do:" content.
Requirements: maybe "What you’ll bring:" (experience, education). Could be Requirements.
Qualifications: maybe similar to Requirements; but we can combine or separate if we have distinct content. The posting says: "A minimum of one year up to three years of similar or related experience, including preparatory experience. Previous cash handling experience and knowledge of financial products and services preferred. High school diploma or equivalent (required); some college coursework or banking experience is a plus." That's qualifications. We could put under Requirements or Qualifications. Since we have both headings, we need to decide which to use. We could put experience under Requirements and education under Qualifications. But we must not create thin sections; better to combine into one section, maybe Requirements, and omit Qualifications if no distinct content. However we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we can combine into Requirements and skip Qualifications.
Skills: maybe we can extract skills from responsibilities: member experience, transaction processing, product promotion, learning & development. Could be a Skills section. But we already have Responsibilities covering duties; Skills could be separate list of skills like "Cash handling, fraud prevention, product knowledge, consultative communication, etc." Might be thin. Better to omit Skills if not distinct.
Benefits: we have content.
Pay: we have weekly pay.
Schedule: we have part-time schedule.
Thus we will output sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
We need to ensure we don't include empty sections.
Now we need to format.
We'll start with a
for location metadata.
Then
About the role
then with the "About this position:" paragraph (maybe also include "Who we are:"? Actually "Who we are:" is about the company, not the role. Could be included in About the role? Might be better to include as part of About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put the description of the role there, maybe also include "Who we are:" as part of it? But "Who we are:" is about the company, not the role. Could be placed in a separate
before the heading? The instruction says do not repeat job title as heading; doesn't forbid other paragraphs before headings. We'll include a short
for location and maybe a
for "Who we are:" as a general intro. Then headings.
Let's extract exact text:
Who we are: "At LMCU, you'll find more than just a job - discover a fulfilling career where your contributions truly matter. Join our talented team at Lake Michigan Credit Union and discover the difference an employer who puts people first can make in your career and life."
About this position: "The Teller is the face of LMCU, responsible for creating a warm and welcoming member experience while accurately processing a high volume of transactions. This position requires a strong focus on service excellence, member retention, and promoting LMCU’s products and services to help all members achieve dreams for a lifetime. Tellers serve as the first line of defense to mitigate fraud and protect LMCU and our members. Tellers are key contributors to the success of the branch by providing exceptional service, maintaining accuracy in transactions, and driving the growth of the organization by utilizing their broad knowledge of LMCU products and services to best position our members to meet their financial needs and dreams."
What you’ll do: bullet-like sentences but not formatted as list. We need to convert to
- . We'll break each sentence or clause.
Member Experience:
- Promote a positive member experience leading to member retention through proactive engagement, building trusting relationships with members.
- Identify and address member needs, offering information and guidance about products and services that align with their financial goals.
- Provide friendly, professional, and efficient service to all members, ensuring a high level of satisfaction.
- Resolve conflicts and de-escalate adverse situations, ensuring positive outcomes for both members and LMCU.
Transaction Processing and Cash Handling:
- Accurately perform basic and advanced teller transactions in accordance with LMCU’s policies and procedures. Transactions include deposits, withdrawals, transfers, loan payments, check cashing, check ordering, and wire requests.
- Maintain and balance a cash drawer daily, ensuring that all cash assigned, received, and disbursed is accounted for.
- Consistently demonstrate accuracy and attention to detail when processing transactions to ensure smooth daily operations.
- Demonstrate strong risk management practices, including knowledge of fraud prevention guidelines and robbery procedures.
- Utilize resources, best practices and consultative conversations to identify red flags for risk and fraud prevention.
- Ensure compliance with LMCU policies, procedures, and regulatory requirements, including handling cash, processing transactions, and managing member data and monitoring for fraudulent activity.
- Adhere to all security protocols, ensuring the safety of both members and employees in the branch environment.
Product Promotion/Growth:
- Demonstrate and apply in-depth knowledge of all LMCU products and services, including their benefits and features.
- Ability to compellingly present solutions to members’ financial needs that are uncovered through consultative conversations.
- Actively identify opportunities to refer members to appropriate products and services based on their financial needs.
- Contribute to branch goals by meeting individual referral and service targets, driving the growth of the organization through member education and product promotion.
Learning & Development:
- Continuously improve knowledge of LMCU products, services, policies and systems through regular training and self-development.
- Identify opportunities to educate members on the features and benefits of LMCU’s digital platforms helping them leverage technology to meet their banking needs, keeping members up to date on emerging technology.
- Responsible for staying up-to-date on all branch systems, operations, and technology to provide accurate and efficient service.
What you’ll bring:
- A minimum of one year up to three years of similar or related experience, including preparatory experience.
- Previous cash handling experience and knowledge of financial products and services preferred.
- High school diploma or equivalent (required); some college coursework or banking experience is a plus.
What you’ll get:
- All Employees: weekly pay and retirement savings options.
- Full Time Employees: comprehensive health coverage including medical (with prescription), dental, vision, HSA match, paid parental leave, and tuition reimbursement.
- To see a full list of our benefit offerings, check out this helpful guide! (This is a link/instruction; maybe we should remove as it's application instruction? It's about benefits guide; could be considered boilerplate? It's a reference to a guide; maybe we keep as part of benefits? It's not essential detail but it's a reference. The instruction says remove application instructions; this is not exactly application instruction but a link to guide. Might be considered boilerplate; safer to omit.
Also we have "Have additional questions about the role? Email the Talent Acquisition Team at: Careers@lmcu.org. If you lack access to the internet or require an accommodation in the application process, please send your resume via mail to PO BOX 2848 Grand Rapids, MI 49501." Remove.
Also "LMCU is an Equal Opportunity Employer" remove.
Now we need to map to sections.
About the role: Could combine Who we are and About this position? Might be too much. But we can put About this position under About the role. Who we are could be a preceding
about company. That's fine.
Responsibilities: all What you’ll do content.
Requirements: What you’ll bring content.
Benefits: What you’ll get content (weekly pay and retirement savings options; full-time health coverage etc). Since the role is part-time, but we still include.
Pay: weekly pay mentioned; but we already included in Benefits. However we need a Pay section if we have specific pay info. The posting says "weekly pay". So we can have Pay section with that detail. Benefits section can then focus on retirement savings options and health coverage etc. But we need to avoid duplication. Let's split: Benefits: retirement savings options, health coverage etc. Pay: weekly pay. Schedule: Part-Time (Tu/Th/F/S). We'll also include location maybe in a preceding
.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
Now we need to ensure we don't include filler like "not specified". All good.
Now produce HTML fragment.
We'll start with a
for location and maybe company intro.
Let's craft:
Location: Hudsonville. Employment type: Part-Time (Tuesday, Thursday, Friday, Saturday). Workplace: Fully on-site.
Who we are: At LMCU, you'll find more than just a job - discover a fulfilling career where your contributions truly matter. Join our talented team at Lake Michigan Credit Union and discover the difference an employer who puts people first can make in your career and life.
Then headings.
About the role
The Teller is the face of LMCU, responsible for
for prose. We must not repeat job title as heading. The job title is Teller. Not to put as heading. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reorganize. We need to remove boilerplate: "General Information Primary Location: Hudsonville Employee Status: Part-Time (Tu/Th/F/S) Workplace Type: Fully On-Site". We can fold into a short
maybe: "Location: Hudsonville. Employment type: Part-Time (Tuesday, Thursday, Friday, Saturday). Workplace: Fully on-site." We need to keep "Who we are:" paragraph. "About this position:" paragraph. "What you’ll do:" we need to break into sub-sections? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings exactly if we have content. So we need to map content to those headings. Thus we need sections: About the role (maybe corresponds to "About this position:" and "Who we are:"? Actually "About the role" could be the description of the position. We'll put the "About this position:" paragraph there. Responsibilities: combine "What you’ll do:" content. Requirements: maybe "What you’ll bring:" (experience, education). Could be Requirements. Qualifications: maybe similar to Requirements; but we can combine or separate if we have distinct content. The posting says: "A minimum of one year up to three years of similar or related experience, including preparatory experience. Previous cash handling experience and knowledge of financial products and services preferred. High school diploma or equivalent (required); some college coursework or banking experience is a plus." That's qualifications. We could put under Requirements or Qualifications. Since we have both headings, we need to decide which to use. We could put experience under Requirements and education under Qualifications. But we must not create thin sections; better to combine into one section, maybe Requirements, and omit Qualifications if no distinct content. However we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we can combine into Requirements and skip Qualifications. Skills: maybe we can extract skills from responsibilities: member experience, transaction processing, product promotion, learning & development. Could be a Skills section. But we already have Responsibilities covering duties; Skills could be separate list of skills like "Cash handling, fraud prevention, product knowledge, consultative communication, etc." Might be thin. Better to omit Skills if not distinct. Benefits: we have content. Pay: we have weekly pay. Schedule: we have part-time schedule. Thus we will output sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We need to ensure we don't include empty sections. Now we need to format. We'll start with a
for location metadata. Then
About the role
thenwith the "About this position:" paragraph (maybe also include "Who we are:"? Actually "Who we are:" is about the company, not the role. Could be included in About the role? Might be better to include as part of About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put the description of the role there, maybe also include "Who we are:" as part of it? But "Who we are:" is about the company, not the role. Could be placed in a separate
before the heading? The instruction says do not repeat job title as heading; doesn't forbid other paragraphs before headings. We'll include a short
for location and maybe a
for "Who we are:" as a general intro. Then headings. Let's extract exact text: Who we are: "At LMCU, you'll find more than just a job - discover a fulfilling career where your contributions truly matter. Join our talented team at Lake Michigan Credit Union and discover the difference an employer who puts people first can make in your career and life." About this position: "The Teller is the face of LMCU, responsible for creating a warm and welcoming member experience while accurately processing a high volume of transactions. This position requires a strong focus on service excellence, member retention, and promoting LMCU’s products and services to help all members achieve dreams for a lifetime. Tellers serve as the first line of defense to mitigate fraud and protect LMCU and our members. Tellers are key contributors to the success of the branch by providing exceptional service, maintaining accuracy in transactions, and driving the growth of the organization by utilizing their broad knowledge of LMCU products and services to best position our members to meet their financial needs and dreams." What you’ll do: bullet-like sentences but not formatted as list. We need to convert to
- . We'll break each sentence or clause.
Member Experience:
- Promote a positive member experience leading to member retention through proactive engagement, building trusting relationships with members.
- Identify and address member needs, offering information and guidance about products and services that align with their financial goals.
- Provide friendly, professional, and efficient service to all members, ensuring a high level of satisfaction.
- Resolve conflicts and de-escalate adverse situations, ensuring positive outcomes for both members and LMCU.
Transaction Processing and Cash Handling:
- Accurately perform basic and advanced teller transactions in accordance with LMCU’s policies and procedures. Transactions include deposits, withdrawals, transfers, loan payments, check cashing, check ordering, and wire requests.
- Maintain and balance a cash drawer daily, ensuring that all cash assigned, received, and disbursed is accounted for.
- Consistently demonstrate accuracy and attention to detail when processing transactions to ensure smooth daily operations.
- Demonstrate strong risk management practices, including knowledge of fraud prevention guidelines and robbery procedures.
- Utilize resources, best practices and consultative conversations to identify red flags for risk and fraud prevention.
- Ensure compliance with LMCU policies, procedures, and regulatory requirements, including handling cash, processing transactions, and managing member data and monitoring for fraudulent activity.
- Adhere to all security protocols, ensuring the safety of both members and employees in the branch environment.
Product Promotion/Growth:
- Demonstrate and apply in-depth knowledge of all LMCU products and services, including their benefits and features.
- Ability to compellingly present solutions to members’ financial needs that are uncovered through consultative conversations.
- Actively identify opportunities to refer members to appropriate products and services based on their financial needs.
- Contribute to branch goals by meeting individual referral and service targets, driving the growth of the organization through member education and product promotion.
Learning & Development:
- Continuously improve knowledge of LMCU products, services, policies and systems through regular training and self-development.
- Identify opportunities to educate members on the features and benefits of LMCU’s digital platforms helping them leverage technology to meet their banking needs, keeping members up to date on emerging technology.
- Responsible for staying up-to-date on all branch systems, operations, and technology to provide accurate and efficient service.
What you’ll bring:
- A minimum of one year up to three years of similar or related experience, including preparatory experience.
- Previous cash handling experience and knowledge of financial products and services preferred.
- High school diploma or equivalent (required); some college coursework or banking experience is a plus.
What you’ll get:
- All Employees: weekly pay and retirement savings options.
- Full Time Employees: comprehensive health coverage including medical (with prescription), dental, vision, HSA match, paid parental leave, and tuition reimbursement.
- To see a full list of our benefit offerings, check out this helpful guide! (This is a link/instruction; maybe we should remove as it's application instruction? It's about benefits guide; could be considered boilerplate? It's a reference to a guide; maybe we keep as part of benefits? It's not essential detail but it's a reference. The instruction says remove application instructions; this is not exactly application instruction but a link to guide. Might be considered boilerplate; safer to omit.
Also we have "Have additional questions about the role? Email the Talent Acquisition Team at: Careers@lmcu.org. If you lack access to the internet or require an accommodation in the application process, please send your resume via mail to PO BOX 2848 Grand Rapids, MI 49501." Remove.
Also "LMCU is an Equal Opportunity Employer" remove.
Now we need to map to sections.
About the role: Could combine Who we are and About this position? Might be too much. But we can put About this position under About the role. Who we are could be a preceding
about company. That's fine. Responsibilities: all What you’ll do content. Requirements: What you’ll bring content. Benefits: What you’ll get content (weekly pay and retirement savings options; full-time health coverage etc). Since the role is part-time, but we still include. Pay: weekly pay mentioned; but we already included in Benefits. However we need a Pay section if we have specific pay info. The posting says "weekly pay". So we can have Pay section with that detail. Benefits section can then focus on retirement savings options and health coverage etc. But we need to avoid duplication. Let's split: Benefits: retirement savings options, health coverage etc. Pay: weekly pay. Schedule: Part-Time (Tu/Th/F/S). We'll also include location maybe in a preceding
. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Now we need to ensure we don't include filler like "not specified". All good. Now produce HTML fragment. We'll start with a
for location and maybe company intro. Let's craft:
Location: Hudsonville. Employment type: Part-Time (Tuesday, Thursday, Friday, Saturday). Workplace: Fully on-site.
Who we are: At LMCU, you'll find more than just a job - discover a fulfilling career where your contributions truly matter. Join our talented team at Lake Michigan Credit Union and discover the difference an employer who puts people first can make in your career and life.
Then headings.About the role
The Teller is the face of LMCU, responsible for