Vetted Kibana Professionals

“Backend/data engineer with strong AWS production experience spanning FastAPI microservices and large-scale data pipelines. Has delivered containerized Python services on EKS with Terraform/Helm/GitHub Actions, implemented robust auth/secrets practices, and owned ETL reliability (Glue/S3/Redshift) including incident response and idempotent reruns. Demonstrated SQL tuning on 50M-record ETL workloads to remove SLA misses and improve reliability.”

“Frontend engineer who led an internal React + TypeScript admin dashboard end-to-end, including a collaboratively owned component system and complex RBAC/permissions workflows. Emphasizes scalable architecture and correctness using React Query (mutations + query invalidation), centralized permission logic, and TypeScript for safe evolution, plus performance tuning for data-heavy tables and pragmatic MVP-driven delivery with gradual rollouts.”

“Frontend-leaning engineer who shipped an end-to-end map-based discovery feature in a React Native mobile app, integrating location-based REST APIs with strong UX polish (loading/empty/error states) and cross-platform performance fixes. Also has experience building a Python backend with JWT auth and layered service structure, plus prior infrastructure work setting up centralized logging and monitoring.”

“Backend/full-stack engineer who owned a cloud-native, AWS-based microservices backend for an HRIS product used by ~10,000 users, including onboarding and workflow orchestration. Strong production focus on event-driven architecture, idempotency/retries, observability, and developer-friendly API design (OpenAPI, versioning, JWT), plus hands-on Selenium automation for resilient checkout-style flows.”

“Full-stack engineer with strong AWS operations experience who helped replace a long-standing manual logistics reporting process by building a production-grade, event-driven On-Time-Performance rules system. Personally owned the Vue-based rule configuration frontend end-to-end (design collaboration through QA/UAT and post-release support) and measures success via accuracy validation against historical data, reduced manual adjustments/tickets, and system latency/error metrics.”