Corporate · onsite · online training worldwide
contact@DevOpsSchool.com· +91 99057 40781·
> Automation & Scripting · DevOpsSchool Trainer

Python Trainer

Private corporate batches, live online cohorts and 1-on-1 mentoring in infrastructure automation, internal tooling and cloud SDK work in Python — taught by a practitioner who runs it in production.

20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank

DeliveryOnline · Onsite · Hybrid
FormatsCorporate · 1-on-1 · Cohort
AgendaCustomisable
Batch size8–30 engineers
Engineers we've trained work at
JPMorgan ChaseBank of AmericaWells FargoVerizonNokiaWorld BankGE HealthcareVMwareOracleQualcommMercedes-BenzAirbusDatadogSplunkDeloitteInfosysWiproCapgemini
# who teaches it

Your Python trainer

Rajesh Kumar

Principal DevOps Engineer & Architect

20 years in productionPrincipal / architect roles10,000+ engineers trainedM.Tech BITS Pilani25+ certifications

Rajesh teaches Python as an infrastructure language rather than as a first programming course — subprocess and signal handling, pathlib, argparse-based CLIs with real exit codes, requests with retry and backoff, and boto3 driven against live cloud accounts. Sessions concentrate on what operational code actually fails on: exception handling, encoding, timeouts, partial failure across a fleet, credential handling, and tests that can run in CI without provisioning cloud resources.

Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.

One practitioner, not a bench

You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.

The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.

18,000+certified learners
500+corporate batches delivered
50+countries served
100+certification programmes
# faculty

Who delivers Python engagements

Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.

How your Python trainer is chosen

Engagements are matched on the tool, not the calendar. For Python that means a trainer who has run it in production — infrastructure automation, internal tooling and cloud SDK work in Python — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.

Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.

Rajesh Kumar

Principal DevOps Engineer & Architect

India20 yrsLead trainer

Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.

Gaurav Aggarwal

IndiaInstructorCoach

Harsh Mehta

IndiaInstructorCoach

Kapil Gupta

IndiaInstructorCoach

Kunal Jain

IndiaInstructorCoach

Nikhil Gupta

IndiaInstructorCoach

Pranab Kumar

IndiaInstructorCoach

Rohit Ghatol

IndiaInstructorCoach

Amit Agarwal

IndiaInstructorCoach

Anil Kumar

IndiaInstructorCoach

Balachandran Anbalagan

IndiaInstructorCoach

Durga Prasad

IndiaInstructorCoach

# how to engage

Four ways to work with this trainer

Private corporate batch

Teams of 8–30

Custom agenda, your timezone, onsite or online, NDA-friendly.

Request a quote

1-on-1 mentoring

Individual engineers

A private instructor and a curriculum built around your goal.

₹99,999

Live & Interactive cohort

Individuals who want peers

Scheduled batch, max 8 to 10 hours of live instruction.

₹34,999

Self-paced video

Self-starters

Full LMS access — 20+ courses and 50+ tools included.

₹833/mo
# private batches

Private Python training for your team

A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.

Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.

Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.

Talk to us about a private Python batch

What you provide vs what we bring

  • You: the room or the call, and the engineers
  • Us: trainer, agenda, labs, assessment, certificates
  • Labs: we guide your team through provisioning their own free-tier cloud environment — the skill goes with them
# the technology

What is Python?

Python is a high-level, interpreted, dynamically typed language that has become the default glue of infrastructure work. It occupies a specific layer of the stack: above shell, where control flow, error handling and structured data start to matter, and below the compiled binaries that get shipped as services. When a task is too complicated for a Bash script and too small to justify writing a daemon, it is almost always written in Python.

The reason is the standard library plus the packaging ecosystem. subprocess and pathlib cover process and filesystem work, argparse turns a script into a real command-line tool, json and csv handle the formats operations run on, and re turns log lines into structured records. Beyond the standard library, requests speaks to every internal API, boto3 and the Azure and Google Cloud SDKs drive cloud control planes directly, and pip with virtual environments makes a tool reproducible on someone else's machine rather than only on the author's.

In a DevOps estate Python turns up in more places than any other language: CI pipeline steps, custom automation modules, Prometheus exporters, Airflow DAGs, Lambda and Cloud Function handlers, Kubernetes operators, chatops bots, data migrations and the internal CLI that every platform team eventually writes. Learning Python for that work is a different exercise from learning it as a first programming course — the parts that decide whether the code survives are processes, files, text, HTTP, retries, timeouts and exit codes.

Why this skill matters now

Automation work has outgrown shell. Estates now span several clouds, dozens of APIs and tens of thousands of resources, and the code that holds them together needs real error handling, structured data and tests — none of which Bash gives you cheaply.

Python is the language that filled that gap, and hiring reflects it. Platform engineering, SRE, cloud engineering, security automation and MLOps specifications almost all list Python, frequently as the only language requirement. It is also the extension language of the tooling itself: automation modules, pytest-based infrastructure tests, AWS CDK, Pulumi and most observability agents are written in Python or expose a Python interface.

What organisations are short of is not people who can write a loop. It is engineers who can ship a tool that other people depend on — packaged, logged, configurable, retried, idempotent and tested. That is the difference between a script that worked once on a laptop and something a team runs in a pipeline every hour.

Python training
# outcomes

What your team can do afterwards

Write Python that replaces shell scripts at the point where control flow, error handling and structured data start to matter
Build command-line tools with argparse — subcommands, configuration, logging and exit codes other engineers and pipelines can rely on
Drive processes safely with subprocess: argument lists over strings, timeouts, streamed output, and why shell=True is a security defect
Parse and reshape operational data — JSON, CSV, YAML and raw log text — using the standard library and regular expressions
Call HTTP APIs correctly, with authentication, pagination, timeouts, rate limiting and retry with exponential backoff
Automate cloud control planes with boto3 and the Azure and Google Cloud SDKs, including paginators, waiters and credential chains
Package and distribute a tool with virtual environments, pyproject.toml and pinned dependencies so it installs the same way twice
Test infrastructure code with pytest — fixtures, parametrisation and mocking — so changes can be verified before they touch production
# curriculum

12 modules. Live demos in a real lab, not slides.

01Python for infrastructure engineers — setup and execution modelLive & Interactive5 hrs · 2 assignments · 1 capstone

What Python is, where it belongs in an automation stack, and how it actually runs. Installation and version management, the interpreter and REPL, module search paths, and virtual environments — because the first real Python problem most teams hit is dependency isolation, not syntax.

Topics: What Python is and why it dominates infrastructure tooling · Choosing an interpreter version and managing several with pyenv · The interpreter, the REPL and script execution · Python syntax and semantics — indentation, truthiness, naming · Virtual environments and dependency isolation · sys.path, imports and how modules are found

  • Assignments: (1) Install and pin a Python version, then create an isolated environment for the course project; (2) Diagnose three deliberately broken import failures
  • Capstone: Produce a reproducible development environment definition your team could adopt unchanged
02Language core — variables, types, operators and control flowLive & Interactive5 hrs · 2 assignments · 1 capstone

The core of the language, taught against operational examples rather than exercises. Variables and data types, operators and expressions, conditional statements and the loop constructs, plus the mutability rules that cause most surprising behaviour in shared automation code.

Topics: Variables and data types · Operators and expressions · Conditional statements · Loops — for, while, else, break and continue · Mutability, identity and copying · Truthiness and the comparison traps

  • Assignments: (1) Rewrite a 60-line Bash script as readable Python; (2) Fix a script that mutates a shared default argument
  • Capstone: Build a host-inventory report that reads raw data and prints a formatted summary
03Functions, modules and packagesLive & Interactive5 hrs · 2 assignments · 1 capstone

How Python code is organised once it stops being a single file. Function definition, arguments and defaults, scope and closures, then modules, packages, __init__ and the layout that keeps a growing internal tool navigable.

Topics: Functions, arguments, defaults and keyword-only parameters · Return values, unpacking and multiple returns · Scope, closures and the LEGB rule · Modules and packages · Entry points and __main__ · Type hints and what they buy in shared code

  • Assignments: (1) Refactor a flat script into a package with a clear entry point; (2) Add type hints to an existing module and run a type checker over it
  • Capstone: Convert a single-file automation script into an installable package
04Object-oriented PythonLive & Interactive5 hrs · 2 assignments · 1 capstone

Classes as they are actually used in operational code — modelling a resource, a client, a configuration object — rather than as an academic exercise. Attributes, methods, inheritance, composition, dunder methods and dataclasses, with an honest look at when a function is the better answer.

Topics: Classes, instances and attributes · Methods, class methods and static methods · Inheritance versus composition · Dunder methods — repr, eq, context managers · dataclasses and named tuples · When not to use a class

  • Assignments: (1) Model a cloud resource as a class with a working __repr__ and equality; (2) Write a context manager that guarantees cleanup on failure
  • Capstone: Design a small client library wrapping an internal API, with tested error types
05Data structures and operational dataLive & Interactive5 hrs · 2 assignments · 1 capstone

The structures every automation script leans on, and the numerical and tabular libraries used for capacity, cost and reliability reporting. Lists, tuples, dictionaries and sets with their performance characteristics, then NumPy arrays and Pandas DataFrames for cleaning, preparing and visualising operational data.

Topics: Lists and tuples · Dictionaries and dictionary methods · Sets and set algebra for diffing state · Comprehensions and generators · NumPy arrays · Pandas DataFrames · Data cleaning, preparation and visualisation

  • Assignments: (1) Diff two inventories using set operations and report additions, removals and changes; (2) Load a month of billing data into a DataFrame and produce a per-service cost summary
  • Capstone: Build a reporting script that turns raw exported data into a chart and a written summary
06Files, directories and serializationLive & Interactive5 hrs · 2 assignments · 1 capstone

Everything an automation tool does to disk. Reading and writing files with correct encoding and buffering, walking and manipulating directories with pathlib, atomic writes and temporary files, and serialising state to JSON, CSV, YAML and pickle — including when each of those is the wrong choice.

Topics: Reading and writing files · Working with directories and pathlib · Encodings, newlines and binary mode · Serialization and deserialization — JSON, CSV, YAML, pickle · Atomic writes and temporary files · File permissions and ownership from Python

  • Assignments: (1) Write a config loader that merges defaults, a file and environment variables; (2) Implement an atomic write that survives being killed mid-run
  • Capstone: Build a state file mechanism an automation tool can safely resume from
07Regular expressions and log parsingLive & Interactive5 hrs · 2 assignments · 1 capstone

Turning unstructured text into structured records — the single most common Python task in an operations team. Pattern syntax, metacharacters, groups, compilation and the difference between match, search and findall, applied to real log formats.

Topics: What regular expressions are and where they belong · Using regular expressions in Python — the re module · Patterns, metacharacters and character classes · Groups, named groups and backreferences · Compiling patterns and matching efficiently · Greedy versus lazy matching and catastrophic backtracking

  • Assignments: (1) Parse a web server access log into structured records and aggregate by status code; (2) Rewrite a pattern that backtracks catastrophically on long input
  • Capstone: Build a log analyser that extracts, aggregates and alerts on a real log format
08Processes, signals and command-line toolsLive & Interactive5 hrs · 2 assignments · 1 capstone

Where Python meets the operating system. Running external commands safely, streaming and capturing output, handling exit codes and timeouts, responding to signals, and wrapping the result in a command-line interface with proper logging — plus a short look at desktop GUI options for the rare case a tool needs one.

Topics: subprocess — run, Popen, argument lists and why shell=True is dangerous · Capturing, streaming and interleaving stdout and stderr · Exit codes, timeouts and killing child processes · Signals, graceful shutdown and cleanup · Building a CLI with argparse — subcommands, defaults and help · Structured logging and verbosity levels · GUI programming in Python — Tkinter and PyQt, and when a desktop tool is justified

  • Assignments: (1) Wrap a long-running shell command with a timeout, streamed output and a correct exit code; (2) Add subcommands, --dry-run and log levels to an existing script
  • Capstone: Ship an operations CLI with subcommands, dry-run mode, logging and a non-zero exit path
09Networking, HTTP and API clientsLive & Interactive5 hrs · 2 assignments · 1 capstone

Talking to the rest of the estate. HTTP requests with authentication, pagination and retry semantics, then the socket layer underneath for the cases where HTTP is not the protocol — health checkers, port scanners and custom agents.

Topics: What networking looks like from an automation script · Creating and sending HTTP requests in Python · Authentication, headers, sessions and connection reuse · Pagination, rate limiting, timeouts and retry with backoff · Creating and managing TCP and UDP sockets · Popular Python networking libraries — requests, httpx, urllib3, paramiko

  • Assignments: (1) Write a paginated API client that retries on 429 and 5xx with exponential backoff; (2) Build a TCP health checker that reports latency across a host list
  • Capstone: Build a resilient client for an internal API, with tests that simulate failures
10Databases and stateful automationLive & Interactive5 hrs · 2 assignments · 1 capstone

When automation needs to remember something. The DB-API, connecting and interacting with relational databases, parameterised queries and transactions, connection pooling, and the SQL injection failure mode that appears the moment someone builds a query with string formatting.

Topics: What database programming is and when automation needs it · Connecting to and interacting with databases from Python · Popular Python database libraries — sqlite3, psycopg, PyMySQL, SQLAlchemy · SQL queries, parameterisation and injection · Transactions, commits and rollback · Connection pooling and long-running jobs

  • Assignments: (1) Store and query run history in SQLite from an automation tool; (2) Fix a query built by string concatenation and prove the injection is closed
  • Capstone: Add durable, queryable run history to the CLI you built earlier
11Internal web services and APIsLive & Interactive5 hrs · 2 assignments · 1 capstone

Exposing automation to other teams. What web development means in a platform context — a small internal service, not a product — using Flask or FastAPI, then deployment behind a real server, and the application security issues that matter when the endpoint can change infrastructure.

Topics: What web development means for a platform team · Creating and deploying web applications with Flask and FastAPI · Routing, request validation and JSON responses · Popular Python web frameworks and how they differ · Serving with WSGI/ASGI behind a real server · Web application security — authentication, authorisation, input validation, secrets

  • Assignments: (1) Expose an existing automation script as an authenticated HTTP endpoint; (2) Add request validation and rate limiting to that endpoint
  • Capstone: Deliver a small internal self-service API that another team could call safely
12Python in the cloud and in the pipelineLive & Interactive5 hrs · 2 assignments · 1 capstone

The delivery end of the course. Driving cloud control planes with the vendor SDKs, deploying Python to serverless runtimes, using Python for CI/CD and infrastructure as code, testing with pytest, and packaging so the tool installs cleanly for the next engineer.

Topics: What cloud computing changes for automation code · Deploying Python applications to the cloud · Cloud SDKs — boto3, azure-sdk, google-cloud, paginators and credential chains · Serverless computing — Lambda and Cloud Functions, cold starts and packaging · Python for DevOps tasks and CI/CD pipeline steps · Infrastructure as code from Python — CDK and Pulumi · Testing with pytest — fixtures, parametrisation, mocking cloud calls · Packaging, dependency pinning and internal distribution · Where machine learning fits in operations tooling

  • Assignments: (1) Write a boto3 script that tags and reports on untagged resources across an account; (2) Package a tool and install it from an internal index in a pipeline
  • Capstone: Ship a tested, packaged Python tool that runs on a schedule in CI against a real cloud account

Need this mapped to your stack?

We rebuild the agenda around the tools you actually run.

Request a custom agenda
# hands-on

Labs and capstones your engineers actually build

LAB · CLI

Ship an operations CLI

Build a multi-subcommand tool with argparse: configuration, structured logging, dry-run mode, correct exit codes, and a --help someone else can actually use.

argparseloggingexit codes
LAB · PROCESSES

Wrapping shell safely

Replace a fragile shell pipeline with subprocess: argument lists, timeouts, streamed output, signal handling and cleanup on failure.

subprocesssignalstimeouts
LAB · TEXT

Log parser and aggregator

Turn a real access log into structured records with regular expressions, aggregate by endpoint and status, and emit a report and a non-zero exit on threshold breach.

regexparsingreporting
LAB · APIs

Resilient API client

Write a paginated, authenticated client with timeouts, rate-limit handling and exponential backoff, then prove it under a fault-injecting test server.

requestsretriespagination
LAB · CLOUD

Account-wide audit with boto3

Scan a live cloud account for untagged, unencrypted and publicly exposed resources using paginators and credential chains, and produce a remediation plan.

boto3auditpaginators
CAPSTONE · DELIVERY

Packaged tool running in CI

Package the tool with pyproject.toml and pinned dependencies, add a pytest suite that mocks cloud calls, and run it on a schedule from a pipeline.

pytestpackagingci
# ecosystem

The tools Python sits next to

pip
virtualenv
pytest
boto3
requests
Pandas
FastAPI
Ansible
Jenkins
Docker
AWS Lambda
Git

Who this is for

  • System administrators and operations engineers moving beyond shell scripting
  • DevOps and platform engineers building internal tooling and pipeline steps
  • SREs writing exporters, checkers, runbook automation and incident tooling
  • Cloud engineers automating account governance with vendor SDKs
  • Security engineers automating scanning, evidence collection and compliance reporting
  • QA and release engineers building test harnesses and deployment automation

Pre-requisites

  • Comfortable on a Linux or macOS command line — files, permissions, processes, environment variables
  • Some scripting exposure in any language, even if only Bash
  • Basic understanding of HTTP requests and responses
  • Familiarity with version control, ideally Git
  • A free-tier cloud account or local VMs for the automation and SDK labs
# pricing

Straightforward pricing

Every plan includes 1 year of full LMS access — not just this course, the entire DevOpsSchool LMS: 20+ courses, 50+ tools, videos, quizzes, assignments and projects.

Self-paced video

₹833/mo

Billed yearly at ₹9,996

Enroll now

1-on-1 mentorship

₹99,999

Full program, private instructor

Enroll 1-on-1

Corporate / private batch

8–30 engineers · custom agenda · onsite or online · PO and GST invoicing

Get a custom quote

Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.

Terms. Course material remains licensed to the attendee. Read the terms.

Your data. We don't share it with third parties. Privacy policy.

Every attendee gets a verifiable certificate

  • Issued per attendee on completion
  • Verifiable at devopsschool.com/certificates
  • Hard copy available on request
  • Corporate batches receive an attendance and assessment report
DevOpsSchool

Python Training

Certificate of completion

# feedback

What engineers say

4.4 / 5 from 26 reviews on Trustpilot.

★★★★★
Great learning experience from a very knowledgeable instructor with well-prepared course notes. The lab exercises on AWS instance work well to learn the hands-on side of the course.
Ando Gg · Trustpilot
★★★★★
Rajesh is a very good trainer I have experienced in DevSecOps training. The number of contents in different topics he has posted on the DevOpsSchool public website are amazing and user friendly for beginners and experienced professionals.
Ashutosh Mishra · Trustpilot
★★★★★
The trainer (Rajesh) provided very good sessions on SRE profession. Not only hands-on learning on the tools but also SRE mindset.
Peter Wang · Trustpilot
★★★★★
Very good training session. Well explained from the basics to the complex concepts. Also tried to cover practicals and demos within the 3 hour sessions. The learning content and videos are of a great deal of help.
Sreekanth Kannoth · Trustpilot
★★★★★
Basics explanation was exemplary from Rajesh where he dealt with complicated topics to be simple. Great learning stuff personally for me.
Krishna Mohan Yelleti · Trustpilot
★★★★★
Very detailed explanation and has lots of patience in attending the questionnaire. Thanks again for your wonderful sessions.
Uttam Samudrala · Trustpilot
# comparison

Why a named practitioner beats a marketplace listing

What mattersYouTube + blogsGeneric online courseFreelance marketplaceDevOpsSchool
Named practitionerNoRarelyVaries per bookingYes — same trainer each time
Production experienceUnknownUnknownUnverified20 years, named employers
Custom agendaNoNoSometimesBuilt from your stack
Onsite deliveryNoNoSometimesYes
Lab environmentNoneSandbox that expiresVariesYour own cloud — skill goes with you
AssessmentNoneQuizRarelyAssignments + capstone per module
Per-attendee certificatesNoSometimesRarelyYes
Corporate invoicingNoLimitedVariesPO and GST
Post-training supportNoneForum, time-limitedNoneLifetime forum access
# questions

Frequently asked

Can the agenda be customised for our stack?
Yes — that is the normal case for a private batch. We start with a discovery call, look at the cloud, CI system and constraints you actually run, and rebuild the module list around them. Examples then use your topology rather than a generic one.
Do you deliver onsite?
Yes. Private batches run onsite at your premises, live online, or hybrid. You provide the room and the engineers; we bring the trainer, agenda, labs, assessment and certificates.
What lab environment do we need?
Attendees provision their own environment — free-tier AWS, Azure or GCP, or local VMs — and we walk them through it. We deliberately do not hand out temporary sandboxes, because the environment they build is the one they keep.
What size are batches?
Private corporate batches run 8 to 30 engineers. Public Live & Interactive cohorts are capped at 10 so everyone gets time with the trainer.
Do attendees get a certificate?
Yes — every attendee receives a completion certificate, verifiable at devopsschool.com/certificates. Corporate batches also receive an attendance and assessment report.
What is your refund position?
If we cancel or postpone a cohort, you receive a full refund within 15 days. There is no general money-back guarantee, and GST and gateway fees are not refunded.
Is this a general programming course or a DevOps one?
It is Python taught for infrastructure work. The language core is covered properly, but the examples are processes, files, logs, APIs, cloud SDKs and pipelines rather than exercises. If you need a data science or web product track instead, we build that as a separate agenda.
Our team already writes Python. Is there anything for them?
Usually a lot. Teams that write Python daily often still have shell=True in production, no timeouts on HTTP calls, no retry policy, unparameterised SQL, and no packaging. We can run a shortened batch that starts at module 6 and concentrates on those.
How long does a private Python batch take?
Typically three to five days. Language core plus files, text and processes fits in three; adding APIs, databases, cloud SDKs, testing and packaging pushes it to five.
Which Python version do you teach?
Current Python 3.x. We cover version management with pyenv because most estates run several versions at once, and we flag the syntax and standard library differences that matter if you are still maintaining older code.
Do you cover testing and packaging, or just scripting?
Both, and they are treated as core rather than optional. A tool other engineers depend on needs pinned dependencies, an installable package and a pytest suite that runs in CI without touching a real cloud account — that is the last module and the capstone.

Still deciding?

Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.

Talk to an advisor
# ready when you are

Book a Python trainer — or ask a question first.

  • No spam, no drip sequence
  • Syllabus in 60 seconds
  • A human reply within one business day

Prefer to call or email?

More ways to reach us on the contact page.

Talk to an advisorRequest a quote