Senior Backend Engineer (Go) at Kake

Role overview

We’re building a talent pool for Senior Backend Engineers specializing in Go . This pipeline role is for engineers with strong backend experience, skilled in building high-performance, scalable systems, and following best practices.

Responsibilities

• Build and maintain scalable backend services using Go.
• Deploy and manage microservices with Kubernetes.
• Manage CI/CD pipelines and ensure smooth deployments.
• Own backend architecture, driving best practices and high-quality code.
• Optimize backend performance for reliability and scalability.

Qualifications

• Strong experience building backend systems in Go .
• Knowledge of SQL and NoSQL databases (PostgreSQL, MySQL, DynamoDB).
• Proficiency with Kubernetes and containerized distributed applications.
• Experience managing CI/CD pipelines and cloud-native systems (AWS, GCP, or Azure).
• Familiarity with microservices, RESTful APIs, and event-driven systems .
• Experience with payment or billing system architecture projects .
• Experience working in a remote environment.

Technology in this role

• AWS: AWS Azure GCP Kubernetes SQL .
• Azure: AWS Azure GCP Kubernetes SQL .
• GCP: AWS Azure GCP Kubernetes SQL .
• Kubernetes: AWS Azure GCP Kubernetes SQL .
• SQL: AWS Azure GCP Kubernetes SQL .
• Go: AWS Azure GCP Kubernetes SQL .
• PostgreSQL: Knowledge of SQL and NoSQL databases (PostgreSQL, MySQL, .
• MySQL: Knowledge of SQL and NoSQL databases (PostgreSQL, MySQL, .
• CI/CD: Manage CI/CD pipelines and ensure smooth .
• DynamoDB: Knowledge of SQL and NoSQL databases (PostgreSQL, MySQL, .

Role-specific candidate guide

Preparation notes based on the employer’s stated responsibilities and qualifications.

Understanding the scope. This Senior Backend Engineer (Go) position at Kake is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “We’re building a talent pool for Senior Backend Engineers specializing in Go . This pipeline role is for engineers with strong backend experience, skilled in building high-performance, scalable systems, and following…” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the software engineering area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Build and maintain scalable backend services using Go.”; “Deploy and manage microservices with Kubernetes.”; “Manage CI/CD pipelines and ensure smooth deployments.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.

How to read the requirements. The listed qualifications include “Strong experience building backend systems in Go .”; “Knowledge of SQL and NoSQL databases (PostgreSQL, MySQL, DynamoDB).”; “Proficiency with Kubernetes and containerized distributed applications.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.

Technology and working evidence. The technology terms associated with this listing are AWS, Azure, GCP, Kubernetes, SQL, Go. Treat this as a set of posting-derived signals, not a guarantee that every tool is used daily or that the list is complete. For each term relevant to your experience, prepare one concrete example: the system or workflow, the part you owned, the alternatives considered, and how you tested reliability, security, performance or usability as appropriate. If you have not used a named tool, explain the closest related system you have worked with and how you would ramp up; do not relabel that experience as direct production use. If the source.

About Kake

Kake describes itself as a remote-first community of experienced software engineers that helps client teams add individual engineers or full engineering groups. Its model combines technical vetting and human selection with AI-supported processes; Kake engineers work as dedicated members of client teams rather than as a separate outsourced delivery queue.

The company recruits across frontend, backend, mobile, quality engineering, data and DevOps. Its public hiring pages emphasize end-to-end ownership, collaboration with product and design, and engineering judgment. The exact client, product, team structure and employment terms can vary by opening, so candidates should verify those specifics in the individual listing.

Browse job categories

Related jobs

• Senior Backend Engineer, External Security at Horizon3 — Horizon3
• Senior Backend Engineer, Growth and MSSP at Horizon3 — Horizon3
• Senior Backend Integrations Engineer at Horizon3 — Horizon3
• Senior Autonomous Defense Backend Engineer at Horizon3 — Horizon3
• Senior Backend Engineer, Precision Defense at Horizon3 — Horizon3
• Backend Engineer, Cloud Security at Linro — Linro