No H1B
- Block’s, GTC (Governance, Transparency and Compliance) team has a need for a Senior SW Engineer/.Net resource who has experience deploying applications into the cloud environment and understands what that deployment looks like. This person will mentor an inhouse, Lead Developer and help them come up to speed.
- The contractor must be a strong developer and understands security really well. The client wants to figure out when their dev pipelines come through, Permissioning on the applications, that get registered for Azure Active Directory, to be able to look at that and go to our internal developers when challenge needs to happen if they’re trying to get permission on the app or if they didn’t do the Permissioning correctly and need to separate it out from a front end and a back end.
- They must have senior level experience with development and security. Their architect (Pulikotol from Dan Cahoon’s team; Dan reports to Ovace) was performing the responsibility however, they need someone else so the architect can focus on architect responsibilities.
Their architect has been helping, but they need to bring in a resource to help their Lead Developer come up to speed. He is not a traditional developer, started out in the call center and is more or less self-taught and went through training. He is currently not at the level they need. So, they need someone who can mentor and lead him on how to look at the code and maintain the code. He will need to learn that for the team to come up with their abilities with the cloud. If the current developer isn’t able to get up to speed, then they would either keep the contractor longer or convert.
Technologies:
MUST HAVE:
- .net, 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
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…PLUS, PLUS