You will get I will build a Python web scraper for login sites to CSV, JSON, or API
Project details
Send me one authorized source and target fields; I will return a working Python scraper with clean CSV/JSON output or a small API/CLI runner.
You get run notes, logs, and a handoff schema.
Good fits include authorized supplier lookups, product/price/stock data, directories or catalogs, dynamic pages that need Playwright/Selenium, repeatable CSV/JSON output, and small local runners.
My approach is reliability-first: confirm the source, allowed access, and fields; build one narrow path before expanding; prefer direct HTTP/parsing when safe and Playwright/Selenium when a browser is required; normalize output fields; add logging, timeouts, and skipped-record reasons; and document how to run, maintain, and safely scale the script.
I do not bypass CAPTCHA, bot protection, paywalls, access controls, or website terms. Use authorized access and Upwork-approved secure sharing only.
Delivery times shown are a safe estimate - I often deliver faster. The clock starts once I have everything I need to begin.
Proof: public Playwright reliability demo - 17/20 before vs 20/20 after, CI-enforced. See my Portfolio.
You get run notes, logs, and a handoff schema.
Good fits include authorized supplier lookups, product/price/stock data, directories or catalogs, dynamic pages that need Playwright/Selenium, repeatable CSV/JSON output, and small local runners.
My approach is reliability-first: confirm the source, allowed access, and fields; build one narrow path before expanding; prefer direct HTTP/parsing when safe and Playwright/Selenium when a browser is required; normalize output fields; add logging, timeouts, and skipped-record reasons; and document how to run, maintain, and safely scale the script.
I do not bypass CAPTCHA, bot protection, paywalls, access controls, or website terms. Use authorized access and Upwork-approved secure sharing only.
Delivery times shown are a safe estimate - I often deliver faster. The clock starts once I have everything I need to begin.
Proof: public Playwright reliability demo - 17/20 before vs 20/20 after, CI-enforced. See my Portfolio.
What's included
| Service Tiers |
Starter
$200
|
Standard
$700
|
Advanced
$1,500
|
|---|---|---|---|
| Delivery Time | 3 days | 7 days | 12 days |
Number of Revisions | 0 | 0 | 0 |
Install Script | - | - | - |
Test Script | - | - | - |
Task Automation | - | - | - |
Frequently asked questions
About Jonathan
Senior QA & Browser Automation Engineer | Playwright, Selenium, Python
Tel Aviv, Israel - 7:12 am local time
What I can help you with:
• Playwright / Selenium framework design or repair — built from scratch or rescued from flakiness
• Flaky-test stabilization — turn random failures into diagnosable ones with traces, screenshots, retries, and stable selectors
• Python automation & web scraping / data pipelines — reliable, logged, maintainable
• CI browser checks — tests that actually run green in CI, not just on your laptop
• Secondary: API/webhook integrations and n8n/Make/Zapier workflow automation
A recent build: a Playwright + MCP system that lets developers write tests far more easily — the kind of reliability tooling I specialize in. At Motorola I owned automated performance/benchmark testing for the LEX 700 (Android) and was the automation focal point for two worldwide teams.
How I work: I start with one narrow, paid first milestone and clear success criteria — one stabilized test path or one working automation, with logging, failure evidence, and handoff notes — then expand once you've seen it work. I'm newer to Upwork than
to automation engineering, so I keep the first step small and low-risk on purpose.
Send me the workflow or the failing test and I'll propose the smallest useful first milestone.
Recent proof: I published a Playwright flaky-test repair demo with a real before/after measurement - the flaky checkout suite passed 17/20 local runs, while the stabilized suite passed 20/20 with CI proof (see Portfolio).
Steps for completing your project
After purchasing the project, send requirements so Jonathan can start the project.
Delivery time starts when Jonathan receives requirements from you.
Jonathan works on your project following the steps below.
Revisions may occur after the delivery date.
Confirm source and fields
We confirm allowed access, target fields, sample inputs, and the first definition of done.
Build the narrow path
I implement the smallest reliable scraper path before expanding to volume or extra queries.