Duck Creek Developer (BIlling)

We need to output HTML fragment with sections: About the role? Actually we have responsibilities, qualifications, pay and benefits, workplace type, maybe about TEKsystems? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting and extract sections. The posting includes: - Intro: "We are hiring a Senior Duck Creek Developer (Billing) to join our team remotely!" (maybe not needed as heading) - Responsibilities: list of bullet points (starting with "Design, develop, configure, and maintain Duck Creek Billing solutions." etc.) - Qualifications: list: "10+ years of software development experience.", "8+ years of hands-on Duck Creek Billing development experience.", "Strong experience configuring Duck Creek Billing components and business rules.", "Experience developing integrations using REST APIs, SOAP services, XML, and JSON.", "Ability to work remotely effectively (CST/EST timezones)" - Job Type & Location: "This is a Contract position based out of Chicago, IL." - Pay And Benefits: includes pay range $60.00 - $73.00/hr. Then description about compensation factors, eligibility, benefits list. - Workplace Type: "This is a fully remote position." - Application Deadline: "This position is anticipated to close on Oct 7, 2026." - About TEKsystems: description (two paragraphs repeated). This is boilerplate? Might be considered "About TEKsystems" but not required heading list. The instructions say we can include sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About company as a required heading, but we could include if there is substantive content. However they say "Prefer a few substantive sections over many thin ones." The About TEKsystems is somewhat generic but could be considered company description. Might be okay to include as a section like "About TEKsystems". But the instruction list didn't include that as example; but they said "e.g." not exhaustive. So we could include a section like "About TEKsystems". However we need to avoid boilerplate/legal EEO etc. The About TEKsystems paragraphs are not boilerplate? They are somewhat generic but still substantive about the company. Might be okay. But we also have duplicated lines: The About TEKsystems appears twice (almost identical). We need to remove duplicated lines. So we should keep only one copy. Also there is legal EEO etc at end: we need to remove that. Also there is "San Francisco Fair Chance Ordinance", "Massachusetts Lie Detector", "Use of Artificial Intelligence (AI)" - these are legal boilerplate; remove. Also "Application Deadline" maybe we could include as a short paragraph under a heading like "Application Details"? Not in list but could be a short p. However they said include a section ONLY when posting has real, specific content for it. The deadline is specific. Could we include a heading like "Application Deadline"? Not in the examples but could be okay. However they prefer few substantive sections; maybe we can fold that into a short p under a general "Details" section? But we don't have a heading for that. Could we just include it as a paragraph after the sections without a heading? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to stick to those headings. The deadline could be included in a paragraph under maybe "About the role"? Not ideal. Could we create a "Details" section? Not in list but maybe okay. However they said "e.g." meaning those are examples, not exclusive. So we can add other headings if needed. But to be safe, we could include a short paragraph after the sections without a heading? The instruction says use

  for section headings; doesn't say we cannot have plain paragraphs without heading. So we could add a

  for the deadline after the sections. But we also have "Job Type & Location" which could be a short paragraph. We need to decide which sections to output. Potential sections: - Responsibilities (as

  Responsibilities

  with
  • ...) - Qualifications (as

    Qualifications

    with
    • ...) - Pay and Benefits: Could combine Pay and Benefits into one section? The instruction list includes Pay and Benefits separate. But we could do

      Pay

      with

      for pay range and maybe note about compensation factors. And

      Benefits

      with
      • for benefits list. - Workplace Type: Could be a short paragraph under maybe "Workplace Type" heading (not in list but okay). Or we could incorporate into a paragraph under "About the role". But we have a specific line: "This is a fully remote position." Could be a short

        . - Job Type & Location: "This is a Contract position based out of Chicago, IL." Could be a short

        . - About TEKsystems: Could be a section

        About TEKsystems

        with

        describing. - Application Deadline: Could be a short

        . We must avoid boilerplate: remove EEO etc. We must preserve all substantive information: So we need to keep the pay range description, benefits list, job type, location, workplace type, deadline, responsibilities, qualifications, about TEKsystems. We must not repeat duplicated lines: The About TEKsystems appears twice; we keep one. We must not include the "Job ID / requisition numbers" - none present. We must not include application instructions: there is none besides deadline maybe. We must not include cookie/navigation/legal/EEO etc. Now let's extract the exact text. Responsibilities list: - Design, develop, configure, and maintain Duck Creek Billing solutions. - Develop and enhance billing transactions using Duck Creek out-of-the-box functionality and custom development. - Build and support integrations between Duck Creek Billing and external systems using REST APIs, SOAP services, and web services. - Collaborate with Business Analysts, Solution Architects, QA teams, and Product Owners to translate requirements into technical solutions. - Develop and support interfaces with payment processors, financial systems, and policy administration platforms. - Troubleshoot production issues, perform root cause analysis, and implement long-term solutions. - Participate in code reviews and ensure adherence to development best practices. - Support Duck Creek upgrades, migrations, and platform modernization initiatives. - Create technical design documents and support system architecture discussions. - Participate in Agile ceremonies including sprint planning, standups, backlog refinement, and retrospectives. - Support SIT, UAT, deployment activities, and post-production validation. Qualifications list: - 10+ years of software development experience. - 8+ years of hands-on Duck Creek Billing development experience. - Strong experience configuring Duck Creek Billing components and business rules. - Experience developing integrations using REST APIs, SOAP services, XML, and JSON. - Ability to work remotely effectively (CST/EST timezones) Job Type & Location: "This is a Contract position based out of Chicago, IL." Pay And Benefits: "The pay range for this position is $60.00 - $73.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave)" Note: The benefits list seems to be a run-on sentence; we need to parse into items. The text: "Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave)". It seems missing punctuation. We can split by commas and maybe "and". But we need to preserve all substantive information; we can keep as a single

        • with the whole sentence? Better to split into logical items: Medical, dental & vision; Critical Illness, Accident, and Hospital; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available; Life Insurance (Voluntary Life & AD&D for the employee and dependents); Short and long-term disability; Health Spending Account (HSA); Transportation benefits; Employee Assistance Program; Time Off/Leave (PTO, Vacation or Sick Leave). We'll do that. Workplace Type: "This is a fully remote position." Application Deadline: "This position is anticipated to close on Oct 7, 2026." About TEKsystems: First paragraph: "We're partners in transformation. We help clients activate ideas and solutions to take advantage of a new world of opportunity. We are a team of 80,000 strong, working with over 6,000 clients, including 80% of the Fortune 500, across North America, Europe and Asia. As an industry leader in Full-Stack Technology Services, Talent Services, and real-world application, we work with progressive leaders to drive change. That's the power of true partnership. TEKsystems is an Allegis Group company." Second paragraph (duplicate): "We’re a leading provider of business and technology services. We accelerate business transformation for our customers. Our expertise in strategy, design, execution and operations unlocks business value through a range of solutions. We’re a team of 80,000 strong, working with over 6,000 customers, including 80% of the Fortune 500 across North America, Europe and Asia, who partner with us for our scale, full-stack capabilities and speed. We’re strategic thinkers, hands-on collaborators, helping customers capitalize on change and master the momentum of technology. We’re building tomorrow by delivering business outcomes and making positive impacts in our global communities. TEKsystems and TEKsystems Global Services are Allegis Group companies. Learn more at TEKsystems.com." We need to keep only one copy; but which one? Both