Data Engineer

Job Description We have a 3 month contract (opportunity for conversion or extension) for an early-career Data Engineer with 1–3 years of experience building and automating ETL pipelines using SSIS, Control-M, and SQL, with additional skills in Power BI for reporting and dashboarding. They demonstrate strong problem-solving abilities, thrive in collaborative remote environments, and are detail-oriented and adaptable, with healthcare or managed care experience considered a plus. 100% Remote. MUST HAVES: • SSIS, control-M, other ETL applications • SQL • Power BI NICE TO HAVES: • Healthcare background • Managed care experience Disqualifiers: • Resume not matching the intended job titles/requirements. About the Role: The goal is to develop more robust ETL processes to support reporting and dashboarding needs. Currently, the data ecosystem includes a mix of tables and queries in Teradata (labspace), reports in Excel, and dashboards in Power BI. However, there is no unified pipeline to manage and automate the flow of data across these platforms. The plan is to implement a pipeline using a combination of Control-M (for enterprise scheduling), SSIS, and potentially other ETL tools. While the surrounding team has strong expertise in Teradata, Excel, and Power BI, there is limited experience with Control-M and SSIS. The work environment is highly collaborative and fully remote, which supports cross-functional coordination and knowledge sharing. Key points: • Objective: Build a more reliable and automated ETL pipeline. • Current tools: Teradata (tables and queries), Excel (reports), Power BI (dashboards). • Target tools: Control-M, SSIS, and other ETL applications. • Team strengths: Teradata, Excel, Power BI. • Team gaps: Limited experience with Control-M and SSIS. • Work environment: Collaborative and fully remote. Responsibilities: • The team holds daily standups to review current project workloads, discuss any issues, and share updates on what each member is working on. • The projects typically involve evaluating and improving various components of the ETL pipeline. For example, if a report currently exists in Excel and is generated from a SQL query, the team assesses what steps are needed to automate parts of the SQL output or the Excel report itself. • They also explore opportunities to transition such reports into Power BI dashboards and consider what that migration would entail. In cases where a full process already exists—from SQL to Power BI—the team looks for ways to enhance efficiency and determine which tools could support those improvements. • This role is unique in that it is not solely focused on ETL development; instead, it requires a broader understanding of reporting workflows and a commitment to completing projects on time and to the best of each team member’s ability. • Performance expectations will be to complete the projects on time.