Required Skills

.Net Developer .net Azure DevOps (ADO

Work Authorization

  • Us Citizen

  • Green Card

  • EAD (OPT/CPT/GC/H4)

  • H1B Work Permit

Preferred Employment

  • Corp-Corp

  • 1099-Contract

Employment Type

  • Consulting/Contract

education qualification

  • UG :- - Not Required

  • PG :- - Not Required

Other Information

  • No of position :- ( 1 )

  • Post :- 5th Feb 2021

JOB DETAIL

 

Technologies:

MUST HAVE:

  • .net, Azure DevOps (ADO) and Terraform are technologies their developers are leveraging.
  • Azure Active Directory (Azure AD) – anything to do with Azure AD is where they focus all their Identity on OpenID Connect for registrations
    • Understand OpenID Connect (OIDC) and SAML re: registration/authentication
      • OpenID Connect - registrations are using OpenID Connect (OIDC) – OPEN OP has been the universal standard for cloud-to-cloud federations
      • SAML - has been the traditional method (i.e. it is an open standard for exchanging authentication and authorization data between parties),but started to unify standards using Open Ops which has been the universal standard to open ID connections and is where OIDC comes in play
  • MS Graph – is the API layer, where they are permissioning access to application.
  • EXCELLENT COMMUNICATION SKILLS
  • SAML and OpenID are both significant part of what we are building out. We have SAML applications that we are migrating to OpenID and most all new apps are written for OpenID.

 

NICE TO HAVE…BIG PLUS:

  • Saviynt – a super BIG PLUS if they know anything about Savient, like really good with Savient to help back up Amanda with performing principle activities, drive design and everything into implementation
  • MySQL - Experience helps since it is backend to Savient. They have issues with queries that are written in My SQL
  • He did say if the person has Identity Access Space experience building .net applications or Azure DevOps pipelines that would be a “nice to have”

 

Interview SAMPLE QUESTIONS FOR VETTING: (note: lookingforsomeone with hands on experience.  Share specific examples ofyourexperience on applications you have worked on)

 

  • Please describe some of the things you have promoted into the cloud and how you had a hand in leading, managing and making updates?
  • Share/demonstrate experience with build pipeline, ADO, and things of that nature.  Have you set that up and worked it through ADO?  If so, please share in detail?
  • Can you take one application as an example and walk through the authentication, registration, and API permissions. 
    • Don’t explain how it works, explain how you would configure? 
    • How would you do an application register?
    • Where would you do the API permissions?
  • What kind of permissions would you set for the application registration?
  • How does Azure know if there is a read or write permission?

Company Information