Mercor
Data Engineer
About this role
Mercor is seeking a Data Engineer to enhance data reliability and availability through robust pipeline development. This role involves collaborating with various teams to support data needs and ensuring high data quality across the organization.
What you'll do
- Build and maintain data pipelines from multiple sources
- Design dbt models to create uniform data schemas
- Implement scalable data workflows using various tools
- Collaborate with cross-functional teams for data usability
- Ensure data quality and reliability from ingestion to consumption
- Enhance pipeline performance and monitoring
What they're looking for
- Proficient in SQL and Python
- Experience with Fivetran, dbt, Snowflake
- Strong data modeling and schema design abilities
- Familiarity with ETL/ELT processes
- Knowledge of data governance and quality assurance
- Ability to work collaboratively across teams
- Bonus: experience with machine learning workflows
Benefits
- Bi-annual performance bonuses
- Generous equity grants over 4 years
- Up to $15k relocation bonus
- $10K housing bonus near office
- $1.5K monthly meal stipend
- Free Equinox membership
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Mercor
Mercor builds a marketplace platform connecting expert talent to AI opportunities, supported by identity infrastructure, matching algorithms, and internal tools for data management. The company is hiring Software Engineers, Machine Learning Engineers, Fullstack Engineers, and Security Engineers to develop backend systems, ML models, cloud infrastructure, and distributed platforms.
- Website
- mercor.io
Likely interview questions
- Walk us through a large-scale ETL pipeline you've built. What sources did you integrate, and how did you handle data quality and reliability across heterogeneous sources?
- Describe your experience with dbt. How have you used it to design data models and transformations, and what patterns have you found most effective for schema standardization?