B2B Lead Pipeline Build
Budget: $250 – $750 USD
I need a seasoned backend / data engineer to build the very first version of our ingestion pipeline for a paid B2B marketplace account. The marketplace lets us download buyer-lead CSV exports, and that single format will be your only upstream source for now. Every quarter the system should:
• Authenticate against our member portal
• Pull the newest CSV file (one or many if they arrive in batches)
• Parse and normalise just two groups of fields—contact information and company details—into a clean, documented schema
• Upsert the results into a landing table inside our existing warehouse (PostgreSQL; we can expose credentials in a .env or secrets manager)
Because my internal team will take over long-term operations, the project finishes once a working, repeatable pipeline is in place and fully handed off. I’m looking for production-grade code (Python is ideal, but you can propose another language), Docker or similar containerisation, and a simple scheduler—cron, Airflow, or a cloud-native alternative—that kicks off the quarterly run.
Deliverables expected at hand-off:
1. Source code repository with clear README and unit tests
2. Dockerfile (or equivalent) plus infrastructure scripts if you choose IaC
3. Sample config showing how to point the job at different environments
4. One short walkthrough call to be certain my team can operate it without you
Clean logs, meaningful error handling, and schema documentation are non-negotiable acceptance criteria. No need to worry about future real-time or hourly variations yet, but please keep the design flexible enough that we could tighten the schedule later without a full rewrite.
If this sounds straightforward to you, let’s talk timelines and any quick access details you need to get started.
• Authenticate against our member portal
• Pull the newest CSV file (one or many if they arrive in batches)
• Parse and normalise just two groups of fields—contact information and company details—into a clean, documented schema
• Upsert the results into a landing table inside our existing warehouse (PostgreSQL; we can expose credentials in a .env or secrets manager)
Because my internal team will take over long-term operations, the project finishes once a working, repeatable pipeline is in place and fully handed off. I’m looking for production-grade code (Python is ideal, but you can propose another language), Docker or similar containerisation, and a simple scheduler—cron, Airflow, or a cloud-native alternative—that kicks off the quarterly run.
Deliverables expected at hand-off:
1. Source code repository with clear README and unit tests
2. Dockerfile (or equivalent) plus infrastructure scripts if you choose IaC
3. Sample config showing how to point the job at different environments
4. One short walkthrough call to be certain my team can operate it without you
Clean logs, meaningful error handling, and schema documentation are non-negotiable acceptance criteria. No need to worry about future real-time or hourly variations yet, but please keep the design flexible enough that we could tighten the schedule later without a full rewrite.
If this sounds straightforward to you, let’s talk timelines and any quick access details you need to get started.
Related categories:
PHP
Python
Software Architecture
MySQL
PostgreSQL
Docker
Backend Development
Data Integration