Experienced Tax Professional
for Qualifications and then inside have
for required and
- for preferred? But we need to keep distinction? The instruction: "Use
- for each duty.
Requirements:
- for each required qualification.
Qualifications:
- for each preferred qualification.
Now About the role:
with the paragraph. Check for any duplicated lines: The responsibilities list had a run-on sentence missing punctuation; we need to separate. Let's craft. We must output only HTML fragment, no or . Use
headings. Let's write:
About the role
As a seasonal Experienced Tax Professional at H&R Block, you are a trusted advisor who helps clients navigate complex tax situations with confidence. You'll use your expertise to prepare accurate returns, uncover savings opportunities, and build lasting client relationships — backed by industry-leading training and technology, a competitive hourly rate, and an incentive plan that rewards your impact as you build your tax expertise and serve clients. Whether you're looking for meaningful seasonal work or a path to grow in tax and financial services, this is the place. This role is in-person at a local H&R Block tax office.
Responsibilities
- Prepare complete, accurate tax returns for clients with diverse and complex tax situations, including individual and business returns
- Conduct in-depth client interviews to understand financial situations, life changes, and tax implications — then provide clear, personalized recommendations
- Build trusted client relationships by delivering empathetic, consultative service and identifying tax savings opportunities and relevant H&R Block products
- Provide IRS support, tax notice assistance, and audit guidance to clients as needed
- Collaborate with team members, share knowledge, and contribute to a positive, client-focused office environment
Requirements
- Successful completion of the H&R Block Tax Knowledge Assessment
- Minimum 1 year of experience in tax preparation, accounting, finance, or bookkeeping, including preparing individual and business returns
- Experience working in a client‑facing, consultative, or advisory role
- Strong verbal and written communication skills, including the ability to explain tax concepts in client‑friendly language
- Must complete continuing education and meet all other IRS and applicable state requirements
- High school diploma / GED / equivalent required
Qualifications
- Bachelor’s degree in accounting, finance or a related field
- 5+ years of experience in tax preparation, accounting, finance, bookkeeping
- CPA or Enrolled Agent (EA), or other IRS Circular 230 credential
- Experience completing complex returns, tax planning, audit support, or tax notice resolution
- Familiarity with GoSystem or Ultratax software
- Familiarity with AI‑powered tools (e.g., Microsoft Copilot, ChatGPT)
- Experience in a consultative or advisory client relationship role (financial advising, insurance, or professional services)
Benefits
- Medical and prescription drug coverage (eligible for employee
- for each preferred qualification.
Now About the role:
- for each required qualification.
Qualifications:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have those headings. We need to map content. We have About the role -> About the role. Responsibilities -> Responsibilities. Requirements -> Could be "Required Qualifications"? Actually "Requirements" heading could be used for required qualifications. Then "Qualifications" heading could be for preferred qualifications? Or we could combine both under Qualifications and omit Requirements. But we have both sections; better to use Requirements for required qualifications, and Qualifications for preferred qualifications. That seems logical. Skills: Could we extract skills from qualifications? Eg strong verbal/written communication, ability to explain tax concepts, etc. But those are already in required qualifications. Could move them to Skills. However we must not lose info. Could put communication skills under Skills. But we also have other skills like familiarity with GoSystem, AI tools, etc. Those are preferred qualifications. Might be better to put them under Skills. But we need to preserve all info; we can split. Let's think: The posting includes "Required Qualifications" list includes items like experience, communication skills, continuing education, HS diploma. "Preferred Qualifications" includes degree, years, CPA/EA, experience with complex returns, familiarity with software, AI tools, consultative experience. We could map: - Requirements (h3) -> Required Qualifications list. - Qualifications (h3) -> Preferred Qualifications list. - Skills (h3) -> maybe communication skills, software familiarity, AI tools? But that would duplicate. Better to keep Requirements and Qualifications as separate headings, and not create Skills unless we have distinct skill items not covered. Since we have communication skills etc already in Requirements, we could still create Skills but would duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we skip Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if we have Benefits content: yes from Pay Range Information paragraph. Pay: pay range. Now we need to format. We must not include boilerplate like "Sponsored Job Hart-12103-HONOLULU HI" maybe drop as minor metadata. Also drop "1 - Enrollment in or completion of the H&R Block Income Tax Course or Tax Knowledge Assessment is neither an offer nor a guarantee of employment." That's a footnote; could be minor metadata; we could drop or include as a short p? It's minor metadata; we can drop. Also drop "Why work for us" paragraph? It's somewhat generic but includes purpose and culture; could be considered Benefits? But we already have Benefits from pay range. The "Why work for us" paragraph is more about culture; not specifically benefits. Could we include it under Benefits? Might be considered fluff. The instruction: remove duplicated lines, boilerplate, etc. This paragraph might be considered boilerplate? It's specific to H&R Block but still generic. However it's substantive about purpose and culture. Could we include as a separate section like "About the company"? Not in allowed headings. Could we fold into Benefits? Not ideal. Safer to drop it as it's not explicitly benefits, pay, schedule, etc. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not exactly those, but it's more marketing. Might be okay to keep? But we have limited headings; we could put it under Benefits as a description. However Benefits should be specific benefits; but we could include a
about culture under Benefits heading. Might be acceptable. But we already have Benefits from pay range info; we could add a
after the list. Let's extract benefits list: - Qualifying associates can enroll themselves and/or their eligible dependents in medical and prescription drug coverage; - can participate in the H&R Block Retirement Savings Plan (401(k) Plan), - the Employee Assistance Program, - (virtual) fitness center programs, - and the associate discount program; - are automatically enrolled in Business Travel Accident Insurance; - and receive Associate Tax Prep benefit. Also mention incentive compensation or short-term incentive plans. We'll make a
- with those items.
Pay:
Pay Range $16.00 - $80.00/Hr.
Now Responsibilities: we need