Hard Requirements
GCP Hands-On Experience: Real production experience with GCP, not just familiarity. You've worked with GKE, Cloud SQL, Memorystore, Cloud Storage, and Secret Manager, and can navigate the GCP ecosystem confidently.
Kubernetes in Production: Proven track record deploying, operating, and scaling Kubernetes workloads in production (GKE preferred). You understand autoscaling, resource tuning, networking, and how to debug a cluster under load.
Infrastructure as Code: Deep, hands-on experience with Terraform and Helm — building reusable, maintainable infrastructure rather than one-off scripts.
CI/CD: Strong experience building and improving CI/CD pipelines (GitHub Actions, Cloud Build, or similar) for fast, safe, repeatable deployments.
Observability: Hands-on experience setting up monitoring, structured logging, distributed tracing, metrics, and alerting (Prometheus, Grafana, or similar).
Additional Technical Skills
- Strong proficiency with containerization (Docker)
- Experience with workflow orchestration (Temporal or similar) is a strong plus
- Knowledge of cloud security, secrets management, authentication/authorization (OAuth 2.0, JWT), and data protection
- Familiarity with PostgreSQL operations (Cloud SQL), backups, and migrations
- Node.js / TypeScript experience is a plus (our current backend stack)
- Experience operating infrastructure in a regulated / financial-services context is a plus
Mindset & Approach
Production Experience: You've been through production launches before and know what it takes — setting up infrastructure, handling edge cases, ensuring reliability, and managing the inevitable surprises.
Pragmatic Perfectionism: You balance technical excellence with business velocity; you know when to refactor and when to ship quickly.
Ownership Mentality: You're proactive, resourceful, and accountable for your work; you don't wait to be told what to do.
Systems Thinking: You understand how components interact, design for reliability and maintainability, and think beyond your immediate task.
Clear Communication: You can explain technical decisions to non-technical stakeholders, document your work, and participate constructively in technical discussions.
