Skip to main content

Sr. Azure Integration Lead

Posted 2 days ago

ecclesiastesNewark (DE)

SENIORITY

Manager

Apply (opens in a new tab)

About the role

Job Description: Job DescriptionJob Description Summary The Sr. Integration developer/ technical lead is responsible for the end to end delivery of, guidance for, strategy and collaboration for integration solutions across the enterprise landscape within the organization's regulatory, architectural, cybersecurity and governance framework. The Sr. integration tech lead participates with management and clients to comprehend complex business problems to derive technical solutions and work closely with developers to ensure requirements are captured accurately and provide code feedback..
Responsibilities:
  • Manages the daily tasks of developers, making sure that deadlines are met, meet's coding standards and resolves issues, can fill in for dev coding if needed
  • Monitors daily the quality of work of developers, performing code reviews, making sure that best practices and company standards are adhered toProvides viable technical recommendations and design based on best practices and company standards
  • Makes sure that whatever has been developed meets business, performance and volume requirements
  • Validates and Performs end-to-end testing with developers
  • Researches and performs POCs to test out technical solutions
  • Assists developers with their issues, making sure integration team does not block any deliverable, prevent potential blockers and can perform development tasks if needed
  • Assists developer on deployment administrative works
  • Makes sure that artifacts are productionalized, e.g. logging, alerts, retries, raising and resolving ticket
  • Provide production hypercare support Qualifications and
  • ExperienceLead experience [small development teams]Ability to understand and clearly articulate functional documentation and requirements to project teams
  • Designed and developed APIsAbility to clearly and proficiently communicate technical and complex integration scenarios
  • Did design and development using cloud technologies
Prepared technical design documents which included various diagrams like process flows, sequence diagrams, ERD, architectural and network diagrams, etc. Have used Agile Delivery methodology Have used JIRA to manage stories, tasks, issues, etc. Experienced in Visual Studio. Technical Skills and KnowledgeJIRACloudTechnologies Experience [MS Azure, Google BQ]Azure Serverless [Logic Apps, Function Apps, Service Bus, Event Grids, ADF]MuleSoft v4.x [AnyPoint, API's, ESBs, DataWeave]
Languages: Swagger, RAML, XSLT, Object-Oriented Programming Languages, Open APIIDE:Eclipse, VisualCode, Anypoint Studio, Visual Studio Configuration Management: Azure Dev/Ops, Clear Case, Rational SCDatabase: Relational database, SQL, Stored Procedures and Functions Familiar with Dev/Ops [Azure, CI/CD, Code Repo's, GitRepo's, Branching]Diagramming Tools, e.g. LucidChart, Visio

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this