How to Apply: Send your application to the email address or visit the application link provided on this page to submit your CV and cover letter.
Prove Your GCP Networking Depth Before the First Screen
This role is not about general cloud familiarity. Abacus needs someone who can design secure landing zones, wire up Apigee, and troubleshoot DNS and routing under pressure. Your application must show concrete GCP networking wins, not just a list of tools.
1. Lead with landing zone proof: Your CV should open with a project where you designed or provisioned a GCP landing zone. State the number of VPCs, subnets, and firewall rules you managed. Mention if you used Private Service Connect or hybrid connectivity. Hiring managers scan for this exact phrase because it is the core of the job.
2. Quantify your Terraform footprint: Do not just say you used Terraform. Specify how many modules you wrote, what resources you provisioned, and whether you managed state remotely. If you automated Apigee or GKE deployments with Terraform, call that out. The team wants to see infrastructure-as-code discipline, not manual console clicks.
3. Show Apigee integration stories: Apigee experience is a differentiator here. Describe a time you deployed Apigee and configured its networking, such as private service access or load balancing. Explain how you connected DevPortal to backend services. Even if your exposure was limited, be honest about what you configured and what you learned.
4. Prepare for deep networking questions: Expect scenario-based questions on VPC design, Cloud NAT, and firewall rule ordering. Be ready to whiteboard a hybrid connectivity setup using Cloud VPN or Interconnect. Interviewers often ask how you would troubleshoot a DNS resolution failure across projects. Practice explaining your diagnostic steps out loud.
5. Highlight security and IAM decisions: This role owns IAM policies and Cloud Armor. On your CV, mention specific IAM roles you designed and how you enforced least privilege. If you implemented Cloud Armor rules to block threats, quantify the impact. Interviewers will probe how you balance security with developer velocity.
6. Map your Kubernetes and Docker work: GKE is preferred, so detail your cluster management experience. Talk about node pools, autoscaling, and network policies you configured. If you used Docker for local development or CI pipelines, explain how you optimized images. The team wants to know you can run containerized workloads securely on GCP.
7. Address the multi-country context: The role supports teams across Pakistan, India, Kenya, Egypt, and Jordan. Show that you have worked with distributed teams or across time zones. Mention any experience with federated architectures or multi-environment setups. This proves you can handle the complexity of a global enterprise.
8. Bring your certifications to the fore: If you hold Professional Cloud Network Engineer or Professional Cloud Architect, put them in your headline and summary. If you are in progress, state the expected date. These certifications signal that you understand Google's recommended patterns. Pair them with a short story of how you applied that knowledge in a real project.