We automate drill-and-blast design and short-term planning for open-pit and underground mines. A surveyed bench goes in; the pattern a driller actually drills comes out - construction lines, hole positions, charge design, firing times. Real mines drill against our output every week. 8+ years building production software, with real ownership of systems that outlived you on a team ~ Depth in storage and data modeling. You write unusually well, about technical things.

Our process runs on design documents: a contract change ships as a document edit before it ships as code. The specifications you write are how three specialists stay composable, so this is a core engineering skill here rather than a soft one. Please send a writing sample - a design doc, RFC, architecture note, or technical post ~ Experience designing declarative or template-driven systems - rules engines, parametric models,



configuration or dataflow systems where users compose behavior instead of writing code ~ The judgment to hold an interface with a specialist more expert than you in their own field, including saying no to code that works but cannot ship Helps, but we don't require it CAD, GIS, CAE, or scientific-computing background - adjacent problem shapes PostGIS, or any responsible spatial-data experience TypeScript, React, three.js.

Part of this surfaces in a 3D web application Our pipeline design, phase contracts, and vocabulary are documented in unusual depth, and we budget three months to real competence A dedicated infrastructure engineer owns environments, deployment, and provisioning Python - FastAPI, NumPy, SciPy, Shapely, trimesh, OR-Tools, SCIP. Next.js, React, and three.js on the front end. Design docs before code, with a hard invariant: shipped code never diverges from an accepted design doc.

Three specialists, no layers between you and the mines running on your output, and unusually broad latitude over how the system is shaped. #

📌 Software Development Engineering, Team Lead (Montreal)
🏢 Watoga Technologies
📍 Montreal