Software Engineer, Merchant Tooling

Whatnot · Consumer · Los Angeles, CA · Engineering

Software Engineer on the Merchant Tooling team, focusing on building large-scale, reliable systems for managing seller merchandise and integrating with external e-commerce platforms, ERPs, and WMS. The role involves designing and implementing bi-directional data synchronization and supporting enterprise-level sellers.

What you'd actually do

  1. Delivering seamless, bi-directional data synchronization across marketplace, ecommerce, ERP, and other enterprise systems, ensuring accuracy, consistency, and low-latency data flow.
  2. Partnering closely with cross-functional stakeholders—including Product, Inventory, Operations, and external partners—to understand business needs, translate them into technical requirements, and drive aligned outcomes.
  3. Architecting and evolving enterprise-grade systems that remain intuitive for developers, easy to iterate on, and capable of supporting rapid product growth.
  4. Contributing to and accelerating the broader Inventory team roadmap, providing technical insight, proactive problem-solving, and hands-on implementation support.

Skills

Required

  • Python
  • Elixir
  • JavaScript
  • backend development
  • frontend development
  • SQL
  • dbt
  • building scalable systems
  • data synchronization
  • enterprise systems integration
  • product instincts
  • delivering features
  • ownership
  • fast-paced environment

Nice to have

  • Shopify
  • Channel Advisor
  • Magento
  • ecommerce SAAS products
  • domain driven design

What the JD emphasized

  • large-scale
  • highly reliable systems
  • largest and most complex customers
  • seamless, bi-directional data synchronization
  • low-latency data flow
  • enterprise-grade systems
  • rapid product growth
  • enterprise-level sellers
  • 5+ years of generalist software development experience
  • building scalable systems
  • work across the stack
  • delivering features
  • shipping products and features lightning-fast
  • take ownership of an ambiguous area
  • define and then drive impact
  • Scalability and data pipeline experience