Track This Job
Add this job to your tracking list to:
- Monitor application status and updates
- Change status (Applied, Interview, Offer, etc.)
- Add personal notes and comments
- Set reminders for follow-ups
- Track your entire application journey
Save This Job
Add this job to your saved collection to:
- Access easily from your saved jobs dashboard
- Review job details later without searching again
- Compare with other saved opportunities
- Keep a collection of interesting positions
- Receive notifications about saved jobs before they expire
AI-Powered Job Summary
Get a concise overview of key job requirements, responsibilities, and qualifications in seconds.
Pro Tip: Use this feature to quickly decide if a job matches your skills before reading the full description.
Position Name – GCP Golang Developer
Type of hiring – Subcon
Duration – Till end of year (can extend, project expected to be about 3 years total)
Location – CST or EST Time zone only (100% remote)
Capital One is looking at TEKsystems to partner with them to help prepare their GenAI Lab on their multi cloud infrastructure. There is demand from the enterprise to start leverage AI services but before putting them into production they want to test in their sandbox.
Job Description:
GCP - Golang (Infrastructure as Code) Engineer
Top Skills Details
- 5+ Years of deep software engineering: Golang to develop code to deploy cloud environments automatically at scale.
- Infrastructure as Code (IaC) - can use Golang or Terraform
- Experience with Landing Zones in GCP
- Strong GCP Cloud administration experience
- Strong Golang Development experience, building Microservices and Rest APIs
- Unit Testing - test driven development
- BDD - behavior driven development leverage Cucumber
- Core Networking understanding - routing, load balance, HTTP
- Experience developing Restful APIs
- Open ID and Federated ID service experience would be nice to have
Major plus:
- OPA - Open Policy Agent
- REGO - Rego is a general-purpose policy language, which means that it works for any layer of the stack and any domain. The primary purpose of Rego is to accept JSON/YAML inputs and data that are evaluated to make policy-enabled decisions about infrastructure resources, identities, and operations.