Senior Staff Software Engineer - Hybrid
The Hartford · Hartford, CT · 1 mo ago
Hybrid$128k–$191k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: description (intro) maybe "About the role". Responsibilities list. Required Qualifications and Preferred Qualifications maybe under Requirements or Qualifications. There's also compensation (Pay). No explicit Benefits or Schedule. So we include About the role (intro paragraph), Responsibilities (ul), Requirements (maybe combine Required Qualifications?), Qualifications (maybe Preferred?), Skills? Could embed skills in responsibilities or qualifications. But we need to follow headings exactly: for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should only emit sections with real content.
We have content for About the role (intro paragraph). Responsibilities (list). Requirements (maybe Required Qualifications). Qualifications (maybe Preferred Qualifications). Skills? Could be derived from required qualifications but we might not have separate skills section; we could omit Skills if no explicit skills list. Pay: we have compensation range. Benefits: none explicit. Schedule: none explicit (full-time mentioned but not schedule details). Could we include Schedule? The posting says full-time but not schedule details; we should not create Schedule unless specific content. So omit.
Thus output:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should only emit sections with real content.
We have content for About the role (intro paragraph). Responsibilities (list). Requirements (maybe Required Qualifications). Qualifications (maybe Preferred Qualifications). Skills? Could be derived from required qualifications but we might not have separate skills section; we could omit Skills if no explicit skills list. Pay: we have compensation range. Benefits: none explicit. Schedule: none explicit (full-time mentioned but not schedule details). Could we include Schedule? The posting says full-time but not schedule details; we should not create Schedule unless specific content. So omit.
Thus output:
About the role
... intro paragraph ...
Responsibilities
- ... each responsibility ...
Requirements
- ... required qualifications ...
Qualifications
- ... preferred qualifications ...
Pay
The annualized base pay range for this role is: $127,600 - $191,400
We need to preserve all substantive information; do not invent or summarize away detail. Must include all responsibilities lines, required qualifications, preferred qualifications, compensation note. We must remove boilerplate like EEO etc. Also remove "Equal Opportunity Employer..." line. Also remove "The Hartford is hiring a full-time Senior Staff Software Engineer to design, build, and modernize Claims IT solutions with strong Guidewire, Java, and AWS depth." That's part of about role. We need to ensure we don't repeat job title as heading. Already not. We need to format as HTML fragment only. Let's extract the intro paragraph: "We’re determined to make a difference and are proud to be an insurance company that goes well beyond coverages and policies. Working here means having every opportunity to achieve your goals – and to help others accomplish theirs, too. Join our team as we help shape the future. The Hartford is hiring a full-time Senior Staff Software Engineer to design, build, and modernize Claims IT solutions with strong Guidewire, Java, and AWS depth. This role blends core platform engineering with select Forward Deployed Engineer responsibilities to accelerate delivery with business teams and drive measurable production outcomes. Hands-on experience creating AI agents using Google ADK is a strong plus." That's the about role. Responsibilities list: each bullet after "Key Responsibilities". Let's capture: - Design, develop, and enhance Guidewire ClaimCenter workflows, rules, and integrations for claims operations. - Build resilient Java APIs and backend services for high-volume claims transaction processing. - Architect and implement cloud-native AWS services with focus on reliability, security, performance, and cost. - Own end-to-end engineering delivery: design, build, test automation, release, and production support. - Implement CI/CD, code quality gates, observability, and engineering standards across services. - Collaborate with product owners, claims SMEs, architects, and operations to convert business goals into technical solutions. - Lead incident troubleshooting, root-cause analysis, and permanent corrective actions. - Mentor engineers through architecture reviews, coding standards, and delivery best practices. - Partner directly with business and operations stakeholders to understand field workflows and convert them into deployable capabilities. - Run discovery workshops to identify high-value use cases, define MVP scope, and prioritize quick-win automation opportunities. - Rapidly prototype solutions, validate with end users, and productionize successful patterns into durable platform services. - Embed with cross-functional teams during critical releases to unblock dependencies and reduce time-to-value. - Build implementation playbooks and onboarding guides that improve adoption across claims teams. - Establish outcome metrics (cycle time, accuracy, throughput, incident rate) and iterate based on production feedback. - Act as technical bridge across engineering, business, and support teams during rollouts and post-launch stabilization. - Build practical agents with Google ADK for document understanding, claims decision support, and workflow orchestration. Required Qualifications list: - Bachelors degree in Computer Science, Engineering, or related discipline. - 7+ years of software engineering experience in enterprise environments. - Strong hands-on Guidewire cloud experience, preferably ClaimCenter implementation and must have - Must have Guidewire claims center certification. - Strong hands-on Java experience building APIs, integrations, and distributed services. - Strong AWS and/or GCP engineering experience delivering production cloud solutions. - Experience with event-driven systems, asynchronous messaging, and secure REST integration patterns. - Proficiency in automated testing, CI/CD pipelines, and DevOps practices. - Experience in observability, logging, and production operations support. - Strong communication and stakeholder collaboration skills. Preferred Qualifications list: - Hands-on Google ADK experience building enterprise-grade agents. - Experience integrating LLM services into business processes with governance and monitoring. - Proven ability to lead delivery across cross-functional teams. Compensation paragraph: "The listed annualized base pay range is primarily based on analysis of similar positions in the external market. Actual base pay could vary and may be above or below the listed range based on factors including but not limited to performance, proficiency and demonstration of competencies required for the role. The base pay is just one component of The Hartford’s total compensation package for employees. Other rewards may include short-term or annual bonuses, long-term incentives, and on-the-spot recognition. The annualized base pay range for this role is: $127,600 - $191,400" We need to include all that substantive info. Could we condense? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the full compensation paragraph, not just the range. So include the whole paragraph. Thus Pay sectionwith that paragraph. Now ensure we don't include boilerplate like EEO line. Now produce HTML. We'll wrap each section with