An application made for this job — a tailored resume and cover letter that speak straight to the posting.
Anblicks is seeking an experienced architect to own end-to-end data and AI program architecture in a client-facing, hands-on role in Dallas. You will connect source systems, applications, cloud infrastructure, data platforms, and downstream consumers, solving hard problems with whiteboards, blueprints, and working code when needed.
You will design target-state architectures, build reference implementations, and drive automation across pipelines, deployment, and operations, while communicating
We are looking for an architect who builds, not one who documents.
At Anblicks, our architects sit at the center of complex data and AI programs — connecting source systems, applications, cloud infrastructure, data platforms, and the downstream consumers who actually use the output. You will own the end‑to‑end picture: how data enters the organization, how it moves, where it lands, how it is governed, and how business teams get value from it.
This is a hands‑on role. You will be in the room when the hard problems come up, and you will be expected to solve them — with a whiteboard, with a blueprint, and with working code when that is what it takes.
Breadth across the enterprise stack You understand how an organization actually fits together — applications, source systems, integration patterns, cloud infrastructure, data platforms, and downstream analytics and AI consumers. You do not need to be the deepest expert in any single one, but you need to know how they connect and where they break.
Hands‑on production experience with Databricks or Snowflake — modeling, performance, cost, ingestion patterns, and governance. Experience with both is a plus.
You design monitoring and alerting into a solution rather than bolting it on afterward. You can debug across the stack — application, integration, infrastructure, and network — and you go deep when the problem is in the data: pipeline failures, silent data quality issues, skew, performance regressions, cost spikes. When another team is stuck, you're the one they call, and you help them find the root cause instead of taking the ticket off their hands.
You can open an IDE and produce working code to prove a pattern, unblock a team, or validate a design. Using AI coding tools to get there faster is not just accepted — it's encouraged. What matters is that you can solve the problem and stand behind the solution.
Your first reaction to repeated manual work is to ask why it isn't automated yet.
You can explain a design to a business stakeholder in outcomes and trade‑offs, and to an engineering team in specifics — and you’re equally credible in both rooms.
This is a client‑facing role. You will be on client calls regularly — presenting architecture, running workshops, handling pushback, and building confidence with senior stakeholders. You should have a track record of owning the technical relationship with a client, not working behind an account or delivery lead.
15–20+ years in technology, with meaningful time in architecture roles on complex, multi‑system environments.
You’ll work across industries and architectures rather than inside one stack for years. Our problems are real, varied, and consequential — and we back architects who want to stay technical.