What is the difference between a pipeline stage and a job?
Interviewer Expectations for this Question
01
Core Competency
Assesses fundamental understanding of CI/CD conventions, runtime behavior, and memory/performance considerations.
02
Evaluation Criteria
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Comprehensive Model Answer
Verified Solution
Stages and jobs structure a pipeline into ordered, parallelisable work.
- Stage: a logical phase such as build, test, or deploy. Stages run in order, and a later stage starts only when earlier stages succeed. Stages express the release lifecycle.
- Job: the actual unit of work inside a stage, running on a runner or agent. Jobs within the same stage can run in parallel. Each job has steps, scripts, and its own environment.
stages: [build, test, deploy]
test:
stage: test
script:
- npm ci
- npm test
For example, a test stage may run unit, integration, and lint jobs concurrently, and then a deploy stage runs only if all pass. Jobs can produce artefacts that later jobs consume. Some tools call these stages and jobs, while others use workflows and jobs, but the concept is the same: ordered phases and parallel tasks.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.