Business Operations and Human Resources Manager
The University of Georgia · Athens, GA · 1 mo ago
Human ResourcesFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About the University of Georgia", "About the College/Unit/Department", "Position Summary", "Knowledge, Skills, Abilities And/or Competencies", "Physical Demands", "Duties/Responsibilities". Also there is "Advertised Salary Commensurate with Experience" - we should not include Pay section because it's not specific (commensurate with experience). So omit Pay. Schedule: "Work Schedule Additional Schedule Information Monday through Friday, 8:00 am – 5:00 pm" - that's schedule info, we can include Schedule section. Benefits: "Benefits Eligible" mention but not details; we should not include Benefits unless specific. So omit Benefits.
We need headings using for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use those exact headings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use those exact headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems we should use those headings when appropriate. But we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those exact headings if we have content. However we have content like "About the University of Georgia" and "About the College/Unit/Department". Those are not exactly "About the role". But maybe we should map to "About the role"? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples, not an exhaustive list. Probably we can use appropriate headings like "About the University", "About the College/Unit/Department", "Position Summary", "Knowledge, Skills, Abilities", "Physical Demands", "Duties/Responsibilities", "Schedule". But they said use those examples; maybe they want us to use those exact headings when applicable. However we have no "About the role" but we have "Position Summary". Could use "About the role" as heading for position summary? Might be okay.
Better to follow instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should produce headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to include only sections that have real specific content. We have content for Responsibilities (Duties/Responsibilities). We have content for Requirements (Minimum Qualifications, Preferred Qualifications). We have content for Qualifications? Could be same as Requirements. We have Skills (Knowledge, Skills, Abilities). We have Schedule (Work Schedule). We have About the role? Could use "About the role" for Position Summary and maybe About the University/College? But we might combine.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information. So we need to include details: About the University of Georgia paragraph, About the College/Unit/Department (just mentions website?), Position Summary paragraph, Knowledge, Skills, Abilities list, Physical Demands details, Duties/Responsibilities with percentages, Schedule info.
We also have Minimum Qualifications and Preferred Qualifications.
We need to output only HTML fragment, no /, no markdown.
Let's structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those exact headings if we have content. However we have content like "About the University of Georgia" and "About the College/Unit/Department". Those are not exactly "About the role". But maybe we should map to "About the role"? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples, not an exhaustive list. Probably we can use appropriate headings like "About the University", "About the College/Unit/Department", "Position Summary", "Knowledge, Skills, Abilities", "Physical Demands", "Duties/Responsibilities", "Schedule". But they said use those examples; maybe they want us to use those exact headings when applicable. However we have no "About the role" but we have "Position Summary". Could use "About the role" as heading for position summary? Might be okay.
Better to follow instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should produce headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to include only sections that have real specific content. We have content for Responsibilities (Duties/Responsibilities). We have content for Requirements (Minimum Qualifications, Preferred Qualifications). We have content for Qualifications? Could be same as Requirements. We have Skills (Knowledge, Skills, Abilities). We have Schedule (Work Schedule). We have About the role? Could use "About the role" for Position Summary and maybe About the University/College? But we might combine.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information. So we need to include details: About the University of Georgia paragraph, About the College/Unit/Department (just mentions website?), Position Summary paragraph, Knowledge, Skills, Abilities list, Physical Demands details, Duties/Responsibilities with percentages, Schedule info.
We also have Minimum Qualifications and Preferred Qualifications.
We need to output only HTML fragment, no /, no markdown.
Let's structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should produce headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to include only sections that have real specific content. We have content for Responsibilities (Duties/Responsibilities). We have content for Requirements (Minimum Qualifications, Preferred Qualifications). We have content for Qualifications? Could be same as Requirements. We have Skills (Knowledge, Skills, Abilities). We have Schedule (Work Schedule). We have About the role? Could use "About the role" for Position Summary and maybe About the University/College? But we might combine.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information. So we need to include details: About the University of Georgia paragraph, About the College/Unit/Department (just mentions website?), Position Summary paragraph, Knowledge, Skills, Abilities list, Physical Demands details, Duties/Responsibilities with percentages, Schedule info.
We also have Minimum Qualifications and Preferred Qualifications.
We need to output only HTML fragment, no /, no markdown.
Let's structure:
About the role
Position Summary ...
Responsibilities
- ... each duty with percentage?
Requirements
- Minimum Qualifications: Bachelor’s degree in a related field or equivalent and 2 years of professional experience
- Preferred Qualifications: At least 2 years of experience with UGA One Source and grants management; Experience using UGA Onesource for financial and HR processes; Experience managing position postings in UGA Jobs
Skills
- Ability to prepare financial statements and work independently to apply accounting practices ... many items. We need to include all from Knowledge, Skills, Abilities And/or Competencies list. Also Physical Demands maybe could be under Requirements? But we could add a section "Physical Demands" as its own heading? Not in examples but we could still use
- . Physical Demands details: - Sitting at desk workstation 6 – 8 hours daily - Traveling/walking to meetings a various locations across campus, occasionally off campus, and rarely at satellite UGA facilities - Setting up tables, chairs, food, beverages, etc. at events - Is driving a responsibility of this position? Yes - Is this a Position of Trust? Yes - Does this position have operation, access, or control of financial resources? Yes - Does this position require a P-Card? No - Is having a P-Card an essential function of this position? No - Does this position have direct interaction or care of children under the age of 18 or direct patient care? No - Does this position have Security Access (e.g., public safety, IT security, personnel records, patient records, or access to chemicals and medications) Yes - Credit and P-Card policy Be advised a credit check will be required for all positions with financial responsibilities. For additional information about the credit check criteria, visit the UGA Credit Background Check website. - Background Investigation Policy Offers of employment are contingent upon completion of a background investigation including, a criminal background check demonstrating your eligibility for employment with the University of Georgia; confirmation of the credentials and employment history reflected in your application materials (including reference checks) as they relate to the job-based requirements of the position applied for; and, if applicable, a satisfactory credit check. You may also be subject to a pre-employment drug test for positions with high-risk responsibilities, if applicable. Please visit the UGA Background Check website. We decided to remove legal boilerplate, so we should remove the credit check and background investigation paragraphs. Also remove the "Credit and P-Card policy" and "Background Investigation Policy". Keep the rest of physical demands. Thus Physical Demands list includes the first items up to Security Access. Now Duties/Responsibilities: there are multiple entries with percentages. Need to combine duplicates? There are two entries about grant proposal preparation (first and fourth). We should keep both as separate? They are similar but different percentages and details. We'll keep both. List them: 1. Assist with grant proposal preparation and management of the submission process. This will include: Budget forecasting and preparation of fiscal year budgets; Resource allocation; Assisting the Director and Faculty with Institute development activities including faculty hires (including scheduling travel and interviews); Data management; Oversight of the Institute’s web site; Facilitation of Institute faculty and committee meetings (including taking and filing notes) Percentage of time 30 2. Manage the Institute’s State, Foundation and Restricted accounts according to accepted UGA and bookkeeping policies with respect to purchases, travel, HR and student funding lines. Accounts include 1 income generating account. Total accounts managed is currently about 15. Most are salary only and have few transactions. Percentage of time 25 3. Organize Institute meetings, symposia and workshops including travel of UGA participants to locations or outside participants traveling to UGA. This may include, but is not limited to: Registration; Room and equipment reservations; Housing; Catering; Meeting brochures; Name tags, etc. Percentage of time 15 4. Assist with grant proposal preparation and management of the submission process. This will include: Budget development and justification; Knowledge of RFPs and required forms for various funding agencies; Collecting and managing biosketches; Use of eGear grant portal and FastLane; Working with multiple faculty members on Institute training grants, workshop and research proposals Percentage of time 10 5. Organize standing staff meetings, including the director, associate director, and director of graduate studies; Attend meetings with the Director and other Institute faculty as needed; Make presentations on status of accounts, grants or other activities as needed Percentage of time 5 6. Attend to Human Resource issues and policies associated with faculty and graduate students; Supervise, evaluate and train Institute staff; Manage sensitive information and personnels Percentage of time 10 7. Proactively seek out opportunities for Institute funding at all levels (program project, research, training, workshops & symposia); Network with relevant
for it; instruction says use for section headings (e.g. ...). It doesn't forbid other headings, but to be safe we could incorporate Physical Demands into Requirements or Skills? Better to add a separate heading "Physical Demands" as . It's substantive.
Schedule: Schedule
. It's substantive.
Schedule: Schedule
Monday through Friday, 8:00 am – 5:00 pm
We should also include About the University of Georgia and About the College/Unit/Department maybe under About the role? Could add a preceding