Hire the Best Cloud Engineers

Clients rate our Cloud Engineers
Rating is 4.8 out of 5.
4.8/5
Based on 759 client reviews
Shunmuga Sundara Perumal T.

Chennai, India

$40/hr
4.9
11 jobs

I’m an AWS Certified Solutions Architect – Professional with multiple AWS specialty certifications and hands-on experience designing scalable, secure cloud architectures. I help businesses migrate applications to AWS, improve infrastructure reliability, and implement DevOps best practices. My AWS Certifications: • AWS Certified Solutions Architect – Professional • AWS Certified Security – Specialty • AWS Certified Advanced Networking – Specialty • AWS Certified Solutions Architect – Associate • AWS Certified Cloud Practitioner I can help with: • Cloud migration to AWS • High-availability architecture design • DevOps automation and CI/CD pipelines • Infrastructure security and networking • Application deployment and monitoring I also teach AWS concepts on my YouTube channel(Learn Tech), helping engineers understand real-world AWS architecture and best practices.

  • Cloud Architecture
  • Cloud Development
  • AWS CloudFormation
  • AWS Development
  • Solution Architecture
  • AWS CloudTrail
  • Cloud Migration
  • Security Infrastructure
  • CI/CD
  • AWS Lambda
  • AWS Glue
  • AWS CloudFront
  • AWS Application
  • AWS Amplify
  • AWS Server Migration
  • Amazon EC2
  • Amazon S3
  • AWS CodeDeploy
Dawid G.

Dover, Delaware

$99/hr
5.0
52 jobs

If your AWS bill keeps climbing, production breaks under load, or a compliance deadline is getting close - the problem is rarely just AWS. It’s the architecture. I step into fragile systems and fix both: cloud infrastructure, and the application design running on it. Because even perfect AWS setup cannot save software that wasn’t designed to scale, isolate failures, or handle real production traffic. Most teams I work with are stuck in one of these situations: - AWS costs rising every month with no clear reason - Systems that pass tests but fail under real traffic - Compliance pressure from regulators or auditors - Constant firefighting instead of controlled releases Hiring more engineers or adding more monitoring increases complexity. I simplify the architecture - both infrastructure and code-level design - so the problems stop repeating. Recent outcomes: - Avoided a $5M federal penalty by delivering a critical federal platform before deadline, focusing only on what was required for compliant launch - Cut hosting costs from $96K to $14K per year by eliminating architectural waste across infrastructure and services - Designed and delivered a FedNow-ready, Federal Reserve-compliant real-time payments system scaling to 60,000 transactions per second using horizontally scaled services built specifically for cloud behavior What changes after I’m done: - Infrastructure and software designed to scale together - Predictable AWS costs - Systems that stay stable under load - Clear documentation and runbooks - A team that can operate it independently I build boring, predictable systems on purpose. Boring systems survive audits, scale events, and 3am incidents. If you’re dealing with cost pressure, reliability issues, or compliance risk, send me your biggest concern. I’ll tell you exactly what I would fix first and whether it’s worth doing. If it’s not a fit, I’ll say so.

  • Amazon DynamoDB
  • Node.js
  • API Development
  • AWS Lambda
  • API
  • Startup Company
  • Amazon ECS
  • AWS AppSync
  • AWS IoT Core
  • Socket Programming
  • AWS CloudFormation
  • AWS CodeDeploy
  • CI/CD
  • AWS Fargate
  • AWS CloudFront
Kisan T.

Kathmandu, Nepal

$65/hr
5.0
2 jobs

Hi, I’m Kisan 👋 I help startups and growing teams design scalable solutions on AWS, reduce cloud costs, and make sense of complex systems without overengineering. If you’re dealing with: - Rising AWS bills - Confusing or fragile cloud architecture - Performance or scalability concerns - Or need clear, developer-focused technical content You’re in the right place. What I do best: ✅ AWS Architecture & Optimization Design and improve cloud architectures that are secure, scalable, and cost-efficient. ✅ AWS FinOps & Cost Optimizatioin Identify waste, optimize services, and help teams build cost-aware cloud systems. ✅ Cloud & DevOps Technical Writing High-quality, SEO-optimized technical content written by someone who actually builds systems. Who am I? - Cloud Solutions Architect (AWS) - Docker Captain - AWS Community Builder - Author of The Cloud Handbook Newsletter - Founder of Towards AWS Why work with me? - AWS Cloud Engineer & Solution Architect with real production experience - Content read by millions of developers worldwide - Strong at both building systems and explaining them clearly How to get started? Send me a short message with: - What you’re building - Your current challenges And I’ll tell you honestly if I can help and how.

  • JavaScript
  • Node.js
  • Amazon DynamoDB
  • API Development
  • AWS Lambda
  • Web Development
  • AWS Amplify
  • Technical Writing
  • Cloud Development
  • Cloud Engineering
  • Serverless Computing
  • Cloud Architecture
  • AWS Development
  • AWS AppSync
Jonathan G.

Colorado Springs, Colorado

$200/hr
4.6
79 jobs

I help clients turn AI initiatives into operational systems that people can actually use and trust. I embed with client teams from discovery through rollout—identifying the right opportunity, designing the architecture, writing the code, integrating existing systems, and building the evaluations and human controls required for adoption. Clients bring me in when an important AI initiative needs more than a strategy deck or prototype. Because I handle both architecture and implementation, I can move from executive conversation to production code without the handoffs and delays of a conventional consulting team. CURRENT WORK • Clinical speech AI and multilingual interpretation For a multi-facility medical clinic in Dallas, I am building the data and model pipeline behind a self-hosted multilingual interpretation platform. The current work centers on collecting dialect-rich Arabic speech from clinic workflows and putting it through rigorous human transcription and review. The system supports segmentation, separate ASR and translation review, second-reader adjudication, consent controls, exact model and audio lineage, and reproducible dataset exports. Generic speech and translation APIs often struggle with regional dialects, medication names, dosages, negations, overlapping speakers, and the messy structure of real medical conversations. This pipeline gives the client a controlled way to evaluate and improve specialized models without allowing unverified AI output to become training truth. The same infrastructure can support Spanish, Vietnamese, Farsi, Urdu, and other high-need languages. The deployment roadmap includes model right-sizing, distillation, and quantization to reduce latency and operating cost across clinic locations. • AI property intelligence and geospatial reasoning Determining what can legally be built on a property is normally a fragmented expert-research process. It requires finding the correct municipal regulations, interpreting ambiguous zoning language, identifying the right parcel and district, understanding road frontage and neighboring conditions, and applying those rules to real geometry. For Plan AI, I built and productionized a property-intelligence engine that performs this work across municipal code, parcel geometry, road networks, building footprints, neighboring lots, FEMA flood data, and permit data. The system converts those sources into setbacks, buildable envelopes, risk signals, maps, and the evidence supporting each conclusion. Because an authoritative-sounding AI answer is not enough, I also built the anti-hallucination and geospatial evaluation layers. They reject invented ordinance language, unsupported calculations, unjustified assumptions, incorrect parcel or building matches, invalid envelopes, and contradictions between the model’s explanation and its result. The result is one evidence-backed workflow for understanding what constrains a property and what can potentially be built—while keeping uncertain cases visible for expert review. SELECTED EXPERIENCE • Led the development of an AI underwriting platform for a publicly traded lender with approximately $40M+ in annual revenue. It automated most application decisions while routing the hardest 10–15% to expert underwriters. • Designed and shipped a production payroll platform for Finally, a $100M Series B company, in approximately six weeks. • Helped build and stabilize Refine.ink, an AI peer-review platform used by faculty at leading U.S. universities. • Built SMART on FHIR and HL7 ADT healthcare integrations, voice-driven legal-intake systems, and computer-vision pipelines for identifying industrial weld defects only a few pixels wide. HOW I WORK I begin with the workflow, the people using it, the cost of failure, and the evidence the system must produce—not with a predetermined model or vendor. I can own the complete path from discovery through production, or embed with an existing team to resolve the critical architecture, integration, evaluation, and adoption challenges. As one Upwork client put it: “Got a week’s worth of work done in less than an hour due to Jonathan’s expertise. Would work with him again, no question.”

  • Python
  • Artificial Intelligence
  • Machine Learning
  • Large Language Model
  • AI Development
  • AI Agent Development
  • Retrieval Augmented Generation
  • Next.js
  • Data Science
  • Microsoft Azure
  • Cloud Architecture
  • Data Engineering
  • Azure OpenAI Service
Harutyun G.

Yerevan, Armenia

$75/hr
5.0
25 jobs

I help engineering teams and technical founders make the right system decisions before they become expensive — scoping what to build, de-risking architecture before irreversible choices are made, and owning delivery through to scale. My background spans cloud architecture, solution architecture, and database systems across AWS and Azure. The combination matters: most production failures I have seen trace back not to bad code, but to structural decisions made early in the schema, the system boundaries, or the deployment model — that compounded quietly until they could not be undone. I am based in Armenia and work async-first with clients across the US, Europe, and Australia. Architecture work — system design, technical reviews, decision documentation, governance frameworks — does not require timezone overlap. My clients do not experience geographic friction. 🔹 𝐓𝐡𝐫𝐞𝐞 𝐫𝐞𝐜𝐞𝐧𝐭 𝐩𝐫𝐨𝐣𝐞𝐜𝐭𝐬 𝐭𝐡𝐚𝐭 𝐜𝐚𝐩𝐭𝐮𝐫𝐞 𝐡𝐨𝐰 𝐈 𝐰𝐨𝐫𝐤: 𝐆𝐃𝐂 𝐌𝐞𝐝𝐢𝐚 (𝐈𝐫𝐞𝐥𝐚𝐧𝐝) — built an LLM-assisted database audit engine running across 3 MySQL clusters and 15 production nodes. 13 independent checkers feed findings to the LLM, which grades each as Critical / Major / Minor / Trivial and writes a short, grounded explanation. Runs hands-off 365 times a year. 𝐇𝐑𝐒 𝐆𝐫𝐨𝐮𝐩 (𝐂𝐨𝐥𝐨𝐠𝐧𝐞, 𝐆𝐞𝐫𝐦𝐚𝐧𝐲) — designed and built financial data pipelines on AWS that bridge MS Navision (ERP) and SAP through a single canonical model. Safe to replay, with scheduled reconciliation. 𝐆𝐥𝐚𝐬𝐬𝐰𝐚𝐥𝐥 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬 (𝐔𝐊) — Cloud Engineer on the Content Disarm and Reconstruction platform now trusted by NATO and U.S. and U.K. national security agencies. Helped adapt the platform for AWS EKS, Azure AKS, and K3s, and built the file ingress orchestration plugin handling terabytes of potentially infected files. 🧭 𝐇𝐨𝐰 𝐈 𝐰𝐨𝐫𝐤 I don't approach projects as feature delivery. I approach them as temporary or ongoing technical ownership — short engagements that clarify direction, longer ones that carry the system through to scale. The shape is the same in both: • Reduce MVP scope while keeping the core value loop intact • Define cloud architecture and system constraints before implementation begins • Make decisions explicit instead of accumulating quiet assumptions • Separate short-term delivery from long-term structural risk • Hand off to in-house engineers cleanly when the moment is right Some engagements take two weeks. Some turn into multi-year work. The goal in both is the same — systems that don't need heroics to keep running. 🎯 𝐖𝐡𝐞𝐫𝐞 𝐩𝐫𝐨𝐣𝐞𝐜𝐭𝐬 𝐮𝐬𝐮𝐚𝐥𝐥𝐲 𝐠𝐞𝐭 𝐬𝐭𝐮𝐜𝐤 In early- and growth-stage systems, the biggest problems are rarely about tooling or raw engineering skill. They are decision gaps: • Feature lists that grow faster than clarity • AI is treated as a black box instead of a constrained system • Developers hired before the success criteria are defined • Architectural decisions deferred until they're expensive to reverse • "We'll fix it later" choices that quietly become permanent That's the layer I focus on stabilizing first — so execution stays fast without becoming brittle. ⛁ 𝐃𝐚𝐭𝐚𝐛𝐚𝐬𝐞 𝐚𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 & 𝐝𝐢𝐚𝐠𝐧𝐨𝐬𝐭𝐢𝐜𝐬 Production databases are where architectural decisions surface most visibly — slow queries, bloated indexes, configuration drift, schema choices that worked at 10K rows and break at 10M. I have extensive hands-on experience with PostgreSQL, MySQL, and MariaDB in high-load production environments. For teams that need a fast, structured assessment: I offer a fixed-price SQL database audit via my Project Catalog — a prioritized diagnostic report delivered in 1–2 days, ranked by business impact. 🧱 𝐒𝐭𝐚𝐜𝐤 • Databases — PostgreSQL, MySQL, MariaDB, OpenSearch, Elasticsearch, DynamoDB • Cloud — AWS, Azure, Kubernetes, Docker, serverless • Security — IAM, encryption, access boundaries, secure data flows • DevOps — CI/CD, GitHub actions, CloudFormation, observability • AI-adjacent — guardrails, confidence gating, deterministic vs. generative boundaries Technology serves decisions, not the other way around. 📅 𝐄𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭 𝐟𝐨𝐫𝐦𝐚𝐭𝐬 • Long-term architecture and delivery ownership • Fractional CTO or technical advisor • Short-term advisory (1–4 weeks) • Fixed-price SQL database audit (Project Catalog — from $750) Most successful collaborations start small and grow naturally once alignment is in place. 📨 𝐋𝐞𝐭'𝐬 𝐭𝐚𝐥𝐤 If you are unsure what to build, what to cut, or how to de-risk a critical phase — or if your database is showing signs of trouble — a short conversation usually makes sense. From there, we decide together on the right shape of engagement.

  • Software Architecture & Design
  • Cloud Architecture
  • Amazon Web Services
  • Microsoft Azure
  • Database Optimization
  • PostgreSQL
  • MySQL
  • Serverless Computing
  • Automation
  • CI/CD
Joshua L.

Houston, Texas

$100/hr
5.0
20 jobs

I'm a Cloud and AI Architect with 15+ years of enterprise experience, including 4 years at Microsoft on the Azure team where I consulted F500 companies like AT&T, Walmart, and Mastercard on AI, cloud adoption, security, and infrastructure at scale. I founded TechVora, a small in-office engineering team based in Houston, TX. We work mainly with clients where security, compliance, and uptime are non-negotiable. All engineers work in-house, we never sub out work, which matters when sensitive data is involved. WHAT MAKES US DIFFERENT I act as the architect on every engagement and don't bill for my time. You get senior-level architecture, design, and oversight built into the cost of your developer. AI & PRODUCTION SYSTEMS Over the last two years we've shifted heavily into production AI - we've shipped four enterprise-grade multi-tenant AI applications across legal, accounting, oil & gas, and media, all involving custom LLM pipelines, RAG, and agents handling real sensitive data at scale. CORE COMPETENCIES - Cloud Architecture & Migration (Azure, AWS, GCP) - AI/LLM Integration — RAG, Agents, Multi-tenant Production Apps - DevSecOps, CI/CD, Infrastructure as Code (Terraform, Bicep) - Data Pipelines, Warehousing & ETL - HIPAA-Compliant Architecture - Monitoring, Observability & Incident Response - M365, Azure Security & Compliance Happy to jump on a quick call - I offer a free strategy session for any new engagement.

  • Cloud Computing
  • AI Development
  • Python
  • DevOps Engineering
  • Infrastructure as Code
  • Microsoft Azure
  • Amazon Web Services
  • Google Cloud Platform
  • Azure OpenAI Service
  • Kubernetes
  • Azure App Service
  • .NET Core
  • Azure Cosmos DB
  • C#
  • DevOps
  • Artificial Intelligence
  • Office 365
  • Azure DevOps
  • Node.js
  • React

How it works

Post a job for freePost a job

Tell us what you need. Create your own job post or generate one with AI then filter talent matches.

Hire top talent fast

Consult, interview, and hire quickly, so you can meet the freelancers you're excited about.

Collaborate easily

Use Upwork to chat or video call, share files, and track project progress right from the app.

Payment simplified

Manage payments in one place with flexible billing options. Only pay for approved work, hourly or by milestone.

Don't just take our word for it

Moving to the Cloud: What to Know & Who to Hire

What is “The Cloud”?

The cloud is synonymous with modern computing. A majority of businesses—from startups to massive corporations—use it in some capacity to augment or streamline their existing operations, data storage, hosting, and app deployment. So what is the cloud and how is it changing traditional server setups across the globe?

The U.S. National Institute of Standards and Technology (NIST) defines the cloud as “a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.”

In short, it’s allowing companies to reengineer their back-end architectures (servers, databases, application software, and more) and put them in virtual environments where they can be accessed remotely, without requiring physical server hardware of their own. Cloud services (also known as web services) are a blanket way to describe these computing capabilities.

The benefits of using cloud and web service providers

Adopting an infrastructure-as-a-service (IaaS) platform like Amazon Web Services (AWS) or a platform-as-a-service model (PaaS) from a provider like Heroku can take some of the responsibilities of hosting, maintaining, updating, and scaling up server operations off the hands of developers and IT managers. An IaaS will provide you with all the components you need to build a backend architecture, offering flexibility and plenty of scalability. Note that deploying a site or app’s back end to the cloud with an IaaS requires more configuration, while deploying with a PaaS doesn’t require as much configuration—just enable the services you need within the platform’s environment, push the code to it, and it handles the rest.

While their clients benefit from a virtual environment, cloud service providers themselves have massive data centers that are as big as multiple football fields. These servers are usually set up in a way that some can fail (or, even a majority of them), but not in a way that all of the services will be taken down. It’s important to know that it’s still possible for cloud computing to have a single point of failure, or to have certain services fail.

This has brought about the need for more engineers who know how to integrate, work with, and fix cloud-based operations. You may not need a full-time network engineer if you’re operating in the cloud, but you’ll definitely need a skilled development operations professional to ensure things run smoothly.

Here’s a look at a few of the top providers in the cloud services market:

  • Amazon Web Services (AWS): Popular with startups looking to get things going in the cloud for cheap, this platform is also powerful enough for large, enterprise operations.
  • Google Cloud Platform: This popular PaaS offers cloud computing, storage, big data and API services so you can build and launch sites or complex applications in the cloud. It offers things like SQL and NoSQL database services, analytics, virtual machines, all of which can be mixed and matched to suit your needs.
  • Microsoft Azure: An enterprise-level Paas and IaaS cloud provider, it offers mobile and web app deployment and scaling, database services, virtual machines, mobile back ends, machine learning, and more.
  • Heroku: A popular PaaS where applications can be completely built, deployed and run in the cloud.
  • Rackspace: This PaaS offers cloud computing through its infrastructure (either dedicated servers, public cloud, or private cloud, all of which can be mixed and matched for a hybrid environment), or their partnerships with Azure and AWS.
  • Cloud Foundry: This open-source PaaS written in Ruby and Go offers cloud computing services with an enterprise-grade option, Pivotal.
  • Xen Cloud Platform (XCP): This open source virtualization solution that provides cloud computing and back-end virtualization. XCP includes an enterprise-ready set of tools with the Xen Hypervisor, with the Xen API for cloud, storage and networking operations.
  • Oracle: This enterprise giant has made recent updates to its cloud capabilities, helping big businesses leverage the cloud, but also offering small- to medium-sized businesses cloud computing services.
  • Apache Cloudstack: a free, open-source cloud software for creating and deploying cloud services that has excellent support for virtualization and the AWS API.

Beyond data centers: making the move to the cloud

With the rise of the cloud, the server landscape is rapidly changing, with more server-side operations being pushed off-site. Small, medium, and enterprise-level companies can easily expand the size, storage, and processing power of their servers in a way that takes less time, and less money.

For startups in particular, these cloud-based platforms take server upkeep and support off their plates so they can focus on growing their businesses. They also offer flexibility and speed, with the ability to scale up quickly when needed. Scaling up can be hard to do in a physical data center: ordering new hardware, provisioning, and racking, and stacking can take anywhere from three to six weeks. In the cloud, you can provision capacity on the fly.

The key to moving to the cloud is striking the right balance for your organization—whether that’s a hybrid approach or all-in.

Adopting a hybrid cloud approach

A majority of businesses are finding that a hybrid approach works best, leaving some things on traditional, local servers and moving more resource-heavy applications to the cloud. This can be a permanent strategic solution, or a stop along the way to going 100% cloud-based. There are benefits to leaving certain portions of your back-end infrastructure on virtualized local servers or co-located data centers, while moving more resource-heavy applications to the cloud.

For example, migrating a back-end architecture to Amazon Web Services (AWS) allows for automatic scaling, the ability to fail over multiple availability zones, its accommodations for peaky traffic and intensive operations (e.g., some of our machine learning models), and the ability to free up a team to focus on application-specific work rather than solving problems Amazon can address.

Public cloud vs. private cloud

A common approach is to divvy up a server’s workload with a mix of private (onsite) and public (cloud services) clouds. Larger, enterprise companies often opt for a private cloud/onsite server architecture. One reason? Protecting sensitive data.

For some organizations in regulated industries, like finance, there are restrictions on what information they can store in the cloud. Because of this, they have to strike a balance between storing sensitive information on-site while still making it available in the cloud, so they can take advantage of the agility and scalability the cloud offers.

Critical apps are often better suited for a private cloud for security and reliability reasons. The main concerns with critical apps are performance (speed, reliability, and no downtime) and security of your information. A privately hosted cloud is a good bet for these, giving you more control along with the flexibility you want.

Less critical apps like web servers, backup services, and infrastructures are safer in the public cloud. There, you’ll get servers that allow you to free up space on-site, plus the benefit of temporary scalability if you need it, with increased capacity just a click away. Also, a public cloud configuration can even be treated like software code and placed in a repository where developers can edit, adjust, and run tests against your current configuration, which is helpful for ensuring a successful deployment, and for getting the most out of the cloud.

Should you move to the cloud? What to consider before deploying to the cloud

For small businesses, there are some clear advantages to using the cloud—whether it’s going entirely to the cloud, or using a hybrid approach that breaks up your server workload between an on-site infrastructure and the cloud.

The benefits? It’s an invisible, offsite server that you can scale up when and how you want. If you have an application that requires a lot of space, data, or resources, you can shift that over to the cloud while freeing up space in your current setup.

Small businesses can strike a strategic balance between traditional on-site servers and cloud servers, so it’s important to ask yourself a few questions about your setup before choosing the one that’s right for you. And if you're not sure you can always seek the advice from cloud consulting specialists.

  1. Take a look at your existing back-end infrastructure. What are your requirements, and what are your end-user’s requirements? What will diversifying to the cloud do to help with these? Consider compatibility of your server-side software. While some businesses don’t move all of their server-side architecture to the cloud, it’s helpful to ensure cloud compatibility in the components they keep on-site.
  2. Decide what should go where. Plan how you’ll virtualize your back end. If you’re a small business, basic server functions like an email server or an app server could probably stay on-site. Or, apps that don’t require as much data storage could stay local, too. Be sure to prioritize your needs. You may opt to divvy up the workload with a hybrid cloud environment, keeping mini servers on-site to handle smaller workloads, like file sharing servers. These can even be designed to sync up with cloud drives.
  3. What’s your budget? This will help narrow down which cloud service is right for you. The great thing about the cloud? Flexibility. If you start out small and find you need more, you can easily upgrade subscriptions or buy more data—no need to switch out hard drives.
  4. Who should you hire or have on your team to help? Do you have a server professional available to help with maintenance or fixes? Because you don’t have to worry about hardware with cloud servers, it can be a more seamless integration for IT professionals, but it’s not without its quirks. Make sure you have a dev ops engineer who has plenty of experience integrating with the cloud and handling issues with network reliability that can arise.
  5. How scalable does it need to be? How much growth you anticipate in terms of traffic and data for your application or site’s server play a very important role in how you decide to set up your server. You’ll want to be able to expand your server space without having to totally replace it, whether that means starting with a setup that allows you to switch out hard drives for hard drives with more memory, or virtualizing your setup across numerous smaller servers.
  6. Security. Security is always a big concern—if you have very sensitive information being stored on your server, you may opt to keep that on-site while moving less sensitive information to the cloud. Or, go for a private cloud/hybrid cloud environment that allows you to maintain a more secure environment, and lets your IT professionals keep tighter control on what data is stored/shared where.

The need for cloud engineers

From a talent standpoint, running your server operations in the cloud means you won’t need the same network and storage engineers on hand to take care of day-to-day server issues—but maintenance and support won’t be totally off the table.

Look for a cloud server architect with plenty of experience deploying operations to the cloud. Some key skills and expertise to look for in a dev ops engineer are:

  • Configuration management skills: Chef, Puppet, Ansible, etc.
  • Virtualization experience: VMware, Kernel-based Virtual Machine (KVM), Xen, etc.
  • Public cloud experience: Amazon Web Services, Google, Rackspace