Responsibilities
- Build and ship web application features end-to-end: backend, API layer, and frontend, without handing off to specialists
- Own what you build in production: monitoring, debugging, and fixing issues when they surface
- Design and maintain REST and GraphQL APIs across a platform with 600+ endpoints
- Integrate LLM-powered features (OpenAI, Anthropic) into merchant workflows: order management, financial analysis, logistics
- Build and maintain integrations with Shopify, Amazon, FedEx, DHL, and other commerce platforms
- Refactor and modernize legacy systems while keeping pace with new feature delivery
- Participate in code reviews and architecture discussions: raise the bar and expect the same in return
Requirements
- 3 to 5 years of Python engineering experience building production systems
- Proven experience owning web applications end to end - not just backend services, but the full product surface, including UI and API contracts
- You have primarily built user-facing web applications or product workflows, not only internal tools, ETL pipelines, infrastructure, or isolated backend services
- Solid fundamentals with ORMs (SQLAlchemy or Django ORM), PostgreSQL, and relational data modelling
- Experience with distributed systems: Celery, Redis, RabbitMQ, or similar background processing tools
- Comfortable writing automated tests with pytest and working collaboratively in Git
- A track record of seeing projects through from design to deployment to ongoing support. Not just closing tickets
- You have worked in environments where engineers are expected to clarify the problem, make tradeoffs, and ship without heavy product or project management layers
Nice to Have
- Domain experience in commerce, logistics, or fintech, order management, inventory, payments, reconciliation
- Hands-on LLM integration in production features, not just personal projects
- Familiarity with Google Cloud, Heroku, or similar platforms
Benefits
- Unlimited PTO, we actually want you to use
Additional Information
- Location: Toronto, ON (in-office during onboarding; hybrid 3 days/week in office after)
- This is not a clock-in, clock-out engineering environment. Most weeks should be sustainable, but when merchant-impacting issues arise, we expect engineers to stay engaged, communicate clearly, and help drive the issue to resolution.
- You’ll thrive here if you value direct, specific feedback, are comfortable discussing tradeoffs openly in Slack and code reviews, and can separate critique of the work from critique of the person.
