Technology · Mid-career
Python Developer Resume Example
Python covers many kinds of work, so this example picks one and commits to it: data pipelines, here in healthcare software. Use it if you build scheduled data workflows, and borrow its structure if your Python is in web services or automation instead: a stated specialism, libraries named in context and evidence of tested, typed code.
The example resume
Laid out in the Proof template. The person, employers, schools and figures in this example are invented for illustration. Any resemblance to real people or organisations is unintended.
Lucía Navarro
Python Developer (Data Pipelines)
- lucia.navarro@example.com
- +1 555 0139
- Valencia, Spain
- github.example.com/lucia-navarro
Professional summary
Python developer with seven years of experience, specialising in data pipelines for healthcare providers. Builds and runs Airflow workflows that move appointment, laboratory and billing records into a PostgreSQL warehouse each night, with data quality checks at every stage. Careful with patient data: all work is done under GDPR using pseudonymised identifiers.
Work experience
Python Developer
Almenara Health Data, Valencia
Mar 2022 – Present
- Built 34 Airflow DAGs in Python that load appointment, laboratory and billing data from 22 clinics into a PostgreSQL warehouse every night
- Rewrote the slowest transformation from row-by-row pandas loops to vectorised operations in Polars, cutting its run time from 95 minutes to 11
- Added data quality checks with Great Expectations and pytest, catching 9 schema changes in source systems before they reached reports in the first year
- Wrote a parser for HL7 v2 laboratory messages that handles 180,000 results a day, maps local test codes to LOINC and quarantines malformed records for review
- Packaged shared pipeline code as an internal library with type hints, mypy checks and 90% test coverage, now used by 3 teams
Junior Python Developer
Turia Bridge Analytics, Valencia
Sep 2019 – Feb 2022
- Developed ETL scripts in Python and SQL for 8 retail and insurance clients, scheduled first with cron and later with Airflow
- Built a FastAPI service exposing cleaned datasets to client dashboards, with pagination, API keys and responses under 200 ms for typical queries
- Replaced one client's manual spreadsheet reconciliation with a pandas report, saving their finance team about 2 days each month
- Containerised the scheduled jobs with Docker so that development and production ran the same Python and dependency versions
Skills
Python: pandas, Polars, SQLAlchemy, Pydantic, FastAPI, pytest, mypy
Data: Airflow, dbt, PostgreSQL, Parquet, Great Expectations
Healthcare data: HL7 v2, FHIR, LOINC, pseudonymisation, GDPR
Tools: Docker, Git, GitLab CI, AWS (S3, RDS), Poetry
Education
BSc Computer Engineering
Levante Polytechnic University, Valencia
2015 – 2019
Languages
Spanish: native, Valencian: native, English: fluent
Open this example in the resume builder Start empty with this template
Why this resume works
- The summary states a specialism (data pipelines for healthcare) in its first sentence, so the reader does not have to work out which of the many kinds of Python developer this is.
- Library names appear where they did the work: Airflow for scheduling, Polars for speed, Great Expectations for data quality, which shows judgement about tools as well as familiarity with them.
- The run time bullet names the cause of the slowness (row-by-row pandas loops) as well as the result (95 minutes to 11), which is what another Python developer would want to know.
- Handling of patient data is mentioned in both the summary and the skills list, because healthcare employers need to see that privacy rules are understood.
- The internal library bullet (type hints, mypy, 90% coverage) signals software engineering discipline in pipeline code, which is often written with less care than application code.
What employers look for in this role
- Build and maintain data pipelines or back-end services in Python
- Write tests with pytest and keep code typed and linted
- Design database schemas and write efficient SQL
- Schedule, monitor and troubleshoot batch jobs and workflows
- Validate incoming data and handle bad records safely
- Package and deploy code with containers and CI pipelines
Skills to consider
List only the skills you can back up with an example. These are the ones that come up most for this kind of role.
- Python and libraries
- pandas or Polars, SQLAlchemy, Pydantic, FastAPI, Django or Flask, asyncio, pytest, Type hints with mypy or pyright
- Data engineering
- Airflow, Dagster or Prefect, dbt, PostgreSQL, Parquet and columnar storage, PySpark, Data quality testing
- Tooling
- Poetry, pip-tools or uv, Docker, Git, CI pipelines, Ruff or Black, Cloud storage and managed databases
More bullet points to adapt
Each of these follows the same pattern as the example: an action, what it was applied to, and what changed. Swap in your own facts and figures. The bullet builder assembles the pattern for you.
- Made a daily load idempotent by switching from inserts to merge statements keyed on source ID, so failed runs could be retried without duplicate rows
- Reduced memory use of a 14 GB CSV import from out-of-memory failures to a steady 1.2 GB by streaming it in chunks
- Migrated 40 cron jobs to Airflow with retries, alerts and backfills, ending the weekly check of log files by hand
- Wrote Pydantic models for 18 inbound file formats, turning silent type errors into rejected files with a clear message to the supplier
- Moved the project from requirements files to Poetry with a lock file, ending dependency mismatches between the laptops of 6 developers
- Profiled an API endpoint with cProfile and removed a repeated database call, bringing response time from 1.4 seconds to 300 ms
Words that recur in adverts
These terms appear often in adverts for this kind of role. Use the ones that are true of you, in sentences that show the skill in use, and check a specific advert with the keyword checker.
Which sections to include
State your specialism in the summary, because "Python developer" covers web services, data engineering, automation and machine learning, and an employer wants to know which one you are. Experience follows, with library and tool names inside the bullets. In the skills section, give Python libraries their own line and separate them from data tooling and infrastructure. A projects section is useful if your paid work is in one area and you are applying to another. Spoken languages are worth a line if you work in a multilingual market. Education comes last unless you graduated recently.
Mistakes to avoid
- Presenting yourself as a web, data, automation and machine learning developer all at once; pick the specialism the advert describes and give the others a line at most.
- Writing "Python" and nothing else in the skills list, when the libraries and frameworks (Airflow, pandas, FastAPI, Django) are what distinguish one Python role from another.
- Describing notebooks and one-off scripts as production pipelines; if the work ran on a schedule with tests and monitoring, say so, and if it did not, describe it honestly as analysis.
- Leaving out testing, typing and packaging, which is how a reader tells a developer who writes maintainable Python from one who only writes scripts.
- Giving row counts with no time frame ("processed 5 million rows"); say whether that was per day or per run, and how long it took.
Questions and answers
Should I call myself a Python developer or a data engineer?
Use the title in the advert if it honestly describes your work. The two overlap heavily in pipeline roles: "Python developer" tends to be used where the emphasis is on code, and "data engineer" where it is on platforms and warehousing. Your headline can change between applications while the experience stays the same.
Do I need Django or Flask if I work on data pipelines?
Not for a pipeline role, though a small API often sits beside the pipelines, and FastAPI or Flask experience helps there. Mention a web framework if you have used one in earnest and leave it out otherwise: a framework listed without evidence invites questions you may not enjoy.
How do I show Python skill without public code?
Describe the engineering in your bullets: tests, type checking, packaging, performance work, code review. Naming the cause of a problem and the fix, as in a pandas loop replaced with vectorised operations, shows more than a repository link. The guide to writing bullet points has more on this pattern.
Is it worth listing the Python version?
A single mention such as "Python 3.12" is fine but rarely decisive, since most current work is on Python 3. It matters more if you carried out a migration, for example from Python 2 or across a major framework version, in which case give it a bullet.