Software Engineer IV/Tech Lead

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Keep all substantive info. We need to decide which sections have content. From posting: - Intro paragraph about AbsenceSoft (company description). Could be "About the role"? Actually "About the role" maybe includes description of role. We have a paragraph describing the role: "The Software Engineer IV / Tech Lead is a hands-on technical leader ...". That's role description. Could put under

About the role

with that paragraph. - Responsibilities: bullet list under "What You’ll Do". Those are responsibilities. So

Responsibilities

with

• items. - Required Skills: bullet list under "What’ll Set You Up for Success". That's requirements/qualifications. Could be

  Requirements

  or

  Qualifications

  . We have both Required Skills and Preferred Skills. Could combine into Requirements (required) and maybe Qualifications (preferred). But we need to avoid thin sections. Could have one section "Requirements" containing both required and preferred? But we need to preserve all info. Could split:

  Required Skills

  and

  Preferred Skills

  . Both are valid headings from list: Skills is allowed. Actually allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use Skills for required and preferred? Could have Skills section with both required and preferred bullet lists. But we need to differentiate? Not required. Could just put all skill bullets under Skills. But we also have "Key Skills & Behaviors" which is more about behaviors. Could also go under Skills. Thus we can have a Skills section containing bullet points from Required Skills, Preferred Skills, Key Skills & Behaviors. But we need to ensure we don't lose nuance: required vs preferred vs behaviors. Could keep separate subheadings? Not allowed; only allowed headings list. Could embed paragraphs to differentiate. Could use

  to label "Required Skills:" then list, then "Preferred Skills:" then list, then "Key Skills & Behaviors:" then list. That's acceptable. - Benefits: The posting includes "Why join us" with bullet-like paragraphs describing values and offerings: "We Offer Impact that matters...", "Flexibility and trust...", "Growth and development...", "Competitive rewards...", "Time for life.", "Belonging and balance." These are benefits. So we can have

  Benefits

  with
  • items for each benefit. - Pay: The posting includes "Final compensation is determined based on a candidate's relevant experience, skills, education, and geographic location. This position is also eligible for annual bonus. The Pay Range For This Role Is 179,391 - 224,238 USD per year(US National)". So we have pay range and bonus eligibility. So we need a Pay section with that info. - Schedule: Not mentioned. No schedule info (remote-first, flexibility). Could infer flexibility but not explicit schedule like full-time, hours. The posting mentions remote-first and results driven, flexibility. Could we put schedule? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not explicitly stated; we have flexibility but not schedule. Safer to omit Schedule section. - About the role: we have intro paragraph about company and role description. Could be under About the role. - Responsibilities: we have bullet list under "What You’ll Do". Good. - Requirements/Qualifications: we could have Requirements for required skills, Qualifications for preferred skills? But we already using Skills section. Could also have Requirements for required skills and Qualifications for preferred skills. Let's see: Allowed headings include Requirements and Qualifications. So we can split: Requirements for required skills, Qualifications for preferred skills (and maybe key skills & behaviors). That seems appropriate. Thus sections:

    About the role

    with paragraph(s): company intro + role description.

    Responsibilities

    with ul list of responsibilities.

    Requirements

    with required skills bullet list.

    Qualifications

    with preferred skills bullet list + key skills & behaviors bullet list (maybe combine).

    Benefits

    with ul list of benefits.

    Pay

    with paragraph about pay range and bonus. No Schedule. We must not include boilerplate like EEO, application instructions, etc. Remove lines like "If your experience doesn’t align perfectly..." etc. That's encouraging to apply; that's application instruction? It's more like encouragement but still maybe considered boilerplate. The instruction says remove application instructions. That line is encouraging to apply; could be considered application instruction. Safer to remove. Also remove "Final compensation is determined..."? That's pay info, keep. Also remove "This position is also eligible for annual bonus." keep as part of pay. Now craft HTML. We need to preserve all substantive information. Let's extract. Company intro paragraph: "At AbsenceSoft, we’re transforming the employee experience. Our secure, intuitive technology helps employers bring humanity, certainty, and efficiency to some of the most complex moments in the workplace. Built by HR professionals for HR professionals, we’re proud of where we’ve been and even more excited about where we’re going." Role description paragraph: "The Software Engineer IV / Tech Lead is a hands-on technical leader who owns the core infrastructure that powers AbsenceSoft's enterprise leave management platform. This is a formal tech lead role, not a senior IC position with a title attached — you'll be expected to mentor engineers, drive architecture, and shape technical planning, in addition to writing production-quality code yourself. You'll lead through technical excellence, architectural influence, and mentorship, partnering closely with Engineering and Product leadership to balance platform investment against product priorities and drive the long-term health of the platform" We can combine into one or two paragraphs under About the role. Responsibilities bullet list (from "What You’ll Do"): - Lead major technical initiatives — set direction, make key decisions, and coordinate engineering efforts across teams - Architect and build enterprise identity systems, implementing OAuth2, SAML 2.0, and OIDC, and defining authorization models like RBAC and data access governance - Own multi-tenant architecture, designing data isolation and provisioning workflows that make customer onboarding seamless and scalable - Ship complex features and platform components using .NET/C# on AWS, applying enterprise-grade engineering practices along the way - Strengthen data infrastructure by improving processing pipelines for reliability, observability, and performance, and by resolving complex production issues before they become bigger problems - Shape the roadmap by partnering with Engineering and Product leadership to balance platform investment against feature delivery, and by evaluating new technologies worth adopting - Raise the bar for the team through code and design reviews, mentorship across multiple teams, and continuous improvement via refactoring, automation, and tooling - Help uphold security and compliance standards across your area of the platform Required Skills bullet list (from "What’ll Set You Up for Success"): - Bachelor's degree in computer science, Engineering, or a related field — or equivalent experience — plus a track record leading complex technical initiatives - Advanced proficiency in .NET/C#, building enterprise-grade software on a modern stack - Hands-on experience implementing identity and authentication protocols (OAuth2, SAML 2.0, OIDC) in enterprise SaaS environments - Proven ability designing multi-tenant SaaS architectures, including tenant isolation, data access patterns, and provisioning workflows - Strong grasp of system architecture, scalability principles, and authorization frameworks (RBAC, data governance) in regulated environments - Sharp problem-solving and debugging skills, with the independence to drive end-to-end solutions Preferred Skills bullet list (from "Preferred Skills"): - 7-12 years of professional software engineering experience with SaaS platforms, distributed systems, and cloud infrastructure (AWS) - Prior involvement in platform-scale initiatives, like framework migrations or multi-tenant redesigns - DevOps fluency, including containerization and CI/CD pipelines - Experience supporting compliance programs such as SOC2 or HIPAA - Polyglot backend skills — Python and/or Node.js/JavaScript — NoSQL (MongoDB, CosmosDB) databases - Familiarity with embedded analytics or BI tooling such as Sisense - Experience with relational databases such as PostgreSQL or other ANSI SQL-compliant databases. Key Skills & Behaviors bullet list (from "Key Skills & Behaviors"): - A natural technical leader and mentor who thrives on guiding direction and coordinating work across teams — not just executing to spec - A clear communicator who can translate complex, systems-level thinking for technical and non-technical audiences alike - Collaborative, adaptable, and results-driven, with genuine pride in the foundational platform work that powers everything else - Curious about AI tools and concepts, and eager to put them to work Benefits bullet list (from "Why join us" and "We Offer"): We need to parse each benefit: - Impact that matters. You’ll do work that shapes the future of the modern workplace - Flexibility and trust. We’re remote-first and results driven. You’ll have the freedom and flexibility to do your best work, wherever you do it best. - Growth and development. We believe the best work happens when people are growing. You’ll have access to learning resources, leadership programs, and real opportunities to take on new challenges and expand your impact. - Competitive rewards. We offer comprehensive benefits, a performance-based bonus program, and equity opportunities – because when we grow, you should too. - Time for life. Recharge and reconnect with flexible time off, paid holidays, and flexible leave programs designed to support every season of life. - Belonging and balance. We’re building an inclusive culture where every voice is valued, collaboration is celebrated, and success is shared. We’re committed to building a team as diverse as the customers we serve. Also there are values: Lead with Innovation, Elevate Every Voice, Achieve Together, Drive Outcome. Those are more values but could be considered benefits? They are part of culture. Might include as benefit items. The instruction: preserve ALL substantive information. So we should include those values as part of benefits or maybe as separate? Since we have Benefits section, we can include them as bullet points. Thus benefits bullets: - Lead with Innovation – We create meaningful change through intelligence, focus and passion. We embrace curiosity, data, and insight to shape the future of our industry. Always innovating, learning and evolving. - Elevate Every Voice – Every perspective matters. We listen, learn, and build a culture where diversity of thought and experience drives better solutions and smarter decisions. - Achieve Together – The customer fuels everything we do. We share knowledge, collaborate, celebrate wins, and face challenges as one team because success is always a collective achievement. - Drive Outcome – Every action we take delivers measurable value to our teams, our customers, and the employees they support. Accountability is non-negotiable. We honor our commitments, take responsibility for results, and see every success and setback as a chance to grow stronger. - Impact that matters. You’ll do work that shapes the future of the modern workplace - Flexibility and trust. We’re remote-first and results driven. You’ll have the freedom and flexibility to do your best work, wherever you do it best. - Growth and development. We believe the best work happens when people are growing. You’ll have access to learning resources, leadership programs, and real opportunities to take on new challenges and expand your impact. - Competitive rewards. We offer comprehensive benefits, a performance-based bonus program, and equity opportunities – because when we grow, you should too. - Time for life. Recharge and reconnect with flexible time off, paid holidays, and flexible leave programs designed to support every season of life. - Belonging and balance