Lead Application Developer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Job Title: Lead Application Developer (we don't repeat as heading). Compensation: $55 - $60 / Hour. Location: Austin, Texas. Benefits: This position is eligible for medical, dental, vision, and 401(k). Then "Knowledge, Skills, And/or Abilities" list: Deep understanding of Legacy ASP.NET Web Forms, .NET framework, .NET Core, Visual Studio, C#, JavaScript. Data transformation, cleansing processes. Must be able to handle various tasks simultaneously, organize, prioritize, make decisions and work efficiently and effectively under deadlines. Must be able to work with geographically disperse teams and stakeholders through both onshore and offshore teams. Estimation and timely delivery of proposed and agreed upon solutions. Experience: 10+ years in software development (prefers minimum of 2 years as a Lead) 8+ years of development in web-related technologies 6+ years of development using .NET Framework, .NET Core, C#, SQL Server 6+ years of development in ASP.NET Web Forms and/or ASP.NET MVC and/or Angular 2+ years of experience in Azure Then "Why choose Addison?" with subpoints: Pay: We negotiate high salaries using U.S. Bureau of Labor Statistics Benefits & Bonuses: You are eligible for medical, dental, vision insurance benefits, 401K, and monetary bonuses Permanent Employment: Many of Addison’s job openings lead to potential permanent employment Connections: You connect directly with hiring managers from renowned organizations Then EEO boilerplate etc to remove. We need to produce sections: About the role (maybe a short description? Not present explicitly. Could we infer? The posting doesn't have an explicit "About the role" paragraph. We could maybe combine the initial description? There's no explicit description besides title, compensation, location, benefits. The "About the role" could be a short paragraph summarizing the role? But we must not invent or summarize away detail. We cannot create filler. So we should only include sections where there is real specific content. If there is no explicit "About the role" content, we should not include that heading. Similarly "Responsibilities": we have some bullet-like statements under Knowledge, Skills, And/or Abilities that could be considered responsibilities: handling tasks, prioritize, work with teams, estimation and delivery. Also maybe "Data transformation, cleansing processes" is a duty. So we can put those under Responsibilities. "Requirements": could be the experience requirements: 10+ years software dev, etc. "Qualifications": maybe overlapping with requirements; but we need to decide. The instructions: Prefer a few substantive sections over many thin ones. So we could combine experience and qualifications into one "Requirements" section. Or we could have "Requirements" for experience, and "Skills" for technical skills. "Skills": list of technical skills: Legacy ASP.NET Web Forms, .NET framework, .NET Core, Visual Studio, C#, JavaScript, SQL Server, ASP.NET MVC, Angular, Azure. "Benefits": we have benefits statement. "Pay": we have compensation $55 - $60 / Hour. Also there is a "Pay: We negotiate high salaries using U.S. Bureau of Labor Statistics" under Why choose Addison? That's vague; we should not include filler like "commensurate with experience". But we have actual pay range. So we can include Pay section with that range. "Schedule": not mentioned; do not include. We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings (none). Remove boilerplate. We need to preserve all substantive information. So we need to include location? Where to put? Could be in a short paragraph under About the role? But we don't have About the role. Perhaps we can include location in a

after the heading? But we need to follow rules: Use

for section headings,

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

  for prose. So we can have a

  for location and compensation? But compensation goes under Pay section. Location could be in a short paragraph maybe under a heading like "About the role"? But we don't have that heading. Could we create a heading "About the role" and put location and maybe a brief description? The description would be just location? That might be considered filler? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". If we put location under About the role, that is specific content (location). So we could have About the role section with a

  containing location. That seems acceptable. But we also have compensation; we could put that under Pay section. Thus sections: About the role (location), Responsibilities (duties), Requirements (experience), Skills (technical skills), Benefits, Pay. We could also combine Requirements and Skills into one? But better separate. Now we need to extract the exact statements. Location: "Austin, Texas" Pay: "$55 - $60 / Hour" Benefits: "This position is eligible for medical, dental, vision, and 401(k)." Also later "Benefits & Bonuses: You are eligible for medical, dental, vision insurance benefits, 401K, and monetary bonuses". We need to preserve all substantive information; we should not duplicate. Combine: medical, dental, vision, 401(k), monetary bonuses. Also mention eligibility for those. We'll put in a

  • list. Responsibilities: list items: - Deep understanding of Legacy ASP.NET Web Forms, .NET framework, .NET Core, Visual Studio, C#, JavaScript. (maybe this is skill not duty) - Data transformation, cleansing processes - Must be able to handle various tasks simultaneously, organize, prioritize, make decisions and work efficiently and effectively under deadlines. - Must be able to work with geographically disperse teams and stakeholders through both onshore and offshore teams. - Estimation and timely delivery of proposed and agreed upon solutions. We could separate skills from responsibilities. The first bullet about deep understanding is more skill. So responsibilities: handling tasks, prioritize, work with teams, estimation and delivery, data transformation/cleansing. Thus responsibilities list: - Handle various tasks simultaneously, organize, prioritize, make decisions, work efficiently and effectively under deadlines. - Work with geographically dispersed teams and stakeholders through onshore and offshore teams. - Perform data transformation and cleansing processes. - Provide estimation and ensure timely delivery of proposed and agreed-upon solutions. We need to preserve original wording but can rephrase slightly? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Rephrasing may be considered summarizing? Safer to keep original phrasing as much as possible. Use the exact sentences. Original sentences: "Deep understanding of Legacy ASP.NET Web Forms, .NET framework, .NET Core, Visual Studio, C#, JavaScript." "Data transformation, cleansing processes" "Must be able to handle various tasks simultaneously, organize, prioritize, make decisions and work efficiently and effectively under deadlines." "Must be able to work with geographically disperse teams and stakeholders through both onshore and offshore teams" "Estimation and timely delivery of proposed and agreed upon solutions." We could keep these as list items. Now Requirements: experience statements: "10+ years in software development (prefers minimum of 2 years as a Lead)" "8+ years of development in web-related technologies" "6+ years of development using .NET Framework, .NET Core, C#, SQL Server" "6+ years of development in ASP.NET Web Forms and/or ASP.NET MVC and/or Angular" "2+ years of experience in Azure" We can list each as
  • . Skills: technical skills list maybe from deep understanding plus others: Legacy ASP.NET Web Forms, .NET framework, .NET Core, Visual Studio, C#, JavaScript, SQL Server, ASP.NET MVC, Angular, Azure. We could list as
  • . Now Benefits: list items: medical, dental, vision, 401(k), monetary bonuses. Now Pay:

    $55 - $60 / Hour

    Now About the role:

    Austin, Texas

    We need to ensure we don't include boilerplate like EEO etc. Now output HTML fragment only. Structure:

    About the role

    Austin, Texas

    Responsibilities

    • Deep understanding of Legacy ASP.NET Web Forms, .NET framework, .NET Core, Visual Studio, C#, JavaScript.
    • Data transformation, cleansing processes
    • Must be able to handle various tasks simultaneously, organize, prioritize, make decisions and work efficiently and effectively under deadlines.
    • Must be able to work with geographically disperse teams and stakeholders through both onshore and offshore teams.
    • Estimation and timely delivery of proposed and agreed upon solutions.

    Requirements

    • 10+ years in software development (prefers minimum of 2 years as a Lead)
    • 8+ years of development in web-related technologies
    • 6+ years of development using .NET Framework, .NET Core, C#, SQL Server
    • 6+ years of development in ASP.NET Web Forms and/or ASP.NET MVC and/or Angular
    • 2+ years of experience in Azure

    Skills

    • Legacy ASP.NET Web Forms
    • .NET framework
    • .NET Core
    • Visual Studio
    • C#
    • JavaScript
    • SQL Server
    • ASP.NET MVC
    • Angular
    • Azure

    Benefits

    • Medical insurance
    • Dental insurance
    • Vision insurance
    • 401(k)
    • Monetary bonuses

    Pay

    $55 - $60 / Hour

    We need to ensure we didn't miss any substantive info: The location is included. The compensation is included. The benefits we captured. The "Why choose Addison?" includes Pay: We negotiate high salaries using U.S. Bureau of Labor Statistics (vague) and Benefits & Bonuses: You are eligible for medical, dental, vision insurance benefits, 401K, and monetary bonuses (we captured). Permanent Employment and Connections are generic but could be considered substantive? They are statements about Addison. The instruction: remove boilerplate, duplicated lines, application instructions. Permanent Employment and Connections are not boilerplate but are marketing fluff. Are they substantive? They are not required to be included? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include them if they are substantive. However they are somewhat generic but still specific to Addison. The instruction also says prefer a few substantive sections over many thin ones. Could we add a section "About Addison" or something? Not in the allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading. So we must fit that info into existing sections if appropriate. Where could "Permanent Employment: Many of Addison’s job openings lead to potential permanent employment" go? Possibly under Benefits? Not really. Could be under About the role? Not really. Could be under Requirements? No. Could be under Skills? No. Could be under Pay? No. Could be under Benefits? Not exactly. Could be under Responsibilities? No. Similarly "Connections: You connect directly with hiring managers from renowned organizations". This is also marketing. Given the strict headings list, we may