Define the work, required evidence, and interview criteria before sourcing SSIS Developer candidates. This guide turns the role into a consistent, auditable hiring process.
Decide whether the role keeps on-premises SQL Server packages running, moves them to Azure, or both. Then test control flow design, data flow buffer behavior, parameterization across environments, and restart logic. Ask how a package recovered after a mid-run failure and how they avoided loading the same rows twice.
SSIS developers build and maintain ETL packages on the Microsoft data stack. Many roles combine package work with T-SQL and a move toward Azure Data Factory. Use this guide to define that mix and to evaluate candidates on the same exercises.
What SSIS Developers do day to day
The core work of the role, before tools and titles. Check that your brief, your interviews, and your scorecard all cover it.
Build and maintain SSIS packages for data integration
Load SQL Server data warehouses reliably
Handle errors, logging, and deployments
Migrate packages to Azure Data Factory or newer tools
Skills to look for in SSIS Developers
Group requirements by area so the job post, the interview plan, and the scorecard test the same things.
01
SSIS
Control flow, data flow, variables, and package configurations.
02
SQL Server
T-SQL, warehousing, and SQL Agent scheduling.
03
Migration
Azure Data Factory and SSIS in the cloud.
Which specialization do you need?
Most SSIS Developers lean toward one of these. Name the one you need in the brief instead of listing every tool.
Warehouse ETL
Loading SQL Server warehouses.
Azure migration
Moving SSIS workloads to Azure.
Legacy maintenance
Keeping existing packages healthy.
SSIS role levels and evaluation evidence
Adjust the scope to the actual job. Seniority should reflect decision ownership and system complexity, not years alone.
1
Junior
Typical scope
Entry-level profile with a strong foundation in Control Flow design, basic Data Flow transformations, and package deployment.
Knowledge areas
SSISControl FlowData FlowSSDT
What to look for
Hands-on experience building SSIS packages with common tasks like Execute SQL Task, Data Flow Task, and For Each Loop Container. Familiarity with SSDT development environment and basic package deployment to SQL Server.
2
Mid
Typical scope
Mid-level profile with proven expertise in complex Control Flow orchestration, Data Flow performance tuning, and multi-environment deployment.
Demonstrated ability to optimize Data Flow buffer sizes and implement parallel execution for high-volume ETL workloads. Experience implementing SSIS Catalog deployment with environment variables and connection parameterization.
3
Senior
Typical scope
Senior profile with deep mastery of Azure Integration Runtime migration, checkpoint recovery architecture, and enterprise-scale ETL optimization.
Proven track record integrating on-premises SSIS packages with Azure Data Factory via Azure-SSIS Integration Runtime. Experience architecting checkpoint recovery and transaction management for mission-critical batch processing.
What should an SSIS Developer role brief include?
State the number of packages, the SQL Server versions, the schedule, and the source systems feeding them. Say whether Azure Data Factory is in scope. Require control flow and data flow design plus strong T-SQL; knowledge of a particular source system can be picked up.
Package inventory, run schedule, and the systems they depend on
SQL Server and catalog deployment setup across environments
Restart, logging, and alerting standards that packages must follow
Plans to host packages in Azure or replace them
How should SSIS Developer candidates be compared?
Give each candidate the same package description: large input, a lookup, and a requirement to restart without duplicates. Strong answers use set-based SQL where it fits, tune buffers where needed, log row counts, and parameterize connections. Score everyone against shared notes.
Ask when a Script Task is justified and when it hurts memory use
Ask how a restart avoids reprocessing completed steps
Ask how connection strings change between test and live environments
Review T-SQL quality alongside package design
What to probe when interviewing SSIS Developer candidates
These are risks a weak hire in this role tends to bring. Turn each into a work-sample task or follow-up question that produces evidence for or against it, and score every candidate on the same set.
Can they prioritize a Script Task over a built-in Transformation component to optimize buffer memory usage?
Have they successfully migrated on-premises SSIS packages to Azure Data Factory with minimal rework?
Do they understand checkpoint recovery well enough to ensure mission-critical batch jobs restart gracefully?
Job description template
A starting draft built from this guide. Replace the bracketed parts, cut anything that does not apply, and keep every requirement tied to the work.
Job description template
About the role
[Two or three sentences on the product, the team, and why this role is open now.]
What you will do
Build and maintain SSIS packages for data integration
Load SQL Server data warehouses reliably
Handle errors, logging, and deployments
Migrate packages to Azure Data Factory or newer tools
What you bring
SSIS: Control flow, data flow, variables, and package configurations.
SQL Server: T-SQL, warehousing, and SQL Agent scheduling.
Migration: Azure Data Factory and SSIS in the cloud.
Nice to have
Warehouse ETL
Azure migration
Legacy maintenance
Level and scope
Junior: Entry-level profile with a strong foundation in Control Flow design, basic Data Flow transformations, and package deployment.
Mid: Mid-level profile with proven expertise in complex Control Flow orchestration, Data Flow performance tuning, and multi-environment deployment.
Senior: Senior profile with deep mastery of Azure Integration Runtime migration, checkpoint recovery architecture, and enterprise-scale ETL optimization.
How we hire
A structured interview and a short work sample, scored against the same criteria for every candidate.
Full-time, contract, or freelance?
SSIS work is common in Microsoft shops and often project-based. A contractor fits an Azure migration or a set of new packages. Hire full-time when SSIS runs critical nightly loads.
FAQ
Frequently Asked Questions About Hiring SSIS Developers
Direct answers for role definition, evaluation, specialist depth, and compensation research.
What does an SSIS developer build?
They build packages that extract data from sources, transform it, and load it into SQL Server or other targets. That includes control flow design, data flow components, logging, error handling, scheduling through SQL Server Agent or the catalog, and tuning. Many also write supporting T-SQL and help migrate packages to cloud services.
Which SSIS skills should I interview for?
Interview for control flow containers, data flow transformations, buffer tuning, parallel execution, the SSIS catalog, parameters, checkpoints, and T-SQL. For migration roles add Azure Data Factory with the SSIS integration runtime. Ask for a package that was too slow and the change that fixed it.
How do I run a fair SSIS assessment?
Give a written scenario instead of a long build: a described input, a lookup, and a restart requirement. Ask for the package design and the failure handling. Use the same scenario and a written scoring guide for every candidate, then probe one detail, such as memory use.
When is an SSIS specialist better than a general SQL developer?
A specialist pays off when you have many packages, tight batch windows, or a cloud move to plan. A strong SQL developer can learn basic packages. Senior profiles design checkpoint recovery and transaction handling for critical batches and lead moves to Azure.
How do I estimate SSIS developer compensation?
Rates depend on seniority, the weight of T-SQL work, and whether Azure migration is included. Gather current postings and recruiter feedback from your own market, comparing SSIS roles with general ETL and data engineering openings. Keep the date and source for each data point, and update the range at each new search.
ConnectDevs can support discovery and structured interview workflows, but the hiring team remains responsible for the role definition, evidence standard, final decision, compensation validation, and applicable legal review.