Enterprise Automation Platform – Multi-DMS Handwritten Note System
Budget: $2 – $8 USD
We are building an enterprise-grade, multi-tenant automation platform that integrates dealership management systems (DMS) with an in-house handwriting print system to generate customized handwritten notes for automotive dealerships. The platform will start with our own dealership group but must be architected from day one for reliability, scalability, and future multi-tenant / whitelabel use.
You will help design and build a backend platform that can:
Integrate with multiple DMS platforms via APIs (or file-based exports where required)
Normalize events/data from different DMS into a unified internal model
Apply per-store / per-tenant business rules (who gets which note, when, and with what template content)
Orchestrate job creation and routing to a handwriting print system / print queue
Maintain full audit trails of all jobs (created, queued, printed, delivered, errors, retries)
Support future expansion to multiple dealerships (50+ rooftops) with different rules and volumes
Key responsibilities:
Design a robust backend architecture suitable for multi-tenant use (initially 1 store, but expanding to many)
Implement APIs and/or connectors to ingest data from one or more DMS systems
Build a rules engine or configurable workflow layer for per-store logic
Implement job queuing and routing to the handwriting print system
Set up data models and persistence (e.g., MySQL or similar relational DB) with clear tenant/store separation
Implement basic admin/ops views or endpoints for monitoring jobs, errors, and throughput
Collaborate on defining phases: initial pilot (single store), then scaling to more stores and higher volumes
Tech stack (preferred):
Backend: Python, PHP, or JavaScript/TypeScript (Node.js)
Database: MySQL (or PostgreSQL)
Strong experience with web development and API integrations
Experience with queues, background jobs, and scalable backend architectures
Nice to have:
Experience with automotive dealership systems or other DMS/ERP-type integrations
Experience building multi-tenant SaaS platforms
Familiarity with AWS or similar cloud platforms (ECS/Fargate, EC2, etc.)
Experience implementing RBAC and admin dashboards
What we are looking for:
Someone who has built production-grade backend systems, ideally multi-tenant or high-volume integrations
Strong communicator who can document architecture and decisions
Comfortable starting from a clear business outcome and helping refine technical scope and milestones
Available 30+ hours/week for 3–6 months
When you apply, please answer:
Describe one backend or integration project you built that needed to scale across many clients/tenants.
Which tech stack (Python, PHP, or Node.js + MySQL) would you choose for this project and why?
How would you approach tenant separation and scaling from 1 store to 50+ stores?
Please start your proposal with the word “DEALERSHIP” so I know you read the description.
You will help design and build a backend platform that can:
Integrate with multiple DMS platforms via APIs (or file-based exports where required)
Normalize events/data from different DMS into a unified internal model
Apply per-store / per-tenant business rules (who gets which note, when, and with what template content)
Orchestrate job creation and routing to a handwriting print system / print queue
Maintain full audit trails of all jobs (created, queued, printed, delivered, errors, retries)
Support future expansion to multiple dealerships (50+ rooftops) with different rules and volumes
Key responsibilities:
Design a robust backend architecture suitable for multi-tenant use (initially 1 store, but expanding to many)
Implement APIs and/or connectors to ingest data from one or more DMS systems
Build a rules engine or configurable workflow layer for per-store logic
Implement job queuing and routing to the handwriting print system
Set up data models and persistence (e.g., MySQL or similar relational DB) with clear tenant/store separation
Implement basic admin/ops views or endpoints for monitoring jobs, errors, and throughput
Collaborate on defining phases: initial pilot (single store), then scaling to more stores and higher volumes
Tech stack (preferred):
Backend: Python, PHP, or JavaScript/TypeScript (Node.js)
Database: MySQL (or PostgreSQL)
Strong experience with web development and API integrations
Experience with queues, background jobs, and scalable backend architectures
Nice to have:
Experience with automotive dealership systems or other DMS/ERP-type integrations
Experience building multi-tenant SaaS platforms
Familiarity with AWS or similar cloud platforms (ECS/Fargate, EC2, etc.)
Experience implementing RBAC and admin dashboards
What we are looking for:
Someone who has built production-grade backend systems, ideally multi-tenant or high-volume integrations
Strong communicator who can document architecture and decisions
Comfortable starting from a clear business outcome and helping refine technical scope and milestones
Available 30+ hours/week for 3–6 months
When you apply, please answer:
Describe one backend or integration project you built that needed to scale across many clients/tenants.
Which tech stack (Python, PHP, or Node.js + MySQL) would you choose for this project and why?
How would you approach tenant separation and scaling from 1 store to 50+ stores?
Please start your proposal with the word “DEALERSHIP” so I know you read the description.