Hire Azure data engineers, including Fabric

An Azure data engineer moves data through Microsoft's platform. For many teams that now means Microsoft Fabric: OneLake, pipelines, and a warehouse or lakehouse the rest of the company can query. Others still run Data Factory, Synapse, and Azure Data Lake Storage as separate services.

The job is the same shape either way:

• Ingestion. Data Factory, Fabric pipelines, or an event source, with a failure you can see.
• Storage. A lake layout someone else can navigate six months later.
• Serving. Tables for Power BI, Excel, or a product, with access that matches the team.

Name Fabric on the role if that is what you run. Name Data Factory or Synapse if you have not moved. People apply to the platform you have.

You probably need this hire when:

• You are moving reporting into Fabric and the pipelines are still a side project.
• Data Factory jobs fail quietly and the dashboard is stale.
• You have Synapse or a lake, and no one person owns refresh and access.
• A Microsoft 365 company wants the data platform next to the identity it already uses.

If the warehouse is Snowflake rather than Fabric, see Snowflake. If the work is the Python around the platform, see Python data talent.

They can say which Azure service does which job. Fabric, Data Factory, Synapse, and a storage account are not interchangeable, and a good hire will not pretend they are.

Refresh and access. They design for a late file and for a colleague who should see one workspace, not the subscription.

A calm cost story. Capacity, pipelines, and storage each have a bill. They can tell you which one moved last month and why.

What to ask

• What did you migrate into Fabric, and what did you leave on Data Factory on purpose?
• How do you notice a pipeline failed before the morning report does?
• Who can read the lake, and how is that decision reviewed?

carbon.talent is a data and AI talent platform. Post a role, see who applied, and hire.

1. Post a role. Title, stack, seniority, and whether you want permanent, contract, or fractional. Set remote or on-site, the country, and the overlap hours.
2. See who applied. Open each profile. Review a real-world data experience test, a working-style profile, and a video interview when they are on the profile.
3. Hire. Interview, agree the terms with the person, and hire on the platform. ID checks are on Team and Scale.

Already found someone? Test a candidate you found, then decide.

Companies post this role from anywhere. You choose where the person is based and which hours they overlap with your team.

Remote, hybrid, and on-site use the same flow. Location is a setting on the role.