NetBrain
Data Analytics Engineer
About this role
NetBrain seeks a Senior Analytics Engineer to architect and build the company's first cloud data warehouse, establish ELT pipelines, and create a governed transformation layer that serves as the foundation for reliable business analytics and internal AI use cases. You'll own the entire technical infrastructure—from raw data ingestion through production models—while partnering with business teams to define metrics and reporting standards.
What you'll do
- Design and maintain NetBrain's cloud data warehouse infrastructure
- Build and own ELT pipelines ingesting data from GTM, Finance, and Product systems
- Develop and document warehouse transformations and curated data models for analytics consumption
- Establish data quality, governance, lineage, and access controls across the warehouse
- Design the semantic layer and metric definitions powering BI tools and executive reporting
- Create data models for product usage, customer adoption, account health, and go-to-market reporting
What they're looking for
- SQL and analytical modeling
- Cloud data warehouse platforms (Snowflake, BigQuery, or equivalent)
- dbt or SQLMesh transformation frameworks
- ELT pipeline design and orchestration
- Python or scripting for automation and validation
- Data quality and testing frameworks
- Data governance and documentation practices
- Semantic layer and BI tool design
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
NetBrain
NetBrain builds a network automation platform powered by AI agents and retrieval systems designed for enterprise network management. The company is hiring senior engineers focused on developing robust, scalable AI systems and solving complex network automation challenges.
View all jobs at NetBrainLikely interview questions
- Walk us through your experience architecting a cloud data warehouse from scratch—what platform did you choose and why?
- Describe a time you owned production data models that other teams depended on; how did you ensure reliability and handle breaking changes?