Konrad Podgórski

Skills and technologies

DevOps, site reliability and software architecture, grouped by area.

The same skills by role: DevOps engineer, site reliability engineer and software architect.

Architecture

Systems designed to be run and changed by the next team, from legacy rewrites to platforms on AWS.

  • Cloud architecture on AWS
  • Software architecture
  • System design
  • Legacy rewrites
  • Route-by-route migrations
  • Domain-driven design
  • Documentation for handover

AWS platform

Multi-account setups, networks and edge, and the compute and data services that run on them.

Compute and containers

  • ECS (Amazon Elastic Container Service)
  • Lambda (AWS Lambda: functions without servers to manage)
  • API Gateway (Amazon API Gateway)
  • ECR (Amazon Elastic Container Registry)
  • Elastic Beanstalk (AWS service that runs web applications on managed servers)

Networking and edge

  • VPC (Amazon Virtual Private Cloud)
  • VPC (Amazon Virtual Private Cloud) endpoints
  • Site-to-site VPN
  • CloudFront (Amazon's content delivery network)
  • CloudFront Functions (Small functions that run at the CloudFront edge)
  • Route 53 (Amazon's DNS service)
  • ACM (AWS Certificate Manager)
  • WAF (AWS WAF, the web application firewall)

Messaging and events

  • SQS (Amazon Simple Queue Service)
  • SNS (Amazon Simple Notification Service)
  • EventBridge (AWS event bus and scheduler)
  • IoT Core (AWS IoT Core, for connected devices)
  • SES (Amazon Simple Email Service)

Data and storage

  • S3 (Amazon Simple Storage Service)
  • RDS (Amazon Relational Database Service)
  • DynamoDB (Amazon's key-value database)
  • ElastiCache (Managed Redis on AWS)
  • AWS Backup

Accounts and access

  • IAM (AWS Identity and Access Management)
  • IAM (AWS Identity and Access Management) Identity Center
  • Organizations (AWS Organizations: many accounts managed as one)
  • Secrets Manager
  • SSM (AWS Systems Manager) Parameter Store
  • KMS (AWS Key Management Service)
  • Cognito (Amazon Cognito: user sign-up and sign-in)

Infrastructure as code

Everything in code and changed through review, including what was clicked before.

  • Terraform
  • Reusable modules
  • Multi-account layouts
  • Importing existing infrastructure
  • Terraform refactoring
  • Terraform Cloud (HashiCorp's hosted Terraform runs)
  • Terraform GitHub provider
  • Serverless Framework (Deploys Lambda functions from one config file)

CI/CD and testing

Pipelines that test what ships, gate every plan, and release in one merge.

  • GitHub Actions
  • Reusable workflows
  • Gated Terraform plan and apply
  • Release automation
  • CodePipeline
  • CodeBuild
  • pytest (Python test framework)
  • Vitest (JavaScript test framework)
  • PHPUnit (PHP test framework)
  • Behat (Behaviour-driven tests for PHP)

Code quality and security

Linters and security scanners on every change, and no stored keys in CI, so problems show up in review rather than in production.

Linting

  • pre-commit (Runs checks before each commit)
  • ShellCheck (Linter for shell scripts)
  • actionlint (Linter for GitHub Actions workflows)
  • hadolint (Linter for Dockerfiles)
  • tflint (Linter for Terraform)
  • Ruff (Python linter and formatter)
  • yamllint (Linter for YAML files)
  • markdownlint (Linter for Markdown files)
  • MegaLinter (Runs many linters in one CI job)

Security scanning

  • gitleaks (Finds secrets committed to git)
  • Semgrep (Static analysis for risky code patterns)
  • Trivy (Vulnerability scanner for container images and infrastructure code)
  • Checkov (Policy scanner for infrastructure code)
  • pip-audit (Checks Python dependencies for known vulnerabilities)
  • Bandit (Security linter for Python)
  • npm audit (Checks JavaScript dependencies for known vulnerabilities)
  • Dependabot (Opens pull requests that keep dependencies up to date)

Secrets and access

  • OIDC (OpenID Connect) federation for CI
  • Ansible Vault (Encrypted secrets files from Ansible)

Reliability and observability

Monitors, SLOs and alerts kept in code, applications kept running in production, and every change planned with a way back.

  • CloudWatch (AWS monitoring, logs and alarms)
  • Structured logging
  • Log review
  • Monitoring as code
  • SLO (Service level objective)s
  • Log pipelines
  • Health checks
  • Alerting
  • Incident triage
  • Change management
  • Rollback plans
  • Datadog (Monitoring and logging service)

Containers and web servers

Local stacks that match production, the clusters they run on and the servers in front of them.

  • Docker
  • Docker Compose
  • Kubernetes
  • Helm (Package manager for Kubernetes)
  • Argo CD (Deploys to Kubernetes from git)
  • Nginx
  • Gunicorn (Python web server for applications)
  • Caddy (Web server with automatic HTTPS)
  • Traefik (Reverse proxy for containers)

AI engineering

Coding agents on infrastructure work, the MCP servers they use, and read-only cloud access for them.

Coding agents

  • Claude Code (Anthropic's coding agent)
  • OpenAI Codex (OpenAI's coding agent)
  • GitHub Copilot
  • AGENTS.md (Instructions file that coding agents read)
  • CLAUDE.md (Instructions file that Claude Code reads)
  • Agent skills
  • AI code review in CI (A model reviews every pull request in CI)

MCP and agent access

  • MCP (Model Context Protocol: how coding agents reach tools and data) servers
  • FastMCP (Python framework for MCP servers)
  • Read-only cloud access for agents

Models and vision

  • Claude API
  • Gemini API
  • YOLOv8 (Object detection model)
  • OpenCV (Computer vision library)
  • Tesseract OCR (Open-source text recognition from images)

Scripting for CI/CD and automation

Bash and Python in pipelines, automation and tooling; SQL, TypeScript and PHP where the application needs them.

  • Bash
  • Python
  • SQL
  • TypeScript
  • PHP

Backend

The frameworks and libraries behind the applications.

  • Flask (Python web framework)
  • SQLAlchemy (Python database toolkit)
  • Alembic (Database migrations for SQLAlchemy)
  • Celery (Python task queue)
  • FastAPI (Python framework for APIs)
  • Symfony
  • Doctrine (Database layer for PHP)

Data

The databases, caches and search engines behind the applications.

  • MySQL
  • Redis
  • PostgreSQL
  • Elasticsearch
  • MongoDB

Integrations

The outside systems a platform talks to.

  • REST APIs
  • OAuth
  • Webhooks
  • ERP integration (SAP) (Connecting a platform to an SAP ERP system)
  • E-commerce platforms
  • Shipping carrier APIs

Ways of working

How I work with the people who build the applications.

  • Supporting development teams
  • Leading small teams
  • Working directly with product owners
  • Gitflow releases

Blue marks what I work with now.