Senior Software Engineer - Devops
Gap Inc. · Spoke - Hyderabad, India
What the posting says
Each fact was read from this posting and checked:Statedin the posting, quotedConflictsposted two ways, both shownNot mentionedwe looked; it is not there
- Employment typeStated
- Full time
- ShiftStated
- on call
· Participate in an on-call rotation with support from senior team members.
from the posting
Not mentioned in this posting
We read the whole posting. These are not in it. Not a no: ask the recruiter, in your own words.
- PayNot mentioned
- The posting does not say
- Work arrangementNot mentioned
- The posting does not say
- ExperienceNot mentioned
- The posting does not say
- EducationNot mentioned
- The posting does not say
- Visa sponsorshipNot mentioned
- The posting does not say
Requirements, each with its sentence from the posting
These are the employer’s words. The index does not judge whether you meet them.
- No requirement has been itemized for this posting yet. The employer’s words are in the full posting below.
Read the full posting as the employer wrote it
About the Role
The Build team at Gap Inc. plays a key role in enabling engineering teams to deliver software efficiently and reliably. As a Software Engineer on the Build team, you will help support and improve the CI/CD infrastructure, tools, and processes used across the organization.What You'll Do
Responsibilities:
· Supporting and maintaining CI/CD systems used by engineering teams.
· Building and improving tools that simplify build and deployment workflows.
· Partnering with platform and product teams to enhance developer experience.
· Reducing friction in build and deployment processes so teams can focus on delivering features.
· Assist in maintaining and improving build systems and CI/CD pipelines.
· Help identify issues in build and deployment workflows and contribute to solutions that improve reliability and reduce build times.
· Follow established best practices for source control, builds, and deployments, and contribute to improving them over time.
· Learn and experiment with new build tools and technologies, sharing insights with the team.
· Participate in code reviews and collaborate with teammates on shared solutions.
· Write and maintain scripts or small tools to improve developer workflows.
· Work with other platform teams (Ship, Schedule, Observe) to support overall engineering goals.
· Participate in an on-call rotation with support from senior team members.
· Help monitor build systems and contribute to resolving incidents and improving stability.
· Contribute to documentation to help teams use build and deployment tools effectively.
Who You Are
· 4+yrs of software engineering experience, with some exposure to CI/CD or build system.
· You have hands-on development experience building and maintaining applications or services and understand basic software development practices.
· You are comfortable working with Git and standard version control workflows.
· You have some experience with CI/CD tools (e.g., GitHub Actions, Jenkins) or are eager to learn.
· You are familiar with at least one programming language (e.g., Terraform, Python, Java, or Go).
· You have basic exposure to Docker or containerized applications.
· You are familiar with cloud platforms (GCP or Azure) at a foundational level.
· You have basic Linux knowledge and can troubleshoot simple issues.
· You are eager to learn, ask questions, and collaborate with teammates.
· You can write clear and simple technical documentation.
· You are comfortable working in a team environment and taking ownership of small to medium-sized tasks.
Core up-front tools/skillsets
- CI/CD tools: GitHub Actions, Jenkins (basic pipeline knowledge)
- Programming/Scripting: Python, Java, or Go, Terraform
- Version Control: Git (branching, PR workflows)
- Containers: Docker; basic Kubernetes concepts
- Cloud: GCP/Azure (foundational knowledge)
- Build Tools: Maven, Gradle, npm (basic usage)
- OS Skills: Linux fundamentals and troubleshooting
- Collaboration: documentation, team communication
The posting text is reproduced as the employer wrote it; the index adds nothing to it.