Solution Architect

FurtherDallas, TX
Hybrid

About The Position

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! You are the architectural conscience of the platform and the technical translator at the front of every client engagement. Half your week is inside the product — reviewing ADRs, holding integration patterns coherent, and partnering with the data architect and senior dev to keep the architecture honest. The other half is in front of clients — taking real operational complexity and turning it into platform configurations the system can actually execute. You are not a slide architect. You write decisions down, defend them with reasons, and change them when the reasons change. This role only works if you genuinely enjoy both sides. The leverage is in the loop between them — what we learn in deployments shapes the platform, and what the platform enforces shapes how we deploy. You will sit in our headquarters in Dallas, TX on a hybrid schedule. The team is in office on Tuesdays, Wednesdays and Thursdays.

Requirements

  • 10+ years of software engineering experience, with at least 4 explicitly accountable for system architecture — Principal Engineer, Staff Engineer, Solution Architect, or equivalent.
  • Production experience with multi-tenant SaaS at meaningful scale. You have personally owned tenant isolation decisions and understand the difference between "we have a tenant_id column" and a defensible isolation model.
  • Deep experience with event-driven or event-sourced systems in production. You have opinions about idempotency, schema evolution, and the cost of getting either wrong.
  • Working fluency in the modern TypeScript/Node ecosystem (NestJS, Next.js, Drizzle, Zod, Postgres, Kafka/Redpanda, Temporal or comparable). You can read the codebase, make changes when it matters, and produce durable architecture artifacts — ADRs, RFCs, decision documents — that someone six months from now can act on.
  • Direct experience leading rooms of senior client or executive stakeholders — consulting, enterprise customer engineering, field architecture, or technical pre-sales. You can translate "the engagement is slipping" into a technical control loop and back again.

Nice To Haves

  • Background in professional services, agency operations, or management consulting — you understand engagement economics from the inside.
  • Observability experience (OpenTelemetry, distributed tracing) at a depth that lets you design for it, not just consume it.
  • Architecture decisions on AI-native or LLM-integrated systems — model gateways, agent orchestration, prompt versioning, or evaluation pipelines.
  • Experience in compliance-conscious environments (SOC 2, HIPAA, GDPR) where audit trails and data residency are first-class concerns.
  • Public writing, conference talks, or open-source contributions that show how you think.

Responsibilities

  • Own the architectural coherence of the platform, ADR backlog, architecture reviews, system shape diagrams, the canonical event envelope, the tenant isolation model. You hold the line on invariants and write down why.
  • Define integration patterns for every external system, identity providers, CRMs, project tools, communication systems, AI providers. You decide how we connect, not just whether.
  • Build and own client deployment patterns, repeatable playbooks from "first connector" to "first signal" to "first governed action." You author them, run the first few personally, and abstract them into reusable configurations as you go.
  • Lead pre-deployment architecture sessions with client technical teams, translating their identity infrastructure, data model, permissions, and compliance posture into a deployment plan the build team can execute.
  • Carry the technical narrative externally. You can sit across from a client CTO, walk them through the architecture, defend it under pressure, and adjust where the pressure is legitimate.
  • Mentor the founding engineering team on architectural reasoning, not by lecturing, but by showing your work in ADRs, reviews, and the way you make trade-offs visible.

Benefits

  • net-zero cost medical option
  • company contributions to your HSA
  • fertility support
  • fully-paid parental leave
  • monthly stipend for your lifestyle spending account
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service