WE’RE HIRING! If you love data and are looking for unlimited growth opportunities, we want to talk with you about joining Further. Further is a data, cloud, and AI company whose focus is helping companies turn raw data into the right decisions.

We have an award winning culture of extraordinary people. Our purpose is to enable people to thrive so that businesses can thrive. We believe that the work you do should matter - it should be meaningful to you professionally and personally, and it should have a positive impact on both you and our clients.

If this sounds exciting to you, let’s chat! Senior Software Developer You are the engineer who can take a hard problem from data layer to UI to model gateway and back without dropping the thread. Full-stack is not a compromise here — it's the job.

LLM integration is part of the everyday work, not a side project. You'll write NestJS services that publish events through a well-defined SDK, consume those events into projections, expose them through APIs, build the console UI that makes them useful, and integrate LLMs as governed components inside workflows — with prompt versioning, evals, observability, and cost discipline. The codebase is strict TypeScript, opinionated, and well-documented.

Every exported symbol has a JSDoc block. Every architectural decision has an ADR. Every PR ships with docs.

You'll match that bar from day one. You will sit in our headquarters in Dallas, TX on a hybrid schedule. The team is in office on Tuesdays, Wednesdays and Thursdays.

What experience should you have: 7+ years of production TypeScript and Node. You write strict TypeScript by reflex; you don't reach for any . Production experience with NestJS or a comparable Node framework at the level where you understand the request lifecycle, dependency injection, and the trade-offs.

js (App Router preferred) and modern React: server components, streaming, client/server boundary discipline. LLM-powered features shipped to production. You've dealt with prompt drift, eval design, hallucination handling, and the cost of getting any of those wrong.

Postgres at a working level: migrations, index design, query plan analysis, trade-off reasoning. Event-driven architecture experience: pub/sub, idempotent consumers, eventual consistency, ordering, retries, dead-letter behavior. Strong testing instincts: unit, integration, end-to-end.

You don't ship without tests and you care about the difference between tests that pass and tests that matter.

Nice To Have

Drizzle ORM, Temporal, or Redpanda/Kafka in production. OpenTelemetry beyond surface-level — sampling strategy, semantic conventions, custom instrumentation. Design system contribution — component libraries, accessibility patterns, design token discipline.

Agent frameworks (LangGraph, custom orchestration), eval tooling (Braintrust, LangSmith), or prompt versioning systems. Open-source contributions to the TS/Node/Next ecosystem. What you’ll be doing in this role: Backend services in NestJS: API design, request validation with Zod, event publishing through the canonical SDK, projection consumers, RLS-aware database access.

You write the service, the tests, and the docs. js console: App Router, server and client components, the in-house design system, real-time UI patterns, the widget framework. You make complex platform state feel direct and obvious to operators.

LLM integration: agent orchestration inside the workflow runtime, prompt engineering with version control, evaluation harnesses, model gateway usage, structured output validation, retry and fallback logic. You treat model calls as production code, not prompts in a notebook. Observability: OpenTelemetry traces, structured logs, meaningful metrics on every meaningful surface.

If a customer reports a problem, your code should make finding it trivial. Engineering culture: you set the bar for engineers who join after you. The next hires learn from your PRs.