Jenkins / GitHub Actions
Also written as Jenkins, GitHub Actions, GitLab CI, CircleCI
Specific tools that implement CI/CD pipelines — Jenkins is an older, highly configurable self-hosted option; GitHub Actions, GitLab CI, and CircleCI are newer, more managed alternatives built into or alongside a code host.
Think of it like
Like different brands of the same assembly-line equipment — Jenkins is the older, endlessly customizable machine you maintain yourself; the newer tools are more plug-and-play.
Junior or senior?
Junior sounds like
Doesn't know why their team uses one CI tool over another.
Senior sounds like
Can explain what made their team choose that specific tool, or whether it was just already in place when they joined.
Ask them
“What made your team choose that specific CI tool, or was it just already in place when you joined?”