---
title: "CircleCI | Skills We Assign For | Azendo"
description: "CircleCI for build pipelines — parallelism, caching and cost control, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/circleci/"
---

[Skills](https://azendo.co/skills/) CI and delivery 

# CircleCI.

CircleCI is a hosted CI/CD platform with pipelines defined in YAML, reusable orbs for common tasks, configurable resource classes and first-class parallelism and caching.

## Where CircleCI fits on a long engagement.

Pipeline speed is a delivery constraint that compounds. A twenty-minute pipeline changes how often people merge, how large each change is, and how quickly a regression is attributed — all of which cost more than the twenty minutes themselves.

The two levers are caching and parallelism, and both are usually left at defaults. Dependencies reinstalled on every run, and a test suite executing serially when it could split across containers, are the normal state of a pipeline nobody has owned. Fixing them is a day's work that pays back weekly.

## What an assigned team does with CircleCI.

Resource classes are the cost lever people forget. Larger machines finish faster and cost more per minute, and the optimum is workload-specific rather than a default anyone can pick correctly in advance.

Treating pipeline efficiency as continuous rather than a setup task is part of an agreed [committed monthly capacity](https://azendo.co/pricing/) for platform work.

## What we use CircleCI for.

* Test suites split across containers Parallel execution with timing-based splitting, so total wall-clock drops rather than shifting.
* Dependencies cached properly Cache keys that actually hit, instead of a cold install on every run.
* Resource classes matched to workload Machine size chosen from measurement rather than left at the default.

## How CircleCI capacity is assigned.

Pipeline work is assigned under [devops as a service](https://azendo.co/services/cloud-and-devops/), alongside the development capacity whose feedback loop it is.

## Roles we assign CircleCI for

* [DevOps Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/devops-engineer/)

## Service lines it sits in

* [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in ci and delivery

* [GitHub Actions — skill we assign for](https://azendo.co/skills/github-actions/)
* [Jenkins — skill we assign for](https://azendo.co/skills/jenkins/)
* [GitLab CI — skill we assign for](https://azendo.co/skills/gitlab-ci/)
* [Fastlane — skill we assign for](https://azendo.co/skills/fastlane/)
* [Codemagic — skill we assign for](https://azendo.co/skills/codemagic/)
* [TestFlight — skill we assign for](https://azendo.co/skills/testflight/)
* [App Store Connect — skill we assign for](https://azendo.co/skills/app-store-connect/)
* [Play Console — skill we assign for](https://azendo.co/skills/play-console/)

## Tell us what your roadmap needs CircleCI for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)