# Databricks consulting in Charlotte, NC > Charlotte is the second-largest banking centre in the United States by assets, with energy and a growing fintech layer around it, and the buying culture is conservative, audit-first and unimpressed by a demo. If that describes your company, it describes how we build. Canonical: https://www.techfabric.com/databricks-consulting-charlotte Serving: Charlotte, Concord, Gastonia, Rock Hill, Winston-Salem, Greensboro Headquarters: 1530 E Williams Field Rd, Ste 201, Gilbert, AZ 85295. No office in Charlotte. --- ## Why Charlotte work is our work A Teradata or SQL Server estate with decades of inputs nobody dares retire won't migrate until someone can show the lineage of every number. Unity Catalog records that by default once the warehouse is on Databricks, so the migration and the governance become one project instead of two budgets. Charlotte's banks and their model risk guidance made it a requirement first, and a utility or a health system here wants the same lineage. ## Work a buyer here would recognise The iLending work automated lead and loan officer assignment, rate sheet processing and stipulation document management, and improved CRM integration and API performance. Manual errors dropped and agent onboarding got faster, which is what a bank's lending operations team wants from automation sitting on the path of a credit decision. ## The regulator asks about the model Bank of America and Truist both keep their headquarters in Charlotte, and banks of that size answer to SR 26-2, the model risk guidance the Federal Reserve, the OCC and the FDIC issued in April 2026 to replace SR 11-7. It takes a risk-based approach tailored to each bank's model risk profile, and at a bank this size the automated credit and fraud decisions are the ones model risk looks at first. ## Questions ### Is there a Databricks community in Charlotte we can plug into? There is. The Charlotte Databricks User Group holds occasional events through the year in Uptown, and in March 2026 it co-hosted an invite-only dinner with Databricks for senior data, AI and finance leaders. UNC Charlotte's Analytics Frontiers Conference each spring is the other date worth keeping. We organise the Gilbert Databricks User Group, which meets at our office in Gilbert, Arizona. If your data team wants to compare notes with the engineers who'd work on your platform, we'll set up a call between the two teams. Sources: [The Charlotte Databricks User Group](https://usergroups.databricks.com/events/details/databricks-user-groups-charlotte-databricks-user-group-presents-the-ai-leaders-guide-to-cfo-conversations/), [the Gilbert Databricks User Group](https://usergroups.databricks.com/gilbert-databricks-user-group/) ### Can Databricks bring together data from a Charlotte health system's hospitals? Slowly enough to keep it trustworthy. Advocate Health, headquartered in Charlotte, lists 69 hospitals and more than 1,000 sites of care across eight states, and at that scale we'd expect every hospital's data to look a little different. We'd land each source system untouched, then map it to one shared model in Lakeflow pipelines with a test on every mapping. The pipelines carry the hospital and source system as columns on every row, and Unity Catalog lineage shows which feeds each table came from, so a quality measure that looks wrong for one site can be traced to the feed behind it. Sources: [Advocate Health](https://www.advocatehealth.org/about) ### How should a Charlotte data team with many juniors lock down production? With a pipeline as the only way in. We'd give juniors a development catalog with production-shaped data, masked where it needs to be. Production jobs run only from a pipeline that deploys reviewed code, so nobody, junior or senior, edits a production table by hand, and a junior's change reaches production through a pull request someone senior approves. Those juniors can keep learning on the job, too. UNC Charlotte's School of Data Science teaches its graduate programme in the evenings at the Dubois Center in Center City. Sources: [UNC Charlotte's School of Data Science](https://dsba.charlotte.edu/about-us/program-overview) ### How do you handle model risk management? An automated decision records what it was given, what it decided and under whose authority, because a bank's model risk team will ask for exactly that, whatever the regulators' guidance says is in scope. Explainability is designed in, since a system that did not record its reasoning cannot have it added later. ## What databricks consulting covers ### Migration off Snowflake, Synapse and Teradata Run through TechFabric Airlift, with executable playbooks for twenty-seven source platforms, signed migration certificates, and a cutover you can reverse at two in the morning. ### Unity Catalog governance Catalogue and schema design, a grant model expressed through groups, row filters and column masks, and lineage that survives a refactor. The boundary your agents and Power BI inherit. ### Lakeflow pipelines Ingestion and Lakeflow jobs with schema evolution handled rather than hoped for, medallion boundaries drawn on purpose, and jobs that recover instead of restarting from zero. ### Databricks Apps and agents Applications that run inside the workspace under their own service principal, and agents on Unity Gateway that inherit catalogue permissions instead of routing around them. ### Genie and AI/BI Metric definitions agreed with the person who owns the number, and a benchmark suite Genie has to keep passing, so the answer holds up when finance checks it. ### Cost that somebody can defend Cluster policies, warehouse sizing, file layout and the queries that actually pay. Instrumented at build time rather than discovered on an invoice. ## Working with us from Arizona Arizona does not observe daylight saving, so we are two hours behind you from November to March and three hours behind from March to November. That leaves most of your afternoon overlapping our morning, which is usually enough. Most delivery is remote or hybrid. We travel for discovery, workshops and the opening weeks of a build.