Jeremias DiabDevOps · Cloud

Open to new roles

Jeremias Diab · Rosario, Argentina

I keep production running and every release on schedule.

DevOps & Cloud Engineer. Two and a half years at Accenture running CI/CD, AWS and Azure infrastructure and production support. Now handling infrastructure and development at Pegasus Studio.

Core stack: AWS · Azure · Azure DevOps · Terraform · Kubernetes · Docker

AWSAzureAzure DevOpsTerraformKubernetesDockerPowerShellBashDatadogCloudWatchFirebaseNode.jsReactNext.jsPython

How I work

If I do something twice, I script it. If something breaks once, I want to know why before it breaks again. I aim for stable, predictable environments, and I explain what happened in words the whole team understands.

About me

Infrastructure is a product too. Someone has to own it.

I am a DevOps and Cloud engineer from Rosario, Argentina. For two and a half years I was part of the environment team at Accenture, keeping production and non-production environments running for global applications: Azure DevOps pipelines across UAT, Performance and Production, AWS and Azure infrastructure, Terraform and Kubernetes, and the scripts that take manual steps out of the day.

A big part of that job was troubleshooting: following an incident across infrastructure, deployments and backend code, and coordinating with development, QA and management until it was solved. Since 2026 I handle infrastructure and development at Pegasus Studio, where I also write the JavaScript, Node.js and React side of the projects.

Systems Engineering studies at UCEL, Rosario.

2+
Years in production environments
2
Clouds operated
4+
Stages from UAT to production
2
Working languages

The tools I work with

  • Cloud

    • AWS EC2
    • S3
    • IAM
    • Lambda
    • CloudFront
    • Route 53
    • RDS
    • Microsoft Azure
  • CI/CD & infrastructure

    • Azure DevOps Pipelines
    • Git
    • Terraform
    • Kubernetes
    • Docker
  • Automation

    • PowerShell
    • Bash
    • Control-M
    • Serverless jobs
  • Operations

    • Production support
    • Incident management
    • Datadog
    • CloudWatch
    • Certificate renewals
  • Mobile distribution

    • Firebase
    • App Center
  • Development

    • JavaScript
    • Node.js
    • React
    • Next.js
    • Python (scripting)
    • SQL

Experience

From an enterprise environment team to a studio that ships every week.

  1. Feb 2026 · Present

    Rosario, Argentina

    Pegasus Studio

    Infrastructure & Development

    Software studio that builds websites, web apps and automation for small and mid-sized businesses.

    • Run the infrastructure behind the studio's projects: containers, deploys, DNS and the pipelines that ship them.
    • Build features on the web side of the projects with JavaScript, Node.js, React and Next.js.
    • Docker
    • CI/CD
    • Node.js
    • React
    • Next.js
  2. Sep 2023 · Feb 2026

    Rosario, Argentina · Hybrid

    Accenture

    DevOps Engineer (Tech Architecture Associate)

    Environment team supporting production and non-production environments for global applications on AWS and Azure.

    • Designed, built and maintained Azure DevOps CI/CD pipelines across UAT, Performance, Production and the stages in between.
    • Managed AWS and Azure infrastructure (EC2, S3, IAM, Lambda, CloudFront, Route 53), including serverless automations for operational tasks.
    • Provisioned and maintained infrastructure with Terraform and Kubernetes, and took part in platform modernization work.
    • Automated pipeline runs and day-to-day operations with PowerShell and Bash, and built internal tools to cut manual work.
    • Handled production support and incidents across infrastructure, deployments and backend applications, coordinating with development, QA, performance and management teams.
    • Contributed to the migration of mobile app distribution from App Center to Firebase.
    • Azure DevOps
    • AWS
    • Azure
    • Terraform
    • Kubernetes
    • PowerShell

Education

Systems Engineering
Universidad del Centro Educativo Latinoamericano (UCEL)
2019University studies
Secondary education
EETSOPI Nº 8013 San José
2011 · 2016High school

Languages

Spanish (native), English (B2)

What I do

Four things that keep software running.

  1. 01

    Pipelines that reach production

    CI/CD across every stage, from UAT and performance to production, built so a release is a routine and not an event.

    • Azure DevOps
    • Git
    • Docker
    • Kubernetes
  2. 02

    Cloud infrastructure as code

    AWS and Azure resources described in Terraform and run on Kubernetes, with access, DNS and delivery configured on purpose.

    • AWS
    • Azure
    • Terraform
    • Kubernetes
  3. 03

    Automation of the repetitive

    Scripts, scheduled jobs and small internal tools that take the manual steps out of running environments.

    • PowerShell
    • Bash
    • Lambda
    • Control-M
  4. 04

    Calm production support

    Monitoring, incident triage and coordination across development, QA and management until the environment is stable again.

    • Datadog
    • CloudWatch
    • Ticketing
    • Incident response

How this site ships

This page is the proof of work.

Every change to this site goes through a pipeline: code checks, a container image, and a Lighthouse and security headers measurement of that same build. The figures below are read from the last build, not typed by hand. When one is missing, it says so.

  1. 01

    Commit

    Status:

    The change that produced this build.

    Commit
  2. 02

    Checks

    Status:

    If any check fails, nothing after it runs.

    Runs
    typecheck · lint · no-comments · unit tests
  3. 03

    Container image

    Status:

    A multi-stage Docker build that runs without root.

    Base
    node:24-alpine
    Output
    Next.js standalone · non-root user
  4. 04

    Measurement

    Status:

    The running container, measured as it is.

    Lighthouse · 0–100
    RoutePerformanceAccessibilityBest practicesSEO
    /
    /es

    Security headers

  5. 05

    Deploy

    Status: ok

    Upload to the server.

  6. 06

    CDN

    Status: ok

    Cloudflare in front of the site.

Now

Pegasus Studio, where I run infrastructure and write code.

Since February 2026 I work at Pegasus Studio, a software studio that builds websites, web apps and automation for small and mid-sized businesses.

I take care of the infrastructure behind the projects, from containers and deploys to DNS and the pipelines that publish them, and I build on the web side with JavaScript, Node.js, React and Next.js.

Visit pegasustudio.com(opens in a new tab)

What I do there

  1. 01Containers, deploys and the servers projects run on
  2. 02CI pipelines that check, build and publish each project
  3. 03DNS, certificates and the edge in front of every site
  4. 04Features in JavaScript, Node.js, React and Next.js

Questions

What recruiters usually ask first.

01What kind of role are you looking for?

DevOps, Cloud or platform roles where I own CI/CD, infrastructure and the operation of environments, at a semi-senior level.

02Remote, hybrid or on-site?

Any of the three. I am based in Rosario, Argentina, and I am used to working with teams in other regions and time zones.

03What is your level of English?

B2. At Accenture I worked day to day with global teams, investigating incidents and coordinating fixes in English.

04How much development do you do?

Infrastructure comes first, but I also write code: JavaScript, Node.js, React and Next.js on the projects at Pegasus Studio, and Python and shell scripts for automation.

Contact

Let's talk about your infrastructure.

Open to DevOps and Cloud roles. Remote, hybrid or on-site in Rosario. Spanish or English.

jeremiasdiab99@gmail.com