Job Description & Details
This 18-month contract puts you right in the middle of a massive migration effort, bridging legacy enterprise architectures with modern Google Cloud Platform data pipelines. If you like untangling data flow bottlenecks and building resilient Java backend applications, this gig gives you plenty of room to operate without getting bogged down in endless bureaucracy.
What You'll Actually Be Doing
Expect to spend your days writing robust Java code and Python-based transformation libraries to ingest data from on-premise systems straight into GCP. You'll be working heavily with BigQuery, Dataflow, and Pub/Sub, dealing with messy real-time streaming issues, implementing slowly changing dimension (SCD) patterns, and making sure masking routines keep sensitive data locked down. It is a mix of heavy software engineering and modern data pipelining, so you'll constantly be pivoting between backend API logic and cloud-native data plumbing.
The Core Tech Stack
You need to bring solid Java 8+ fundamentals, multi-threading mastery, and a deep understanding of the Spring framework to build high-performance services. On top of that, you must have real-world familiarity with GCP services like BigQuery and Dataflow, alongside streaming tools like Kafka or Google Pub/Sub. CI/CD tooling like Jenkins, GitHub Actions, and Gradle will be your daily drivers for pushing code safely through the pipeline.
Interview Expectations
Expect the technical leads to probe deep into how you handle backpressure and data loss in streaming architectures using Pub/Sub or Kafka. They want to see how you reason about distributed state and failure recovery. They'll also likely test your concurrency knowledge in Java—be ready to explain how you avoid deadlock scenarios when optimizing multi-threaded data ingestion routines.
Application Advice
Skip the generic template and tailor your resume to heavily emphasize your hands-on cloud migration experience, specifically calling out GCP, BigQuery, and Dataflow alongside your Java and Spring background. Make sure keywords like Apache Beam, RESTful APIs, CI/CD, and microservices are explicitly stated in your recent project descriptions so you easily clear the initial ATS filters.