Senior Python / Browser Automation Developer Needed – New Registration Automation Project

IMPORTANT: Read the full description from A to Z before applying. I am looking for a senior Python / browser automation developer to build a new registration automation project from scratch. For this contract, the scope is registration only. There will be two additional parts later (prepare and bulk + $300 bonus), but they are NOT included in this first contract. If you successfully build and stabilize the registration system, I will hire you immediately afterward for the prepare and bulk parts as separate work. 1. Real Debugging – Find Why Accounts Get Blocked This is the most important part of the project. Manual registration is considerably more stable, while automated registration can result in accounts getting blocked afterward. I do not want random patches, assumptions, or repeated trial-and-error changes. I need the developer to perform real debugging and determine exactly where an automated workflow may differ from the normal supported browser workflow and why the accounts are getting blocked. You must inspect things such as: * browser workflow and page states * redirects and navigation * session/cookie state * timing-related problems * proxy/network consistency * SMS stage * unnecessary or duplicated actions * differences between a successful manual registration and the automated registration The objective is to identify the actual root cause of the account blocking and build the registration workflow correctly from the beginning. I am not looking for attempts to bypass provider security controls. The automation should follow the provider’s normal supported registration flow correctly and consistently. 2. Study and Correctly Integrate the SMS API Before implementing the SMS part, you must properly understand how the SMS API works. You should review: * requesting a phone number * activation/session IDs * checking SMS status * retrieving verification codes * timeouts * API errors * number cancellation/release where supported * retry behavior * per-worker SMS state A common issue is that sometimes the SMS does not arrive. The script must handle this cleanly. Where the registration flow legitimately allows another number to be entered, the script should preserve the current browser/session state rather than unnecessarily restarting everything. For example: * first number does not receive SMS * request another number * retry the SMS stage * keep the same valid registration session * use a limited number of attempts * if all attempts fail, terminate that worker cleanly and log the exact reason 3. Browser-Based Registration Only – No Direct Request-Based Registration The registration workflow must be implemented as real browser automation, not as a direct HTTP/API request-based registration flow. The developer may use Playwright, Patchright, or another appropriate browser automation framework based on their professional judgment. I am not forcing a specific library. What matters is that the developer is experienced enough to understand the complete browser workflow, session lifecycle, page states, network behavior, and the code they are implementing. The registration process should be performed through the normal browser interface and supported website flow, including: * real page navigation * visible form interaction * keyboard/mouse/browser actions where appropriate * proper page-state detection * redirects * session/cookie handling * SMS verification flow * dynamic elements and loading states * correct error and timeout handling I do not want the registration process implemented through direct backend requests or undocumented API calls simply to make it faster. The developer should choose the technically appropriate browser-automation approach and be able to explain and debug every important part of the implementation. This is not a project for beginners. If you are still learning Python, Playwright, Patchright, or browser automation, please do not apply. I need an experienced automation engineer who knows exactly what they are doing, can manually debug the registration flow, and can build a clean and stable browser-based implementation from scratch. 4. Manual Coding Only – No AI-Generated Code This requirement is non-negotiable. If you are planning to build this project using AI-generated code, do not apply. I am telling you this clearly before the contract starts: the developer must code the project manually and must fully understand every part of the implementation. I am not looking for someone who copies code from AI tools and then tests random patches until something works. If I review the delivered script and find that it has been primarily generated by AI, or that the developer cannot clearly explain, debug, and maintain the code they delivered, I will cancel the contract. I need a real experienced developer who can: * write the code manually * design the architecture themselves * understand every important part of the code * debug problems directly * explain the root cause of failures * inspect browser behavior and logs * test the implementation themselves before delivery If you cannot work this way, please do not apply. 5. Parallel Registration & VPS Capacity The registration system must support parallel execution. The number of simultaneous workers should be configurable based on the available VPS/server resources. The developer must ensure proper isolation between workers, including: * browser/session state * cookies/storage * registration state * SMS activation state * proxy/network assignment * logs/results * failures/retries One failed worker must not affect the others. The developer should test progressively increasing concurrency and determine the highest stable worker count supported by the VPS configuration. I care about speed, but stability comes first. A system that runs more workers but produces a high failure rate is not acceptable. 6. Failure Handling Failures must not simply appear as generic failed results. I need clear failure classification so we can understand exactly what happened. Examples: * proxy/network failure * SMS timeout * SMS API failure * browser/page failure * registration rejection * unexpected redirect * session failure * timeout * script/internal error Every failed worker should record the exact stage and reason. 7. Testing & Acceptance Requirement I will not test unfinished versions, intermediate builds, partial implementations, or trial-and-error patches. The developer must complete the registration script and perform their own testing first. Before asking me to test anything, you must: * complete the registration implementation * successfully run real registrations yourself * verify that the registrations complete correctly * monitor the successfully registered accounts afterward * verify that the accounts remain alive and usable for more than 5 hours after registration * investigate and fix any blocking that happens during this validation period * test multiple registrations * test parallel execution * verify failure handling * provide clear evidence of the results I do not want messages such as: “Please test this version.” “Try this patch.” “Run this and tell me what happens.” That is not how I want this project handled. You are responsible for debugging and validating your own implementation before involving me in testing. Once you have successfully created accounts with your script and verified that they remain alive for more than 5 hours, then contact me and I will perform my own final testing. Until that point, I will not be used as the QA tester for unfinished versions. 8. Communication Requirement Good communication is very important for this project. I need a developer who communicates clearly, consistently, and professionally throughout the work. You should keep me informed when: * a technical problem is discovered * an important decision needs to be made * something is blocking progress * a meaningful test has been completed * a major implementation change has been made * there is any risk to the expected delivery I do not want long periods without updates or vague answers. I need someone who can explain technical problems clearly and keep me informed of real progress throughout the project. Who Should Apply Please apply only if you already have strong experience with: * Python * Playwright / Patchright * browser automation * asynchronous/concurrent systems * APIs * SMS API integrations * Linux/VPS environments * debugging complex browser workflows * proxy/network troubleshooting * production automation reliability When applying, briefly explain your real experience with similar browser automation systems and how you normally debug differences between a manual workflow and an automated one. Do not send a generic proposal.