Senior Software Engineer | REMOTE

You will:

• Own the planning, design, implementation, and testing of mission-critical full-stack features.
• Gain deep understanding of the cannabis industry, its supply chain, and our customers' nuanced workflows.
• Work closely with product managers, designers, and customer support to shape and deliver projects end-to-end.
• Proactively communicate status updates to the rest of the organization.
• Balance speed and quality — leaning on AI tooling to move faster while keeping a high bar for what actually ships.

Features you might work on

• AI-native features — design how AI agents fit into real customer workflows: things like AI-assisted order and purchase intake, smart product matching, and systems that learn from user feedback over time.
• Distru Commerce — build out our growing commerce layer: storefronts, ordering, and the workflows that connect buyers and sellers across the supply chain.
• Manufacturing — extend production, assembly, and inventory functionality so operators can track product from raw inputs to finished goods.
• Distribution — sharpen the order, fulfillment, and logistics workflows that move product between businesses.
• Cultivation — improve the tools growers use day-to-day, including our mobile flows for work happening on the floor and in the field.
• Compliance — keep customers audit-ready with reporting, traceability, and integrations with state systems (e.g. Metrc) that the cannabis industry runs on.

Your Experience

• Comfort in modern tech stacks — we use React, TypeScript, Apollo, GraphQL, Elixir/Phoenix, and Postgres, but we believe great engineers can learn anything.
• Hands-on experience building with AI coding tools — and a point of view on where they help, where they don't, and how to keep quality high.
• Worked at early-stage startups.
• Fully owned and delivered features end-to-end, with quality and predictability.
• Write high-quality code with effective test coverage.
• Express complex, involved logic through clean, easy-to-understand code.
• Strong SQL/Postgres background — important for an ERP with deep data relationships.
• Define timelines and proactively communicate progress with the team and stakeholders.
• Raise concerns early about risky changes — data integrity, compliance, irreversible operations.
• Clear, concise verbal and written communication.
• Bonus: built complex SaaS products (logistics, supply chain, accounting, etc.).
• Bonus: experience in cannabis.
• Bonus: worked remotely, ideally on a distributed team.

Company Culture

• Obsess over customers and product.
• Cultivate positivity and show gratitude.
• Take ownership.
• Stay curious and keep learning.
• Communicate asynchronously and thoughtfully.
• Check your ego.
• Default to transparency.
 
See us in action: our company offsite in Mexico and our Eng + Product trip to Portugal.

Engineering Team & Process

• 1 team with 7 senior engineers.
• Half of the engineers are US-based, the other half are based in Europe.
• Projects are run by 1-3 engineers depending on project size.
• Engineers work closely with product managers and designers during the feature spec phase.
• Engineers write a high-level technical spec for mid-to-large projects and get feedback from peers.
• Engineers freely organize, plan, and execute the implementation phase.
• Most of our code is now written with AI tools. We expect engineers to direct them well — specify clearly, review critically, and own the result.
• Engineers continuously improve our AI harnesses — prompts, context, rules, and tooling — to get better, more reliable output over time.
• Engineers write thorough automated tests in the backend and perform manual QA in the frontend.
• Engineers open small, frequent Pull Requests and provide valuable, non-nit-picky code reviews.
• Daily deployments with CI/CD.
• ~10% of your time will be spent on meetings, ~90% will be uninterrupted focus time.
• No on-call team. The system is very stable, and issues are fixed during regular work hours.

Our Interview Process

1. Intro call — a non-technical conversation to get to know each other, walk through your background, and make sure there's a mutual fit.
2. Technical call — a deeper technical conversation with our Director of Engineering.
3. Take-home assignment — a practical exercise you complete on your own time.
4. Final call — a conversation with our CTO to align on vision, ways of working, and any remaining questions on both sides.