Open Lance

DevOps, Cloud & Security

Hire CI/CD Engineers

CI/CD engineers automate how code gets from a commit to production: building, testing and deploying on every change.

Post a job How hiring works

The role

What CI/CD engineers do

A CI/CD engineer builds pipelines that run tests, build artefacts, deploy to staging and production, and roll back when something fails. They speed up slow pipelines with caching and parallel jobs, and keep secrets and deployment permissions safe.

Typical deliverables

  • Build and test pipelines
  • Automated deployments to each environment
  • Faster pipelines with caching and parallel jobs
  • Approval steps and rollbacks
  • Secrets management in CI

Tools you will see

  • GitHub Actions
  • GitLab CI
  • Jenkins
  • CircleCI
  • Argo CD
  • Docker

Choosing

How to choose CI/CD engineers

What to look for

  • Pipelines defined in code in the repository.
  • Deployments that can be rolled back.
  • Secrets kept out of logs and repository files.
  • Measurably faster pipelines in previous work.

Questions to ask

  1. 1What would you automate first in our release process?
  2. 2How do you make a slow pipeline faster?
  3. 3How do you handle secrets in CI?
  4. 4How would a failed deployment be rolled back?

Planning

Before you post the job

Tests first

Automated deployment is only safe with tests that catch problems. Check your test coverage before automating releases.

What drives cost

The number of services and environments, test suite speed, and deployment targets.

Hiring on Open Lance

  • Posting a job and reviewing proposals are free.
  • Each milestone is funded into escrow before work starts and paid when you approve it.
  • Hire fixed-price, hourly, as a monthly Dedicated Hire, or buy a packaged Drop-In.
  • Client fees are shown before you pay and added on top of the work.

How escrow and approval work · Pricing

FAQ

Questions about hiring CI/CD engineers

What is the difference between CI and CD?

CI builds and tests every change. CD delivers or deploys tested changes automatically.

GitHub Actions or Jenkins?

GitHub Actions is simpler for repositories on GitHub. Jenkins suits complex self-hosted setups.

Can they add CI to an old project?

Yes. Start with builds and tests, then automate deployments.

Related

Related skills

Before you hireWriting the job postReading the proposalsSetting milestones

Post a job for CI/CD engineers

Describe the work and compare proposals. You only fund the first milestone once you have chosen someone.

Post a job