Public Genie Platforms website, shown for company context. The internal product described in this case is not shown.

Public Genie Platforms website, shown for company context. The internal product described in this case is not shown.

Genie Platforms

AI SDR / GTM platform

Senior Software Engineer · AI Platform

Server-side platform for conversational AI used by sales, RevOps, and go-to-market teams — an AI SDR that has to run as production services, not a chat demo.

01Problem

Conversational GTM workflows had to run as evented production services: APIs, partner integrations, and several data stores — not a standalone prototype that dies when a third-party call fails.

02Selected contributions

Owned server-side technical direction and roadmap for the Genie Platforms backend. Designed the NestJS microservice layout, APIs, and Kafka paths, and wired persistence across PostgreSQL, MongoDB, and Redis plus partner integrations. The GTM clients are the product surface; this engagement was the services underneath them.

  • Server-side microservice architecture and API contracts
  • Kafka streaming paths between services
  • Persistence across PostgreSQL, MongoDB, and Redis
  • Partner and third-party integrations on the AWS / Kubernetes path

03System context

NestJS services expose APIs, stream work over Kafka, persist in PostgreSQL, MongoDB, and Redis, and call partner APIs. The platform runs on Kubernetes on AWS. Amplication was in the scaffolding/tooling mix; it is not claimed as the production architecture.

  • GTM product surfaceOutside my scopeCalls the APINestJS servicesMy scope
  • NestJS servicesMy scopeStreams workKafka
  • NestJS servicesMy scopePersists dataPostgreSQL · MongoDB · Redis
  • NestJS servicesMy scopeCalls an external systemPartner APIsOutside my scope
  • NestJS servicesMy scopeRuns onKubernetes on AWS

My scope in the system: NestJS services

Implementation tools

Amplication (scaffolding, not the production architecture). Not runtime services.

04Scale & constraints

  • Event-driven microservice backend
  • Polyglot persistence: PostgreSQL, MongoDB, Redis
  • Third-party and partner API integrations
  • Kubernetes on AWS as the runtime

05Outcome

A production microservice backend on Kubernetes / AWS, with Kafka-backed integrations instead of a single service talking to every store. Throughput and conversion figures are not published.

  • Microservice backend in production on Kubernetes / AWS
  • Kafka paths across PostgreSQL, MongoDB, and Redis

06Stack

  • Node.js
  • NestJS
  • KafkaJS
  • PostgreSQL
  • MongoDB
  • Redis
  • Kafka
  • Docker
  • Kubernetes
  • AWS
  • Amplication

No verified public metrics are published for this engagement.

Categories: AI, SaaS

Year: 2024

Open live project ↗

Related services