Data Platform Architect
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract content from posting.
We have:
- About the role: maybe from "Job Summary" and intro paragraphs. We'll create an About the role section with prose summarizing role.
- Responsibilities: list of key responsibilities (bulleted). Use - .
- Requirements: maybe "Required Qualifications". Use
Requirements? Actually they said use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include.
We have Required Qualifications and Preferred Qualifications. Could combine into Requirements and Preferred? But they said include a section only when posting has real specific content. We can have Requirements (maybe Required Qualifications) and maybe Preferred Qualifications as Skills? Or we could have Qualifications section covering both required and preferred? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple of those headings as appropriate.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include details like salary range, location, experience required, sponsorship, etc. Those could go into About the role or maybe a separate section like Pay, Schedule, Benefits. They said only create Pay/Schedule/Benefits sections if posting actually states them. The posting states Salary Range: $100,000–$175,000 Annually. That's Pay. Also location: 100% Remote (U.S.) maybe Schedule? Not exactly schedule but could be remote. They didn't specify work hours. So we can include Pay section with salary range. Benefits: not mentioned besides maybe career growth potential but not explicit benefits. So we should not create Benefits section unless explicit. Schedule: not mentioned. So we omit Schedule and Benefits.
We need to include About the role: maybe combine the introductory paragraphs: "Data Platform Architect – Remote Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential." plus Job Summary.
We'll put that in About the role as prose (
).
Responsibilities: list each bullet from "Key Responsibilities". We'll need to preserve each responsibility exactly as given, but we can split into separate
- items.
Requirements: maybe "Required Qualifications". We'll list each bullet as
- . Also include experience required 12+ years, sponsorship etc. Those could be part of Requirements or maybe separate? The posting includes "Experience Required: 12+ years", "Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position." Also "Job Title: Data Platform Architect Location: 100% Remote (U.S.) Position Type: Full-time, Direct W2". Those could be placed in About the role or maybe a separate "Details" but we don't have a heading for that. Could put them in About the role as prose.
Qualifications: maybe "Preferred Qualifications". We'll list those as
- under Qualifications.
Skills: maybe we could extract skills from responsibilities? But we already have Required and Preferred qualifications covering skills. Could create Skills section summarizing technical skills: e.g., expertise in Snowflake, Databricks, etc. But we risk duplicating. The instruction: prefer a few substantive sections over many thin ones. So maybe we combine Required and Preferred into Requirements and Qualifications sections, and not create Skills unless we have distinct skill list not covered. We have required qualifications list includes deep expertise across at least two major data platforms, understanding of lakehouse, hands-on experience with Spark/Flink/Kafka, data modeling expertise, governance, cloud platforms, communication, track record. Preferred qualifications list includes data mesh, semantic layers, regulated industries, certifications, public talks. Those could go under Qualifications (maybe split required vs preferred). But we have both Requirements and Qualifications headings available. We could put Required Qualifications under Requirements, and Preferred Qualifications under Qualifications. That seems appropriate.
Thus sections:
- About the role (prose)
- Responsibilities (ul)
- Requirements (ul) for Required Qualifications plus maybe experience required, sponsorship, location, position type? Could include those as list items as well.
- Qualifications (ul) for Preferred Qualifications
- Pay (p) for salary range
We must not repeat job title as heading. Already not.
We must not include Job ID/requisition numbers.
We must remove boilerplate: EEO statement, "How to Apply", "Learn more about Bright Vision Technologies", "Powered by JazzHR". Also remove "Job Summary:" heading? We'll incorporate its content.
We must preserve all substantive information: ensure we include salary range, location, remote, full-time, direct W2, experience required 12+ years, sponsorship details, etc.
Let's craft.
About the role: combine intro and job summary.
Intro: "Data Platform Architect – Remote Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential."
Job Summary: "We are seeking a Data Platform Architect to define and lead the architecture of our enterprise data platform, spanning ingestion, storage, processing, governance, and consumption layers. The role drives the strategic direction of data infrastructure, sets standards for data modeling and lifecycle management, and partners with data engineering, analytics, ML, and business stakeholders to deliver a coherent, scalable data foundation. The ideal candidate combines deep technical mastery of modern data platforms with strong architectural judgment, and has led data-platform programs of meaningful scope and complexity."
We'll put that in
maybe two paragraphs.
Responsibilities: list each bullet from "Key Responsibilities". Need to preserve each line exactly. Let's extract:
- Define the target-state architecture of the enterprise data platform, including ingestion, storage, processing, and consumption layers
- Establish standards for data modeling, schema evolution, partitioning, file formats, and storage organization
- Architect lakehouse, warehouse, and streaming patterns leveraging technologies such as Snowflake, Databricks, BigQuery, Redshift, Iceberg, Delta Lake, or Hudi
- Design end-to-end data pipelines that balance latency, cost, reliability, and maintainability across batch and streaming workloads
- Lead the integration of governance, lineage, and catalog tools such as Collibra, Alation, Atlan, Unity Catalog, or DataHub
- Define security architecture including row- and column-level controls, masking, encryption, and identity-aware access patterns
- Partner with ML, BI, and product teams to ensure platform capabilities align with downstream consumption needs
- Establish data contract and data product principles to drive ownership, quality, and decoupling between producers and consumers
- Lead architecture reviews and provide guidance on pipeline and warehouse design proposals across teams
- Drive cost optimization and capacity planning across the data platform estate
- Design disaster recovery, multi-region, and high-availability strategies for critical data assets
- Mentor data engineers and architects on platform standards and emerging best practices
- Produce architecture artifacts including context diagrams, decision records, and reference patterns
- Stay current with data platform research, vendor offerings, and open-source ecosystem developments
We'll put each as
- .
Requirements: include Required Qualifications bullets plus experience required, sponsorship, location, position type maybe.
Required Qualifications bullets:
- Bachelor’s or Master’s degree in Computer Science, Information Systems, or a related field
- Eight or more years of experience in data engineering, with significant time in architecture roles
- Deep expertise across at least two major data platforms such as Snowflake, Databricks, BigQuery, or Redshift
- Strong understanding of lakehouse architectures, modern table formats, and streaming systems
- Hands-on experience with Spark, Flink, or Kafka at production scale
- Strong data modeling expertise across dimensional, normalized, and data-vault patterns
- Experience implementing governance, lineage, and catalog capabilities
- Solid grasp of cloud platforms, networking, identity, and cost optimization
- Excellent communication, facilitation, and stakeholder management skills
- Track record of leading large data platform initiatives across teams
Additionally, we have "Experience Required: 12+ years" (somewhat overlapping with 8+ years but more specific). Also "Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position." Also location and position type.
We could add list items for those.
Qualifications: Preferred Qualifications bullets:
- Experience with data mesh or data product architectures
- Familiarity with semantic layers such as dbt Semantic Layer, Cube, or LookML
- Exposure to regulated industries with strict data residency or audit requirements
- Cloud or platform certifications (Snowflake, Databricks, AWS, Azure, GCP)
- Public talks or writing on data architecture
Pay: Salary Range: $100,000–$175,000 Annually.
We'll output as
maybe.
Now ensure we don't include any boilerplate like "How to Apply", "Learn more about Bright Vision Technologies", EEO statement, "Powered by JazzHR". Also remove duplicated lines.
Now produce HTML fragment:
About the role
...
Responsibilities
...
Requirements
...
Qualifications
...
Pay
Salary Range: $100,000–$175,000 Annually.
We should not add extra whitespace? It's fine.
Check that we didn't include Schedule or Benefits sections.
Now craft the About the role prose: combine two paragraphs maybe.
Let's write:
Data Platform Architect – Remote Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential.
We are seeking a Data Platform Architect to define and lead the architecture of our enterprise data platform, spanning ingestion, storage, processing, governance, and consumption layers. The role drives the strategic direction of data infrastructure, sets standards for data modeling and lifecycle management, and partners with data engineering, analytics, ML, and business stakeholders to deliver a coherent, scalable data foundation. The ideal candidate combines deep technical mastery of modern data platforms with strong architectural judgment, and has led data-platform programs of meaningful scope and complexity.
That preserves all.
Now Responsibilities list as above.
Now Requirements list: include the Required Qualifications bullets plus experience required 12+ years, sponsorship, location, position type.
We need to be careful not to duplicate: Required Qualifications already includes "Eight or more years of experience in data engineering, with significant time in architecture roles". Experience Required says 12+ years, which is more specific; we can include both but maybe we should include the 12+ years as separate item. It's okay to have both; they are not contradictory but we preserve all info.
Sponsorship: we can add as list item.
Location: "Location: 100% Remote (U.S.)"
Position Type: "Position Type: Full-time, Direct W2"
We'll add those.
Now Qualifications list: Preferred Qualifications bullets.
Now Pay: salary range.
Now output.
Check for any leftover boilerplate: we removed "How to Apply", "Learn more about Bright Vision Technologies at www.bvteck.com.",
Requirements? Actually they said use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include.
We have Required Qualifications and Preferred Qualifications. Could combine into Requirements and Preferred? But they said include a section only when posting has real specific content. We can have Requirements (maybe Required Qualifications) and maybe Preferred Qualifications as Skills? Or we could have Qualifications section covering both required and preferred? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple of those headings as appropriate.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include details like salary range, location, experience required, sponsorship, etc. Those could go into About the role or maybe a separate section like Pay, Schedule, Benefits. They said only create Pay/Schedule/Benefits sections if posting actually states them. The posting states Salary Range: $100,000–$175,000 Annually. That's Pay. Also location: 100% Remote (U.S.) maybe Schedule? Not exactly schedule but could be remote. They didn't specify work hours. So we can include Pay section with salary range. Benefits: not mentioned besides maybe career growth potential but not explicit benefits. So we should not create Benefits section unless explicit. Schedule: not mentioned. So we omit Schedule and Benefits.
We need to include About the role: maybe combine the introductory paragraphs: "Data Platform Architect – Remote Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential." plus Job Summary.
We'll put that in About the role as prose (
). Responsibilities: list each bullet from "Key Responsibilities". We'll need to preserve each responsibility exactly as given, but we can split into separate
maybe two paragraphs. Responsibilities: list each bullet from "Key Responsibilities". Need to preserve each line exactly. Let's extract: - Define the target-state architecture of the enterprise data platform, including ingestion, storage, processing, and consumption layers - Establish standards for data modeling, schema evolution, partitioning, file formats, and storage organization - Architect lakehouse, warehouse, and streaming patterns leveraging technologies such as Snowflake, Databricks, BigQuery, Redshift, Iceberg, Delta Lake, or Hudi - Design end-to-end data pipelines that balance latency, cost, reliability, and maintainability across batch and streaming workloads - Lead the integration of governance, lineage, and catalog tools such as Collibra, Alation, Atlan, Unity Catalog, or DataHub - Define security architecture including row- and column-level controls, masking, encryption, and identity-aware access patterns - Partner with ML, BI, and product teams to ensure platform capabilities align with downstream consumption needs - Establish data contract and data product principles to drive ownership, quality, and decoupling between producers and consumers - Lead architecture reviews and provide guidance on pipeline and warehouse design proposals across teams - Drive cost optimization and capacity planning across the data platform estate - Design disaster recovery, multi-region, and high-availability strategies for critical data assets - Mentor data engineers and architects on platform standards and emerging best practices - Produce architecture artifacts including context diagrams, decision records, and reference patterns - Stay current with data platform research, vendor offerings, and open-source ecosystem developments We'll put each as
maybe. Now ensure we don't include any boilerplate like "How to Apply", "Learn more about Bright Vision Technologies", EEO statement, "Powered by JazzHR". Also remove duplicated lines. Now produce HTML fragment:
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Pay
Salary Range: $100,000–$175,000 Annually.
We should not add extra whitespace? It's fine. Check that we didn't include Schedule or Benefits sections. Now craft the About the role prose: combine two paragraphs maybe. Let's write:Data Platform Architect – Remote Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential.
We are seeking a Data Platform Architect to define and lead the architecture of our enterprise data platform, spanning ingestion, storage, processing, governance, and consumption layers. The role drives the strategic direction of data infrastructure, sets standards for data modeling and lifecycle management, and partners with data engineering, analytics, ML, and business stakeholders to deliver a coherent, scalable data foundation. The ideal candidate combines deep technical mastery of modern data platforms with strong architectural judgment, and has led data-platform programs of meaningful scope and complexity.
That preserves all. Now Responsibilities list as above. Now Requirements list: include the Required Qualifications bullets plus experience required 12+ years, sponsorship, location, position type. We need to be careful not to duplicate: Required Qualifications already includes "Eight or more years of experience in data engineering, with significant time in architecture roles". Experience Required says 12+ years, which is more specific; we can include both but maybe we should include the 12+ years as separate item. It's okay to have both; they are not contradictory but we preserve all info. Sponsorship: we can add as list item. Location: "Location: 100% Remote (U.S.)" Position Type: "Position Type: Full-time, Direct W2" We'll add those. Now Qualifications list: Preferred Qualifications bullets. Now Pay: salary range. Now output. Check for any leftover boilerplate: we removed "How to Apply", "Learn more about Bright Vision Technologies at www.bvteck.com.",