Boolean search strings for Python developers: Django, FastAPI, data pipelines and the analyst collision
On this page
- Frameworks, kinds of work and credentials that change what a Python search finds
- Ten Boolean strings by kind of Python work
- What LinkedIn, Dice, GitHub and Google actually support
- Narrowing by what the code does and by seniority
- False positives worth excluding with NOT
- A worked example: three passes on a Django backend search
- What a search cannot verify
- Questions people ask
A Python developer search has to separate people who build software in Python from the much larger group who use it: data analysts, data scientists, testers and DevOps engineers all list Python. The strings that work pair the title variants (Python developer, Python engineer, Django developer, backend engineer) with a web or service framework (Django, Flask, FastAPI) and a production word (API, deployed, services), then exclude analyst, instructor and recruiter titles. As of November 2026, LinkedIn's Boolean search takes AND, OR, NOT, quotes and parentheses, with operators in capitals and no wildcards.
Below are ten strings by kind of Python work, and what LinkedIn, Dice, GitHub and Google support as of November 2026. For pipeline-heavy roles, see Boolean search strings for data engineers; for the operators themselves, see Boolean search strings for recruiters.
Frameworks, kinds of work and credentials that change what a Python search finds
| Kind of Python work | Terms candidates write | Common titles |
|---|---|---|
| Web and API backend | Django, Django REST Framework, Flask, FastAPI, PostgreSQL, Celery, Redis | Python developer, backend engineer, Django developer |
| Data pipelines | pandas, PySpark, Airflow, dbt, SQL, ETL | Data engineer, Python data engineer |
| Automation and tooling | Scripting, boto3, Ansible, CLI tools, internal tools | Automation engineer, software engineer, DevOps engineer |
| Quant and scientific | NumPy, SciPy, pandas, Jupyter, market data | Quantitative developer, research engineer |
| Machine learning | PyTorch, TensorFlow, scikit-learn | Machine learning engineer (a separate search) |
- "Uses Python" is not "builds in Python." An analyst who writes pandas in a notebook and a developer who maintains a payments API both list Python. Require the framework and a production word, and decide with the client whether data-heavy backgrounds are in or out before you write the exclusion block.
- The framework is the strongest single signal. Django's overview describes a full web framework with its own object-relational mapper and an automatic admin interface; Flask calls itself a lightweight WSGI web application framework; FastAPI describes itself as a web framework for building APIs with Python based on standard type hints. Name the client's framework first and add the others only if the pool is thin; asyncio and Celery on a profile point to concurrency and background-job work.
- Python Institute certifications are optional. The Python Institute, operated by OpenEDG, shows PCEP (Certified Entry-Level Python Programmer), PCAP (Certified Associate Python Programmer) and PCPP1 (Certified Professional Python Programmer 1) as active exams on its General-Purpose Programming track and PCPP2 as work in progress, as of November 2026. Treat them as evidence of study, not of production work.
- Python 2 is a legacy signal. Python.org's sunset page says January 1, 2020 was the day Python 2 was sunset and that it would not be improved after that, even for security problems. A profile that mentions a "Python 2 to 3" migration describes modernization work, which matters when the client still runs old code.
Ten Boolean strings by kind of Python work
Swap in the framework, cloud and metro from your own intake; these are examples.
Web and API backend
1. Python backend developer, Django — LinkedIn general search
("python developer" OR "python engineer" OR "django developer" OR "backend engineer") AND (django OR "django rest framework") AND (postgresql OR postgres) NOT (recruiter OR instructor OR "data analyst")
2. API developer, FastAPI or Flask — LinkedIn Recruiter, Job titles + Keywords filters
("python developer" OR "backend engineer" OR "software engineer") AND (fastapi OR flask) AND ("rest api" OR "rest apis" OR microservices) AND (docker OR kubernetes)
3. Senior Python engineer, async and queues — LinkedIn general search
("senior python developer" OR "senior python engineer" OR "lead python developer") AND (asyncio OR celery OR rabbitmq OR "message queue") AND (aws OR gcp OR azure)Data, automation and quant
4. Python pipeline developer — Dice resume search
(python) AND (airflow OR pyspark OR dbt) AND (etl OR "data pipeline") NOT ("data analyst")
5. Automation and internal tooling — LinkedIn general search
("python developer" OR "automation engineer" OR "software engineer") AND (automation OR "internal tools" OR "command line") AND (boto3 OR ansible OR "rest api") NOT ("manual testing" OR "qa analyst")
6. Python developer in trading or risk — LinkedIn Recruiter, Keywords filter
("python developer" OR "quantitative developer" OR "software engineer") AND (pandas OR numpy) AND (trading OR "risk models" OR "market data") NOT ("financial advisor" OR recruiter)Quality signals and credentials
7. Python developer who tests and types their code — LinkedIn general search
("python developer" OR "python engineer") AND (pytest OR "unit tests") AND (mypy OR "type hints" OR "code reviews")
8. Python Institute certification — LinkedIn general search
("python developer" OR "python programmer" OR "software engineer") AND (pcap OR pcpp1 OR "certified associate python programmer" OR "certified professional python programmer")GitHub and search-engine X-ray
9. Public GitHub accounts by language and city — GitHub user search
language:python location:"austin" followers:>10
10. Public LinkedIn profiles by framework and metro — Google X-ray
site:linkedin.com/in ("python developer" OR "python engineer") "fastapi" "austin" -jobs -recruiter
The resume version is a filetype search:
filetype:pdf "python developer" resume ("django" OR "fastapi") -template -sample. As with
any X-ray, the results are leads, and they reach only what someone has made public.
What LinkedIn, Dice, GitHub and Google actually support
As of November 2026, LinkedIn's Boolean help page requires AND, OR and NOT in capitals, supports quotes and parentheses, gives OR the lowest precedence and does not support wildcards, so "developer," "development" and "engineer" each need writing out. LinkedIn Recruiter's Boolean page treats Job titles and Skills and Assessments as Boolean filters and warns that too many facets in one query can cause a search result issue, so split the title block and the framework block between those two filters instead of stacking everything in Keywords.
Dice's Boolean guide says its database fills in word endings and recommends the shortest form of a word; its own example is (admin) finding admins, administrators and administrative experience. Keep NOT blocks short there, because Dice applies an exclusion to the whole resume.
GitHub's user
search documents language:, location:, followers: and
repos:, and says language: matches users with a majority of their repositories
in that language. GitHub's repository
languages page says it uses the open-source Linguist library to determine file languages, and
Linguist lists Jupyter Notebook separately from
Python. Notebook-heavy accounts, often analysts' and scientists', may therefore fall outside
language:python, which suits a developer search. Google's
search operators page documents quotes,
site:, the minus sign and filetype:, but not OR, so test the OR block in an
X-ray before relying on it.
Narrowing by what the code does and by seniority
Ask the client what their Python code does all day: serve web requests, move data, automate infrastructure, or run models. Each produces a different profile vocabulary, and a candidate strong in one is not automatically ready for another. A web backend profile talks about endpoints, latency, migrations and background jobs; a pipeline profile about schedules, backfills and data quality; an automation profile about scripts, cloud APIs and the teams that used the tools. Put the client's version in a required block.
Seniority shows in ownership words: "designed the API," "owned the service," "on call," "scaled," "profiling," "code reviews" and "mentored," over "worked on," "wrote scripts" and "assisted." LinkedIn's page on premium search filters lists Years of Experience and Seniority Level as Recruiter and Sales Navigator filters; on a basic account, an experience phrase in the keyword string only finds people who wrote one.
False positives worth excluding with NOT
- Data analysts and BI developers. "Data analyst," "reporting analyst" and "BI developer" profiles list Python, SQL and pandas. Exclude them for software roles, and see Boolean search strings for data analysts when the client actually wants reporting.
- Data scientists, for backend roles. They write Python every day, mostly in notebooks and models. Exclude "data scientist" unless the client wants someone who can also ship services.
- Test automation engineers. SDETs write pytest and Selenium in Python. Exclude "sdet," "qa engineer" and "test automation" for development roles; see Boolean search strings for QA engineers for the reverse.
- DevOps and SRE profiles. Many write Python glue around infrastructure. Keep them for automation roles and exclude "devops" and "site reliability" when the job is product code.
- Instructors, tutors and bootcamp staff. "Python instructor," "tutor" and "teaching assistant" profiles list every library they teach.
- The snake. On a Google X-ray, python alone also matches reptile breeders and pet supply pages. Quote "python developer" or "python engineer" rather than the bare word.
None of these strings targets or excludes anyone by age, sex, race, religion, national origin, disability or veteran status, and yours should not either; that includes proxies such as graduation years.
A worked example: three passes on a Django backend search
An invented search, shown as it actually gets narrowed.
Intake: A health-tech company needs a backend Python developer to own the Django REST APIs and Celery background jobs behind its appointment scheduling app. Not looking for data scientists or analysts, and not looking for test automation engineers.
Pass 1: python AND django: a long list mixing analysts who once
followed a Django tutorial, data scientists, testers and recruiters.
Pass 2: ("python developer" OR "backend engineer" OR "django developer") AND
(django OR "django rest framework") AND (postgresql OR postgres) NOT ("data analyst" OR "data scientist"
OR sdet): relevant, though many profiles describe simple create-read-update endpoints only.
Pass 3: add AND (celery OR "task queue" OR "background jobs") AND ("on call" OR
monitoring OR "production incidents"). Those terms tend to come from developers who kept a live
system running. The list is short enough to call, and the screen asks about a background job that failed
silently and how they found out.
The framework found Python web developers; the production words found the ones who have been paged for their own code. That second block is usually what the hiring manager means by "senior."
What a search cannot verify
A string can find someone whose profile names the right framework and production terms. It cannot show whether they designed the system or extended someone else's, how readable their code is, or whether a framework on the profile was used last month or five years ago. The Python developer screening questions test Python versions, Django and FastAPI, packaging, async and tests on the call, and the software engineer phone screen questions add general depth questions without a coding exercise. Both work best once the client has said which row of the table above the role really belongs to.
Questions people ask
How do I tell a Python developer from someone who only uses Python for analysis?
Require framework and production words such as Django, FastAPI, Flask, REST API, deployed or services, and exclude analyst and data scientist titles with NOT. Analysts and scientists list Python as a tool for notebooks and reports; developers build and maintain software in it, and their profiles describe what they shipped.
Are Python certifications worth searching for?
Only as optional terms. The Python Institute, operated by OpenEDG, lists PCEP, PCAP and PCPP1 as active exams as of November 2026, with PCPP2 marked work in progress, and some candidates list them, but many experienced Python developers hold no certification. A certification shows study; a profile that names a framework and a production system shows work.
Which Python framework should go in the string?
The one the client actually runs: Django for full web applications with an ORM and admin, Flask or FastAPI for lighter APIs and services. If the pool is thin, put the frameworks in one OR block and confirm on the call how recently and how deeply the candidate used the client's framework.
Can GitHub show me Python developers near a specific city?
Yes. GitHub's user search documents language: and location: qualifiers, as in language:python location:"austin". It only reaches public code, and an account made mostly of notebooks may be labeled Jupyter Notebook rather than Python, because GitHub's language detection treats notebooks as their own language.