1

Buildkite Jobs in Texas (NOW HIRING)

DevOps Engineer

Austin, TX

$52.25 - $71.50/hr

Hands-on experience with at least one major CI system (GitHub Actions, GitLab CI, Jenkins, Buildkite, CircleCI, Bitbucket Pipelines, etc.) and an understanding of the build and cache layers ...

DevOps Engineer

Austin, TX · On-site

$52.25 - $71.50/hr

Hands-on experience with at least one major CI system (GitHub Actions, GitLab CI, Jenkins, Buildkite, CircleCI, Bitbucket Pipelines, etc.) and an understanding of the build and cache layers ...

Buildkite information

What is the difference between Buildkite vs Jenkins?

AspectBuildkiteJenkins
Required CredentialsCloud account, API accessServer setup, Java knowledge
Work EnvironmentCloud-based, SaaS platformSelf-hosted or cloud, open-source
Industry UsageDevOps, CI/CD pipelinesDevOps, CI/CD, automation
Common Search/ComparisonYesYes

Buildkite and Jenkins are both popular CI/CD tools used to automate software testing and deployment. Buildkite offers a cloud-based, user-friendly platform with minimal setup, ideal for teams seeking quick deployment. Jenkins, on the other hand, is an open-source, self-hosted solution with extensive plugin support, suitable for organizations needing customizable pipelines. While Buildkite emphasizes ease of use and cloud integration, Jenkins provides more control and flexibility for complex workflows.

What are the key skills and qualifications needed to thrive as a Buildkite Engineer, and why are they important?

To thrive as a Buildkite Engineer, you need strong experience in CI/CD pipelines, scripting languages (like Bash, Python, or Ruby), and a background in software development or DevOps. Familiarity with Buildkite's platform, cloud infrastructure (such as AWS or GCP), and tools like Docker, Git, and Kubernetes is typically required. Excellent problem-solving, communication, and collaboration skills help you work effectively with development and operations teams. These abilities ensure efficient automation, smooth deployments, and robust software delivery processes.

What is Buildkite and what does a Buildkite Engineer do?

Buildkite is a continuous integration and continuous deployment (CI/CD) platform that helps software teams automate the building, testing, and deployment of their code. A Buildkite Engineer is responsible for configuring and optimizing Buildkite pipelines, integrating Buildkite with source control systems, and ensuring efficient, reliable automation for software delivery. They often collaborate with developers and DevOps teams to troubleshoot build issues, improve workflow efficiency, and maintain secure, scalable CI/CD processes.

What are some typical challenges faced by engineers working with Buildkite pipelines, and how can they be addressed?

Engineers working with Buildkite pipelines often encounter challenges related to pipeline configuration complexity, managing secrets securely, and optimizing build times. To address these, it's important to modularize pipeline steps for maintainability, use environment variables or secret management plugins for sensitive data, and leverage Buildkite's parallelism and agent scalability features to speed up builds. Collaborating closely with development and DevOps teams ensures that best practices are shared and pipelines remain efficient and secure.
What are popular job titles related to Buildkite jobs in Texas? For Buildkite jobs in Texas, the most frequently searched job titles are:
Infographic showing various Buildkite job openings in Texas as of July 2026, with employment types broken down into 98% Full Time, and 2% Contract. Highlights an 57% Physical, 1% Hybrid, and 42% Remote job distribution.
DevOps Engineer

$52.25 - $71.50/hr

Other

Posted 12 days ago


Job description

JOB SUMMARY

As a Senior DevOps Engineer, your mission is to make our software engineers faster. Every minute a developer waits on a build, fights with a flaky pipeline, or hand-rolls a deployment is a minute not spent shipping robots. You will own the CI/CD systems, build infrastructure, and developer-facing platforms that determine how quickly the rest of the company can move from idea to running code. The work spans on-prem and cloud, and your impact is measured in build times, deployment frequency, and the number of problems developers no longer have to think about. 

ESSENTIAL DUTIES AND RESPONSIBILITIES or KEY ACCOUNTABILITIES

  • Improve developer experience end-to-end - faster builds, cleaner release flows, better self-service - and drive down toil with code rather than runbooks.
  • Own the CI/CD systems used by every software team in the company, from build triggers through artifact distribution.
  • Responsible for driving the company's strategy for the release, packaging, and distribution of robot software.
  • Build and maintain the tooling, templates, and self-service workflows that let software teams ship without needing to understand the infrastructure underneath.
  • Partner with adjacent teams (security, embedded, ML) as their needs touch shared infrastructure.
  • Participate in on-call for shared infrastructure and help shape the team's reliability practices as we scale.
SKILLS AND REQUIREMENTS
  • Strong Linux fundamentals and confidence working at the systems level - networking, storage, processes.
  • Production experience with Kubernetes and infrastructure-as-code (Terraform, Helm, or similar).
  • Hands-on experience with at least one major CI system (GitHub Actions, GitLab CI, Jenkins, Buildkite, CircleCI, Bitbucket Pipelines, etc.) and an understanding of the build and cache layers underneath.
  • Experience with at least one major cloud provider (AWS, GCP, or Azure).
  • Fluent in Python and Bash; comfortable writing the small tools and glue code that infrastructure work demands.
  • A GitOps mindset - version-controlled, reviewable, reproducible infrastructure changes.
  • Strong written communication and a bias toward documenting decisions so they outlast the conversation that produced them.

Preferred (Nice to Have):

  • Experience running infrastructure on a mix of on-prem and cloud, and an understanding of when each is the right tool.
  • Familiarity with build systems used in C++ or robotics codebases (Bazel, CMake).
  • Background in hardware-heavy or robotics environments - release engineering for embedded targets, ARM cross-compilation, or fleet rollout patterns.
  • Experience with the open-source observability stack (Prometheus, Grafana, OpenTelemetry, VictoriaMetrics).
  • Experience operating self-hosted infrastructure services (container registries, artifact stores, distributed object storage).

EDUCATION and/or EXPERIENCE

  • Bachelor's degree in Computer Science, Computer Engineering, or a related technical field, or equivalent practical experience.
  • 5+ years operating production infrastructure for a software engineering organization, with meaningful ownership of CI/CD or platform work.
  • A proven track record of accelerating software development teams by building reliable infrastructure and effective tooling.

PHYSICAL REQUIREMENTS

  • Prolonged periods of sitting at a desk and working on a computer
  • Must be able to lift 25-45 pounds at times
  • Vision to read printed materials and a computer screen
  • Hearing and speech to communicate
  • International travel likely; passport highly desired
  • Travel up to 50% may be required