Find your next opportunity
Browse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert rolesBrowse expert rolesBrowse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert roles10610 openings
2129-2136 of 10610
MindBridge Analytics Inc.
Free to start · No card · 5 credits the moment you sign up
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.
Maintain deep working knowledge of MindBridge's core 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 and maintain authoritative understanding of how, why, and to what extent MindBridge's core 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, and determine whether it is feasible with 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.
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, determine whether 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 product capability, and route the latter through Product/Engineering governance. Do not build bespoke workarounds to cover product gaps; document and escalate them instead.
Convert recurring model and configuration questions into FAQs, decision guides, and training material for Success Engineers, Success Engineering Architects, and Delivery Services.
Act as an internal subject-matter-expert resource for Solutions Architects and Data Engineers specifically when an implementation calls for a control point or ensemble configuration that has not been built or validated before; not for routine, previously-validated feasibility questions, which remain owned by Delivery Services. This is consultative, time-boxed input at the point a novel configuration is being designed, not ownership of the Technical Requirements Blueprint or any implementation deliverable, which remains with Delivery Services throughout the technical blueprint phase.
5+ years of applied experience in data science, analytics engineering, or a closely related technical discipline, ideally supporting enterprise software customers after implementation. Working knowledge of the statistical and machine learning techniques used in anomaly and risk detection — scoring models, ensemble/combination methods, outlier detection — sufficient to reason about why a model behaves as it does, not only what it outputs; building such models from scratch is not required. Strong SQL, Python and data literacy; able to independently investigate whether a data set can support a proposed control point or ensemble configuration. Demonstrated ability to translate technical model behavior into terms a non-technical, often finance, audit, or compliance stakeholder can act on. Direct experience working with enterprise customers on technical questions, in a support, technical account management, implementation, or applied customer-facing data science capacity. Credible enough with model internals and engineering constraints to partner directly with Engineering and AI/ML teams as a peer. This role sits between the customer-facing and product-technical sides, not solely on the customer-facing side. Comfortable operating inside a defined product boundary: recommending within existing capability and escalating clearly rather than building around gaps.
Experience in audit, internal controls, financial risk, or fraud analytics. Familiarity with explainability and interpretability expectations in regulated or audit-facing environments. Experience producing enablement content i.e. FAQs, playbooks, training materials, for internal technical teams. Prior experience in a dedicated post-implementation optimization function, as distinct from initial delivery. Background in ML engineering, applied statistics, or a related technical field with direct exposure to production model constraints; not solely academic or research modeling experience.
Fulfill requirements necessary to obtain full background check.
Pay Range The expected base salary range for this position is to $130,000 to $155,000 and may be eligible for bonus awards. The determination of an applicant’s base salary within this range is based on the individual’s location, skills, experience and competencies, and unique qualifications.
Originally posted on Himalayas
Start with a role or skill you want to use in your next job. Use the location and role filters to narrow the results, then open a listing to review the description. A title alone rarely explains the level of responsibility, working arrangement, or experience a team needs. Compare those details before deciding which opportunities deserve a tailored application.
Employers use different titles for similar work. If an exact phrase produces no results, try a shorter title, a core skill, or an alternative name for the role. Remove one filter at a time to understand which requirement is narrowing your search. A broader search can reveal suitable work without asking you to change your actual qualifications.
For each promising listing, read the responsibilities and separate essential requirements from preferences. Note the location, schedule, employment type, and compensation when provided. Missing details are questions to confirm with the employer. A remote opening may still require a particular country, work authorization, or time-zone overlap, so check the full posting before treating it as a location-independent opportunity.
Choose a few examples that demonstrate the skills this employer names. Explain your contribution and its outcome, using accurate numbers where available. Put the most relevant experience first and keep your resume easy to scan. Avoid adding technologies, qualifications, or achievements simply because they appear in a description. Your application should make your existing strengths easier to understand.
Follow the employer’s instructions for resumes, cover letters, work samples, and screening questions. Review the exported file before submitting it: confirm that contact details are correct, text can be selected, and links reach the intended pages. A resume check can help you spot unclear writing before you apply. Its feedback is advisory and does not predict a hiring decision.
Listings are collected from external sources and may change after they appear here. The employer or recruiting destination controls whether applications are open. If an original link is unavailable, check the company’s careers page for the title or move to another opening. An employer website link is a place to check current vacancies, rather than confirmation that a particular job is still accepting applications.
Keep a simple record of the company, role, job reference, application date, and documents you sent. Record any follow-up instructions and the next action you plan to take. This makes it easier to prepare for interviews, compare opportunities, and avoid applying repeatedly to the same opening through different boards. Review your shortlist as employers update their listings and prioritize opportunities with clear requirements that match the work you want to do.