Senior Data Science Engineer

Senior Data Science Engineer (Canada, EST, Remote)

MindBridge Analytics, 80 Aberdeen Street, Ottawa, Ontario, Canada

Job Description

Posted Monday, August 24, 2026 at 4:00 a.m.

MindBridge is the global leader in AI-powered financial risk intelligence. Our platform, MindBridge AI™ is enabling finance and audit professionals to build the AI-powered finance department of the future. With over 120 billion financial transactions analyzed with MindBridge’s AI, we set the standard for innovation, scalability, and customer satisfaction.

At MindBridge, we're driven by innovation and excellence, united as a team to revolutionize financial integrity. Here, your ideas matter, and your efforts make a meaningful impact. If you're passionate about using AI to drive positive change, MindBridge is the perfect fit. What distinguishes us is our unwavering commitment to our values: Innovation, Collaboration, and Integrity. These principles foster a vibrant workplace culture, where appreciation and a strong sense of community flourish.

Role Overview

We are looking for a Senior Data Science Engineer to provide applied data science expertise within our Success Engineering team, helping customers maximize the value of MindBridge’s control points and ensembles. You will configure and tune existing models, assess their application to customer data, investigate model behaviour and results, and translate complex findings into practical solutions. Working primarily post-launch, you will partner closely with Success Engineering, Product, Engineering, and AI/ML teams to solve complex customer needs within MindBridge’s existing capabilities.

What You Will Do

• Maintain deep working knowledge ofMindBridge'score detection methodologies: scoring logic, risk indicators, and how ensembles combine individual control points into a single output.
• Serve as the go-to technical resource within Success Engineering for questions about how a model or ensemble actually works.
• Maintain an active, ongoing working relationship with Product, Engineering, and AI/ML teams to stay current on model changes, known limitations, and upcoming capability shifts.
• Use that relationship to bring well-informed, technically grounded context back to Product/Engineering when a configurability gap is identified, a clear technical brief on what was requested, why it isn't currently supported, and what the customer's underlying value requirement needs, not just an administrative escalation.

Configurability boundaries & value mapping

• Develop andmaintainauthoritative understanding of how, why, and to what extentMindBridge'score models and ensembles can be configured, which parameters are flexible, which are structurally fixed, and the statistical or product reasoning behind each boundary.
• Map a customer's stated business value requirement onto the specific configuration options actually available, and explain in plain terms what is, and is not, achievable within the current product.

Post-launch feasibility & configuration advisory

• Evaluate customer requests to add,modify, or reconfigure a control point or ensemble, anddeterminewhether it isfeasiblewith existing product capability and the customer's available data.
• Define the specific data requirements: fields, quality, volume, structure — needed to support a proposed configuration.
• Recommend the configuration approach that best fits the customer's control objective within supported product capability.

Explainability & customer communication

• Translate model and ensemble behavior into language finance, audit, and compliance stakeholders can act on: what it measures, how it scores, and why a specific result occurred.
• Support customers who need to justify or defend MindBridge's outputs to their own internal or external stakeholders, a recurring requirement in audit-facing use cases.

When a control point or ensemble underperforms post-launch,determinewhether the cause is data quality, configuration, or a genuine product limitation, and recommend the correct fix.

Escalation & product boundary stewardship

• Distinguish clearly between a configuration question and a request that requires new productcapability, androute the latter through Product/Engineering governance.
• Do not build bespoke workarounds to cover product gaps; document and escalat them instead.

Enablement & knowledge capture

Convert recurring model and configuration questions into FAQs, decision guides, and training material for Success Engineers, Success Engineering Architects, and Delivery Services.

Bounded support to Delivery Services

• Act as an internal subject-matter-expert resource for Solutions Architects and Data Engineers specifically when an