ZipRecruiter

Log In

2

Non Customer Facing Remote Jobs in Quebec (NOW HIRING)

Omm IT Solutions

It is a 100% Remote position in Canada. \n * Candidates Preferred from EST\/CST Time Zone. \n JOB ... Fabric for customer\-facing and revenue\-impacting digital products hosted in Azure. This is a ...

Danaher

Country Manager

Montreal, QC · On-site +1

CA$150K - CA$175K/yr

Works across all customers facing field personnel to implement Team Selling. * Develop specific ... We recognize the benefits of flexible, remote working arrangements for eligible roles and are ...

Canonical

Software Engineer - App Stores

Montreal, QC · On-site +1

Our customers include the world's leading public cloud and silicon providers, and industry leaders ... You have demonstrated professional proficiency in developing public-facing APIs and web ...

Devoted Studios

Gameplay Engineer

Montreal, QC · Remote

Description Devoted Studios is a globally remote game development company specializing in Co ... Write code that is reviewable: clean, commented where logic is non-obvious, consistent with project ...

Inizio Engage

CA$90K - CA$100K/yr

... clients engaging customers, patients, and/or healthcare professionals, in a robust clinical ... non-telecommunication duties as needed * Adhere to all company policies and Standard Operating ...

Go RH

Sales Development Representative (SDR)

Quebec, QC · On-site +1

CA$70K - CA$75K/yr

Location: Montreal, Quebec City or surrounding areas (Remote/Hybrid) Who We Are At Can-Ex ... sales, customer service, telemarketing, recruitment, inside sales, or a client-facing role is ...

previous pagenext page

Showing results 21-40

All JobsNon Customer Facing JobsNon Customer Facing Remote JobsNon Customer Facing Remote Jobs in Quebec

Non Customer Facing Remote information

What are some common challenges faced in non customer facing remote roles, and how can they be addressed?

A key challenge in non-customer facing remote roles is maintaining effective communication and collaboration with team members, as there is less direct interaction compared to in-office settings. It can also be difficult to stay motivated and organized without regular supervision or immediate feedback. To address these challenges, it's important to establish clear communication channels, set regular check-ins or team meetings, and utilize project management tools to track progress. Prioritizing self-discipline and proactively seeking clarification when needed can also help remote employees thrive in these roles.

What is the difference between Non Customer Facing Remote vs Customer Service Representative?

AspectNon Customer Facing RemoteCustomer Service Representative
Work EnvironmentRemote, no direct customer interactionRemote or in-office, direct customer interaction
Required SkillsTechnical skills, data analysis, documentationCommunication, problem-solving, empathy
Common CertificationsNone specific, depending on industryCustomer service certifications often preferred
Industry UsageIT, finance, administrative rolesRetail, tech support, hospitality

Non Customer Facing Remote roles focus on tasks like data management and technical support without direct customer contact, while Customer Service Representatives handle customer inquiries and support. Both can be remote, but their skills and interactions differ significantly.

What are the key skills and qualifications needed to thrive in a non customer facing remote role, and why are they important?

To thrive in a non-customer-facing remote role, you typically need strong self-management skills, proficiency in your field (such as data entry, research, or software development), and relevant educational or experience-based qualifications. Familiarity with collaboration tools like Slack, project management systems such as Trello or Asana, and remote communication platforms is often essential. Excellent organizational skills, reliability, and proactive communication are standout soft skills in this context. These abilities ensure that tasks are completed efficiently and accurately, supporting team goals without direct supervision.

What is a non customer facing remote job?

Non customer facing remote jobs are positions that allow employees to work from home or another remote location without directly interacting with customers. These roles typically involve internal tasks such as data analysis, software development, content writing, accounting, or IT support. Employees in these jobs communicate mainly with coworkers or management rather than clients or the public, making them ideal for those who prefer behind-the-scenes work. The demand for such remote roles has increased with the rise of digital workplaces and flexible work arrangements.

What are popular job titles related to Non Customer Facing Remote jobs in Quebec?

For Non Customer Facing Remote jobs in Quebec, the most frequently searched job titles are:

What job categories do people searching Non Customer Facing Remote jobs in Quebec look for?

The top searched job categories for Non Customer Facing Remote jobs in Quebec are:

Non Customer Facing Remote jobs near you
Infographic showing various Non Customer Facing Remote job openings in Quebec as of August 2026, with employment types broken down into 80% Full Time, 17% Part Time, and 3% Contract. Highlights an 92% Physical, 2% Hybrid, and 6% Remote job distribution.

Consulting Senior Data Architect (Microsoft Fabric Focus)

Omm IT Solutions

Remote

Contractor

Re-posted 13 days ago

Job description

\n <\/head>\n \n

PLEASE NOTE:<\/b><\/span><\/span><\/u> <\/b><\/span><\/span>
<\/b><\/span><\/p>\n

    \n
  • It is a 100% Remote position in Canada.<\/b><\/span><\/span>
    <\/b><\/span><\/span><\/li>\n
  • Candidates Preferred from EST\/CST Time Zone.<\/b><\/span><\/span>
    <\/b><\/span><\/span><\/li>\n <\/ul>

    JOB SUMMARY:<\/b><\/span><\/span><\/u>
    <\/span><\/span><\/p>\n

    \n We are seeking a Consulting Senior Data Architect with deep, production\-grade Microsoft Fabric experience to accelerate our active rollout of Fabric for customer\-facing and revenue\-impacting digital products hosted in Azure. This is a hands\-on role responsible for designing and building Fabric artifacts (pipelines, lakehouses, eventstream\/real\-time patterns), defining data architecture standards (conceptual\/logical\/physical), and implementing governance and security guardrails that scale across multiple product teams.<\/span><\/span>
    \n <\/div>\n
    \n
    \n <\/div>\n
    \n Key Responsibilities:<\/b><\/span><\/u><\/span>
    \n <\/div>

    Microsoft Fabric Enablement (Hands\-on Delivery + Standardization)<\/b><\/span><\/span>
    <\/span><\/p>\n

      \n
    • Architect and implement Fabric solutions for data engineering (Spark), Data Factory pipelines<\/b>, and real\-time analytics \/ Event streams <\/b>aligned to digital product needs.<\/span><\/span>
      <\/span><\/li>\n
    • Build and standardize Fabric patterns for ingestion, transformation, and serving across workloads including operational analytics, near\-real\-time, batch, and data science\/ML.<\/b><\/span><\/span>
      <\/span><\/li>\n
    • Create repeatable reference implementations for common digital product scenarios (IoT telemetry, time series, transactional + event fusion, documents, geospatial).<\/span><\/span>
      <\/span><\/li>\n <\/ul>

      Unified Data Platform Architecture (Target State + Roadmap)<\/b><\/span><\/span>
      <\/span><\/p>\n

        \n
      • Produce and maintain the target\-state architecture<\/b> for Fabric\-based data platform capabilities.<\/span><\/span>
        <\/span><\/li>\n
      • Define domain\-oriented data product patterns<\/b> including how shared\/enterprise datasets are curated and reused.<\/span><\/span>
        <\/span><\/li>\n
      • Establish architectural boundaries and integration guidance for shared datasets vs. product\-owned datasets.<\/span><\/span>
        <\/span><\/li>\n <\/ul>

        Data Modeling Standards (Conceptual \/ Logical \/ Physical)<\/b><\/span><\/span>
        <\/span><\/p>\n

          \n
        • Define and enforce data modeling standards and templates appropriate to Fabric Lakehouse\/Warehouse patterns and product analytics needs.<\/span><\/span>
          <\/span><\/li>\n
        • Provide modeling guidance for high\-variance data types (telemetry, geospatial, documents) and hybrid operational\-analytics use cases.<\/span><\/span>
          <\/span><\/li>\n
        • Define standards for schema evolution, versioning, and contract\-first data interfaces (where applicable).<\/span><\/span>
          <\/span><\/li>\n <\/ul>

          Governance, Security, and Compliance by Design<\/b><\/span><\/span>
          <\/span><\/p>\n

            \n
          • Design and implement a governance model covering classification, retention, lineage,<\/b> and auditability.<\/span><\/span>
            <\/span><\/li>\n
          • Ensure compliance guardrails are built into delivery patterns and operational processes to meet GDPR, ISO 27001, and data residency<\/b> requirements.<\/span><\/span>
            <\/span><\/li>\n
          • Define and enforce Fabric access controls using Entra ID, RBAC,<\/b> and workspace\-level controls<\/b> (including guidance for separation of duties and least privilege).<\/span><\/span>
            <\/span><\/li>\n <\/ul>

            CI\/CD + Infrastructure as Code (IaC) for Fabric<\/b><\/span><\/span>
            <\/span><\/p>\n

              \n
            • Define and implement a CI\/CD approach for Fabric artifacts<\/b> as the enterprise source of truth.<\/span><\/span>
              <\/span><\/li>\n
            • Establish release patterns for Fabric changes (promotion strategy, environment separation, approvals, and quality gates) aligned to platform standards.<\/span><\/span>
              <\/span><\/li>\n
            • Manage Fabric\-related platform configuration using Terraform<\/b> as the IaC approach (including reusable modules\/patterns).<\/span><\/span>
              <\/span><\/li>\n
            • Create golden path templates and guidance that product teams can adopt with minimal friction.<\/span><\/span>
              <\/span><\/li>\n <\/ul>

              Capacity Planning, Cost Model, and Chargeback\/Show back<\/b><\/span><\/span>
              <\/span><\/p>\n

                \n
              • Design Fabric capacity strategy (SKU sizing, workload isolation, scaling model) to support multiple products reliably.<\/span><\/span>
                <\/span><\/li>\n
              • Define guardrails and operational practices that reduce waste and improve predictability.<\/span><\/span>
                <\/span><\/li>\n <\/ul>

                Reliability, Observability, and Operational Readiness<\/b><\/span><\/span>
                <\/span><\/p>\n

                  \n
                • Define reliability patterns and operational standards for data pipelines and real\-time workloads.<\/span><\/span>
                  <\/span><\/li>\n
                • Integrate logging\/monitoring with Log Analytics<\/b> and security monitoring with Sentinel,<\/b> including alerting and incident response considerations.<\/span><\/span>
                  <\/span><\/li>\n
                • Define and operationalize data quality SLAs<\/b> (freshness, completeness, accuracy, timeliness) and embed quality checks into delivery pipelines.<\/span><\/span>
                  <\/span><\/li>\n <\/ul>

                  Consulting Engagement + Governance Forums<\/b><\/span><\/span>
                  <\/span><\/p>\n

                    \n
                  • Participate in architectural governance and provide architecture review\/sign\-off, with authority to mandate standards<\/b> when necessary to protect platform integrity<\/span><\/span>
                    <\/span><\/li>\n
                  • Partner closely with platform engineering to align patterns across identity, network, DevOps, and security.<\/span><\/span>
                    <\/span><\/li>\n <\/ul>

                    Working Style & Mindset<\/b><\/span><\/span>
                    <\/span><\/p>\n

                      \n
                    • Hands\-on architect:<\/b> you can design <\/span>and<\/span><\/i> build the critical Fabric artifacts to prove patterns.<\/span><\/span>
                      <\/span><\/li>\n
                    • Platform\-oriented:<\/b> you think in reusable standards, templates, and repeatable governance.<\/span><\/span>
                      <\/span><\/li>\n
                    • Strong consultative presence:<\/b> you can advise product teams while also driving decisions and outcomes.<\/span><\/span>
                      <\/span><\/li>\n
                    • Comfortable with authority:<\/b> you can mandate standards when required to protect the platform and business.<\/span><\/span>
                      <\/span><\/li>\n
                    • Documentation discipline:<\/b> you produce clear ADRs, standards, and operating playbooks.<\/span><\/span>
                      <\/span><\/li>\n <\/ul>

                      Engagement & Collaboration<\/b><\/span><\/span>
                      <\/span><\/p>\n

                        \n
                      • Supports product teams through office hours<\/b> and project\-based sprints.<\/b><\/span><\/span>
                        <\/span><\/li>\n
                      • Works primarily with: Azure lead architect, security architect\/engineer, DevOps platform engineer, and product engineering teams.<\/span><\/span>
                        <\/span><\/li>\n
                      • Data ownership remains with product teams;<\/b> this role defines the how (standards\/patterns\/governance), not centralized ownership.<\/span><\/span>
                        <\/span><\/li>\n <\/ul>\n
                        \n
                        <\/span>\n <\/div><\/span>
                        Requirements<\/h3>

                        Required Deliverables:<\/b><\/span><\/u><\/span>
                        <\/p>

                        You will be accountable for producing the following:<\/span><\/span>
                        <\/span><\/p>\n

                          \n
                        • Target\-state architecture <\/b><\/span><\/span>
                          <\/span><\/li>\n
                        • Data model standards:<\/b> conceptual \/ logical \/ physical + templates<\/span><\/span>
                          <\/span><\/li>\n
                        • Domain\-oriented data product patterns<\/b> and operating guidance<\/span><\/span>
                          <\/span><\/li>\n
                        • Governance model:<\/b> classification, retention, lineage, access controls<\/span><\/span>
                          <\/span><\/li>\n
                        • Fabric workspace strategy + operating model<\/b> (environments, isolation, ownership, lifecycle)<\/span><\/span>
                          <\/span><\/li>\n
                        • CI\/CD approach for Fabric artifacts<\/b> integrated with platform guardrails<\/span><\/span>
                          <\/span><\/li>\n
                        • IaC approach using Terraform<\/b> for Fabric\-related configuration and<\/span><\/span>
                          <\/span><\/li>\n
                        • Cost model + capacity planning strategy<\/b> (SKU sizing, isolation, show back\/chargeback)<\/span><\/span>
                          <\/span><\/li>\n
                        • Architecture Decision Records (ADRs)<\/b> for key platform decisions<\/span><\/span>
                          <\/span><\/u><\/li>\n <\/ul>

                          Qualifications:<\/b><\/span><\/u><\/span>
                          <\/p>

                          Required Experience & Skills<\/b><\/span><\/span>
                          <\/span><\/p>\n

                            \n
                          • 10+ years<\/b> in data architecture\/data engineering roles, including platform\-scale design.<\/span><\/span>
                            <\/span><\/li>\n
                          • Proven Microsoft Fabric production implementations<\/b> <\/b>you have delivered Fabric solutions that run in production with real operational constraints.<\/span><\/span>
                            <\/span><\/li>\n
                          • Deep hands\-on expertise in Fabric areas central to our rollout:<\/span><\/span>
                            <\/span><\/li>\n
                              \n
                            • Data Engineering <\/b><\/span><\/span>
                              <\/b><\/span><\/li>\n
                            • Data Factory (pipelines)<\/b><\/span><\/span>
                              <\/b><\/span><\/li>\n
                            • Real\-time analytics \/ Event Streams<\/b><\/span><\/span>
                              <\/span><\/li>\n <\/ul>\n
                            • Strong architecture capability across mixed data types: transactional, telemetry\/events, documents, geospatial, time series.<\/span><\/span>
                              <\/span><\/li>\n
                            • Demonstrated experience implementing and governing:<\/span><\/span>
                              <\/span><\/li>\n
                                \n
                              • Data modeling standards (conceptual\/logical\/physical)<\/span><\/span>
                                <\/span><\/li>\n
                              • Data governance (classification, retention, lineage)<\/span><\/span>
                                <\/span><\/li>\n
                              • Security patterns using Entra ID<\/b>, RBAC, workspace\-level controls<\/span><\/span>
                                <\/span><\/li>\n
                              • Compliance guardrails for GDPR, ISO 27001,<\/b> and data residency<\/b><\/span><\/span>
                                <\/span><\/li>\n <\/ul>\n
                              • Strong DevOps fluency:<\/span><\/span>
                                <\/span><\/li>\n
                                  \n
                                • CI\/CD patterns and operational delivery<\/span><\/span>
                                  <\/span><\/li>\n
                                • Terraform<\/b> as mandatory IaC for repeatability and standardization<\/span><\/span>
                                  <\/span><\/li>\n <\/ul>\n
                                • Ability to define standards and enforce guardrails<\/b> while maintaining a delivery\-first, pragmatic approach.<\/span><\/span>
                                  <\/span><\/li>\n <\/ul>

                                  Preferred<\/u><\/b><\/span><\/span>
                                  <\/span><\/p>\n

                                    \n
                                  • Experience supporting IoT<\/b> and telemetry\-heavy product ecosystems.<\/span><\/span>
                                    <\/span><\/li>\n
                                  • Experience designing data quality frameworks and SLAs for operational analytics and near\-real\-time processing.<\/span><\/span>
                                    <\/span><\/li>\n
                                  • Familiarity integrating observability\/security signals into Log Analytics<\/b> and Sentinel.<\/b><\/span><\/span>
                                    <\/span><\/li>\n <\/ul>\n
                                    \n
                                    <\/span>\n <\/div><\/span>
                                    \n <\/body>\n<\/html>

Apply