DemandLabs is pre-launch. We are not posting positions yet, and we would rather say that plainly than run a job board with nothing behind it. When roles open, they will be listed here first.
There is no pipeline of unlisted roles behind this page and no talent-network form collecting details for later. When a role opens it will appear here with a real description, a real scope and a named person on the other end of it.
[email protected] →Not a culture deck - just the working conditions, so you can judge whether the email is worth writing.
The person who designs a surface builds it, ships it, and answers for it in production. There is no hand-off queue between engineering and delivery.
Supply chain is the hard part. Forecasting, constraint solving, allocation, cost to serve - the interesting problems are in the domain, not in the build tooling.
Decisions get written down with the reasoning attached. It is the same standard we hold the product to, and it is what makes a distributed group workable.
Work is validated against client data and live planning cycles, not a demo dataset. That is demanding, and it is the only way to know something actually works.
The disciplines below are where a speculative note is most likely to land. None of them are open postings - they are simply the areas we are building in.
Write to [email protected] with what you have built and what you would want to work on here. Links to work beat a CV, and a short note beats a long one.
Be concrete about the problem you solved and what was hard about it. If you have planning, forecasting, optimisation or enterprise-integration scars, lead with those - they are rare and we read those notes first.
Full-stack product work on the planning surfaces, plus the modelling and data plumbing underneath them.
Forecasting, causal modelling and constraint solving that has to survive contact with messy enterprise history.
Supply chain practitioners who can sit with a planning team, model their reality, and get a first cycle live.