DEAMS Deployment Senior Trainer

We need to output only HTML fragment, using

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. Must include sections only when posting has real specific content. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also must not include Pay/Schedule/Benefits sections unless posting actually states them. The posting includes salary range and benefits details, so we can include Pay and Benefits sections. Schedule? Not mentioned; no schedule info, so omit Schedule. Also include About the role? The posting includes description of role: "Kearney & Company is currently seeking a DEAMS Deployment Senior Trainer to join our DEAMS team. The successful candidate will interact with AF major commands and bases in support of the worldwide deployment, sustainment, and day-to-day operations of DEAMS." That's about the role. Could be "About the role". Also responsibilities list: many bullet points. Requirements: qualifications required and preferred. Skills: maybe we can include skills as part of qualifications? But we need a Skills section only if posting has real specific content for it. The posting mentions abilities: ability to analyze financial data using MS Office, ability to brief and communicate effectively, ability to obtain clearance, etc. Those could go under Skills. However we already have Requirements (Qualifications). Might combine required qualifications under Requirements, and preferred under Qualifications? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Typically Responsibilities = duties list. Requirements = mandatory qualifications. Qualifications = preferred qualifications? Skills = specific abilities. Benefits = benefits list. Pay = salary range. We must not create sections with filler like "commensurate with experience". We have actual content. We must not repeat job title as heading. So no

DEAMS Deployment Senior Trainer

. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About the role: The first paragraph: "Kearney & Company is currently seeking a DEAMS Deployment Senior Trainer to join our DEAMS team. The successful candidate will interact with AF major commands and bases in support of the worldwide deployment, sustainment, and day-to-day operations of DEAMS. The candidate will demonstrate solid technical and functional experience." That's about role. Responsibilities: The list after "Other responsibilities may include:" includes many bullet points. Let's list them: - Act as the initial DEAMS Functional Management Office (FMO) representative to the deploying bases, briefing the Base POC, RAs, etc., on DEAMS and the planned deployment to their base - Assist with base Site Profile distribution and collection of end user and financial data; analyze the data, organize, and participate in site visits - Support DFAS and AF (AD, AFRC & ANG) DEAMS end users in registering for DEAMS and assist in identifying required training - Facilitate user set-up and assignment of system Roles and Responsibilities - Coordinate training activities with assigned bases - Manage comprehensive checklist of deployment and cutover tasks - Provide targeted assistance to users based on DEAMS metrics, recurring critical task results, and results of other data analysis - Provide ad hoc and on-the-job training to DEAMS users via telephone, video-teleconference, webinar, or on-site visit (when local), to include general training for new users and functional problem areas - Collect and submit deployment related metrics - Facilitate and promote Strategic Communications/Change Management activities - Assist with DEAMS Discoveries/Lessons Learned activities at the deployed base That's responsibilities. Requirements (mandatory qualifications): Listed under "Qualifications Required Qualifications". Actually they have "Required Qualifications" then bullet list: - Minimum 3.5 years direct DEAMS experience - Experience in AF Funds Control, Accounting, Financial Analysis, Accounts Payable, Government Purchase Card, or Defense Finance and Accounting Service - Ability to analyze financial data using Microsoft Office products, including Excel and Access, as well as the ability to create and use PivotTables and complex functions - Candidate must be willing and able to travel as part of DEAMS Deployment as required or to support sustainment activities for MAJCOM of assignment - up to 50% travel - Ability to brief and communicate effectively with senior leaders and managers - Ability to obtain and maintain a U.S. Secret level security clearance (requires US Citizenship) We could put these under Requirements. Preferred Qualifications: list under "Preferred Qualifications": - 10 years of experience - MA/MS degree - Knowledge of AF legacy systems and programs such as: (list many) - Other systems to consider include Automated Funds Management (AFM), Defense Travel System (DTS), G-Invoicing, Government Purchase Card (GPC), Job Order Cost Accounting System II (JOCAS II), and Wide Area Work Flow (WAWF) We could put these under Qualifications (as preferred). Or maybe under Qualifications heading. Skills: Could extract specific abilities like ability to analyze financial data using MS Office, ability to brief and communicate, ability to obtain clearance, etc. But those are already in requirements. Might be redundant. However we need to follow instruction: Use headings only when posting has real specific content for it. If we put skills same as requirements, might be duplication but still specific content. Could decide to not include Skills section if content overlaps heavily; but we could still include Skills with items like "Ability to analyze financial data using Microsoft Office products (Excel, Access), create and use PivotTables and complex functions", "Ability to brief and communicate effectively with senior leaders and managers", "Ability to obtain and maintain a U.S. Secret level security clearance". That's specific. But we already have those in Requirements. Might be okay to have both sections; but we must not invent or summarize away detail. Duplication is okay as long as we preserve all info. However we should avoid unnecessary thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to combine required qualifications and skills into one section? But headings are prescribed; we can still use them but we need to decide which sections to include. If we include both Requirements and Skills, we might be splitting content thinly. Better to include Requirements (mandatory) and Qualifications (preferred) and maybe Skills not needed. However the instruction says we can use those headings; we are not forced to use all. So we can omit Skills if not needed. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if we have Schedule: none. Now Benefits: The posting lists benefits: "Medical, Dental, Vision, Life, AD&D, and Disability Insurance 401(k) Retirement Plan and 529 Education Savings Plan Flexible Spending & Health Savings Account Accident, Critical Illness, Hospital Indemnity Insurances Legal Insurance and Pet Insurance Employee Assistance Program, fitness and wellness benefits, and other firm benefits. Paid holidays, vacation, and sick time". Also mention bonuses eligibility. We'll capture that. Pay: Salary range $69,000 to $105,000, base pay only, plus note about bonuses eligibility. We must not include boilerplate like EEO notice, FMLA, EPPA, accommodation request, etc. Also remove "Overview Exclusively focused on the Government..." paragraph? That's about company overview; might be considered boilerplate? It's not strictly legal/EEO but it's generic company description. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The overview paragraph is not explicitly listed but could be considered boilerplate? It's about the firm; might be considered part of job posting but not essential substantive info about the role. However it's not duplicated lines; it's descriptive. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The overview is substantive about the company; but maybe it's considered boilerplate? Not sure. Usually they want to keep role-specific info, not generic company description. The overview says "Exclusively focused on the Government, Kearney & Company provides financial services, including auditing, consulting, and technology services. Our commitment to our employees and clients as well as to dedication and trust, critical values to our Firm, have led to Kearney’s recognition as one of the leading accounting firms in the country. Based on our employees’ feedback, we are also consistently rated a Best Place to Work. Employment at Kearney means a flexible, collaborative, and open-minded work environment. We hope it is your “first easy decision.” Learn more at www.kearneyco.com/careers." This is generic marketing; could be considered boilerplate. I'd lean to remove it as it's not specific to the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those categories, but it's still generic fluff. Might be safe to keep? However they said "Preserve ALL substantive information". This is substantive about the company but not about the role. I'd keep it maybe under About the role? But About the role already has role description. Could add a paragraph about company overview under About the role? Might be okay. However the instruction says "Prefer a few substantive sections over many thin ones." Adding a company overview may be thin. I'd omit it to keep focused. Thus final HTML:

About the role

Kearney & Company is currently seeking a DEAMS Deployment Senior Trainer to join our DEAMS team. The successful candidate will interact with AF major commands and bases in support of the worldwide deployment, sustainment, and day-to-day operations of DEAMS. The candidate will demonstrate solid technical and functional experience.

Responsibilities

• Act as the initial DEAMS Functional Management Office (FMO) representative to the deploying bases, briefing the Base POC, RAs, etc., on DEAMS and the planned deployment to their base
• Assist with base Site Profile distribution and collection of end user and financial data; analyze the data, organize, and participate in site visits
• Support DFAS and AF (AD, AFRC & ANG) DEAMS end users in registering for DEAMS and assist in identifying required training
• Facilitate user set-up and assignment of system Roles and Responsibilities
• Coordinate training activities with assigned bases
• Manage comprehensive checklist of deployment and cutover tasks
• Provide targeted assistance to users based on DEAMS metrics, recurring critical task results, and results of other data analysis
• Provide ad hoc and on-the-job training to DEAMS users via telephone, video-teleconference, webinar, or on-site visit (when local), to include general training for new users and functional problem areas
• Collect and submit deployment related metrics
• Facilitate and promote Strategic Communications/Change Management activities
• Assist with DEAMS Discoveries/Lessons Learned activities at the deployed base

Requirements

• Minimum 3.5 years direct DEAMS experience
• Experience in AF Funds Control, Accounting, Financial Analysis, Accounts Payable, Government Purchase Card, or Defense Finance and Accounting Service
• Ability to analyze financial data using Microsoft Office products, including Excel and Access, as well as the ability to create and use PivotTables and complex functions
• Candidate must be willing and able to travel as part of DEAMS Deployment as required or to support sustainment activities for MAJCOM of assignment - up to 50% travel
• Ability to brief and communicate effectively with