Solartis Architect

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Keep substantive info. We need to parse the posting. Key info: Company Overview: NTT DATA description, but we might include as About the role? Actually "Company Overview" could be considered "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company overview under About the role? Or maybe we can create an "About the role" section summarizing role description. The posting includes "Solartis Architect Job Description" paragraph: "We are seeking an experienced Solution Architect specializing in Property & Casualty Insurance focusing on commercial lines & Solartis Insure platform, including policy administration and microservices deployment, experience in integrating Solartis with enterprise applications is critical skill for this role. The ideal candidate should have over 8 years of experience in the insurance domain, strong communication skills, and the ability to manage teams and relationships with stakeholders." That's about the role. Then "Day to Day job Duties: (what this person will do on a daily/weekly basis) Roles & Responsibilities of Solution Architect (P & C Insurance - Commercial Lines)" then bullet list of responsibilities. Then "Basic Qualifications: (what are the skills required to this job with minimum years of experience on each)" then a long list of qualifications. Then "Nice to Have; (But not a must) Experience in SaaS is a plus but not mandatory" Then "About NTT DATA:" description. Then compensation: "Where required by law, NTT DATA provides a reasonable range of compensation for specific roles. The starting hourly range for this remote role is $90 to $106. This range reflects the minimum and maximum target compensation for the position across all US locations. Actual compensation will depend on several factors, including the candidate's actual work location, relevant experience, technical skills, and other qualifications. This position may also be eligible for incentive compensation based on individual and/or company performance." Then benefits: "This position is eligible for company benefits that will depend on the nature of the role offered. Company benefits may include medical, dental, and vision insurance, flexible spending or health savings account, life, and AD&D insurance, short-and long-term disability coverage, paid time off, employee assistance, participation in a 401k program with company match, and additional voluntary or legally required benefits." Then accessibility statement etc (boilerplate). Remove EEO etc. Travel: Remote. Preferred location is East coast or Midwest. Degree: Bachelors in Computer Science or equivalent work experience. Schedule? Not mentioned explicitly. It says remote role, but schedule not given. So we should not create Schedule section unless present. No schedule details. Pay: we have hourly range $90 to $106. So we can create Pay section. Benefits: we have benefits list. So Benefits section. Skills: maybe we can extract skills from qualifications: but we have Qualifications section already. The instruction includes Skills as a possible heading. We could put technical skills under Skills, but we already have Qualifications. Might combine? The instruction says prefer a few substantive sections over many thin ones. We have About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Requirements? But Qualifications covers requirements. Could also have Requirements separate but we can skip to avoid thin sections. We need to use

for section headings. Use

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

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them as lists or paragraphs. We must not repeat job title as heading. So no heading "Solartis Architect". Good. We must not put Job ID/requisition numbers as headings; we can drop them or fold into short p. Probably drop. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we remove the EEO statements, accessibility contact, etc. We must keep the company overview description (NTT DATA) maybe under About the role? Or we could have an "About the company" but not in allowed headings. Since allowed headings are limited, we could put company overview under About the role as part of role description? Might be okay. Better: Use About the role for role description (the paragraph about seeking experienced Solution Architect). Use Responsibilities for duties. Use Qualifications for basic qualifications and nice-to-have. Use Benefits for benefits list. Use Pay for compensation range. We also need to include degree requirement and travel/location info. Where to put? Could be under Qualifications (as part of qualifications) or maybe under About the role? Probably Qualifications includes education and location preferences. We also need to include "Preferred location is East coast or Midwest." and "Travel: Remote." Could be under Qualifications or maybe a separate section like "Location" but not allowed. So we can include in Qualifications as a bullet. We must not create sections with filler like "commensurate with experience". We have actual pay range. Now let's extract details. About the role paragraph: "We are seeking an experienced Solution Architect specializing in Property & Casualty Insurance focusing on commercial lines & Solartis Insure platform, including policy administration and microservices deployment, experience in integrating Solartis with enterprise applications is critical skill for this role. The ideal candidate should have over 8 years of experience in the insurance domain, strong communication skills, and the ability to manage teams and relationships with stakeholders." That's the core. Responsibilities: list from "Day to Day job Duties:" and the bullet points under Roles & Responsibilities. Let's extract each bullet: - Technical Leadership * Prioritize AI throughout the SDLC. * Skilled in AI-assisted coding tools for higher productivity. * Skilled in one stack and adaptable polyglot engineer across entire application stack. * Design and develop solutions with Azure, ReactJS and .NET. * Set standards in code, reviews, and best practices. * Guarantee architecture compliance, performance, and technical quality. - Agile Delivery * Work with the Product Owner and Scrum Master to plan sprints, estimate tasks, and refine the backlog. * Break down business requirements into technical stories or tasks. * Participate in daily stand-ups and technical ceremonies as required. - Integration Ownership * Contribute to all aspects of application integration, including REST APIs, Azure Service Bus, Event Grid, Logic Apps, and other Azure Integration Services. * Serve as the primary point of contact for integration requirements, coordinating with platform and partner teams as necessary. * Prepare and verify API contracts, data models, event schemas, and integration patterns through comprehensive documentation and validation processes. - Requirement & Interface Management * Convert application-specific features into precise technical artifacts. * Coordinate system interface specifications, data flow processes, and communication protocols. - Stakeholder Communication * Share technical vision, risks, and progress with architects, project managers, and business stakeholders. * Participate in cross-team architecture and design discussions as an application representative. We need to preserve all these details. We'll format as

  • each bullet. Could group under subheadings? Not allowed; only headings are the specified ones. So we just list all responsibilities as a flat list? Might lose grouping but still preserve content. Could we embed subheadings as inside li? That might be okay but not required. Safer to just list each bullet as li. Now Qualifications: Basic Qualifications list is long. Let's extract each item. From "Basic Qualifications: (what are the skills required to this job with minimum years of experience on each)" then a paragraph with many items separated by periods. Let's parse: - 8+ years’ experience in Solartis Insure - Policy Admin Platform, full policy lifecycle—from submission and quoting to endorsements, (renewals, and audits - nice to have). - 8+ years’ experience in integration of Solartis with enterprise systems - UX using React, Rect js, and reasonable experience in python Fast API, and SQL Server RDBMS. - Proficient in using AI code generation tools like GitHub Copilot, Codex, Claude Code, Cursor, etc. - Understanding of CI/CD and infrastructure automation. - Knowledgeable about integration patterns (sync/async, event-driven, pub-sub). - Very good knowledge of Solartis microservices - experience in working with Azure cloud platform and services, Strong knowledge of cloud architecture patterns, principles, and best practices, Proficient in C#, .NET, SQL, and Azure DevOps, Experience in using Azure services such as App Services, Functions, Logic Apps, Service Bus, Cosmos DB, Key Vault, etc. - Experience and knowledge of BPMN 2.0 driven jBPM rule flows and Knowledgebase servers - Knowledge & experience in collection framework plug-ins for database access, mail, document generation, etc. - 8+ years of Hands-on experience Supporting Applications Property & Causality insurance domain - commercial Lines insurance experience (especially Workers’ comp, Audit, Auto, GL, Property, packaged policies.) - Strong exposure to Underwriting, Policy admin application (Preferably Policy Decision) & functional knowledge - Strong communication skills, coupled with the ability to engage effectively with internal and external stakeholders and should be able to communicate in business language. - The ability to work with existing regional teams managing and mentoring. - Ability to communicate effectively with a diverse set of customers or partners across multiple disciplines. - Display patience in difficult situations and drive customer delight in every action. - A passion for the business which we operate in and a dedication and drive towards continuous improvement. - Follow and drive appropriate departmental and company procedures and policies. - Recognize and develop the technical nontechnical skills and abilities of team members. - Willing to go the extra miles to provide excellent service. - Reliable, able to work independently and inspire/motivate staff. - Travel: Remote. Preferred location is East coast or Midwest. - Degree: Bachelors in Computer Science or equivalent work experience Also "Nice to Have; (But not a must) Experience in SaaS is a plus but not mandatory" We need to include all these as qualifications. Could separate into Required and Nice-to-have but we only have Qualifications heading. Could still list all, maybe mark nice-to-have with a note. We'll create
    • for each qualification item. Now Benefits: list from "Company benefits may include medical, dental, and vision insurance, flexible spending or health savings account, life, and AD&D insurance, short-and long-term disability coverage, paid time off, employee assistance, participation in a 401k program with company match, and additional voluntary or legally required benefits." We'll make a list. Pay: The starting hourly range for this remote role is $90 to $106. Also mention incentive compensation based on individual/company performance. We'll include that. Now About the role: we have the paragraph. Also maybe include company overview? Could add a short paragraph about NTT DATA under About the role? But that's company overview, not role. However we have no separate heading for company. Could we include it under About the role as a brief description? Might be okay but risk of mixing. The instruction says "About the role" heading for section headings. It didn't forbid adding extra content like company overview inside that section. It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have those headings only. Inside each we can put any relevant content. So we can put company overview inside About the role as well, or we could put it under Responsibilities? No