MATCH REPORT — Senior Backend Engineer 1. MATCH SCORE - Hard skills & tools: 26/40 - Experience & seniority fit: 27/30 - Keyword / ATS alignment: 13/20 - Soft skills & domain signals: 8/10 WEIGHTED TOTAL: 74/100 Strong, mentor-ready senior engineer whose distributed-systems experience is largely transferable, but the stack (Java vs Go) and observability tooling are the gating gaps. 2. ATS KEYWORD MAP MATCHED: PostgreSQL, Kafka / event-driven architecture, AWS, CI/CD, mentoring, microservices, API design PARTIAL: Kubernetes (runs on AWS ECS — container orchestration experience, but not K8s specifically); gRPC (built REST APIs, adjacent but not gRPC) MISSING (HIGH PRIORITY — listed as "must have"): Go, Kubernetes, gRPC, observability (Prometheus/Grafana) 3. GAP ANALYSIS 1. Go (true gap) — the JD's #1 must-have; resume shows Java/Spring only. Hardest blocker. 2. Kubernetes (presentation gap) — candidate runs containers on ECS; likely understands orchestration but never names K8s. Closable on paper, real on the job. 3. Observability (true gap) — no Prometheus/Grafana mention; required. 4. gRPC (presentation gap) — strong API design, just not this protocol. 4. PRIORITIZED FIX PLAN 1. Add a "Go (learning / project)" line only if genuinely true — do not claim production Go you don't have. 2. Reframe ECS work to surface orchestration depth: "Operated containerized microservices in production, including scaling and zero-downtime deploys [INSERT YOUR REAL METRIC: e.g., X services / Y deploys per week]." 3. Surface any monitoring you actually used: "Instrumented services for [INSERT YOUR REAL TOOL] dashboards and alerting." 4. Quantify the mentoring and reliability work: "Mentored [INSERT REAL NUMBER] engineers; improved service uptime to [INSERT REAL METRIC]." 5. VERDICT Apply after edits — but only if you can honestly position Go as in-progress. The systems thinking and seniority are there; the gap is stack-specific. Worth a tailored application, not a stretch.