Senior Backend Architect Needed
Budget: $50 – $0 CAD
I’m leading the build-out of a custom enterprise-grade business application and now need an experienced backend architect to validate existing architecture.
The stack is not yet fixed; strong, production-level mastery of any modern backend environment—Node.js, Python, or Java—will be considered as long as you can justify how it serves scalability, resilience, and easy maintainability in an enterprise context. Expect to work with high-traffic data flows, role-based access control, and a modular service layout that can grow into multiple business domains over time.
What I need from you:
• A comprehensive architecture blueprint (micro-services vs. modular monolith, database sharding strategy, messaging, CI/CD pipeline choices).
• Clear API specifications and data-model documentation ready for hand-off to the development team.
• A migration and rollout plan that minimises downtime for our existing pilot users.
• Ongoing mentoring of mid-level developers through code reviews and best-practice guidelines.
Acceptance criteria: the delivered blueprint must be detailed enough for a separate engineering team to implement without back-and-forth clarification, include diagrams plus written reasoning for each major design decision, and demonstrate how non-functional needs (scalability, fault tolerance, observability, and security) are met.
If you’re the kind of architect who designs with both current requirements and future change in mind, I’d love to see how you’d approach this challenge.
The stack is not yet fixed; strong, production-level mastery of any modern backend environment—Node.js, Python, or Java—will be considered as long as you can justify how it serves scalability, resilience, and easy maintainability in an enterprise context. Expect to work with high-traffic data flows, role-based access control, and a modular service layout that can grow into multiple business domains over time.
What I need from you:
• A comprehensive architecture blueprint (micro-services vs. modular monolith, database sharding strategy, messaging, CI/CD pipeline choices).
• Clear API specifications and data-model documentation ready for hand-off to the development team.
• A migration and rollout plan that minimises downtime for our existing pilot users.
• Ongoing mentoring of mid-level developers through code reviews and best-practice guidelines.
Acceptance criteria: the delivered blueprint must be detailed enough for a separate engineering team to implement without back-and-forth clarification, include diagrams plus written reasoning for each major design decision, and demonstrate how non-functional needs (scalability, fault tolerance, observability, and security) are met.
If you’re the kind of architect who designs with both current requirements and future change in mind, I’d love to see how you’d approach this challenge.
Related categories:
NoSQL Couch & Mongo
Node.js
Backend Development
Database Design
API Development
Microservices
Architecture
CI/CD