Ramp on the StreamModule pipeline and the cork/uncork backpressure model. Walk the Oct 15 / Oct 22 DB incidents and the duplicate-message incident. Land a scoped pipeline or provider-abstraction improvement.
Own a slice of the BullMQ → Kafka consolidation. Ship event-driven OTEL instrumentation for at least one critical pipeline stage. Harden one provider plugin path so a new model can be added without core changes.
Drive a measurable reliability or latency win on the call path. Be the backend owner that agents and FDE teams pull in for design reviews on new providers and pipeline changes.

You’ve built real-time or streaming systems in production — media pipelines, streaming data, or event-driven backends. You’ve debugged a backpressure cascade.
You have opinions on queue architecture (BullMQ, Kafka, Temporal) and when each is the right fit.
You’ve built plugin or adapter architectures — extending base classes cleanly, with decoupled implementations.
You’ve operated Postgres at scale: connection pooling, read replicas, schema migrations (Liquibase or similar).
You instrument with OpenTelemetry and think in event-driven traces, not just logs.
TypeScript + Node.js + NestJS. The codebase is huge NestJS, but a strong systems-thinking engineer ramps fast — language doesn’t gate the hire.

Member of Technical Staff – Core Backend

Key skills