Role Proficiency:
Understands customer requirements streamline DevOps practices and translate them into reference architecture for DevOps (CI/CD) and automation components by managing multiple scrum teams.
Outcomes:
Interprets the DevOps Tool/feature/component design to develop/support the same in accordance with specifications Adapts existing DevOps solutions and creates own DevOps solutions for new contexts Codes debugs tests documents and communicates DevOps development stages/status of DevOps support issues Selects appropriate technical options for development such as reusing improving or reconfiguration of existing components Optimises efficiency cost and quality of DevOps process tools and technology development Validates results with user representatives; integrates and commissions the overall solution Assesses current state of DevOps maturity and advises clients on improving maturity and DevOps roadmap Assess readiness of clients to adopt DevOps practices advising clients on appropriate change approaches and technology choices Looks for patterns of struggle and experiments with new designs and new ways of applying existing designs to solve problems Guides DevOps leads and engineers and observe how the processes are working in practice Works towards reducing variations in practice by challenging status quo and tweaking processes and tools Resolve architecture issues and deliver / own architecture of application solutions spanning across multiple technologies for projects of the following nature - high revenue projects / complex projects / large strategic maintenance projects Manage multiple stakeholders and handle their expectations Contribute to business development and organizational activities Support Architect/Sr. Architect in drafting recommendations based on findings of Proof of ConceptMeasures of Outcomes:
Quality of Deliverables Defect injection at various stages of lifecycle SLA/KPI for onboarding projects or applications Percentage achievement of specification/completeness/on-time delivery # of reusable components / processes developed Delivery efficiency (Adherence to UST defined principles) Contribution to technology capability development (e.g. Training Webinars Blogs) Customer feedback on overall technical quality (zero technology related escalations) # of white papers/document assets contributed to Feedback from Project Team/Program Management on project support Error rate/completion rate at various stages of SDLC/PDLC Uptime/System reliability metrics (if the design is not meeting with agreed SLA’s) # of domain certification/ product certification obtained Adoption rates of CI/CD tools DevOps practices (efficiency improvement rate)Outputs Expected:
Automated components :
Deliver components that automat parts to install components/configure of software/tools in on premises and on cloud Deliver components that automate parts of the build/deploy for applications
Configured components:
Scripts:
Training/SOPs :
Measure Process Efficiency/Effectiveness:
innovation and technology changes
Operations:
Solution Definition & Design:
architects and client SME Present the detailed design documents to relevant stakeholders and seek feedback Undertake project specific Proof of Concepts activities to validate technical feasibility with guidance from the Application Architect Implement best optimized solution and resolve performance issues Support the team in the design of functional modules and review the deliverables Conduct code reviews
Project Estimation:
module level estimations for more standard projects with focus on estimation effort alone
Measure Process Efficiently/Effectiveness:
Skill Examples:
Design branching and merging strategies Defining DevOps tool stack Designing build/release plans Defining monitoring strategy/service provisions/middleware configuration Integrate with code quality analysis tools like SONAR Scripting skills (Javascript Python Linux PowerShell) Infrastructure automation skill (ansible/terraform) Quality automation skills(selenium) Experience of build deploy pipeline for polygot tools Database automation Java Python Perl Creating build plan in Bamboo/Jenkins/GITLAB and necessary scripting to implement build Setting and managing Jira projects and Git/Bitbucket repositories Skilled in Automated Build and Deployment and tools like Maven Ant.etc Skilled in Automated Monitoring(Splunk) Skilled in containerization tools like Docker Monitoring reviewing and managing technical operationsKnowledge Examples:
Knowledge of Config/Build/Deploy processes and tools Knowledge of infrastructure planning testing and development Knowledge of IAAS - Cloud providers (AWS Azure Google etc.) and their tool sets Knowledge of the application development lifecycle Knowledge of Quality Assurance processes Knowledge of Quality Automation processes and tools Knowledge of multiple tool stacks not just one Knowledge of Branching/Merging strategies Knowledge about microservices and containerization Understanding of rapid technology changes and concepts Knowledge of software security compliance (GDPR/OWASP) and tools (Blackduck/ veracode/ checkmarxs)Additional Comments:
Job Title: Specialist DevOps Engineer (GitHub Migration) Overall experience: 9+ years Relevant Experience: 7+ years of specific experience working with GitHub enterprise and preferably Perforce. Preferred Certification: GitHub Administration Job Summary: As a DevOps engineer working on Perforce to GitHub migration, you are expected to be experienced with GitHub Enterprise and Perforce, be familiar with version control concepts, possess scripting ability (especially in Python or shell), and have adequate knowledge of large-scale source control systems to efficiently execute the migration and handle potential pitfalls. To be successful in this role, you must be a motivated self-starter and self-learner, possess strong problem-solving skills; and be someone who embraces challenges. Key Responsibilities: Analyzing and preparing Perforce repositories, including cleaning workspaces, merging streams, and removing unnecessary files. Handling large files efficiently by configuring Git Large File Storage (LFS) to accommodate files that exceed GitHub's size limits (typically 100MB per file). Using git-p4 fusion, a Python-based tool, to clone Perforce repositories to Git, and managing the migration process incrementally to ensure data integrity. Deciding on the migration scope, such as how much history to migrate and planning repository structure. Managing branch renaming and organizing the Git repository for an optimized workflow post-migration. Collaborating with development teams to determine migration points and confirm a shared migration strategy. Troubleshooting issues related to file sizes, Python compatibility with git-p4 fusion, and network or permission issues during migration. Required Qualification We are looking for a DevOps Engineer with deep technical and analytical skills. Strong knowledge of Git/GitHub version control systems and preferably Perforce (Helix Core), including understanding their differences and workflows. Hands on experience in P4-Fusion. Familiarity with cloud infrastructure (AWS, Azure) and containerization technologies (Docker, Kubernetes). Proficiency with migration tools like git-p4 fusion, including installation, configuration, and troubleshooting. Ability to analyze Perforce repositories to identify large files and manage them using Git Large File Storage (LFS) to meet GitHub size limits. Scripting skills, especially in Python and shell scripting, to automate migration tasks and handle repository restructuring. Experience in planning and executing source control migrations, including deciding migration scope (e.g., relevant history retention), branch mapping, repository restructuring, and user/permission translation. Familiarity with CI/CD pipelines integration and validation post-migration to ensure testing and deployment workflows are not disrupted. Understanding of source code management best practices, version history handling, and repository organization in GitHub. Communication and collaboration skills to work with teams to decide on migration timing and strategies and addressing other technical challenges. Practical migration experience, source control expertise, and the ability to manage repository history and large file storage configurations for a smooth transition from Perforce to GitHub Git/GitHub, perforce (Helix Core), AWS, Azure, Docker, Kubernetes, hands on experience with P4-fusion, Scripting (Python & Shell), CI/CD pipelines