Job Description:

JD :

A GitHub Architect is a senior technical expert
responsible for designing, implementing, and governing enterprise -grade
development workflows, repository structures, and CI/CD pipelines on the GitHub
platform.

Key Responsibilities

- Enterprise Design: Architect scalable, enterprise -grade GitHub
organizations and repository structures matching business and security
needs.

- Governance Strategy: Create policies for access control, branch
protection, repository lifecycle management, and auditing.

- Platform Migration: Lead complex migrations and strategy roadmaps moving
codebases and CICD pipelines from Jenkins, Bitbucket, or Azure DevOps to
GitHub

- Security Enforcement: Implement GitHub Advanced Security (GHAS) controls,
including secret scanning, dependency tracking, and code scanning

- Technical Mentorship: Act as a trusted advisor to teach development teams

- Stakeholder Engagement: Collaborate with security, product, and leadership
teams to translate business requirements into technical solutions.


Required Technical Skills

- Expert GitHub Administration: Deep knowledge of GitHub Enterprise Server,
Cloud, organization provisioning, and GitHub APIs.

- Advanced Version Control: Mastery of Git internals, complex branching
strategies (GitFlow, Trunk -Based), and merge conflict resolutions.

- CI/CD Mastery: Deep experience crafting custom, reusable GitHub
Actions, runners, and environments.

- DevSecOps Tooling: Practical experience configuring security
scanners, binary repositories, and quality monitoring systems.

- Cloud & Containers: Proficiency with cloud -native hosting (AWS,
Azure, GCP) and container ecosystems like Docker and Kubernetes


Soft Skills & Leadership

- Consultative Mindset: Ability to actively listen to engineering
friction points and offer structural remedies.

- Explicit Communication: Adept at translating complex DevOps setups into
high -level visual roadmaps for executive leadership.

- Problem Solving: Technical curiosity to debug deep pipeline
blockers, caching issues, or runner resource limitations