[Hiring] Azure Integration Engineer @System Soft Technologies

Role Description

We are seeking an Azure Integration Engineer to design, configure, secure, and validate a private batch-data exchange between Microsoft Azure and Adobe Experience Platform. The engineer will mobilize after the AEP schema and dataset build gate has been completed. The role will establish reliable inbound source-file delivery to AEP and outbound audience-file delivery from AEP to Azure. The engineer will work closely with the AEP platform team, Azure infrastructure and security stakeholders, data owners, and QA resources.

• Review approved AEP schemas, datasets, source mappings, and batch-interface requirements before beginning integration configuration.
• Design and configure the Azure storage structure required for inbound and outbound batch exchange.
• Configure Azure Blob Storage containers, folders, paths, naming conventions, and retention requirements.
• Establish private connectivity and coordinate private endpoints, network controls, firewall rules, and allowlisting.
• Configure and manage service principals, credentials, secrets, certificates, and access permissions.
• Support configuration of AEP source and destination connections to Azure.
• Define inbound and outbound file conventions, including filenames, manifests, delimiters, compression, encryption, and control files.
• Configure or support scheduled batch-file movement and processing.
• Develop automation or orchestration required to prepare, place, move, archive, or validate files.
• Implement retry, restart, exception-handling, and failure-notification procedures.
• Validate inbound batch loads from Azure to AEP.
• Validate outbound audience-file delivery from AEP to Azure.
• Reconcile source files, processed files, record counts, rejected records, and delivered audience counts.
• Troubleshoot connectivity, authentication, storage, scheduling, and file-processing defects.
• Support security, governance, privacy, and production-readiness reviews.
• Produce deployment documentation, monitoring procedures, operational runbooks, and knowledge-transfer materials.

Qualifications

• Strong hands-on experience with Microsoft Azure integration services and Azure Storage.
• Experience configuring Azure Blob Storage, access controls, service principals, managed identities, and secrets.
• Experience implementing private endpoints, network restrictions, firewall rules, and secure cloud connectivity.
• Experience designing and supporting scheduled batch-data interfaces.
• Experience with file-based integration patterns, including manifests, control files, archival, retry, and reconciliation.
• Ability to troubleshoot authentication, authorization, network, file-format, and scheduling issues.
• Experience developing automation using PowerShell, Azure CLI, Python, Azure Functions, Logic Apps, Data Factory, or comparable tools.
• Strong understanding of production monitoring, operational support, and incident recovery.
• Ability to coordinate across application, platform, infrastructure, networking, security, and data teams.
• Strong technical documentation and communication skills.

Requirements

• Experience integrating Azure Blob Storage with Adobe Experience Platform.
• Familiarity with AEP Sources, Destinations, batch ingestion, datasets, and audience activation.
• Experience with Azure Data Factory, Logic Apps, Functions, Key Vault, Monitor, and Log Analytics.
• Familiarity with customer, CRM, marketing, or audience data.
• Experience with privacy-sensitive or regulated data transfers.
• Experience supporting globally distributed implementation teams.

Required Deliverables

• Approved Azure batch-exchange design.
• Configured storage containers, folders, and naming standards.
• Private-endpoint and network-control configuration.
• Credential, secret, and access-control configuration.
• Inbound and outbound file specifications.
• Batch schedules and orchestration configuration.
• AEP source and destination connectivity support.
• Monitoring, alerting, retry, and restart procedures.
• Inbound-load reconciliation evidence.
• Outbound audience-file validation evidence.
• Security and production-readiness documentation.
• Operational runbook and knowledge-transfer materials.

Success Criteria

• Private connectivity between Azure and AEP is operational and approved.
• Authorized users and services have appropriate least-privilege access.
• Inbound files load into the approved AEP datasets and reconcile to source totals.
• Failed batches can be identified, corrected, and restarted using the documented runbook.
• Outbound audience files arrive in the correct Azure location on schedule.
• Audience-file counts and contents pass business and QA validation.
• Monitoring, alerts, ownership, escalation procedures, and known limitations are documented and accepted.