Snowflake Architect

Job Description

Job Description

Lead Data Engineer / Snowflake Data Architect - Houston, TX

iSphere is looking for a Lead Data Engineer / Snowflake Data Architect for a long-term hybrid opportunity in Houston. You do need to live in the Houston area.

Our client is building out a modern Snowflake platform for Trading Risk, and they need someone who has done more than inherit an environment and keep the lights on. They want someone who can help decide how this thing should be built, get their hands dirty building it, and keep the architecture from becoming a pile of exceptions nobody understands a year from now.

You will be working across Snowflake architecture, data engineering, security, governance, ingestion, transformation, CI/CD, monitoring, performance, and cost. In other words, the platform stuff that is easy to ignore early and painful to fix later.

The work is being delivered in waves. Each wave needs to solve an actual Trading Risk problem while also making the platform better for the next team that comes along. That means reusable patterns, sane standards, clean security, and data people can trust.

What we need:

• Strong hands-on Snowflake experience

• Enterprise data architecture experience

• Data modeling and warehouse/lakehouse design

• Snowflake performance tuning and cost optimization

• RBAC, roles, security groups, authorization, and access controls

• Experience designing ingestion, transformation, and publishing patterns

• Data governance, metadata management, semantic modeling, and ontology concepts

• CI/CD, version control, automated testing, and DataOps

• AWS experience including S3, Glue, Lambda, Athena, EMR, and Redshift

• Experience working with Trading, ETRM, ERP, financial, or other complex transactional data

• Ability to explain architecture decisions to technical and business people without making either group want to leave the room

Trading Risk experience would be a big plus. Energy trading, commodities, financial services, or another environment where a bad number can become a very expensive conversation will also get our attention.

We would especially like someone who has already helped build reusable data platform capabilities. Not “I built a pipeline.” More like “I helped create the standards and patterns the next ten pipelines used.”

You need to be comfortable talking architecture and then opening Snowflake and proving the idea actually works. If you prefer drawing boxes and arrows while somebody else figures out the hard part, this probably is not your role.

If Snowflake, enterprise data engineering, and complex Trading Risk data are your kind of problem, we should talk.