Licenced Underwriting Services Associate

We need to output only HTML fragment, with headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Must preserve all substantive information. We need to parse the posting and extract relevant sections. Let's read the posting: - Quick Summary: "Serve as the trusted voice of Kin, supporting and advocating for homeowners across 13 states. Handle policies, payments, and coverage questions while delivering fast, empathetic service in a high-volume environment. Active P&C license required. Join a team that puts customers first every single day." That's a summary; could be placed under "About the role" maybe. - Who We Are: description of Kin, founded 2016, remote-first, etc. That's company overview; could be "About the company" but we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use

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

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should only use those headings. So we need to map content to those sections. We have: - About the role: could include quick summary and maybe who we are? But "About the role" likely describes the role itself. The quick summary fits. Also "The Opportunity" section describes the role in detail. So we can combine. - Responsibilities: list under "Your Responsibilities". That's a list. - Requirements: maybe "What You'll Bring" includes license required, experience, etc. That's requirements. - Qualifications: maybe overlapping with requirements; but we can treat "What You'll Bring" as qualifications. However we need both Requirements and Qualifications sections if there is distinct content. The posting includes "Active Property & Casualty (P&C) or Personal Lines license (required)" etc. Also "Bonus: prior experience with Kin's underwriting queues..." and "Availability to work our following shifts...". That could be under Requirements or Qualifications. We'll decide. - Skills: maybe we can extract skills like "Strong written communication", "Sound judgment", "Comfort navigating multiple systems", etc. Could be a Skills section. - Benefits: there is a "We offer a comprehensive, competitive benefits program..." and then sub-sections: Core Benefits, Health & Wellbeing, Growth & Development. So we can include Benefits section with those details. - Pay: The posting does not mention specific salary or pay range. It mentions "Competitive salary and company equity through RSUs". That's somewhat pay info but not specific numbers. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The posting says "Competitive salary and company equity through Restricted Stock Units (RSUs), granted as part of our standard compensation package and based on role and level". That is not a specific number but it's a statement about compensation. Is that considered filler? It's not a placeholder like "commensurate with experience". It's a statement that they offer competitive salary and equity. Might be acceptable to include Pay section with that statement. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (competitive salary and equity). So we can include Pay. - Schedule: The posting includes shift times and rotating Saturday shift. So we can include Schedule. We must not include boilerplate like EEOC statement, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions like "Application Deadline Applications will close on Friday, October 9th at 3:00 pm CST." That's application instruction; we should remove. Also "How We Hire", "How We Work", "Where we work", "EEOC statement" etc. Must remove. We must preserve all substantive information. So we need to keep details about role, responsibilities, requirements, qualifications, skills, benefits, pay, schedule. We must not invent or summarize away detail. Keep specifics like shift times, license required, etc. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

...

Maybe include quick summary and the opportunity description. Better to keep concise but preserve all details. However we must not invent or summarize away detail. Summarizing may be okay if we keep all details? The instruction: "Do NOT invent or summarize away detail." Means we should not omit details; we should preserve all substantive information. So we need to keep the details, not just a summary. That suggests we should include the full text of the relevant sections, maybe as paragraphs or lists. But we can keep the original wording, just restructure into HTML. Thus we can copy the relevant sections verbatim (minus boilerplate) and wrap in appropriate tags. Let's extract sections: About the role: Could combine Quick Summary and The Opportunity. Quick Summary: "Serve as the trusted voice of Kin, supporting and advocating for homeowners across 13 states. Handle policies, payments, and coverage questions while delivering fast, empathetic service in a high-volume environment. Active P&C license required. Join a team that puts customers first every single day." The Opportunity: paragraphs describing Underwriting Services, role, etc. We'll keep that. Thus About the role section will contain those paragraphs. Responsibilities: list under "Your Responsibilities". We'll output

• each item. Requirements: maybe "What You'll Bring" includes license required, experience, etc. But also there is "Bonus: prior experience with Kin's underwriting queues..." and "Availability to work our following shifts...". Those could be under Requirements or maybe under Schedule. The shift availability is schedule. Bonus experience maybe qualifications. We need to decide sections. Let's define: - Requirements: mandatory items: Active P&C or Personal Lines license required; Direct underwriting, underwriting-support, or advanced policy-servicing experience in home insurance; Working knowledge of property risk review, inspections, and pre-bind requirements; Sound judgment applying defined rulesets to individual policies, with the discernment to know when a case falls outside the rules and needs escalation; Strong written communication for customer-facing and cross-functional correspondence; Comfort navigating multiple systems and working in a fast-moving, evolving environment with limited structure. - Qualifications: maybe Bonus: prior experience with Kin's underwriting queues, inspections, or RBR workflows. Also maybe the shift availability? But shift is schedule. - Skills: maybe we can extract skills like "Strong written communication", "Sound judgment", "Comfort navigating multiple systems". But those already in requirements. Could combine. Given the instruction to prefer a few substantive sections over many thin ones, we might combine Requirements and Qualifications into one section? But they ask to use headings for those specific ones. We could still include both if they have content. We need to avoid filler like "commensurate with experience". Not present. Thus we can have:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ...

  Qualifications

  ...
  (maybe just bonus experience)

  Skills

  ...
  (maybe we can list specific skills like "Strong written communication", "Sound judgment applying defined rulesets", "Comfort navigating multiple systems", etc.)

  Benefits

  ...
  (list benefits)

  Pay

  Competitive salary and company equity through Restricted Stock Units (RSUs), granted as part of our standard compensation package and based on role and level.

  Schedule

  Availability to work our following shifts, Monday - Friday (will be placed based upon need): 7:00 AM - 4:00 PM CST; 8:00 AM - 5:00 PM CST; 9:00 AM - 6:00 PM CST; 10:00 AM - 7:00 PM CST. Note: Rotating Saturday shift required every 4–6 weeks.

  We must ensure we don't include any boilerplate like "EEOC statement", "How We Hire", etc. Now we need to verify that we preserved all substantive information. Let's extract the exact text from the posting for each section. First, About the role: Quick Summary: "Serve as the trusted voice of Kin, supporting and advocating for homeowners across 13 states. Handle policies, payments, and coverage questions while delivering fast, empathetic service in a high-volume environment. Active P&C license required. Join a team that puts customers first every single day." The Opportunity: paragraphs: "Underwriting Services is a new function at Kin that owns the risk work across the full policy lifecycle, from initial review through active service and renewal. As an Underwriting Services Associate, you'll put your property-risk and underwriting expertise to work at every stage: reviewing risk, adjudicating inspection findings, resolving requirements directly with customers, and partnering with Underwriting to keep policies moving accurately and quickly whether they're being bound, serviced, or renewed. This is a licensed, hands-on risk role with real ownership. You'll manage complex risk files end to end, make the calls that sit within your delegated authority, and work directly with customers, Sales, and Underwriting to drive each case to a clear outcome. It's a strong fit for someone with underwriting or advanced policy expertise who wants to own the risk side of the customer experience and see cases through from open questions to resolution." We could combine them. Now Responsibilities list: From "Your Responsibilities": - Conduct risk reviews across the policy lifecycle, applying Kin's underwriting rulesets and exercising judgment within your delegated authority - Review and adjudicate inspection findings, including Coverage A valuations in the $1M to $2M range and escalated inspection cases - Own the risk file end to end at pre-bind, in active service, and at renewal: gather required documentation from customers, resolve open items, and prepare the file so Underwriting can make the coverage decision without rework - Field transferred calls and live inquiries from the Customer Service team related to underwriting inspection results, requirements, and coverage conditions, resolving them directly with customers - Serve as the risk-side partner to Sales on referred cases, taking the information-gathering and customer follow-up off the sales team while keeping the policy moving to bind - Manage post-bind and renewal underwriting requirements, including follow-ups on incomplete inspections and outstanding conditions - Complete RBR document gathering and manage escalated knockout-question resolution and complex customer correspondence - Process premium-bearing policy actions accurately and in compliance with state and underwriting requirements - Communicate underwriting outcomes to customers and partner teams clearly, including declines and additional-requirement conversations - Surface patterns and process gaps that can be turned into rules, reducing the volume that needs manual review over time We'll keep each as
• . Now Requirements (mandatory): From "What You'll Bring": - Active Property & Casualty (P&C) or Personal Lines license (required) - Direct underwriting, underwriting-support, or advanced policy-servicing experience in home insurance - Working knowledge of property risk review, inspections, and pre-bind requirements - Sound judgment applying defined rulesets to individual policies, with the discernment to know when a case falls outside the rules