Job description

Position: Google Apigee Migration Engineer / Developer Company: Global Professional Services Organization Client Industry: Transportation Location: Dallas, TX or San Antonio, TX Work Arrangement: Hybrid – Onsite at Client HQ 2 Days per Week Employment Type: W2 Contract-to-Hire Engagement Requirement: W2 candidates only; C2C is not permitted Primary Focus: Apigee Migration, API Proxies, Policies, API Development, GCP, OAuth/JWT, REST, CI/CD Overview The Google Apigee Migration Engineer / Developer will join a Global Professional Services organization supporting a major Transportation client and provide hands-on engineering and development expertise for the migration, development, configuration, testing, and deployment of APIs onto Google Apigee. This is an execution-focused engineering position. The successful candidate must be able to personally analyze existing APIs, understand their behavior and dependencies, develop or migrate API proxies into Apigee, configure appropriate policies, implement security requirements, troubleshoot migration issues, and move APIs through testing and deployment into a stable production environment. The engineer will work extensively with Apigee, Google Cloud Platform (GCP), REST APIs, OAuth, JWT, and CI/CD processes. The individual must understand how these capabilities work together and be capable of diagnosing problems across API logic, proxy configuration, security policies, deployment pipelines, and the underlying cloud environment. This is also a client-facing hybrid position requiring onsite presence at the client headquarters in Dallas or San Antonio two days per week. Success will be demonstrated by working APIs migrated and deployed into Apigee, rather than architecture documents or migration recommendations alone. Purpose: Play a direct role in modernizing the API ecosystem of a major Transportation organization by moving critical APIs onto Google Apigee. The engineer's work will help establish secure, reliable, and supportable API capabilities that applications and services can depend upon. Build deeper expertise across Google Apigee, GCP, API development, API security, OAuth, JWT, REST services, automation, and CI/CD while gaining hands-on experience with the technical challenges associated with enterprise API migration. The W2 contract-to-hire structure also provides the opportunity to demonstrate technical and client-facing capabilities that can support a longer-term role. Performance Objectives 1. Migrate Priority APIs Successfully to Google Apigee. Beginning immediately and throughout the engagement, analyze assigned APIs and migrate or develop the required API proxies, policies, configurations, and supporting components within Google Apigee. Preserve required API functionality while adapting implementations appropriately for the target Apigee and GCP environment rather than simply reproducing legacy configurations. Personally troubleshoot technical problems encountered during migration and work directly with client and professional services teams when resolution requires changes outside the API layer. 2. Implement Secure API Authentication and Authorization. Throughout the migration, configure and validate appropriate API security using OAuth, JWT, and other required Apigee security capabilities. Ensure migrated APIs properly authenticate and authorize requests while maintaining required application and service functionality. Troubleshoot token, authentication, authorization, policy, and access-related problems and collaborate with client security or identity resources when issues cross technical boundaries. 3. Establish Reliable API Deployment Through CI/CD. During the first 90–180 days, support or improve CI/CD processes for building, configuring, testing, and deploying Apigee APIs across appropriate environments. Reduce unnecessary manual deployment steps, identify configuration inconsistencies, troubleshoot pipeline failures, and ensure deployments can be repeated predictably. Maintain appropriate controls and validation so deployment automation increases speed without introducing unacceptable production risk. 4. Stabilize Migrated APIs and Support Production Readiness. As APIs move through the migration lifecycle, proactively identify and resolve issues involving API behavior, proxies, policies, REST interactions, authentication, JWT processing, GCP dependencies, or deployment configuration. Work with client testing, platform, development, and other technical teams to investigate defects and determine root causes rather than repeatedly addressing symptoms. Ensure assigned APIs satisfy required functional and technical expectations before being considered migration-complete Critical Subtasks 1. Assess Existing APIs and Migration Requirements. At the beginning of assigned migration work, review existing APIs, interfaces, dependencies, security requirements, proxy behavior, and relevant target-state requirements. Determine what must be migrated, redesigned, configured, or rebuilt within Apigee and identify technical dependencies that could affect delivery. Use onsite engagement with client resources in Dallas or San Antonio to accelerate understanding of requirements and technical dependencies where appropriate. 2. Develop and Configure Apigee API Proxies. Throughout migration execution, personally create, modify, and configure API proxies within Google Apigee to support required REST API behavior. Translate existing API functionality into appropriate Apigee implementations while maintaining required routing, transformations, error behavior, and integrations. Test configurations as development progresses and troubleshoot problems before handing APIs into downstream validation. 3. Implement and Troubleshoot Apigee Policies. As proxies are developed or migrated, configure the policies necessary to support required API functionality, security, and processing behavior. Apply appropriate Apigee capabilities rather than introducing unnecessary custom development when platform functionality can meet the requirement. Troubleshoot policy sequencing, configuration, runtime behavior, and interactions with dependent services when failures occur 4. Implement OAuth, JWT, and API Security Requirements. Throughout development and migration, implement and validate authentication and authorization requirements involving OAuth and JWT. Test both expected and failure scenarios to ensure unauthorized requests are handled appropriately while valid application and service interactions continue to function. Investigate token, claims, policy, permission, and related security issues in collaboration with appropriate client and professional services resources. 5. Integrate Apigee Delivery with GCP and CI/CD. During the migration, work with applicable GCP capabilities and CI/CD processes to ensure API configurations can be built, deployed, promoted, and validated consistently across environments. Troubleshoot pipeline, configuration, environment, or deployment problems and identify opportunities to automate repetitive activities. Ensure deployment processes include appropriate validation and recovery considerations. 6. Validate and Stabilize Migrated APIs for Production. As assigned APIs approach migration completion, work with client testing, platform, development, and other technical teams to resolve outstanding defects and confirm production readiness. Investigate failures across Apigee proxies, policies, REST interactions, security, GCP dependencies, and deployment configurations until root causes are understood and resolved. Use the required onsite client engagement to accelerate collaboration and issue resolution when appropriate, and document significant implementation decisions and recurring troubleshooting patterns. 7. Continuously Evaluate and Integrate AI to Improve Performance. Within the first 90–180 days, or within the available engagement period, identify how AI and automation can safely improve Apigee migration and API engineering activities. Evaluate opportunities involving API analysis, proxy development, policy configuration, REST troubleshooting, test generation, CI/CD diagnostics, documentation, and migration issue analysis, and incorporate useful capabilities where client and organizational policies permit. Independently review and validate AI-generated code, configurations, policies, security recommendations, and troubleshooting conclusions before they are implemented. Success will be measured by demonstrable improvements in migration speed or engineering quality without compromising API security, reliability, maintainability, confidentiality, or technical judgment. Requirements The candidate must demonstrate hands-on Google Apigee engineering and development experience. Experience should include personally creating, configuring, modifying, troubleshooting, and deploying API proxies and policies rather than simply participating in projects where Apigee was used. Strong REST API development and troubleshooting capability is required. The individual should be able to explain how an API behaves from the incoming request through the Apigee proxy and policies to the backend service and back through the response. Practical experience with OAuth and JWT is important and should include implementation and troubleshooting rather than conceptual familiarity alone. The candidate must also demonstrate working knowledge of GCP and CI/CD sufficient to support API migration, deployment, environment promotion, and troubleshooting. Because this is a Global Professional Services engagement, the engineer must also be comfortable operating in a client-facing delivery environment, working collaboratively with both professional services and client technical teams. Ideal Candidate Profile The strongest candidate is a hands-on Apigee engineer who can be given an existing API and take meaningful ownership for getting it migrated into the target environment. During an interview, the candidate should be able to walk through an actual Apigee migration or implementation and explain the original API, the proxies and policies they personally developed, OAuth/JWT requirements, technical problems encountered, CI/CD deployment approach, and how they validated that the API worked after migration. The differentiator is demonstrated execution. Apigee appearing on a résumé is not enough; the candidate should be able to demonstrate that they have personally built, migrated, troubleshot, secured, and deployed APIs using the platform. The candidate must also be able to work the required hybrid schedule, including onsite presence at the client headquarters in Dallas, Texas or San Antonio, Texas two days per week. Employment and Location Requirements This position is a W2 Contract-to-Hire opportunity with a Global Professional Services organization supporting a Transportation industry client. Candidates must be able to work on a W2 basis. C2C candidates and C2C arrangements are not permitted for this engagement . The role is hybrid and requires onsite presence at the client headquarters in Dallas, Texas or San Antonio .

Requirements

Must-haves

Position: Google Apigee Migration Engineer / Developer
Company: Global Professional Services Organization
Client Industry: Transportation
Location: Dallas, TX or San Antonio, TX
Work Arrangement: Hybrid – Onsite at Client HQ 2 Days per Week
Employment Type: W2 Contract-to-Hire
Engagement Requirement: W2 candidates only; C2C is not permitted
Primary Focus: Apigee Migration, API Proxies, Policies, API Development, GCP, OAuth/JWT, REST, CI/CD
Performance Objectives
Critical Subtasks
Practical experience with OAuth and JWT is important and should include implementation and troubleshooting rather than conceptual familiarity alone.
The candidate must also demonstrate working knowledge of GCP and CI/CD sufficient to support API migration, deployment, environment promotion, and troubleshooting.
Ideal Candidate Profile
The strongest candidate is a hands-on Apigee engineer who can be given an existing API and take meaningful ownership for getting it migrated into the target environment.
The candidate must also be able to work the required hybrid schedule, including onsite presence at the client headquarters in Dallas, Texas or San Antonio, Texas two days per week.
Employment and Location Requirements
This position is a W2 Contract-to-Hire opportunity with a Global Professional Services organization supporting a Transportation industry client.
Candidates must be able to work on a W2 basis. C2C candidates and C2C arrangements are not permitted for this engagement .
The role is hybrid and requires onsite presence at the client headquarters in Dallas, Texas or San Antonio .

Nice-to-haves

None flagged.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

apigcprestci/cdai

Platform: catsone
Effort: medium

Benefits

Benefits detected in the listing.

Pto