Quince
Software Development Engineer III (Storefront)
About this role
Quince, a DTC fashion and essentials retailer founded in 2018, is seeking a Software Development Engineer III to lead storefront platform development. This senior role involves architecting and shipping high-impact features for a rapidly scaling e-commerce platform serving millions of customers.
What you'll do
- Design and implement scalable storefront features and infrastructure for the Quince e-commerce platform
- Lead technical decisions and mentor junior engineers on the storefront team
- Collaborate with product, design, and backend teams to deliver customer-facing experiences
- Own end-to-end delivery of complex features from architecture through production
- Optimize storefront performance and user experience through data-driven improvements
- Establish best practices and contribute to engineering culture and code quality
What they're looking for
- Full-stack web development (frontend frameworks, backend integration)
- E-commerce platform architecture and optimization
- System design and scalability planning
- Performance optimization and monitoring
- Leadership and mentoring experience
- Cross-functional collaboration
- Analytics and data-driven decision making
- Version control and CI/CD practices
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Quince
Quince builds a supply chain planning platform focused on forecasting, inventory management, and vendor relations for retail enterprises. The company is hiring Software Development Engineers at multiple levels to develop and lead this platform, with an emphasis on hands-on coding, AI integration, and cross-functional collaboration.
- Website
- quince.com
Likely interview questions
- Describe your experience building or scaling e-commerce storefronts. What were the key technical challenges and how did you solve them?
- Tell us about a time you led the architectural design of a significant feature. How did you make trade-offs between speed, scalability, and maintainability?