Real-time
Two-way sync
Changes in Dremio or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Human resources
Dremio to Smartrecruiters integration — real-time, two-way sync
Keep Dremio and Smartrecruiters in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Dremio and Smartrecruiters
Land the people and organization records from Smartrecruiters in Dremio as live tables for workforce reporting, without extract jobs, and write computed results back where Smartrecruiters can use them.
Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Smartrecruiters is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Dremio next to everything else the company measures.
Stacksync syncs Interviews, Offers, Users, Approvals from Smartrecruiters into tables in Dremio continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Dremio, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Smartrecruiters where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
Common use cases
- 01 Sync curated Dremio views into an operational Postgres so applications get low-latency access to lakehouse data.
- 02 Reverse-ETL aggregates computed over lake data out to CRMs and finance tools for business users.
- 03 Stream Jobs and Job Postings into a reporting database for requisition, funnel, and time-to-fill dashboards.
- 04 Export Interviews and Offers to a data warehouse to analyze interviewer load, offer-acceptance rates, and hiring outcomes.
Common sync patterns
Queryable history for planning and audit
A continuously synced copy in Dremio gives you a durable, queryable record of how Smartrecruiters's records change over time, for headcount planning and audit questions.
Write-back of computed values
Segments, rollups, or risk flags computed in Dremio sync back onto the matching records in Smartrecruiters, where the HR team sees them in the system they already use.
HR data in the warehouse, minus the pipeline
People and organization records from Smartrecruiters arrive in Dremio as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
What you can sync between Dremio and Smartrecruiters
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Dremio objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Jobs Query execution records useful for monitoring sync workloads. | Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. | Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. | Physical datasets is specific to Dremio and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. | Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. | Virtual datasets (views) is specific to Dremio and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Apache Iceberg tables Lakehouse tables supporting DML and snapshot metadata usable for incremental reads. | Job Postings Job ads and publications pushed to the career site and job boards; created and managed via the job publication endpoints (rate-limited to 2 requests/sec). | Apache Iceberg tables is specific to Dremio and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Spaces and folders Namespaces that organize virtual datasets and govern access. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Spaces and folders is specific to Dremio and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Reflections Materialized accelerations that make repeated extraction queries cheaper. | Offers Offer records tied to an Application with status, custom offer fields, and offer documents; readable and writable, commonly synced to an HRIS on hire (documents endpoint limited to 2 requests/sec). | Reflections is specific to Dremio and Offers to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Dremio and Smartrecruiters
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Dremio Smartrecruiters Interval-based propagation
DetectionStacksync polls Dremio for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters Dremio Sub-second propagation
DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.
DeliveryEach detected change is applied to Dremio as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Dremio: Bounded by engine capacity and workload management rather than API rate limits.
- Smartrecruiters: Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
What ships with Dremio ⇄ Smartrecruiters
Connect Dremio and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dremio–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dremio or Smartrecruiters data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Dremio or Smartrecruiters record.
Observability
Monitoring
Track your Dremio ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Dremio and Smartrecruiters.
How the Dremio and Smartrecruiters connectors work
Dremio
- Integration surface
- Arrow Flight SQL, JDBC/ODBC, and a REST API
- Authentication
- Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
- Change detection
- Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
- Capabilities
- read · write
- Rate limits
- Bounded by engine capacity and workload management rather than API rate limits
Smartrecruiters
- Integration surface
- SmartRecruiters REST APIs (SmartAPIs) on api.smartrecruiters.com — Candidates, Application, Jobs, Interviews, Offers, Users, Approvals, plus a Webhooks API for event subscriptions
- Authentication
- X-SmartToken API key header for a customer's own integration (grants full company access, no scopes or expiry), or OAuth 2.0 authorization-code flow for partner and Marketplace apps with user-scoped permissions
- Change detection
- Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture.
- Capabilities
- read · write · webhooks
- Rate limits
- Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
How it works
How to connect Dremio to Smartrecruiters — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Dremio and Smartrecruiters with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Dremio
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dremio and Smartrecruiters objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Dremio ⇄ SmartrecruitersCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Dremio SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dremio and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Dremio and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Dremio's Jobs and Physical datasets), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Dremio: Dremio queries data in place on lake storage (S3, ADLS, HDFS) rather than ingesting it, so syncs read through Dremio to underlying files and Iceberg tables. Smartrecruiters: Authentication is either an X-SmartToken API key (full company access, no scopes or expiry) or an OAuth 2.0 authorization-code flow that scopes access to the authorizing user's permissions. Stacksync's field mapping accounts for these differences between Dremio and Smartrecruiters without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Dremio and Smartrecruiters records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dremio and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dremio–Smartrecruiters integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Dremio and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Dremio: Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed. On Smartrecruiters: Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 434 integrations available for Dremio and Smartrecruiters.
Popular · 7 of 434
-
Dremio ⇄ Lever -
Dremio ⇄ Paylocity -
Dremio ⇄ Ukg Ready -
Smartrecruiters ⇄ Apache Druid -
Smartrecruiters ⇄ Apache Hive -
Smartrecruiters ⇄ Apache Impala -
Smartrecruiters ⇄ Apache Kylin
No integrations match .
