IT Analyst

We need to output HTML fragment with sections: About the role? Actually we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive information. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes benefits details: "We offer a comprehensive, competitive benefits program..." includes core benefits: salary, equity, 401k, medical, dental, vision, HSA, life insurance, short-term disability, supplemental benefits, mental health, flexible PTO, holidays, parental leave, professional development budgets. So Benefits section is appropriate. Pay: Not explicitly stated salary amount; only "Competitive salary". That's vague but it's still mention of competitive salary. However rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Competitive salary and company equity through RSUs". That's mention of salary but not a specific number. Is that considered stating pay? Likely yes, they mention competitive salary. But we must avoid filler like "commensurate with experience". "Competitive salary" is not filler? It's somewhat generic but still states they offer competitive salary. The rule says: 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. Since they state "Competitive salary", that's not placeholder; it's a statement. So we can include Pay section with that sentence. However we also have Benefits section that includes many details; maybe we can combine Pay and Benefits? The instruction: Prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section? But they ask to use headings for Benefits, Pay, Schedule separately if content exists. Since we have both Pay and Benefits content, we could have both sections. However we might avoid thin sections: Pay would be just a sentence about competitive salary and RSUs; Benefits would be a longer list. That's okay. Schedule: The posting mentions hybrid in Chicago, requirement to provide in-office support at least one week per month. Also mentions remote-first, offices in Chicago and St. Petersburg. There's mention of "Hybrid in Chicago" and "Able to provide in-office support at our Chicago location at least one week per month". That's schedule info. So we can include Schedule section with that. Now we need sections: About the role (maybe a summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to avoid duplication. The posting includes sections: "Quick Summary", "Who We Are", "The opportunity", "Your Responsibilities", "Success in this role", "What You’ll Bring" (hard skills, soft skills), "How We Hire", "How We Support You" (benefits), "How We Work", "Where we work", EEOC etc. We need to map to headings. About the role: Could combine Quick Summary and Who We Are and The opportunity? But we need to avoid filler. Let's create About the role with a paragraph summarizing the role: IT Analyst to own tier2 helpdesk, onboarding/offboarding, etc. Use info from Quick Summary and The opportunity. Responsibilities: Use bullet list from "Your Responsibilities". Must preserve all details. Requirements: Could be from "What You’ll Bring" hard skills? Actually requirements often include hard skills and soft skills. Qualifications maybe similar. But we need to decide: Use Requirements for hard skills? Qualifications for soft skills? Or combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content goes where. We have hard skills: 2+ years IT experience, tier2 support, remote-first, macOS/Windows troubleshooting, administration experience with Google Workspace, Slack, Okta, JumpCloud, BetterCloud, day-to-day fluency with ticketing system (Jira Service Management), habit of documenting (Confluence), some experience using AI tools (Claude, ChatGPT) or aptitude. Soft skills: white-glove service instinct, ability to identify issues, communicate solutions, collaborate, able to provide in-office support at Chicago at least one week per month. We could put Requirements = hard skills, Qualifications = soft skills, Skills = maybe combine? But we already have hard and soft. Could treat Skills as both? But we need to avoid thin sections. Perhaps we combine Requirements and Qualifications into one section? But headings are separate; we could omit one if content is thin. However we have enough for both. Better: Requirements = hard skills (experience, technical). Qualifications = soft skills (service instinct, communication, in-office). Skills = maybe mention specific tools? But that overlaps with requirements. Could treat Skills as the specific tools (Okta, Google Workspace, etc.) but that's also hard skills. Might be redundant. Given instruction to prefer few substantive sections over many thin ones, maybe we combine Requirements and Qualifications into a single "Requirements" section that includes both hard and soft. Then we could omit Qualifications and Skills headings. But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must include all; we include only those with real content. So we can include About the role, Responsibilities, Requirements (covering both hard and soft), Benefits, Pay, Schedule. That's enough. We must not repeat job title. No mention of "IT Analyst" as heading; fine. We must preserve all substantive information. Need to ensure we don't lose any details from the posting. Let's extract substantive content: - Quick Summary: "Support kinfolk, solve problems, reduce friction, automate processes. Make work-life easier and more pleasant for everyone at Kin. Hybrid in Chicago" - Who We Are: description of Kin, mission, founded 2016, remote-first, etc. Many details: they serve homeowners insurance, expand, data, technology, human support, etc. Also list of accolades: Built In Chicago's Best Places to Work, Midsize Companies (2021-2026), Forbes' America's Best Startup Employers (2026), Inc. 5000 Fastest-Growing Private Companies, Forbes’ Fintech 50 (2023-2026), Great Places to Work Certified (May 2024-May 2027). Also mention building Kin to be a place where people do meaningful work. - The opportunity: description of IT Analyst role: owning tier2 helpdesk, onboarding/offboarding, provisioning/deprovisioning access across Okta, Google Workspace, Slack, BetterCloud, auditing RBAC, managing device records via Jira Assets and JumpCloud, maintaining Chicago office day-to-day (A/V, security badge, covering extended hours during catastrophic events), triaging issues, enforcing security policy as frontline for Security and IT Engineering, writing/maintaining Confluence documentation and runbooks, spotting friction, raising improvement projects, training/mentoring interns and Jr. Analysts, using AI tools like Claude. - Success in this role: first 6-12 months impact, SLA target 90-95%, fluency with systems by month6, contributing to helpdesk improvements by month12, mentorship. - What You’ll Bring: Hard skills: 2+ years IT experience, tier2 support, remote-first support, proficiency troubleshooting macOS and Windows, administration experience with Google Workspace, Slack, Okta, JumpCloud, and/or BetterCloud, day-to-day fluency with ticketing system (Jira Service Management) and habit of documenting (Confluence), some experience using AI tools (Claude, ChatGPT, or similar) for workflow efficiency - or strong aptitude and eagerness to build that skill quickly. Soft Skills: White-glove service instinct - equal respect and responsiveness whether you're helping an intern or an exec, Ability to identify issues, communicate solutions clearly, and collaborate for win-win outcomes across technical and non-technical audiences, Able to provide in-office support at our Chicago location at least one week per month. - How We Hire: description of hiring process, deadline Oct 2, 2026, AI tools for efficiency but resumes screened by recruiters, decisions by recruiters and hiring teams, prompt updates, interviews with recruiters, hiring managers, team members, skills assessment if applicable, genuine human interaction. - How We Support You: benefits description: comprehensive competitive benefits program, choose benefits best for you and family, starting first day of month following start date. Core Benefits: Competitive salary and company equity through RSUs, granted as part of standard compensation package based on role and level; 401(k) with company match up to 4% of eligible earnings; Multiple medical plan options, plus dental and vision coverage; Company-funded HSA contributions (based on medical plan selection); Company-paid life insurance and short-term disability; Health & Wellbeing: variety of supplemental benefit options (long-term disability, critical illness, accident, legal, pet insurance); Access to mental health support and confidential counseling resources; Flexible PTO for exempt employees (most employees take 15–20 days per year), plus 8 company-observed holidays; Paid parental leave, including up to 14 weeks at 100% pay for birthing parents and 8 weeks at 100% pay for non-birthing parents; Growth & Development: Career mobility and internal growth opportunities across the organization; Professional development budgets for certifications, conferences, and learning available, subject to management approval. - How We Work: values: Run through walls together, High performance, Low drama, Always respectful, Assume best, challenge ideas not intentions, show up work hard play to strengths, Raise the bar drop ego, Attitudes contagious, Act like an owner, Operate lean deliver more, Keep asking What if? (curiosity, experimentation, data-driven, learning). - Where we work: remote-first with offices in Chicago, IL and St. Petersburg, FL; list of states for Sales Agents and Customer Service Agents; list of states for all other positions; remote technical positions in Canada only Ontario; must live and work full-time in listed states. - EEOC statement: remove. We need to remove boilerplate: navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove "How We Hire" maybe? It's not boilerplate; it's about hiring process. Might be considered part of application instructions? The instruction says remove application instructions. "How We Hire" includes deadline, process, etc. That could be considered application instructions. Safer to remove it. Also "Where we work" includes state eligibility; that's not exactly application instructions but could be considered location requirement. Might be considered part of job details; we should keep location info? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Where we work" includes location restrictions; that is not exactly application instructions but could be considered part of job details. However it's similar to "Where we work" which is about eligibility; might be considered part of job details. The instruction didn't explicitly say to remove location info. It says remove application instructions. "Where we work" is more about where you can work; not exactly instructions to apply. I'd keep it as part of About the role or maybe a separate section? But we don't have a heading for location. Could incorporate into About the role or maybe into