OEM Auto Parts Research Tool Developer

I need a senior full-stack developer to build a private OEM auto parts research application for my automotive recycling business. The software must allow me to enter ONLY a vehicle's Year, Make, and Model, press Search once, and automatically research every OEM part category for that vehicle. I do not want to manually select engines, transmissions, trim levels, drivetrains, or categories before searching. The result must be a complete junkyard pull list that includes every worthwhile OEM part I could remove and sell. Each part should include: Before I hire anyone, I will ask you to demonstrate how you would solve this exact workflow using a real vehicle. I am looking for someone who understands the end-user experience, not just the underlying technology. Active listing count Sold listing count Average sold price Sell-through rate Expandable links to the actual eBay sold and active listings The software must intelligently separate different OEM parts when necessary (for example: ABS Module, BCM, ECU, Climate Control Module, SRS Module), but it should not create dozens of unnecessary subgroups that slow down decision-making. For example, I want one Radio category, not 40 different radio categories. I can inspect the listings myself after opening them. The software must automatically exclude categories I do not sell, including engines, transmissions, differentials, complete doors, complete bumpers, and tailgates. This is NOT a proof of concept. I need a production-ready application that I can operate myself every day in junkyards without contacting the developer to perform searches. Experience with eBay APIs, web scraping, large-scale data processing, and production software is required. Communication requirements I need a developer who actively communicates during the workday. I expect prompt replies while development is in progress, multiple check-ins when questions arise, and progress updates every 1–2 days. IMPORTANT To confirm you actually read this job posting, start your proposal with: OEM READY Also answer these three questions: After I type 2008 Honda Accord and press Search, exactly what will I see? How will your system automatically search every supported OEM category without me selecting categories manually? Describe a similar application you have personally built.