Senior Software Engineer, Benefits

About the role

This role focuses on owning large-scale projects in a regulated benefits environment, collaborating across product and operations teams, and driving reliable solutions that improve employer and employee experiences. The work supports business growth by simplifying complex benefits processes and strengthening outcomes for customers.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Performance, reliability, and scalability of existing systems are improved through iterative enhancements and technical leadership. Engineering excellence is advanced through knowledge-sharing, documentation, mentorship, and influence across teams. High-volume, fault-tolerant processing infrastructure is extended to support benefits management and data needs. Testing, monitoring, and continuous deployment processes are enhanced to increase stability and delivery confidence. Sensitive employee and benefits data is kept secure and properly compartmentalized through controlled access and careful handling.

Requirements

A minimum of 7 years of professional hands-on experience is required for this role. Mastery of modern server-side languages is expected, with Golang as a plus but not required. Proficiency with SQL and cloud infrastructure management, preferably on AWS, must be demonstrated. Experience supporting and mentoring other engineers is necessary to act as a force multiplier across the team. Close collaboration with designers and product managers is required to align solutions with user and business needs. All Justworkers apply behaviors aligned with the COGIS values of Camaraderie, Openness, Grit, Integrity, and Simplicity in this role.

Nice to have

Experience working in highly regulated environments and with benefits or HR systems is valued. Familiarity with data privacy and security best practices for sensitive information is encouraged.

Skills & tools

Core tools and technologies used in this role include Golang, Ruby on Rails, JavaScript, MySQL, Kafka, AWS, Git, Memcache, Redis, ElasticSearch, Docker, Terraform, Kubernetes, CircleCI, and DataDog. These technologies support scalable, reliable, and secure solutions in a fast-paced product environment.

Practical notes

This role is based in New York, New York, with hybrid work expectations. Actual pay varies by candidate skills and experience. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Work in this role involves large-scale systems in a highly regulated domain. Collaboration across product, design, and operations is central to delivering reliable benefits solutions. The team uses modern cloud and infrastructure tools to support scalability and security. Continuous learning and knowledge-sharing help engineers grow and improve outcomes. Mentoring and influence across disciplines strengthen the impact of each contribution.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.