Head of DevOps

The Forte Principal DevOps Engineer

About The Client:

We have built our technology using the best of cloud and open-source technologies to create an open, data-first platform that is enriched with analytical models and connected to the most modern internal and external apps. This platform provides the foundation for our digital front door through which we are creating a more accessible, personalized patient experience which includes telehealth, connected devices, and remote patient monitoring capabilities among many others.

Our technology solutions are 100% cloud-native and designed with elasticity, automation, and with API-first principles. Security is at the core of our operating mentality and is native to our investment thesis when procuring technology and deploying solutions.

Integral to the strategy of our Infrastructure & DevOps organization, the Principal DevOps Engineer will drive a wide variety of projects to support and maintain the organization’s converged infrastructure & tooling in a multi-site environment.

You are an Agile Team Member

Job #1 is to be part of a self-organizing team – a team that solves complex challenges and builds working software. Being a good team member means you contribute to it’s success by:

• Collaborating with your PO to groom backlog and break down stories into small functional slices
• Maintaining an attitude of commitment through outward display of willingness.
• Impressing responsibility on others by displaying ownership in tasks.
• Practicing positive interactions – lean on encouragement in place of judgment.
• Being open to new ideas and encouraging innovative practices amongst peers
• Actively working on broadening or adding a skill
• Asking for assistance when problems become challenging
• Balancing best practice decisions with delivering high business value (right vs right now)
• Delivers stories/tasks that are “committed” within a timebox

You are also the Principal Engineer

The Principal Engineer is considered the premier developer on the team. It is therefore your responsibility to engineer solutions within a large-scale platform to enable our client’s business while supporting the strategic architectural vision of quality, scalability, performance and function.

Principal Accountability | Technical Planning

• Owns technical design for a sprint including high-level flow diagrams, ERD, service contracts
• Ensures the whole team understands the technical plan, reasons for it, and adherence to it.
• Considers testability in design with focus on code determinism, abstraction, and modularity
• Commands a broad awareness of dependent projects and considers them in design
• Works with Enterprise Architects to ensure a team’s direction is in line with the enterprise vision
• Defines technical acceptance criteria (where necessary) for each story
• Integrates the technical PBIs and works with PO/client to justify and schedule those efforts

Principal Accountability | Software Development

• Communicates important details of the solution design to everyone on the team
• Encourages collective code ownership through CI and promotes frequent code check-ins (daily)
• Practices and teaches unit test development to achieve at least 80% code coverage
• Addresses technical debt constantly - escalating when it becomes risky to time or quality
• Develops with an awareness for team needs and acts as resource/mentor for junior members
• Oversees the merge up/down process
• Carries out root cause analysis on defects to ensure fixes are happening in the right way
• Keeps an up-to-date local development environment to reduce risk

Principal Accountability | Team Leadership

• Translate and break-down strategic technical vision into a consumable form for the team
• Assure team productivity meets a high standard that can be quantified
• Low-level development, testing and deployment tasks have ownership by team members
• Frequently thinks out loud about design with the team and a higher level design committee
• Helps team members define clear, small, and testable tasks
• Enforces the team’s Definition of Done
• Liaises between the team and management to assure needed skills are represented on the team

Principal Accountability | Software Inspection

• Ensures daily code check-ins (through spot checks) are happening by each member of the team
• Employs static code analysis to identify code readability, anti-patterns, vulnerabilities & defects
• Monitors unit level test results after code is committed and holds team to account on quality
• Considers cyclomatic complexity of code and drives project refactors where necessary
• Enforces transparency of the inspection process via Continuous Integration and reporting
• Reviews QA test plans for technical coverage
• Conducts cross team and inter-team code reviews

Principal Accountability | Release Planning

• Drives and adheres to a well-defined code promotion process
• Supports and is accountable for timely releases and adherence to release activities
• Resolves defects in a timely and effective manner
• Identifies tactical risks and raises/resolves issues effectively
• Ensures that operational teams are effective during deployment (dry-run or production)
• Follows up with infrastructure to create service accounts, permissions, access rights, etc
• Creates deployment documentation which outlines WHERE & WHAT?

Principal Accountability | Thought Leadership

• Collaborates outside of the product team to encourage a development community
• Establishes and carries out formal and informal educational sessions (lunch & learn, etc)
• Encourages self-study by promoting best practices and bringing in external perspective

What Will Make You Successful Here?

• A low ego and humility.
• Love for automation and strong analytical and data-driven approach to solve systemic problems.
• Effective communication including patience to listen and high degree of comfort with transparency.
• Ability to maintain calm and methodically driving resolution for high-impact production issues.
• Ability to deeply leverage Agile methods and practices to manage your work.

The Following Technical Experience is Relevant to us:

• Bachelor's degree in Computer Science, Information Systems, or related field.
• 5+ years of multi-disciplinary experience supporting cloud hosted infrastructure (AWS, Azure).
• Programming languages (Python, PowerShell, Go, Typescript).
• 5+ years of CICD and infrastructure-as-code experience (Terraform, SAM, Ansible, Kubernetes, GitHub Workflows, Drone CI).
• Monitoring and incident management tools such as DataDog, OpsGenie.
• Operating in local, remote, and containerized Linux environments.
• Source version control using Git and remote Git hosting providers such as GitHub and BitBucket.
• Ability to effortlessly deploy front end applications, APIs, and SaaS services on hard metal or containerized environments using infrastructure-as-code.
• Implementing security into the practice of DevOps. Intimate knowledge of AWS virtual private networks, security groups, IAM (Identity and Access Management).