About the role
- Order Management & Fulfillment — Millions of orders monthly, warehouse operations, inventory across locations
- Financial Systems — Automated accounting, bank reconciliation, revenue recognition for merchants processing millions in revenue
- Integrations — Shopify, Amazon, 3PLs, carriers, EDI — thousands of orders per minute flowing through our connectors
- Monday: Lead design review for a system that needs to handle 10x current scale. Whiteboard with the team, make the architecture call.
- Tuesday: Build a prototype. Benchmark against production data. Ship the first version.
- Wednesday: Call with a merchant. Walk through their operations — whether that's warehouse workflows, month-end close, or multi-channel selling. Translate their problems into solutions.
- Thursday: Code review for SDE-IIs. Guide them on edge cases, performance, and reliability patterns.
- Friday: Deploy to production. Monitor it handling real traffic. Start planning next week.
- Architecture decisions that affect millions of transactions
- System reliability and performance at scale
- Technical direction for your domain (with Product Lead)
- Mentoring engineers on your team
- Direct relationships with merchants using your systems
- 4-6 years building backend systems
- Expert Python skills — you've worked in large, mature codebases
- Deep PostgreSQL knowledge: query optimization, transactions, data integrity
- Experience with distributed systems: Celery, Redis, RabbitMQ, or similar
- Strong debugging skills across services and system boundaries
- Clear communication with both engineers and non-technical stakeholders
- You ship fast and take ownership
- E-commerce, logistics, or warehouse systems
- Financial systems, fintech, or accounting software
- Integration platforms, third-party APIs at scale
Hiring Process (We move fast).
- Initial interview — What you've built and owned
- Live coding — Real-time problem solving
- Interview loop — Architecture, system design, bar raiser
- Bootcamp — Even senior engineers start in Product Support to learn how merchants use Fulfil
- Leverage LLMs (OpenAI API, Claude API) to embed AI-driven capabilities into Fulfil’s ERP, powering natural language interfaces, intelligent automation, and merchant-facing insights (e.g., Fulfil x MCP integrations with Claude).
- Focus on AI for commerce operations — integrating models to solve real problems like order management, financial analysis, customer insights, and logistics optimisation.
- We are not a core ML/AI research company — we don’t train or fine-tune foundation models.
- We focus on integration and productisation of AI, not building new ML frameworks or developing custom model architectures.
Big Tech and VC-backed startups are 400-horsepower engines running at 25% efficiency. They have bloated teams, endless meetings, six months to ship a feature. At Fulfil, we’re a 200-horsepower engine running at 100%. We’re bootstrapped, profitable, and growing steadily. No permission layers. No “alignment meetings” about alignment meetings. Everyone ships everyday.The work: You’ll own meaningful problems with direct customer impact. Our customers run 24/7 operations across time zones, and when they’re launching on BFCM or scaling from $10M to $100M, they need us to move fast. That urgency flows downstream. This is high-intensity work with real consequences.What high-intensity actually means:
- Most weeks are 45-55 hours; peak seasons (BFCM, major launches) hit 60+
- Occasional off-hours calls with our distributed team or for customer launches
- Long days (10+ hours) aren’t uncommon
- The work doesn’t pause even if we try to protect your focus time
- Real autonomy over execution (we measure impact, not facetime)
- Ownership of problems that matter to real businesses
- Unlimited PTO we actually want you to use (we’d rather you rest than burn out)
- If you’ve ever felt like you’re capable of 10x more than your current environment allows you to output, that’s the gap between your potential and your actual impact. Fulfil eliminates that gap.
This isn’t for you if: you need a strict 40-hour boundary, prefer structured oversight, or want work to be a contained part of your life.