Staff Data Engineer, Platform Administration
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Include section only when posting has real specific content. Avoid filler like "commensurate with experience". Need to extract content.
Let's parse the description.
First paragraph: description of Realtor.com. That's likely "About the company" but not a required heading. Could be part of "About the role"? Actually "About The Role" heading appears later. The initial paragraph is company overview; we could include as a
before sections? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text.
Thus we need to decide which sections have content.
From posting:
- About The Role: paragraph after that heading: "We have an exciting and unique opportunity for a motivated and energetic Staff Software Engineer to join the Realtor.com Data Operations team. In this position, you will lead the administration, optimization, and strategic evolution of our enterprise Snowflake Platform to support data-driven decisions across the organization. You will develop and maintain best practices for data warehouse management, build sophisticated monitoring and optimization tools, ensure enterprise-grade security and compliance, and mentor engineers on Snowflake administration. You will incorporate DevOps practices, learn about and leverage new technologies, work with an experienced team of engineers, and be part of a team that has a lot of fun along the way!"
That's prose.
- What You'll Do: list of duties (many bullet-like sentences). Should be a list under Responsibilities (or maybe "What You'll Do" corresponds to Responsibilities). We'll create a section
Responsibilities
with - items.
- What You'll Bring: list of qualifications/experience/skills. Could be split into Requirements, Qualifications, Skills. The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide based on content. The list includes: 8+ years experience, 4+ years Snowflake, deep technical knowledge, strong proficiency in SQL, proficiency in Python, ability to manage requests, demonstrated experience driving technical initiatives, experience with cloud architectures, experience using IaC, experience building monitoring tools, strong understanding of data security, ability to mentor, driven engineer, Bachelor's degree. Then "Nice to Have Experience:" list.
Thus we could have:
Requirements
with the mandatory items (maybe up to Bachelor's degree). Or we could separate Qualifications (education) and Skills (technical). But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content.
We have content for Requirements (experience, skills). Qualifications maybe education (Bachelor's degree). Skills maybe technical proficiencies (Snowflake, SQL, Python, etc). But the list mixes them. Could split: Requirements: years of experience, Snowflake experience, ability to manage requests, etc. Qualifications: Bachelor's degree. Skills: technical knowledge (Snowflake architecture, SQL, Python, IaC, monitoring, security, mentoring). However the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine into one Qualifications
that includes both requirements and skills. But we need to follow the allowed headings; we can choose which to include. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require us to use all; we can pick those that have content.
Thus we could have:
About the role
... (the paragraph)
Responsibilities
...
Qualifications
...
(including both mandatory and nice-to-have? maybe separate nice-to-have as part of same list but we could note "Nice to have" as a sub-bullet? But we should preserve all substantive info; we can include nice-to-have as part of the list with a note.
We also have Benefits section: after "How We Reward You:" list of benefits. That's substantive. So we should include Benefits
with - items.
Pay and Schedule: not mentioned specifically. No pay or schedule details. So we should NOT include those sections.
Thus final HTML: include About the role, Responsibilities, Qualifications, Benefits.
We need to ensure we don't include boilerplate like EEO etc. Remove the diversity statement at end. Also remove "How We Work:" paragraph? That's about in-person collaboration; could be considered part of company culture but not a standard heading. Might be considered boilerplate? It's not EEO but it's about work style. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We Work:" is not explicitly listed but could be considered company culture; but it's not a standard heading. Might be okay to keep as a
under About the role? But we already have About the role section; we could incorporate that paragraph into About the role? However the "How We Work:" appears after the benefits? Actually after benefits there is "Do the best work of your life at Realtor.com®..." then diversity statement. That's more marketing fluff. Could be considered boilerplate? It's not EEO but it's promotional. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that marketing paragraph? It's not about the role but about company culture. Might be considered substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we could keep it as a
maybe under About the role or as a separate section like "Company Culture". But we don't have a heading for that; we could just include as a
after the About the role section before Responsibilities? However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings and put any extra prose in
under appropriate section or as a general
before sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have stray
not under a heading. But typical approach: we can have a leading
for company overview, then sections.
Thus we could structure:
Recognized as the No. 1 site trusted by real estate professionals, Realtor.com® has been at the forefront of online real estate for over 25 years, connecting buyers, sellers, and renters with trusted insights and expert guidance to find their perfect home. Through its robust suite of tools, Realtor.com® not only makes a significant impact on the real estate industry at large, but for consumers, navigating the biggest purchase they will make in their life, by providing a user experience that is easy to use, easy to understand, and most of all, easy to make decisions.Join us on our mission to empower more people to find their way home by breaking barriers to entry, making the right connections, and building confidence through expert guidance.
About the role
We have an exciting and unique opportunity for a motivated and energetic Staff Software Engineer to join the Realtor.com Data Operations team. In this position, you will lead the administration, optimization, and strategic evolution of our enterprise Snowflake Platform to support data-driven decisions across the organization. You will develop and maintain best practices for data warehouse management, build sophisticated monitoring and optimization tools, ensure enterprise-grade security and compliance, and mentor engineers on Snowflake administration. You will incorporate DevOps practices, learn about and leverage new technologies, work with an experienced team of engineers, and be part of a team that has a lot of fun along the way!
Responsibilities
- Own the delivery, quality, reliability, and strategic evolution of the Snowflake Data Warehouse infrastructure supporting 900+ unique users and petabyte-scale analytics
- Lead incident response and root cause analysis for production data pipeline failures; maintain and improve operational runbooks and SLA tracking
- Prioritize and triage platform requests from a large user base; balance urgent operational needs against strategic platform improvements
- Maintain comprehensive internal documentation including onboarding guides, runbooks, and architecture decision records for the Snowflake platform
- Design and implement comprehensive Snowflake administration best practices including security frameworks (RBAC, masking, encryption), access control, and compliance requirements
- Build and maintain advanced monitoring, alerting, and observability tools for Snowflake; develop Streamlit apps to track warehouse health, performance, and costs
- Automate routine administration tasks (user provisioning, warehouse scheduling, access reviews) to reduce manual toil and enable self-service
- Manage schema migration and configuration change processes across dev, staging, and production environments with appropriate review and rollback procedures
- Develop optimization strategies and tools to reduce Snowflake infrastructure costs while maintaining or improving performance; lead continuous optimization initiatives
- Partner with data engineering and analytics teams to design optimal data warehouse schemas and integration patterns that support business requirements
- Establish and enforce data governance policies, data quality standards, and compliance controls; ensure regulatory requirements (CCPA) are met
- Mentor and guide team members on Snowflake DBA activities, best practices, and emerging technologies; serve as subject matter expert for data warehouse architecture
- Work collaboratively with cross-functional teams including Product Managers, Data Engineers, and Analytics teams to understand requirements and deliver solutions
- Actively evaluate new technologies and approaches; make recommendations to evolve and modernize our data platform capabilities
- Perform technical presentations and architecture reviews with internal stakeholders and leadership
- Work in a primarily Agile/Scrum product development process
Qualifications
- 8+ years of experience in data platform engineering or database administration roles
- 4+ years of hands-on experience administering and optimizing Snowflake in production environments
- Deep technical knowledge of Snowflake architecture, including compute/storage separation, query optimization, clustering, materialized views, and time travel
- Strong proficiency in SQL; expertise in data structures, data integrity, schema design, and dimensional modeling best practices
- Proficiency in Python or other scripting languages for automation, tooling, and operational workflows
- Demonstr
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Include section only when posting has real specific content. Avoid filler like "commensurate with experience". Need to extract content. Let's parse the description. First paragraph: description of Realtor.com. That's likely "About the company" but not a required heading. Could be part of "About the role"? Actually "About The Role" heading appears later. The initial paragraph is company overview; we could include as a
before sections? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text.
Thus we need to decide which sections have content.
From posting:
- About The Role: paragraph after that heading: "We have an exciting and unique opportunity for a motivated and energetic Staff Software Engineer to join the Realtor.com Data Operations team. In this position, you will lead the administration, optimization, and strategic evolution of our enterprise Snowflake Platform to support data-driven decisions across the organization. You will develop and maintain best practices for data warehouse management, build sophisticated monitoring and optimization tools, ensure enterprise-grade security and compliance, and mentor engineers on Snowflake administration. You will incorporate DevOps practices, learn about and leverage new technologies, work with an experienced team of engineers, and be part of a team that has a lot of fun along the way!"
That's prose.
- What You'll Do: list of duties (many bullet-like sentences). Should be a list under Responsibilities (or maybe "What You'll Do" corresponds to Responsibilities). We'll create a section
Responsibilities
with - items.
- What You'll Bring: list of qualifications/experience/skills. Could be split into Requirements, Qualifications, Skills. The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide based on content. The list includes: 8+ years experience, 4+ years Snowflake, deep technical knowledge, strong proficiency in SQL, proficiency in Python, ability to manage requests, demonstrated experience driving technical initiatives, experience with cloud architectures, experience using IaC, experience building monitoring tools, strong understanding of data security, ability to mentor, driven engineer, Bachelor's degree. Then "Nice to Have Experience:" list.
Thus we could have:
Requirements
with the mandatory items (maybe up to Bachelor's degree). Or we could separate Qualifications (education) and Skills (technical). But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content.
We have content for Requirements (experience, skills). Qualifications maybe education (Bachelor's degree). Skills maybe technical proficiencies (Snowflake, SQL, Python, etc). But the list mixes them. Could split: Requirements: years of experience, Snowflake experience, ability to manage requests, etc. Qualifications: Bachelor's degree. Skills: technical knowledge (Snowflake architecture, SQL, Python, IaC, monitoring, security, mentoring). However the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine into one Qualifications
that includes both requirements and skills. But we need to follow the allowed headings; we can choose which to include. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require us to use all; we can pick those that have content.
Thus we could have:
About the role
... (the paragraph)
Responsibilities
...
Qualifications
...
(including both mandatory and nice-to-have? maybe separate nice-to-have as part of same list but we could note "Nice to have" as a sub-bullet? But we should preserve all substantive info; we can include nice-to-have as part of the list with a note.
We also have Benefits section: after "How We Reward You:" list of benefits. That's substantive. So we should include Benefits
with - items.
Pay and Schedule: not mentioned specifically. No pay or schedule details. So we should NOT include those sections.
Thus final HTML: include About the role, Responsibilities, Qualifications, Benefits.
We need to ensure we don't include boilerplate like EEO etc. Remove the diversity statement at end. Also remove "How We Work:" paragraph? That's about in-person collaboration; could be considered part of company culture but not a standard heading. Might be considered boilerplate? It's not EEO but it's about work style. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We Work:" is not explicitly listed but could be considered company culture; but it's not a standard heading. Might be okay to keep as a
under About the role? But we already have About the role section; we could incorporate that paragraph into About the role? However the "How We Work:" appears after the benefits? Actually after benefits there is "Do the best work of your life at Realtor.com®..." then diversity statement. That's more marketing fluff. Could be considered boilerplate? It's not EEO but it's promotional. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that marketing paragraph? It's not about the role but about company culture. Might be considered substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we could keep it as a
maybe under About the role or as a separate section like "Company Culture". But we don't have a heading for that; we could just include as a
after the About the role section before Responsibilities? However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings and put any extra prose in
under appropriate section or as a general
before sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have stray
not under a heading. But typical approach: we can have a leading
for company overview, then sections.
Thus we could structure:
Recognized as the No. 1 site trusted by real estate professionals, Realtor.com® has been at the forefront of online real estate for over 25 years, connecting buyers, sellers, and renters with trusted insights and expert guidance to find their perfect home. Through its robust suite of tools, Realtor.com® not only makes a significant impact on the real estate industry at large, but for consumers, navigating the biggest purchase they will make in their life, by providing a user experience that is easy to use, easy to understand, and most of all, easy to make decisions.Join us on our mission to empower more people to find their way home by breaking barriers to entry, making the right connections, and building confidence through expert guidance.
About the role
We have an exciting and unique opportunity for a motivated and energetic Staff Software Engineer to join the Realtor.com Data Operations team. In this position, you will lead the administration, optimization, and strategic evolution of our enterprise Snowflake Platform to support data-driven decisions across the organization. You will develop and maintain best practices for data warehouse management, build sophisticated monitoring and optimization tools, ensure enterprise-grade security and compliance, and mentor engineers on Snowflake administration. You will incorporate DevOps practices, learn about and leverage new technologies, work with an experienced team of engineers, and be part of a team that has a lot of fun along the way!
Responsibilities
- Own the delivery, quality, reliability, and strategic evolution of the Snowflake Data Warehouse infrastructure supporting 900+ unique users and petabyte-scale analytics
- Lead incident response and root cause analysis for production data pipeline failures; maintain and improve operational runbooks and SLA tracking
- Prioritize and triage platform requests from a large user base; balance urgent operational needs against strategic platform improvements
- Maintain comprehensive internal documentation including onboarding guides, runbooks, and architecture decision records for the Snowflake platform
- Design and implement comprehensive Snowflake administration best practices including security frameworks (RBAC, masking, encryption), access control, and compliance requirements
- Build and maintain advanced monitoring, alerting, and observability tools for Snowflake; develop Streamlit apps to track warehouse health, performance, and costs
- Automate routine administration tasks (user provisioning, warehouse scheduling, access reviews) to reduce manual toil and enable self-service
- Manage schema migration and configuration change processes across dev, staging, and production environments with appropriate review and rollback procedures
- Develop optimization strategies and tools to reduce Snowflake infrastructure costs while maintaining or improving performance; lead continuous optimization initiatives
- Partner with data engineering and analytics teams to design optimal data warehouse schemas and integration patterns that support business requirements
- Establish and enforce data governance policies, data quality standards, and compliance controls; ensure regulatory requirements (CCPA) are met
- Mentor and guide team members on Snowflake DBA activities, best practices, and emerging technologies; serve as subject matter expert for data warehouse architecture
- Work collaboratively with cross-functional teams including Product Managers, Data Engineers, and Analytics teams to understand requirements and deliver solutions
- Actively evaluate new technologies and approaches; make recommendations to evolve and modernize our data platform capabilities
- Perform technical presentations and architecture reviews with internal stakeholders and leadership
- Work in a primarily Agile/Scrum product development process
Qualifications
- 8+ years of experience in data platform engineering or database administration roles
- 4+ years of hands-on experience administering and optimizing Snowflake in production environments
- Deep technical knowledge of Snowflake architecture, including compute/storage separation, query optimization, clustering, materialized views, and time travel
- Strong proficiency in SQL; expertise in data structures, data integrity, schema design, and dimensional modeling best practices
- Proficiency in Python or other scripting languages for automation, tooling, and operational workflows
- Demonstr
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Thus we need to decide which sections have content. From posting: - About The Role: paragraph after that heading: "We have an exciting and unique opportunity for a motivated and energetic Staff Software Engineer to join the Realtor.com Data Operations team. In this position, you will lead the administration, optimization, and strategic evolution of our enterprise Snowflake Platform to support data-driven decisions across the organization. You will develop and maintain best practices for data warehouse management, build sophisticated monitoring and optimization tools, ensure enterprise-grade security and compliance, and mentor engineers on Snowflake administration. You will incorporate DevOps practices, learn about and leverage new technologies, work with an experienced team of engineers, and be part of a team that has a lot of fun along the way!" That's prose. - What You'll Do: list of duties (many bullet-like sentences). Should be a list under Responsibilities (or maybe "What You'll Do" corresponds to Responsibilities). We'll create a section
Responsibilities
with- items.
- What You'll Bring: list of qualifications/experience/skills. Could be split into Requirements, Qualifications, Skills. The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide based on content. The list includes: 8+ years experience, 4+ years Snowflake, deep technical knowledge, strong proficiency in SQL, proficiency in Python, ability to manage requests, demonstrated experience driving technical initiatives, experience with cloud architectures, experience using IaC, experience building monitoring tools, strong understanding of data security, ability to mentor, driven engineer, Bachelor's degree. Then "Nice to Have Experience:" list.
Thus we could have:
Requirements
with the mandatory items (maybe up to Bachelor's degree). Or we could separate Qualifications (education) and Skills (technical). But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content. We have content for Requirements (experience, skills). Qualifications maybe education (Bachelor's degree). Skills maybe technical proficiencies (Snowflake, SQL, Python, etc). But the list mixes them. Could split: Requirements: years of experience, Snowflake experience, ability to manage requests, etc. Qualifications: Bachelor's degree. Skills: technical knowledge (Snowflake architecture, SQL, Python, IaC, monitoring, security, mentoring). However the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine into oneQualifications
that includes both requirements and skills. But we need to follow the allowed headings; we can choose which to include. The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require us to use all; we can pick those that have content. Thus we could have:
About the role
... (the paragraph)
Responsibilities
- ...
Qualifications
- ...
Benefits
with- items.
Pay and Schedule: not mentioned specifically. No pay or schedule details. So we should NOT include those sections.
Thus final HTML: include About the role, Responsibilities, Qualifications, Benefits.
We need to ensure we don't include boilerplate like EEO etc. Remove the diversity statement at end. Also remove "How We Work:" paragraph? That's about in-person collaboration; could be considered part of company culture but not a standard heading. Might be considered boilerplate? It's not EEO but it's about work style. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We Work:" is not explicitly listed but could be considered company culture; but it's not a standard heading. Might be okay to keep as a
under About the role? But we already have About the role section; we could incorporate that paragraph into About the role? However the "How We Work:" appears after the benefits? Actually after benefits there is "Do the best work of your life at Realtor.com®..." then diversity statement. That's more marketing fluff. Could be considered boilerplate? It's not EEO but it's promotional. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that marketing paragraph? It's not about the role but about company culture. Might be considered substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we could keep it as a
maybe under About the role or as a separate section like "Company Culture". But we don't have a heading for that; we could just include as a
after the About the role section before Responsibilities? However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings and put any extra prose in
under appropriate section or as a general
before sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have stray
not under a heading. But typical approach: we can have a leading
for company overview, then sections. Thus we could structure:
Recognized as the No. 1 site trusted by real estate professionals, Realtor.com® has been at the forefront of online real estate for over 25 years, connecting buyers, sellers, and renters with trusted insights and expert guidance to find their perfect home. Through its robust suite of tools, Realtor.com® not only makes a significant impact on the real estate industry at large, but for consumers, navigating the biggest purchase they will make in their life, by providing a user experience that is easy to use, easy to understand, and most of all, easy to make decisions.Join us on our mission to empower more people to find their way home by breaking barriers to entry, making the right connections, and building confidence through expert guidance.
About the role
We have an exciting and unique opportunity for a motivated and energetic Staff Software Engineer to join the Realtor.com Data Operations team. In this position, you will lead the administration, optimization, and strategic evolution of our enterprise Snowflake Platform to support data-driven decisions across the organization. You will develop and maintain best practices for data warehouse management, build sophisticated monitoring and optimization tools, ensure enterprise-grade security and compliance, and mentor engineers on Snowflake administration. You will incorporate DevOps practices, learn about and leverage new technologies, work with an experienced team of engineers, and be part of a team that has a lot of fun along the way!
Responsibilities
- Own the delivery, quality, reliability, and strategic evolution of the Snowflake Data Warehouse infrastructure supporting 900+ unique users and petabyte-scale analytics
- Lead incident response and root cause analysis for production data pipeline failures; maintain and improve operational runbooks and SLA tracking
- Prioritize and triage platform requests from a large user base; balance urgent operational needs against strategic platform improvements
- Maintain comprehensive internal documentation including onboarding guides, runbooks, and architecture decision records for the Snowflake platform
- Design and implement comprehensive Snowflake administration best practices including security frameworks (RBAC, masking, encryption), access control, and compliance requirements
- Build and maintain advanced monitoring, alerting, and observability tools for Snowflake; develop Streamlit apps to track warehouse health, performance, and costs
- Automate routine administration tasks (user provisioning, warehouse scheduling, access reviews) to reduce manual toil and enable self-service
- Manage schema migration and configuration change processes across dev, staging, and production environments with appropriate review and rollback procedures
- Develop optimization strategies and tools to reduce Snowflake infrastructure costs while maintaining or improving performance; lead continuous optimization initiatives
- Partner with data engineering and analytics teams to design optimal data warehouse schemas and integration patterns that support business requirements
- Establish and enforce data governance policies, data quality standards, and compliance controls; ensure regulatory requirements (CCPA) are met
- Mentor and guide team members on Snowflake DBA activities, best practices, and emerging technologies; serve as subject matter expert for data warehouse architecture
- Work collaboratively with cross-functional teams including Product Managers, Data Engineers, and Analytics teams to understand requirements and deliver solutions
- Actively evaluate new technologies and approaches; make recommendations to evolve and modernize our data platform capabilities
- Perform technical presentations and architecture reviews with internal stakeholders and leadership
- Work in a primarily Agile/Scrum product development process
Qualifications
- 8+ years of experience in data platform engineering or database administration roles
- 4+ years of hands-on experience administering and optimizing Snowflake in production environments
- Deep technical knowledge of Snowflake architecture, including compute/storage separation, query optimization, clustering, materialized views, and time travel
- Strong proficiency in SQL; expertise in data structures, data integrity, schema design, and dimensional modeling best practices
- Proficiency in Python or other scripting languages for automation, tooling, and operational workflows
- Demonstr
- items.
Pay and Schedule: not mentioned specifically. No pay or schedule details. So we should NOT include those sections.
Thus final HTML: include About the role, Responsibilities, Qualifications, Benefits.
We need to ensure we don't include boilerplate like EEO etc. Remove the diversity statement at end. Also remove "How We Work:" paragraph? That's about in-person collaboration; could be considered part of company culture but not a standard heading. Might be considered boilerplate? It's not EEO but it's about work style. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We Work:" is not explicitly listed but could be considered company culture; but it's not a standard heading. Might be okay to keep as a