Sr. Apigee engineer to support Apigee hybrid environment on Google Cloud Platform (GCP) for a major insurance client - 784

Position: Sr. Apigee engineer to support Apigee hybrid environment on Google Cloud Platform (GCP) for a major insurance client - 784

Duration: 6 months with possible extension

Location: Hybrid Toronto (2 days in office, no exceptions)

On-call may be required: On rotation with other team members in case of severity 1 production support issues.

Weekly billable hours: 35

Must haves:

• 5+ yrs Google Apigee support exp (Apigee Hybrid, Control Plane, Runtime Plane, Developer Portal, Cassandra and PostgreSQL)
• 5+ yrs Google Cloud Platform (GCP) exp
• Integration concepts: APIs, proxies, API Gateway, microservices
• DevOps tools: Docker, OpenShift, Kubernetes, and CI/CD
• Software engineering tools: Git (GitHub), Jira, Confluence
• Monitoring and alerting technologies: Grafana, Dynatrace, ELK

Nice to haves:

• Hashicorp Vault, k8sas Secrets/Keys, Terraform Cloud
• AWS and Azure
• Experience with security policies OAuth, SAML, etc
• Experience in Change Management and Incident Management processes

Summary of responsibilities

• Be responsible for the Apigee platform in its initial stages and also responsible for setting up best practices and standards for platform users being onboarded, including support during non-business hours.
• Support initial setup, configuration, operationalization, and onboarding of new software teams that will start using Apigee;
• Ensure best practices in configuration management, development cycle and security are being followed on Apigee.
• Support Apigee Hybrid installation on Google Cloud Platform (GCP) and Red Hat OpenShift or Kubernetes;
• Develop technical initiatives to make software engineering teams more effective.
• Work closely with software engineering teams to support them in the process of using the development lifecycle tool chain and platforms.
• Cross-train current support team to be able to support the platform as well.
• Support the architecture team in defining processes:

o to create, promote, test, manage and document proxies;

o to handle access tokens;

o to provision access to APIs;

o to deal with authorization (WebSeal and ODIC)

o and also standards/global policies, and patterns for proxies (ingress and egress) to support development teams