Sr IT Administrative Analyst job

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes description of company, description of post (responsibilities), qualifications, competencies, salary, benefits, work setting, etc. We need to extract relevant info. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Important: To apply, candidates must provide a cover letter and a resume." That's application instruction, remove. Also remove "Work Setting: in-person (onsite)" maybe keep? It's not a heading; could be part of description but not needed. We can include as a paragraph under maybe "Work Setting" but we don't have a heading for that unless we create a section; but we only create headings for specified list. So we can embed that info in a paragraph under maybe "About the role" or "Responsibilities"? Better to keep as a short paragraph under maybe "About the role". However "About the role" is not explicitly in posting but we can create a section summarizing the role description. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if content exists. We need to decide which sections have content. We have: - About the role: could be a brief overview of the position (description du poste). We'll include a paragraph summarizing the role. - Responsibilities: list of essential functions (calendar management, communication management, meeting & event coordination, project management support, administrative support, data & document management, confidentiality & professionalism, problem solving & initiative, office management). We'll put as

• . - Requirements: maybe education and experience? Could be under Qualifications. The instruction includes Requirements and Qualifications separate. We can put education/experience under Requirements, and competencies/skills under Skills. Or we could combine. Let's follow: Requirements: education and experience (minimum). Qualifications: maybe "College degree a plus but not required." But that's also qualification. However we can treat Qualifications as education/experience, and Skills as competencies. Let's decide: - Requirements: Education: High School Diploma and two years of recent post-high school education required. College degree a plus but not required. Experience: 3-7 years administrative. Advanced Microsoft Office Suite experience required. Attention to detail... etc. That seems like qualifications. But we also have "Competencies, Knowledge, Skills And Abilities" list. That's clearly Skills. Thus: - Requirements: Education and experience bullet points. - Skills: list of competencies. - Benefits: list of benefits (comprehensive health coverage, wellness program, paid vacation, sick leave, holidays, retirement savings, Public Service Loan Forgiveness, Free Commute on SEPTA, Tuition Discounts and Scholarships). Also maybe mention "We offer Comprehensive health coverage..." etc. - Pay: Salary range $55,000-$66,950, note cannot exceed $66,950. - Schedule: Not explicitly given. There's no schedule info. So we should NOT create a Schedule section. We must not include placeholder text like "commensurate with experience". We have actual salary range. We must not include duplicated lines. Ensure we preserve all substantive info. We need to remove boilerplate: EEO statement, vaccination policy, residency requirement? The residency requirement: "The successful candidate must be a city of Philadelphia resident within six months of hire" - that's substantive? It's a requirement. Should we keep? It's a condition of employment. It's not boilerplate; it's a specific requirement. Should we include under Requirements? Probably yes. Also vaccination policy: "Effective May 22, 2023, vaccinations are no longer required for new employees that work in non-medical..." That's also a condition but maybe considered boilerplate? It's about vaccination policy; could be considered legal/EEO? It's not exactly EEO but it's a policy. Might be considered boilerplate; but it's substantive info about vaccination requirement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Vaccination policy could be considered legal. Safer to remove it. Also the EEO statement at end: remove. Also remove "Discover the Perks of Being a City of Philadelphia Employee:" heading? We'll incorporate benefits. Also remove "Join the City of Philadelphia team today..." promotional fluff? Might be considered boilerplate but it's part of benefits description. We'll keep the substantive benefits but remove fluff. We need to output only HTML fragment, no or . Use

  headings,

  • for lists,

    for prose. Let's craft:

    About the role

    The Senior IT Administrative Analyst supports the Chief Project Management Officer and Chief Enterprise Officer, providing administrative and operational support to ensure effective communication, project coordination, and management of key city initiatives. The role requires managing schedules, communications, meetings, project tracking, administrative tasks, data management, confidentiality, problem solving, and office management.

    Responsibilities

    • Calendar and Schedule Management: manage and prioritize schedules of the CPMO and CEO; schedule meetings, appointments, and travel; resolve scheduling conflicts.
    • Communication Management: serve as primary point of contact for internal/external stakeholders; screen calls, emails, correspondence; draft, proofread, edit documents; facilitate communication flow and follow up on action items.
    • Meeting & Event Coordination: organize and prepare materials for meetings, conferences, public events; take minutes, track action items, ensure follow-up; assist in planning, logistics, execution of city‑wide events and stakeholder engagement.
    • Project Management Support: assist CPMO in tracking and supporting execution of city projects; help prepare and maintain project reports, status updates, documentation; track timelines and milestones; handle project‑related inquiries.
    • Administrative Support: handle day‑to‑day tasks (filing, organizing records, office supplies); coordinate travel arrangements; support special projects; record and distribute meeting notes; answer telephone and personal inquiries; create and maintain documents.
    • Data & Document Management: organize, maintain, update confidential files and databases; assist in preparing reports and presentations for senior leadership and public; ensure accuracy and integrity of project‑related documentation.
    • Confidentiality & Professionalism: maintain strict confidentiality; exhibit professionalism in all interactions.
    • Problem Solving & Initiative: anticipate needs, proactively address administrative challenges, offer recommendations for process improvements.
    • Office Management: communicate with staff regarding office needs; recommend improvements; assist with setup/breakdown of office events; coordinate with office manager on building/facility‑related issues.

    Requirements

    • Education: High School Diploma and two years of recent post‑high school education required; college degree a plus but not required.
    • Experience: 3‑7 years of administrative experience.
    • Advanced Microsoft Office Suite experience required.
    • Strong attention to detail, able to prepare and interpret procurement requests and invoice statements.
    • Ability to handle multiple tasks accurately and expeditiously.
    • Solid analytical and problem‑solving abilities.
    • Strong proven organizational skills.
    • Comfortable with basic IT issues and willing to learn new technological trends.
    • Must be a City of Philadelphia resident within six months of hire.
    • An equivalent combination of education and experience deemed acceptable by OIT HR, CPMO and CEO will be considered.

    Skills

    • Work independently on difficult or complex administrative and clerical tasks.
    • Accomplish work requirements in a timely manner.
    • Exercise good judgment, courtesy, and professionalism with callers and problem disposition.
    • Establish and maintain effective working relationships with internal and external clients.
    • Operate standard office equipment, phone, personal computers, printers, scanners.
    • Maintain confidential information and data.
    • Set and maintain priorities with a large workload.
    • Fluency in Microsoft Office Suite (Word, Excel, PowerPoint, Outlook, SharePoint).
    • Strong problem‑solving skills – communicate clearly, evaluate information/data to recommend courses of action.
    • Excellent communication skills – verbal and written, ability to engage IT and functional managers at all levels, influence across teams, cross‑team training and documentation.
    • Ability to manage time effectively, set priorities, work with minimal supervision, independently or as part of a team, maintain professional demeanor under stress.
    • Demonstrated customer focus – evaluate decisions through customer’s eyes, build strong relationships, create processes from customer viewpoint, partner with customers.
    • Working knowledge of Microsoft Visio is a plus.
    • Working knowledge of Microsoft Outlook or other automated email/scheduling system.
    • Basic office operations knowledge.

    Benefits

    • Comprehensive health coverage for employees and eligible dependents.
    • Wellness program offering eligibility into discounted medical plan.
    • Paid vacation, sick leave, and holidays.
    • Generous retirement savings options.
    • Public Service Loan Forgiveness program eligibility (qualifying employer).
    • Free Commute on SEPTA – eligible employees receive free SEPTA Key cards for buses, trains, trolleys, and regional rails (effective September 1, 2023).
    • Tuition discounts and scholarships through partnerships with over a dozen colleges and universities – savings of 10% to 40% on educational expenses (may extend to spouse/dependents).

    Pay

    Salary range: $55,000 – $66,950 (salary cannot exceed $66,950).

    We should not include Schedule section. Check for any duplicated lines: we have not repeated. Check for any boilerplate left: we removed EEO, vaccination policy, application instructions, "Discover the Perks..." fluff (we kept benefits but removed promotional sentences). We kept "Join the City of Philadelphia team today..." removed. Good. Check that we preserved all substantive info: company description? We omitted the initial "Description De L'entreprise" paragraph about Philadelphia. That's substantive info about the city and OIT. Should we include that? It's about the company. Could be placed under "About the role" or maybe a separate "About the company" but not in allowed headings. However we could incorporate into About the role paragraph. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid adding other headings, but says use those for section headings. It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we could also add other headings but better to stick to those. The company description is substantive; we could include it in About the role paragraph as context. Let's add a sentence: "The City of Philadelphia is a best‑in‑class city with over 30,000 employees and 1,000 job categories, valuing inclusion, integrity, innovation, empowerment, and hard work. The Office of Innovation & Technology (OIT)