Further
Technology
DataArchitect
Neural analysis suggests this role is
optimal for Senior candidates.
“Data Architect at Further. Skills: Data architecture, Event-sourced systems, Postgres, Streaming platforms, Analytical data infrastructure, AI/ML data infrastructure, RAG systems. Define event envelope strategy. Define schema evolution strategy”
Industry & Context.
Schema evolution problem; Tenant isolation requirements; AI workloads; Query plan analysis; Data volume; Schema evolution; Tenant isolation; AI workloads; Data governance; Data lineage; Data retention; Data deletion; Audit story; Operational playbook; Projection rebuilds; Replay procedures; Schema migrations; Vector index maintenance; Capacity planning
What They're Looking For.
Must Have
10+ years data engineering experience, 10+ years data platform experience, 10+ years database architecture experience, 3+ years architecture ownership, Production experience event-sourced systems, Implemented event envelope, Evolved event envelope, Dealt with upcaster chain, Deep Postgres expertise, Schema design expertise, Indexing expertise, Query plan analysis expertise, RLS expertise, Streaming platforms experience, Production analytical data infrastructure experience, Warehouse design experience, Modern OLAP patterns experience, Hands-on AI/ML data infrastructure experience, Shipped RAG system, SQL proficiency
Nice to Have
Drizzle ORM production depth, Prisma ORM production depth, TypeScript ORM production depth, Workflow engine experience, Feature stores background, ML pipelines background, Model evaluation infrastructure background, Semantic layer experience, Compliance experience
What You'll Do.
Define event envelope strategy
Define schema evolution strategy
Define upcaster chaining strategy
Define projection rebuild strategy
Define transactional data layer
Design Postgres schema
Implement tenant isolation
Define indexing strategy
Define query patterns
Define migration discipline
Define read-side architecture
Design projection design
Design materialized views
Define semantic layer
Define AI/ML data infrastructure
Define embedding pipelines
Define feature stores
Define data retention policies
Define data deletion policies
Create operational playbook
Create projection rebuild procedures
Create replay procedures
Create schema migration procedures
Create vector index maintenance procedures
Create capacity planning procedures
How You'll Work.
Team & Collaboration
Work with Solution Architect; Work with Senior Developer
Full Job Description
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! Data Architect You own the data spine of the platform: the canonical event envelope, the multi-tenant transactional store, the read-side projections that power every console view and API response, and the AI/ML data infrastructure that makes the system intelligent rather than just instrumented. This is not a specialist role. We are hiring one person who has done all three surfaces at production depth and can hold the trade-offs simultaneously. The data volume is significant, the schema evolution problem is hard, the tenant isolation requirements are unforgiving, and the AI workloads sit on top of all of it. If any of those three surfaces feel uninteresting, this isn't the role. You'll work shoulder-to-shoulder with the Solution Architect on the canonical data model and with the Senior Developer on implementation. You write the migration playbooks, the upcaster chains, the projection rebuild procedures, and the runbooks that let us sleep at night. 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: 10+ years of data engineering, data platform, or database architecture experience, with at least 3 owning the architecture, not just the implementation. Production experience with event-sourced systems. You have personally implemented or evolved an event envelope, dealt with the
Applying for this Data Architect role?
Most applicants get filtered before a human reads their resume. See if yours makes the cut.
How to Apply on Greenhouse
- Create a Greenhouse profile before applying — it saves time across multiple applications.
- Upload your resume as a PDF; the parser handles it better than Word.
- Answer all knockout questions carefully — wrong answers auto-reject before a human sees you.
- Enable email notifications to track application status in real time.
ANONYMOUS · UNFILTERED
What do employees actually say about Further?
Real rants from real employees. Read before you apply.