
Job Titl: Technical Lead - Java
HM Ideal Job Title Technical Lead Insurance Policy Booklet Generation
Duration: 6-12 mo CTHire
Location : Hartford, CT (Hybrid 3 days) relocation is acceptable local or regional priorized
Daily Schedule 8:00 AM 5:00 PM ET Number of Openings 1
CSA Screening MUST include availability Submittal Limit (per Supplier) 2
Interview Mode Virtual is acceptable, Onsite interview is a clear plus especially for second round interviews. Specify in your submission.
Java Technical Lead
API Design:
o Strong background in good API design, understanding restful practices, and scalable API architecture.
o Experience in defining clear open APIs.
o "They're a lead developer for developers."
Responsibilities:
o Leading the effort to develop and wire APIs into Pega workflows for automation.
o Primarily focused on Java development, not Pega coding.
Additional Skills:
o Experience writing MCP clients tools is highly beneficial for creating AI agents to wrap APIs.
Responsibilities:
o Responsible for implementation, production, support, and testing.
DevSecOps and Cloud Deployment
DevSecOps is implemented in the CI/CD pipeline.
Developers are deploying applications and maintaining DevOps pipelines using enterprise tooling.
API developers should be writing APIs for cloud deployment, specifically AWS gateway.
Candidates should be proficient in CI/CD, Jenkins, and GitHub.
API Developer Expectations
Modern API developers should be fully conversant on DevSecOps pipelines and writing for the cloud, including Terraform scripts.
They should know how to monitor application health on AWS and configure pods and clusters.
Missing these skills is a "big red flag."
Story Behind the Need Business Group & Key Projects
Compelling Story & Candidate Value Proposition
Candidate Requirements
Years of experience required
Degrees or certifications required
Disqualifiers
Best vs. average
Performance indicators
Top 3 must-have hard skills
Level of experience with each
What are the top 3 skills that your ideal candidate would have? (Years of experience with each)
1
Java (8+ years): enterprise back-end development, service design, code quality and reviews, technically leading others (4+ years).
2
Technical Design & Data Modeling (5+ years): simplify complex legacy models; design extensible, product-agnostic data structures.
3
AWS & Cloud-Native Engineering (3 5+ years): cloud services, security/IAM, CI/CD, observability; building scalable APIs/microservices.
Candidate Review & Selection
Shortlisting process
Second touchpoint for feedback
Interview Information
and Expectations
Availability of HM for interview:
Immediately
Number and Type of Interviews:
Interviewing can begin immediately. Anticipated process: 2 rounds. Round 1: technical interview (Java, architecture, data modeling, AWS/cloud patterns). Round 2: solutioning/leadership interview (technical design, refactoring and simplification approach, trade-offs, stakeholder collaboration). No formal coding test required; expect whiteboarding and design discussion using prior examples.
Extra Interview Prep for Candidate
Be prepared to discuss an example where you simplified an overly complex architecture/data model, including before/after diagrams, trade-offs, and measurable outcomes.
Job Description: Technical Lead to lead the design and development of the Policy Booklet Generation module within a policy administration system. Responsible for reviewing and simplifying an overly complex architecture, streamlining and extending the data model to support multiple employee benefits products, defining integration patterns and APIs, and providing hands-on technical leadership (design reviews, code reviews, mentoring) through delivery.
Key Responsibilities
Technical & Design Leadership
Delivery Leadership