Performance Outcome: Development of Products or Systems

A Software Engineer II will have a deeper understanding of the development processes and tools, including a stronger focus on quality, than more junior engineers. Initially the Software Engineer II might write code according to a specification or ticket written by someone else, using an architecture and/or design created by others. However, as they advance, they will contribute increasingly more to defining the requirements, architecture, and design of what they are building. They are more capable of working independently and not being blocked by others, and will have developed some expertise in their area of focus, which may include several different approaches to solving problems with their area. The Software Engineer II will begin to work on components that span a product and potentially a system and will also understand the components of other immediate team members and how their system interacts with these components. While still focused on tasks and tickets, they will begin to see beyond the current ticket and solve problems outside of the task at hand – they will see beyond an individual sprint, with an understanding of work that is happening several sprints out.

Individual tasks include:

• Frontend (as applicable):

• Perform frontend coding for web and/or mobile, using React, React Native, HTML, CSS, JavaScript, Node, or similar

• Implement UI primitives spanning web and mobile (contributing to internal open-source frameworks)

• Implement products used by external customers and service providers

• Backend (as applicable):

• Perform backend coding for systems and components, using C#/.Net, Node.js, or similar

• Implement new features and functionality in Node.js, and .NET as needed

• Write reliable and tested code including unit testing and CI/CD (continuous integration/continuous delivery) pipeline contributions

• Track problems, resolutions, and bug fixes throughout testing and create a comprehensive database of defects and successful mitigation techniques

• Use agentic AI coding tools (e.g., Claude Code, GitHub Copilot, Cursor) proficiently to accelerate feature development, reduce boilerplate, and increase throughput — demonstrating that one engineer + AI can match a small team’s output

• Serve as a quality gate for AI-generated code: critically review output for logical errors, security flaws, performance issues, and alignment with requirements before merging

• Engage in ongoing personal study of modern technologies and industry-related knowledge and skills

Performance Outcome: Engagement and Collaboration

The Software Engineer II will work intricately with their teammates and neighboring teams’ software engineers, product managers, and others. They will welcome and seek opportunities to learn and grow from more senior engineers as they also continue to develop their own leadership skills.

Engagement responsibilities include:

• Work closely and effectively with teammates, which may include fellow software engineers, program/product managers, software test engineers, and others

• Contribute to the implementation of dynamic requirements/initiatives with teammates, cross-team collaborators, and with business partners as appropriate

• Participate in daily agile stand-ups, story creation/sizing/updating

• Share on-call/escalation responsibilities with your team

Education, Knowledge, and Experience

• 2-5 years of industry experience in software engineering

• Bachelor’s degree in Computer Science or related field, or equivalent industry experience

• Coding proficiency:

• Frontend-focused software engineers: Intermediate ability to code in React, React Native, HTML, CSS, JavaScript, Node, or similar web technologies

• Backend-focused software engineers: Intermediate ability to code in C#/.Net, or similar object-oriented languages

• Attributes:

• Demonstrated proficiency with agentic AI coding tools (e.g., Claude Code, Cursor, GitHub Copilot) to accelerate development while maintaining code quality

• Ability to decompose problems into well-scoped tasks that can be effectively delegated to and validated from AI agents

• Ability to critically evaluate AI-generated code for correctness, security vulnerabilities, and architectural fit

• Willingness to learn new approaches and technologies

• Ability to work well with other engineers in a collaborative environment

• Attention to detail and quality

• Open-minded approach to new ideas and approaches

• Willingness to challenge others and be challenged

• Share in the goal of creating the best design and architecture possible

FLSA Status

Exempt

Physical Requirements/ Work Environment

Employee must be able to sit or stand for long periods of time, with the physical ability to work at the computer or other sedentary tasks for long periods of time. Employee can conduct duties discreetly and impartially. If working remotely, employee is able to work in a space that allows them to effectively complete their job tasks, including having reliable internet connectivity and the ability to participate effectively while on phone and video calls. Employee has regular and predictable attendance and punctuality.