How to Put Python on a Resume (With Examples)

Python belongs in two places on a resume: the skills line, written as "Python" plus the libraries you have shipped with (say "Python: pandas, FastAPI, pytest"), and at least one experience bullet where a script or service you wrote changed something measurable. State your level by describing the work, not with a label like "expert". Name a library only if you have used it on real work, because interviewers pick one and ask. This applies to any role that uses Python, from finance and operations to data and engineering.

Where Python Goes on a Resume

Skills section. Write "Python" with the libraries and one signal of depth: "Python 3 (working): pandas, openpyxl, requests". If you specialise, name the area: web, data, automation or testing.

Experience bullets. This is where the claim becomes believable. Name Python in the bullet itself, with what it did and what came out of it. Do not leave it only in a tech-stack line at the end of the job entry.

Projects. A GitHub repo with a readable README, tests and a clear purpose is useful evidence, especially for beginners and career changers who have fewer work bullets. Link it.

Not sure your CV shows the Python a job ad asks for? Paste both into the free job match tool to check whether the ad asks for Python and whether your CV shows it. It is deterministic, needs no signup, and lists the terms from the ad that your CV is missing.

How to Show Your Python Level Honestly

Interviewers often ask for a short coding exercise, so overstating your level tends to come out in the first technical question. Describe what you have done:

• Basic: Scripts, loops and functions, reading and writing files, calling an API. Write "Python (basic)" or list the tasks.
• Working: Libraries like pandas or requests in regular use, virtual environments, reading other people's code, simple tests. Write "Python (working)" and name the libraries.
• Advanced: Packaged and tested code in production, type hints, async code, performance work, code review for others. Write "Python (advanced)" and give a bullet that proves it.

Example Python Bullets by Level

The bullets below are made up to show the pattern. Use your own work, and only numbers you can explain.

Scripting and automation in a non-dev role (illustrative example):

Wrote a Python script with pandas and openpyxl that merged the three weekly sales spreadsheets and produced the summary report; the task went from about two hours of manual copying to a few minutes.

Data analyst (illustrative example):

Used Python (pandas, matplotlib) to clean and analyse 18 months of support-ticket data, and found that one product category drove most repeat contacts; the findings went into the quarterly planning deck.

Developer (illustrative example):

Built a FastAPI service with pytest coverage and Docker deployment that replaced a manual order-validation step; validation errors reaching the warehouse team fell sharply in the first quarter.

What ATS Systems and Hiring Managers Look For

"Python" alone matches a keyword filter. The words around it tell a recruiter which kind of Python you write: FastAPI, Django or Flask suggest web work; pandas, NumPy or scikit-learn suggest data work; Airflow, dbt or Spark suggest data engineering; pytest, Selenium or Playwright suggest testing. Match your wording to the job ad where it is true.

Past the keywords, hiring managers for developer roles look for:

• Python 3 and a recent version. Python 2 is end-of-life. Naming a current 3.x release shows you keep up.
• Environment and packaging. Poetry, pip, virtualenv or conda, and why you chose one.
• Type hints. mypy or Pyright usage suggests production habits.
• Tests. pytest or unittest. Any role above entry level expects them.

Developer Bullets: Turning Tasks into Outcomes

The usual weakness is a bullet that describes a task. "Wrote Python scripts for data processing" tells the reader nothing. Say what the code did, what it ran on and what changed. The figures in these examples are made up to show the shape of a bullet; use your own.

Illustrative example:

Before: Wrote Python scripts for data processing automation.

After: Built a Python ETL pipeline with pandas and SQLAlchemy that loads daily transaction exports from five source systems; replaced a manual preparation step and removed a recurring reconciliation error in the monthly report.

Illustrative example:

Before: Developed a REST API using Flask.

After: Designed a Flask REST API for an e-commerce platform with JWT authentication and Redis caching on the busiest endpoints, and added a circuit breaker around the payment provider so its outages no longer took the checkout down.

Illustrative example:

Before: Used Python for machine learning projects.

After: Trained a scikit-learn gradient-boosting model to predict customer churn, served it through a FastAPI endpoint in Docker on AWS Lambda, and documented the precision and recall trade-off for the retention team.

Libraries: What to Mention and Where

Not all of Python's ecosystem belongs on every CV. Group what you have used meaningfully, and put the important tools inside bullets too.

Web and API: Django, Django REST Framework, FastAPI, Flask, SQLAlchemy, Celery, Pydantic

Data and analytics: pandas, NumPy, Polars, PySpark, Jupyter, matplotlib, Plotly

Machine learning: scikit-learn, PyTorch, TensorFlow, Hugging Face Transformers, MLflow

Data engineering: Airflow, Prefect, dbt, Kafka clients, AWS Glue

Testing and quality: pytest, hypothesis, mypy, ruff, pre-commit

Infrastructure: boto3, Ansible, Terraform CDK

Tools that appear in a bullet next to an outcome read as proven. Tools that only appear in a long list read as padding.

Certifications and Credentials

Python has no dominant certification, so work history and public projects usually count for more. Ones that can help:

• PCEP / PCAP / PCPP (Python Institute): useful for early-career candidates, or enterprise roles where formal credentials matter.
• Google Professional Machine Learning Engineer and AWS Certified Machine Learning Specialty: relevant for ML-adjacent roles.
• Merged contributions to a well-known package: worth a line, and often worth more than a certificate.

Common Mistakes That Weaken Python CVs

Listing Python with no context. "Proficient in Python" says little. Add the version, the libraries and the kind of work.

Mixing levels in one list. Django next to "wrote Python scripts" invites a question. Be clear about what you shipped and what you only tried.

Skipping async and testing. For web or I/O-heavy roles, say so if you have written async code (asyncio, httpx) in production. If you write tests, make pytest visible.

Vague project descriptions. "Built a web app using Flask" is a topic. Say what problem it solved, who used it and what was hard.

Closing

Python appears on a lot of CVs, so the word alone carries little. Show where you used it, at what level, and what changed because of it.

NextCV reads the job description you are targeting and surfaces the Python experience in your background that matches it, so the right version of your work leads each CV.

Ready to put this into practice? Tailor your CV to a job with NextCV →

The AWS CV guide, the DevRel CV guide, and the DevOps Engineer CV guide cover the closest adjacent ground. Cross-reference the Data Analyst CV guide and the tech layoff CV guide before you settle on a final draft.

Related Articles

• The Best CV Format in 2026: Chronological, Functional, or Hybrid?
• TypeScript on Your CV: How to Showcase It So Employers Actually Notice
• React on Your CV: How to Showcase It So Employers Actually Notice
• Full Stack Developer CV Guide: What Recruiters Actually Look For in 2026
• Frontend Developer CV Guide: What Recruiters Actually Look For in 2026