Golang Developer - Senior

Job Description

Join our Realm team, where you’ll design and develop command-line tools, developer productivity utilities, and automation pipelines that simplify the testing resource reservation process (Phoenix, ECG, TCU, SYNC4). The goal of this role is to enable developers to spend less time maintaining testing hardware pipelines and more time innovating. This is a hands‑on senior engineering role focused on Golang, CLI tooling, and Dev Ops pipelines.

Candidates must bring strong technical depth and practical experience building developer infrastructure and automation tools, not just application features.

• Design and implement functionalities for Golang-based command‑line tools.
• Develop and implement unit, integration, and end‑to‑end tests.
• Write technical specifications for new features and improvements.
• Actively participate in Agile ceremonies and contribute to a culture of continuous improvement.
• Contribute to process improvements, CI/CD pipelines, and toolchain upgrades.

• Application Development Expectation:
  • Example: I expect the candidate to drive the development lifecycle, ensuring that the codebase is modular and adheres to SOLID principles. They should be able to perform deep code reviews that focus not just on logic, but on the long‑term maintainability and extensibility of the feature.
• Application Support Expectation:
  • Example:
    Should be proficient in ‘Observability.’ This means setting up structured logging, distributed tracing (Cloud Trace), and meaningful SLIs/SLOs. They should be able to lead a Root Cause Analysis (RCA) after an incident and implement preventative measures to ensure the issue does not recur.
• Application Testing Expectation:
  • Example: I expect the candidate to be far beyond simple unit tests. They should be capable of designing/implementing a ‘Testing Pyramid’ that includes unit tests, integration tests using test containers, and end‑to‑end (E2E) contract testing to ensure that changes in one service do not break dependent systems.
• Docker Expectation:
  • Example:
    Ability to create optimized, multi‑stage Docker builds to keep image sizes small and reduce the attack surface. They must demonstrate knowledge of container security, such as running processes as non‑root users and scanning images for vulnerabilities before they reach the registry.
• Google Cloud Platform Expectation:
  • Example:
    Able to navigate the GCP Console and CLI fluently. More importantly, they should be able to provision infrastructure using Terraform, manage IAM roles with the principle of least privilege, and choose the right tool for the job (e.g., Pub/Sub for async messaging vs. Cloud Tasks for scheduled execution).
• Sonar Qube Expectation:
  • Example: I expect the engineer to know how to integrate Sonar Qube (or experience with equivalent static analysis tooling) into a CI/CD pipeline to automate code quality checks. They should understand how ‘Quality Gates’ are defined and enforced that block pull requests if they introduce security vulnerabilities, technical debt, or if code coverage falls below a certain threshold (e.g., 80%).

• GCP Cloud Run, Go, API, Application Design, Application Development, Application Support, Application Testing, Docker, Google Cloud Platform, Sonar Qube
• GCP Cloud Run Expectation:
  • Example: I expect the engineer to configure Cloud Run for production‑grade workloads, including setting up custom VPC connectors for private database access, managing secrets via Secret Manager, implementing traffic splitting for canary releases, and optimizing ‘cold start’ times through min‑instances and optimized container entry points.
• Go Expectation:
  • Example:
    Beyond basic syntax, the candidate must demonstrate expertise in Go routines and channels for concurrency, implement robust error handling patterns, and write performant code that avoids memory leaks.
• API Expectation:
  • Example:
    Should design RESTful or gRPC APIs using OpenAPI/Swagger specifications. I expect them to implement advanced patterns like idempotency keys for POST requests, versioning strategies (header vs. URL), and security protocols such as OAuth2/OIDC and rate limiting to protect the backend.
• Appli…