Senior TypeScript Backend engineering

Our client, a 3rd-generation management consulting firm. They are now looking to add to their team and are hiring a Senior TypeScript Backend Engineer can be 100% remote

Project Description
Client is building an agentic workflow-orchestration platform in-house, starting with vulnerability discovery as its first workflow. The client's engineering team with two architect-level, hands-on TypeScript engineers plus a part-time solution-partner subject-matter expert, working the priorities the client sets rather than owning delivery of a fixed scope end to end.

Keywords:

• Workflow/orchestration engines (Temporal, Dapr, AWS Step Functions)
• Distributed systems and event-driven architecture
• Kubernetes
• Senior TypeScript backend engineering

Required (Must have)

• Tech lead or team lead level TypeScript development: writes production code hands-on as a lead, not solely reviewing architecture or delegating implementation.
• Direct experience building on workflow/orchestration engines such as Temporal, Dapr, or AWS Step Functions.
• Strong distributed-systems background: message queues/pub-sub (e.g. Kafka), event-driven architecture, and retry/idempotency patterns.
• Kubernetes or Red Hat OpenShift experience: deployment, scaling, and networking basics.
• Enterprise architecture background sufficient to work from a design document and exercise sound, independent judgment in a fast-moving environment where scope is still being designed and priorities may shift.

Nice to have (ideal to have)

• Comfort evaluating and comparing infrastructure platforms and making build-vs-buy recommendations.
• Experience in regulated or financial-services environments: governance and audit-trail thinking.
• Integrate LLM/AI agent tool-use into platform workflows as directed by the client.
• Duties to be performed (Details around what the consultant would do on the project)
• Augment the client's engineering team building the agentic workflow-orchestration platform, per client direction and prioritization.
• Evaluate and recommend workflow/orchestration engine and infrastructure choices.
• Design and implement composable, polyglot workflow steps within the orchestration harness.

Environment (Details around what technologies are used at the client)

• TypeScript
• Temporal or a comparable workflow orchestration engine
• Kubernetes or Red Hat OpenShift
• Kafka or a comparable message queue/pub-sub system
• Containerized, polyglot workflow steps