phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

E-commerce Backend Architect - Node.js Expert

  • Posted:
  • Proposals: 46
  • Remote
  • #4506651
  • Expired
Óscar P.Safeer H.Anne O.Cornelius O.Synergic Softek Solutions Pvt. Ltd. + 41 others have already sent a proposal.
  • 9

Description

Experience Level: Expert
Backend Architect / Senior Node.js Engineer – E-commerce Platform

We are building a scalable e-commerce backend and are looking for a Backend Architect / Senior Engineer (Node.js) to design the system architecture and lead the backend foundation.
This is a long-term project starting with an MVP, but the focus is on building a clean, scalable, production-ready system from the beginning.

--What You Will Do
Design backend architecture for an e-commerce platform
Define database structure (PostgreSQL)
Design authentication system (JWT, roles, password reset)
Architect product, cart, checkout, and order systems
Design Stripe payment integration flow
Define API structure and backend standards

--MVP Scope
Authentication system
Product catalog (categories, variants, search/filter)
Cart & wishlist
Stripe checkout
Order management
Basic admin APIs

--Tech Stack
Node.js (NestJS preferred), TypeScript, PostgreSQL, Prisma, Redis, Stripe

--Requirements
Strong experience in Node.js backend development
Experience designing scalable system architecture
Experience with PostgreSQL and API design
Experience with Stripe or payment systems
Background in e-commerce or marketplace systems is a plus

--Please include in your proposal:
Relevant experience in backend architecture
Similar systems you have built
Your approach to designing this kind of system
Estimated timeline for MVP design and/or development

--Note
We are looking for someone who can help design the foundation of a scalable e-commerce platform, not just build endpoints.

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • Satwinder S.

    Hi Rowan, Do you have an existing frontend or admin panel that the backend needs to integrate with, or will the frontend be built later?

  • Yasir Ali M.

    Would you like the backend to be designed as a single store system for the MVP, or should it be planned from day one to support multi vendor features like vendor dashboards, commissions, and fulfilment workflows later on?

  • CYTNHIA W.

    Before finalising the architecture, I'd like to understand your long-term vision: do you expect this platform to evolve into a true multi-vendor marketplace with separate vendor dashboards, commissions, and fulfilment workflows, or will it remain a single-store e-commerce platform for the foreseeable future? That decision has a significant impact on how the database schema, order lifecycle, permissions model, and service boundaries should be designed from the outset.