Hiring brief scenarios
Build the ML Engineer brief around the work.
These scenarios connect location context to role responsibilities. Use them as prompts to verify with the employer, not as measures of Calgary demand, clients, or candidate supply.
Sourced energy and environment context
Assets, production, and emissions records: ML Engineer
The Calgary Plan describes a transition from the city's historic energy base and identifies renewable and net-zero energy as an investment area. Tie the sector scenario to a concrete outcome and data-generating process. Ask how the engineer would detect label leakage, sampling bias, missing history, and a metric that looks strong but fails the business use case. Energy work can connect physical assets, production, meters, forecasts, maintenance, contracts, markets, safety, emissions calculations, financial postings, and public reporting.
Evidence to request: Review a feature or training pipeline and ask the candidate to trace one record from source through validation, training, and evaluation. Name the assets and energy process, source measurements, calculation method, commercial boundary, maintenance window, reconciliation, reporting rule, and approval evidence.
Sourced health, science, and technology context
Research, digital products, and health systems: ML Engineer
The Calgary Plan names health, science, and technology among the sectors used to diversify and modernize the city's economy. Define the inference environment before screening. Batch scoring, low-latency APIs, edge deployment, and analyst-facing tools require different software design and operating evidence. These roles may serve research, clinical operations, regulated products, digital services, data platforms, or enterprise functions with different proof and access requirements.
Evidence to request: Use a production scenario with throughput, latency, and reliability limits. Require an API or batch design plus a test plan. Set the user and outcome, scientific or product stage, data authority, regulated boundary, validation need, deployment target, access model, and acceptance owner.
Sourced aerospace, agribusiness, and inland-port operations context
Production, supply, and distribution networks: ML Engineer
Calgary's municipal plan identifies aerospace and agribusiness as investment sectors and states that industrial land supports the city's inland-port role. Assign responsibility for drift, retraining, and model retirement. Candidates should explain the thresholds, review cadence, and human decision that follows an alert. These operations can join engineering or product records, crops or materials, equipment, quality, suppliers, plants, warehouses, rail and road movement, inventory, and financial settlement.
Evidence to request: Ask for a model degradation example and the evidence used to separate data change, code change, and user-behavior change. Trace the product or shipment from source through production, quality release, storage, transport, customer handoff, exception, accounting, and support ownership.