Senior Software Architect Needed: High-Frequency Inventory Mirroring Platform (Reverse Engineering & Fintech)
Budget: $20,000 – $50,000 USD
1. Executive Summary
We are a Tier-1 Auto Dealership located in Miami (Doral), aiming to disrupt the wholesale-to-retail market. We are seeking a highly qualified Lead Software Architect to develop an end-to-end "Inventory Mirror" platform.
The goal is to effectively connect wholesale inventory from Manheim, OVE, and Copart directly with our end clients through a membership model. The platform must incorporate a secure "Virtual Wallet" system to enable bidding and immediate purchasing.
This is a complex engineering challenge requiring expertise in stealth web automation, financial integrations, and scalable architecture.
2. The Core Technical Challenge (Crucial Constraints)
There is NO official API access. This platform must be built entirely using advanced web automation and reverse engineering techniques using legitimate dealer credentials that we will provide.
If you do not have significant experience bypassing enterprise-grade anti-bot systems in high-security environments (e.g., banking, auctions), please do not apply.
Key Technical Requirements:
• Advanced Anti-Bot Evasion: Manheim and OVE use protections like Akamai, Imperva, or PerimeterX. You must demonstrate techniques beyond simple proxy rotation, specifically managing browser fingerprinting consistency (Canvas, WebGL, AudioContext) to maintain high "trust scores" and avoid detection over long periods.
• MFA/2FA Automation & Persistence: The system must log in automatically and maintain persistent sessions 24/7. You must architect an authentication flow that handles MFA (e.g., TOTP automation) without manual intervention and without triggering security alerts for suspicious login behavior.
• Smart Synchronization Strategy (Hybrid Model): To avoid rate limits while ensuring accuracy, we require a hybrid sync strategy for the ~10,000 listings:
• General Browsing: A "Daily Sweep" or low-frequency update (e.g., data can be 15-30 mins old) for general inventory listing.
• Just-in-Time (JIT) Validation: Crucial real-time validation triggered only when a user attempts to bid or buy, ensuring the car is still available and the price is current right before execution.
3. Financial Layer & Business Logic
The "Virtual Wallet" & Stripe Connect:
Since we are not a licensed bank, we cannot hold funds indefinitely. We need a compliant flow using Stripe Connect (likely Custom or Express accounts).
• Workflow: Users must deposit funds (e.g., $5k-$10k) to unlock "Bid/Buy Now" buttons.
• Charge Mechanism: We require an implementation that handles immediate capture upon a win, or separate charges and transfers, ensuring compliance.
• Strict No-Cancellation Policy: Once a user wins a bid or clicks "Buy Now", funds are committed immediately as we are instantly liable to the auction house. There are NO automatic refunds on the platform. All disputes are handled manually offline.
Pricing & Fees Engine:
• Dynamic Pricing: The displayed price is calculated: Source Auction Price + Auction Fees + Logistics Cost + Our Variable Dealer Fee.
• Dealer Fees: Must be configurable via admin panel (tiered or percentage-based structures).
• Logistics: Integration with Central Dispatch for live rates (preferred) or a fallback distance-based rate table.
4. User Workflow & Governance
Onboarding & KYC (MVP Phase):
• Users must sign a Dealer Agreement and upload a Driver’s License.
• Admin Approval: The MVP requires a manual "Verify" toggle in the admin panel. A user cannot bid until manually approved by us. (Architecture must support future automated KYC integration like Stripe Identity in Phase 2).
Purchase Execution Logic:
• Offers & Bidding: Support for "Buy Now" and "Make Offer" (mirroring OVE functionality).
• Copart Integration: Public browsing sync + private execution using dealer credentials for bidding.
• Instant Documentation: Upon winning, the system must generate a digital Bill of Sale for immediate user signature.
Post-Sale Title & Tax Logic (Location-Based):
The system must differentiate between buyers based on location:
• Scenario A (Florida Residents): System calculates and adds FL Sales Tax. We handle registration and tags.
• Scenario B (Out-of-State): Generally tax-exempt. We mail the Title and Bill of Sale to the client for them to register locally.
5. Operational Requirements & Risk Mitigation (Non-Negotiable)
To ensure long-term stability and security, the following operational standards are required:
• "Sacrifice Account" Strategy: The architecture must separate high-traffic browsing from transaction execution. We will provide secondary "sacrifice" credentials for general scraping, reserving the main Dealer Account solely for final "Bid/Buy" execution to minimize ban risk.
• Emergency "Kill Switch": A prominent button in the Admin Dashboard (mobile-accessible) to immediately terminate all active bot threads and sever connections to auction sites in case of emergency.
• Source Code Ownership: We require a private GitHub/GitLab repository owned by us. Daily commits are required from Day 1. We will not accept a "code dump" at the end of the project; we need full visibility throughout development.
6. Submission Requirements
To be considered, your proposal must answer the following questions:
• What is your realistic estimate for the full end-to-end product (Backend scraper + DB + Frontend + Stripe Wallet + Admin Panel)? Are you proposing a fixed price for the entire scope or an MVP first?
• Describe your specific experience bypassing advanced bot protections like Akamai/Imperva without relying solely on rotating residential proxies. How do you manage browser fingerprint stability?
• Given the requirement for sticky IPs and persistent browser contexts, what is your rough estimate of the monthly operational infrastructure costs (servers, premium proxies, etc.) we should expect?
• Please confirm you agree to the "Daily Commit" requirement in our private repository.
We are a Tier-1 Auto Dealership located in Miami (Doral), aiming to disrupt the wholesale-to-retail market. We are seeking a highly qualified Lead Software Architect to develop an end-to-end "Inventory Mirror" platform.
The goal is to effectively connect wholesale inventory from Manheim, OVE, and Copart directly with our end clients through a membership model. The platform must incorporate a secure "Virtual Wallet" system to enable bidding and immediate purchasing.
This is a complex engineering challenge requiring expertise in stealth web automation, financial integrations, and scalable architecture.
2. The Core Technical Challenge (Crucial Constraints)
There is NO official API access. This platform must be built entirely using advanced web automation and reverse engineering techniques using legitimate dealer credentials that we will provide.
If you do not have significant experience bypassing enterprise-grade anti-bot systems in high-security environments (e.g., banking, auctions), please do not apply.
Key Technical Requirements:
• Advanced Anti-Bot Evasion: Manheim and OVE use protections like Akamai, Imperva, or PerimeterX. You must demonstrate techniques beyond simple proxy rotation, specifically managing browser fingerprinting consistency (Canvas, WebGL, AudioContext) to maintain high "trust scores" and avoid detection over long periods.
• MFA/2FA Automation & Persistence: The system must log in automatically and maintain persistent sessions 24/7. You must architect an authentication flow that handles MFA (e.g., TOTP automation) without manual intervention and without triggering security alerts for suspicious login behavior.
• Smart Synchronization Strategy (Hybrid Model): To avoid rate limits while ensuring accuracy, we require a hybrid sync strategy for the ~10,000 listings:
• General Browsing: A "Daily Sweep" or low-frequency update (e.g., data can be 15-30 mins old) for general inventory listing.
• Just-in-Time (JIT) Validation: Crucial real-time validation triggered only when a user attempts to bid or buy, ensuring the car is still available and the price is current right before execution.
3. Financial Layer & Business Logic
The "Virtual Wallet" & Stripe Connect:
Since we are not a licensed bank, we cannot hold funds indefinitely. We need a compliant flow using Stripe Connect (likely Custom or Express accounts).
• Workflow: Users must deposit funds (e.g., $5k-$10k) to unlock "Bid/Buy Now" buttons.
• Charge Mechanism: We require an implementation that handles immediate capture upon a win, or separate charges and transfers, ensuring compliance.
• Strict No-Cancellation Policy: Once a user wins a bid or clicks "Buy Now", funds are committed immediately as we are instantly liable to the auction house. There are NO automatic refunds on the platform. All disputes are handled manually offline.
Pricing & Fees Engine:
• Dynamic Pricing: The displayed price is calculated: Source Auction Price + Auction Fees + Logistics Cost + Our Variable Dealer Fee.
• Dealer Fees: Must be configurable via admin panel (tiered or percentage-based structures).
• Logistics: Integration with Central Dispatch for live rates (preferred) or a fallback distance-based rate table.
4. User Workflow & Governance
Onboarding & KYC (MVP Phase):
• Users must sign a Dealer Agreement and upload a Driver’s License.
• Admin Approval: The MVP requires a manual "Verify" toggle in the admin panel. A user cannot bid until manually approved by us. (Architecture must support future automated KYC integration like Stripe Identity in Phase 2).
Purchase Execution Logic:
• Offers & Bidding: Support for "Buy Now" and "Make Offer" (mirroring OVE functionality).
• Copart Integration: Public browsing sync + private execution using dealer credentials for bidding.
• Instant Documentation: Upon winning, the system must generate a digital Bill of Sale for immediate user signature.
Post-Sale Title & Tax Logic (Location-Based):
The system must differentiate between buyers based on location:
• Scenario A (Florida Residents): System calculates and adds FL Sales Tax. We handle registration and tags.
• Scenario B (Out-of-State): Generally tax-exempt. We mail the Title and Bill of Sale to the client for them to register locally.
5. Operational Requirements & Risk Mitigation (Non-Negotiable)
To ensure long-term stability and security, the following operational standards are required:
• "Sacrifice Account" Strategy: The architecture must separate high-traffic browsing from transaction execution. We will provide secondary "sacrifice" credentials for general scraping, reserving the main Dealer Account solely for final "Bid/Buy" execution to minimize ban risk.
• Emergency "Kill Switch": A prominent button in the Admin Dashboard (mobile-accessible) to immediately terminate all active bot threads and sever connections to auction sites in case of emergency.
• Source Code Ownership: We require a private GitHub/GitLab repository owned by us. Daily commits are required from Day 1. We will not accept a "code dump" at the end of the project; we need full visibility throughout development.
6. Submission Requirements
To be considered, your proposal must answer the following questions:
• What is your realistic estimate for the full end-to-end product (Backend scraper + DB + Frontend + Stripe Wallet + Admin Panel)? Are you proposing a fixed price for the entire scope or an MVP first?
• Describe your specific experience bypassing advanced bot protections like Akamai/Imperva without relying solely on rotating residential proxies. How do you manage browser fingerprint stability?
• Given the requirement for sticky IPs and persistent browser contexts, what is your rough estimate of the monthly operational infrastructure costs (servers, premium proxies, etc.) we should expect?
• Please confirm you agree to the "Daily Commit" requirement in our private repository.