Technical Account Manager

Role Overview

Customer‑embedded technical counterpart at one of NX1’s flagship enterprise accounts. The role is structured roughly 70% solution architecture and technical advisory + 30% TAM‑flavored work.

• Act as the NX1 technical voice across the customer’s daily technical operations – architecture review boards, security reviews, design discussions, integration planning, and platform governance forums.
• Establish architectural credibility with the customer’s senior engineers, architects, and platform team – earning trust within the first 20 minutes.
• Translate between the customer’s technical reality and NX1’s engineering team – handling escalations, design clarifications, and roadmap requests while maintaining fidelity.
• Read design documents, ask the right questions, and produce written technical artifacts that the customer’s review boards take seriously.
• Provide technical context that informs but does not replace the work of the Principal SA (when one is deployed at the same account) and the FDEM (when an engagement is active).

• Own the NX1‑side technical context for each account – keeping engineering, FDEs, product, the SAD, and the AE aligned on the customer’s technical status.
• Route customer‑side technical escalations to the appropriate resource at NX1 without becoming a bottleneck.
• Maintain working relationships with the customer’s technical middle layer – senior ICs, tech leads, and engineering managers, not just architecture leadership.
• Support the AE/SAD on technical pre‑renewal conversations and expansion‑context preparation, without owning the commercial motion.
• Navigate vendor governance at a major enterprise – third‑party risk reviews, audit responses, change management, and vendor due diligence.

• 10–16 years in enterprise data/cloud architecture as an SA, principal engineer, TAM, or equivalent.
• At least one prior multi‑year embedded engagement at a Tier 1 enterprise customer (bank, top‑tier insurer, public‑sector flagship, automotive OEM, healthcare system).
• Hands‑on or recent hands‑on depth in the modern OSS data stack – Spark, Trino, Airflow, Iceberg, Kubernetes, S3‑compatible object storage, Kafka – at scale.
• Track record of being the customer’s technical go‑to person at a prior vendor engagement – named examples of senior architects requesting you by name on specific problems.
• Strong written technical communication – design memos, architecture decision records, exec briefs that withstand senior technical review.
• Willingness to be on‑site at the customer in Charlotte, NC (primary) and NYC (secondary) at 80%+ cadence for the WF deployment.
• For deployments at large banks: deep familiarity with bank IT culture and governance (risk and control frameworks, TPRM, change management, audit cycles).

• Prior background as a Forward Deployed Engineer at Palantir, Resident SA at Databricks, Principal SA at Snowflake/Confluent, or Customer Engineer at a top data platform vendor.
• Open‑source contributions to NX1 stack components (Iceberg, Spark, Trino, Airflow).
• Conference presence at Subsurface, Trino Summit, Airflow Summit, Data + AI Summit.

• A collaborative team culture built on curiosity and respect.
• Challenging work where your contributions clearly matter.
• A leadership team that invests in learning and development.
• The opportunity to work at the intersection of cloud, data, and AI innovation.