Part Time Teller Trainee Leominster Branch

We need to output HTML fragment with sections only when there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the job description and extract sections. Let's read the description: - Opening paragraph about Rockland Trust: description of company. Could be "About the role"? Actually "About the role" could be a summary of the role. The description includes: "As a Teller Trainee at Rockland Trust, you are at the heart of our branches..." That's role description. So we can put that under

About the role

with paragraphs. - Then "What You’ll Experience" includes bullet-like statements: Meaningful relationships, Commitment to community, Recognition & reward, Training & development, Comprehensive benefits: list of benefits. This could be under Benefits? Actually it's more about what you'll experience (culture, benefits). Could be split: maybe "Benefits" section for benefits list, and maybe "About the role" for other experience? But we need to follow headings list. We have Benefits, Pay, Schedule, Skills, Qualifications, Requirements, Responsibilities, About the role. We need to decide where each piece goes. Responsibilities: there is a "What You’ll Do" section with bullet points (Make the first impression..., Engage..., Serve..., Ensure..., Make decisions..., Work closely..., Perform any other duties...). That's responsibilities. Qualifications: there is "Required Qualifications" list (high school diploma, communication skills, comfortable using tech, sales/service-oriented, professional appearance, positive approach, ability to work normal office req with standing, ability to lift up to 50 lbs, willingness to work flexible week inc weekends, ability to complete training). That's qualifications. Preferred Skills/Experience: "Candidates should have 1-2 years prior teller experience or cash handling/customer service skills." That's skills. Benefits: there are two benefits sections: one under "What You’ll Experience" (Comprehensive benefits: list includes competitive compensation with performance incentive awards, Health Insurance, Dental Insurance, Vision and Pet Insurance, 401K retirement plan, Long Term Disability & Life Insurance, Child Care Reimbursement, Tuition Assistance for graduate and undergraduate programs, an award winning wellness program and much more.) Then later "Benefits & Culture" repeats similar: competitive compensation with performance-based incentive awards, health and dental insurance, a 401(k) and DC retirement plan, LTD and life insurance, paid vacation, day care reimbursement, tuition assistance for undergraduate and graduate programs, an award-winning wellness program, and much more! So we need to combine benefits info, preserving all substantive info, not duplicating? We should preserve all info but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say to deduplicate, but we should not repeat duplicated lines. It says "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 combine benefits, removing duplicate statements. Let's list unique benefits: - competitive compensation with performance incentive awards (or performance-based incentive awards) – essentially same. - Health Insurance - Dental Insurance - Vision and Pet Insurance - 401K retirement plan (or 401(k) and DC retirement plan) – we can note both 401K and DC. - Long Term Disability & Life Insurance (LTD and life insurance) - Child Care Reimbursement (day care reimbursement) - Tuition Assistance for graduate and undergraduate programs - award winning wellness program (award-winning wellness program) - Paid vacation (mentioned only in second) - Possibly "much more" but that's vague; we can keep phrase "and much more" but it's not specific. Might be considered filler? It's not a specific benefit; but it's part of the benefits description. The instruction: 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. "and much more" is vague but not a placeholder like TBD; it's just saying there are more benefits. It's okay to keep. Pay: There is a "Pay Transparency" section: "Compensation for this role will be based on a variety of factors, including skills, experience, education, and internal equity. The salary range posted reflects the company’s good-faith estimate of the range for this position at the time of posting. Actual compensation may vary. In addition to base salary, certain positions may be eligible for additional compensation, including commissions, incentive awards or stipends." This is pay info. So we need a Pay section with that content. Schedule: Not mentioned explicitly. There's mention of flexible work week, may include weekends. That's schedule info. Could be placed under Schedule heading. The posting says: "Willingness and ability to work within a flexible work week, which may include weekends, as customer needs dictate." That's schedule. So we can create a Schedule section with that sentence. Skills: we have Preferred Skills/Experience: 1-2 years prior teller experience or cash handling/customer service skills. Also maybe "Strong verbal and written communication skills" is under qualifications but could also be skill. But we already have qualifications. We'll put preferred skills under Skills heading. Requirements: Could be same as Qualifications? The headings list includes both Requirements and Qualifications. Usually Requirements are mandatory, Qualifications are preferred? But we have Required Qualifications and Preferred Skills/Experience. We could map Required Qualifications to Requirements heading, and Preferred Skills/Experience to Skills heading. Qualifications heading maybe we could use for something else? But we have both Required Qualifications and Preferred Skills/Experience. The instruction: Use headings only when posting has real, specific content for it. So we need to decide if we need both Requirements and Qualifications sections. We have Required Qualifications (mandatory) and Preferred Skills/Experience (preferred). We could treat Required Qualifications as Requirements, and Preferred Skills/Experience as Skills. Then we might not need a Qualifications heading unless there is other qualification content not covered. There's also "Who We Are" etc but that's company info not role-specific. Could be About the role? Actually About the role could include company overview? But we already have About the role for role description. The company overview could be placed under About the role as well? But the instruction: About the role heading for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can put company overview under About the role? Might be okay. However the description already has a paragraph about Rockland Trust at start, then "As a Teller Trainee..." etc. So we could combine that into About the role. Let's structure:

About the role

Rockland Trust is a full-service commercial bank ... (the initial paragraph about company) ... As a Teller Trainee at Rockland Trust, you are at the heart of our branches and the frontline of customer service, proactively exploring customer needs and offering personalized advice that serves to develop and maintain relationships. Each day, you create a memorable experience for customers whilst contributing to the fulfillment of branch and company goals in a meaningful way. With a positive, can-do attitude and a genuine desire to work with customers in a caring and empathetic way, you are responsible for providing efficient, effective, and courteous customer service while performing a variety of transactions. You are the friendly face of Rockland Trust, promoting our mission and helping customers navigate the world of banking.

But we need to ensure we don't duplicate content. The "What You’ll Experience" section includes statements about Meaningful relationships, Commitment to community, Recognition & reward, Training & development, Comprehensive benefits. Those are more about culture/benefits. Could be placed under Benefits or maybe under About the role as well? But we have a Benefits heading for benefits list. The "What You’ll Experience" also includes non-benefit items like Meaningful relationships, Commitment to community, Recognition & reward, Training & development. Those could be considered part of culture/benefits but not strictly benefits. However we don't have a Culture heading. Could we put them under About the role? Might be okay. But we need to preserve all substantive info. We could create a separate section for "What You’ll Experience" but not in allowed headings. So we must fit into allowed headings. The allowed headings are limited; we cannot create custom headings. So we need to map content to those headings. We have: - About the role: role description and maybe company overview. - Responsibilities: What You’ll Do list. - Requirements: Required Qualifications list. - Skills: Preferred Skills/Experience. - Benefits: benefits list (from both sections). - Pay: Pay Transparency paragraph. - Schedule: flexible work week statement. - Qualifications: maybe we could use for something else like "Who We Are" or "What You’ll Experience" non-benefit items? But we already used About the role for role description; we could put company overview and "What You’ll Experience" non-benefit items under Qualifications? That seems odd. Better: Use Qualifications heading for the "What You’ll Experience" items that are not benefits but about culture/training etc. But the heading name "Qualifications" suggests qualifications of candidate, not culture. However the instruction says we can use these headings only if posting has real, specific content for it. It doesn't strictly define meaning; we just need to use them as section headings. So we could put "What You’ll Experience" content under Qualifications heading, but that might be misleading but still follows instruction? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but doesn't restrict meaning. So we can use Qualifications for any section as long as we have content. However typical usage: Qualifications for candidate qualifications. But we already have Requirements for mandatory qualifications. Could we have both Requirements and Qualifications? Possibly Requirements for mandatory, Qualifications for preferred? But we already have Skills for preferred skills. Hmm. We could assign: - Requirements: Required Qualifications (mandatory) - Qualifications: Preferred Skills/Experience (preferred) - but we also have Skills heading; maybe we use Skills for something else like "Strong verbal and written communication skills"? But that's already in Required Qualifications. Better to follow typical pattern: Requirements = mandatory qualifications, Qualifications = preferred qualifications, Skills = specific skills (like technical skills). But we have limited content. Let's see: Required Qualifications list includes education, communication skills, tech comfort, sales/service-oriented, professional appearance, positive approach, ability to work normal office req with standing, lift up to 50 lbs, flexible week inc weekends, ability to complete training. Preferred Skills/Experience: 1-2 years prior teller experience or cash handling/customer service skills. Thus we could map: - Requirements: Required Qualifications (mandatory) - Qualifications: Preferred Skills/Experience (preferred) - Skills: maybe we could list specific skills like "cash handling", "customer service", "technology usage", "communication". But that would duplicate. Alternatively, we could combine Required Qualifications and Preferred Skills/Experience under Requirements and Qualifications respectively, and not use Skills heading (since we don't have distinct skills beyond those). But the instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if not substantive. But we have some skills content; we could put them under Skills. Let's think: The posting includes "Strong verbal and written communication skills." That's a skill. "Comfortable using technology, including computers, to facilitate the achievement of business goals." That's a skill. "Sales and service