Engineering Leader, Google COE
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, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading followed by filler placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Content:
Intro: "It's fun to work in a company where people truly BELIEVE in what they are doing! We're committed to bringing passion and customer focus to the business. Fractal is a strategic AI partner to Fortune 500 companies with a vision to power every human decision in the enterprise. Fractal is building a world where individual choices, freedom, and diversity are the greatest assets; an ecosystem where human imagination is at the heart of every decision. Where no possibility is written off, only challenged to get better. We believe that a true Fractalite is the one who empowers imagination with intelligence. Fractal has been featured as a Great Place to Work by The Economic Times in partnership with the Great Place to Work® Institute and recognized as a ‘Cool Vendor’ and a ‘Vendor to Watch’ by Gartner. Please visit Fractal | Intelligence for Imagination for more information about Fractal."
That's about company, maybe "About the role"? Actually "Role Overview" heading appears later. We can treat "About the role" as a heading for company description and role overview? The instructions: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to include only sections with real content.
Let's extract:
- About the role: Could include company description and role overview. The posting has "Role Overview" paragraph: "We're looking for someone recognized as a subject matter expert on the Google Cloud Platform, with deep roots in Data Engineering and a sharp eye for AI/ML-driven solutions. This is not a purely advisory role you'll own architecture, drive delivery, and be the technical anchor clients trust when the stakes are high. If you've spent 12+ years building large-scale data platforms on GCP, know BigQuery and Vertex AI inside out, and thrive at the intersection of strategy and hands-on execution read on."
That's role overview.
Also earlier company description could be part of About the role.
Thus we can put About the role section with paragraphs.
- Responsibilities: The posting lists sections: Architecture & Strategy, Delivery Leadership, Client Engagement, Community & Enablement. Those are responsibilities. So we can combine them under Responsibilities heading, with bullet lists for each subcategory? The instruction: Use - for any list of duties/requirements/benefits. So we can create
- for each bullet point. Could also have subheadings? Not required but we can keep plain list.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each bullet point from those sections.
Let's extract bullet points:
Architecture & Strategy:
- Define short- and long-term technology vision for clients, evaluating their current landscape and charting a path forward.
- Lead end-to-end architecture for Data Engineering, Data Warehousing, and AI/ML solutions on GCP.
- Design scalable, secure, future-proof solutions using GCP-native services BigQuery, Dataflow, Cloud Composer, Vertex AI, Dataproc, Cloud Storage, and more.
- Build foundational architectures: microservices, event-driven systems, event streaming, and online ML systems.
- Champion data governance, data management best practices, and platform maintainability.
Delivery Leadership:
- Act as Delivery Lead on large-scale programs owning timelines, quality, risk, and client satisfaction end to end.
- Drive program governance across workstreams, keeping cross-functional and cross-geography teams aligned.
- Step in hands-on during critical delivery phases architecture validation, performance tuning, production issue resolution.
- Bridge the gap between architecture decisions and execution realities, ensuring long-term scalability is never sacrificed for short-term speed.
- Mentor delivery teams, instilling strong engineering practices, accountability, and a culture of continuous improvement.
Client Engagement:
- Become a trusted thought partner to senior client leaders understanding their pain points and translating them into actionable technical strategies.
- Proactively identify client needs and align them with innovative, business-impacting solutions.
- Communicate complex technical concepts clearly across executive, business, and engineering audiences.
- Build lasting relationships with senior stakeholders and cross-functional teams.
Community & Enablement:
- Contribute to best practices, reference architectures, and technical content that elevate the broader practice.
- Collaborate with data engineers and data scientists to co-develop architecture that serves both analytical and operational needs.
Thus responsibilities list.
- Requirements / Qualifications / Skills: The posting has "Must-Have" and "Nice to Have". Must-Have includes: 12+ years in Data Engineering and Cloud-native technologies, with deep GCP expertise. Hands-on mastery of: BigQuery, Dataflow, Cloud Composer, Vertex AI, Dataproc, Cloud Storage, GCP serverless infrastructure. Proven delivery of end-to-end Data Engineering, Data Warehousing, or Analytics platforms at scale. Strong programming skills in Python and/or Java. Experience with Agile, CI/CD, DevOps, and MLOps pipelines. Track record leading large, complex, client-facing delivery programs. Ability to manage cross-functional, cross-geography teams with clarity and accountability. Prior Google with direct exposure to first party tooling. Write and optimize queries using PLX to support data analysis and product features Proficiency in PLX or similar structured querying languages (e.g. SQL, Dremel/Spanner). Nice to Have: Docker & Kubernetes experience. DevOps on GCP. AWS experience, especially in hybrid cloud contexts. Google Cloud Professional Cloud Architect Certification.
We need to decide sections: Requirements, Qualifications, Skills. The instruction says we can use those headings. We need to avoid filler. We have substantive content for Must-Have and Nice to Have. Could combine into Requirements (must-have) and Skills (nice-to-have) or Qualifications. But we need to avoid thin sections. Perhaps we can have one section "Requirements" containing must-have, and another "Skills" containing nice-to-have. Or "Qualifications" for must-have and "Skills" for nice-to-have. Let's see typical: Requirements often list must-have; Skills list nice-to-have. We'll do that.
Thus:
Requirements
with - items for each must-have bullet.
Skills
with nice-to-have bullets.
- Benefits: The posting has a Benefits paragraph: "As a full-time employee of the company or as an hourly employee working more than 30 hours per week, you will be eligible to participate in the health, dental, vision, life insurance, and disability plans in accordance with the plan documents, which may be amended from time to time. You will be eligible for benefits on the first day of Employment with the Company. In addition, you are eligible to participate in the Company 401(k) Plan after 30 days of employment, in accordance with the applicable plan terms. The Company provides 11 paid holidays and 12 weeks of Parental Leave. We also follow a “free time” PTO policy, allowing you the flexibility to take the time needed for either sick time or vacation."
We need to output as list? Could be prose . The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. Benefits is a list of items; we could make
- . But we can also keep as prose. Safer to use
- for benefits list. Let's extract each benefit:
- health, dental, vision, life insurance, and disability plans
- eligibility on first day of employment
- Company 401(k) Plan after 30 days
- 11 paid holidays
- 12 weeks of Parental Leave
- “free time” PTO policy (flexible sick/vacation)
We'll list each as
- .
- Pay: The posting has Pay section: "The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Fractal, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the starting base range is: $225,000. In addition, you may be eligible for a discretionary bonus for the current performance period."
We need to include Pay section only if real specific content. It gives a starting base range estimate $225,000 and mentions discretionary bonus. That's specific enough. So we include Pay heading with maybe
prose.
- Schedule: No mention of schedule (e.g., full-time, hours). Not present. So we omit Schedule section.
- Also we might need to include "About the role" section with company description and role overview. Let's craft that.
Company description paragraph: "It's fun to work in a company where people truly BELIEVE in what they are doing! We're committed to bringing passion and customer focus to the business. Fractal is a strategic AI partner to Fortune 500 companies with a vision to power every human decision in the enterprise. Fractal is building a world where individual choices, freedom, and diversity are the greatest assets; an ecosystem where human imagination is at the heart of every decision. Where no possibility is written off, only challenged to get better. We believe that a true Fractalite is the one who empowers imagination with intelligence. Fractal has been featured as a Great Place to Work by The Economic Times in partnership with the Great Place to Work® Institute and recognized as a ‘Cool Vendor’ and a ‘Vendor to Watch’ by Gartner."
Then role overview paragraph: "We're looking for someone recognized as a subject matter expert on the Google Cloud Platform, with deep roots in Data Engineering and a sharp eye for AI/ML-driven solutions. This is not a purely advisory role you'll own architecture, drive delivery, and be the technical anchor clients trust when the stakes are high. If you've spent 12+ years building large-scale data platforms on GCP, know BigQuery and Vertex AI inside out, and thrive at the intersection of strategy and hands-on execution read on."
We can combine into About the role section with two
paragraphs.
Now we need to output only HTML fragment, no /, no markdown fences.
Thus final HTML:
About the role
It's fun to work in a company where people truly BELIEVE in what they are doing! We're committed to bringing passion and customer focus to the business. Fractal is a strategic AI partner to Fortune 500 companies with a vision to power every human decision in the enterprise. Fractal is building a world where individual choices, freedom, and diversity are the greatest assets; an ecosystem where human imagination is at the heart of every decision. Where no possibility is written off, only challenged to get better. We believe that a true Fractalite is the one who empowers imagination with intelligence. Fractal has been featured as a Great Place to Work by The Economic Times in partnership with the Great Place to Work® Institute and recognized as a ‘Cool Vendor’ and a
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading followed by filler placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: Intro: "It's fun to work in a company where people truly BELIEVE in what they are doing! We're committed to bringing passion and customer focus to the business. Fractal is a strategic AI partner to Fortune 500 companies with a vision to power every human decision in the enterprise. Fractal is building a world where individual choices, freedom, and diversity are the greatest assets; an ecosystem where human imagination is at the heart of every decision. Where no possibility is written off, only challenged to get better. We believe that a true Fractalite is the one who empowers imagination with intelligence. Fractal has been featured as a Great Place to Work by The Economic Times in partnership with the Great Place to Work® Institute and recognized as a ‘Cool Vendor’ and a ‘Vendor to Watch’ by Gartner. Please visit Fractal | Intelligence for Imagination for more information about Fractal." That's about company, maybe "About the role"? Actually "Role Overview" heading appears later. We can treat "About the role" as a heading for company description and role overview? The instructions: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to include only sections with real content.
Let's extract:
- About the role: Could include company description and role overview. The posting has "Role Overview" paragraph: "We're looking for someone recognized as a subject matter expert on the Google Cloud Platform, with deep roots in Data Engineering and a sharp eye for AI/ML-driven solutions. This is not a purely advisory role you'll own architecture, drive delivery, and be the technical anchor clients trust when the stakes are high. If you've spent 12+ years building large-scale data platforms on GCP, know BigQuery and Vertex AI inside out, and thrive at the intersection of strategy and hands-on execution read on."
That's role overview.
Also earlier company description could be part of About the role.
Thus we can put About the role section with paragraphs.
- Responsibilities: The posting lists sections: Architecture & Strategy, Delivery Leadership, Client Engagement, Community & Enablement. Those are responsibilities. So we can combine them under Responsibilities heading, with bullet lists for each subcategory? The instruction: Use - for any list of duties/requirements/benefits. So we can create
- for each bullet point. Could also have subheadings? Not required but we can keep plain list.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each bullet point from those sections.
Let's extract bullet points:
Architecture & Strategy:
- Define short- and long-term technology vision for clients, evaluating their current landscape and charting a path forward.
- Lead end-to-end architecture for Data Engineering, Data Warehousing, and AI/ML solutions on GCP.
- Design scalable, secure, future-proof solutions using GCP-native services BigQuery, Dataflow, Cloud Composer, Vertex AI, Dataproc, Cloud Storage, and more.
- Build foundational architectures: microservices, event-driven systems, event streaming, and online ML systems.
- Champion data governance, data management best practices, and platform maintainability.
Delivery Leadership:
- Act as Delivery Lead on large-scale programs owning timelines, quality, risk, and client satisfaction end to end.
- Drive program governance across workstreams, keeping cross-functional and cross-geography teams aligned.
- Step in hands-on during critical delivery phases architecture validation, performance tuning, production issue resolution.
- Bridge the gap between architecture decisions and execution realities, ensuring long-term scalability is never sacrificed for short-term speed.
- Mentor delivery teams, instilling strong engineering practices, accountability, and a culture of continuous improvement.
Client Engagement:
- Become a trusted thought partner to senior client leaders understanding their pain points and translating them into actionable technical strategies.
- Proactively identify client needs and align them with innovative, business-impacting solutions.
- Communicate complex technical concepts clearly across executive, business, and engineering audiences.
- Build lasting relationships with senior stakeholders and cross-functional teams.
Community & Enablement:
- Contribute to best practices, reference architectures, and technical content that elevate the broader practice.
- Collaborate with data engineers and data scientists to co-develop architecture that serves both analytical and operational needs.
Thus responsibilities list.
- Requirements / Qualifications / Skills: The posting has "Must-Have" and "Nice to Have". Must-Have includes: 12+ years in Data Engineering and Cloud-native technologies, with deep GCP expertise. Hands-on mastery of: BigQuery, Dataflow, Cloud Composer, Vertex AI, Dataproc, Cloud Storage, GCP serverless infrastructure. Proven delivery of end-to-end Data Engineering, Data Warehousing, or Analytics platforms at scale. Strong programming skills in Python and/or Java. Experience with Agile, CI/CD, DevOps, and MLOps pipelines. Track record leading large, complex, client-facing delivery programs. Ability to manage cross-functional, cross-geography teams with clarity and accountability. Prior Google with direct exposure to first party tooling. Write and optimize queries using PLX to support data analysis and product features Proficiency in PLX or similar structured querying languages (e.g. SQL, Dremel/Spanner). Nice to Have: Docker & Kubernetes experience. DevOps on GCP. AWS experience, especially in hybrid cloud contexts. Google Cloud Professional Cloud Architect Certification.
We need to decide sections: Requirements, Qualifications, Skills. The instruction says we can use those headings. We need to avoid filler. We have substantive content for Must-Have and Nice to Have. Could combine into Requirements (must-have) and Skills (nice-to-have) or Qualifications. But we need to avoid thin sections. Perhaps we can have one section "Requirements" containing must-have, and another "Skills" containing nice-to-have. Or "Qualifications" for must-have and "Skills" for nice-to-have. Let's see typical: Requirements often list must-have; Skills list nice-to-have. We'll do that.
Thus:
Requirements
with - items for each must-have bullet.
Skills
with nice-to-have bullets.
- Benefits: The posting has a Benefits paragraph: "As a full-time employee of the company or as an hourly employee working more than 30 hours per week, you will be eligible to participate in the health, dental, vision, life insurance, and disability plans in accordance with the plan documents, which may be amended from time to time. You will be eligible for benefits on the first day of Employment with the Company. In addition, you are eligible to participate in the Company 401(k) Plan after 30 days of employment, in accordance with the applicable plan terms. The Company provides 11 paid holidays and 12 weeks of Parental Leave. We also follow a “free time” PTO policy, allowing you the flexibility to take the time needed for either sick time or vacation."
We need to output as list? Could be prose . The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. Benefits is a list of items; we could make
- . But we can also keep as prose. Safer to use
- for benefits list. Let's extract each benefit:
- health, dental, vision, life insurance, and disability plans
- eligibility on first day of employment
- Company 401(k) Plan after 30 days
- 11 paid holidays
- 12 weeks of Parental Leave
- “free time” PTO policy (flexible sick/vacation)
We'll list each as
- .
- Pay: The posting has Pay section: "The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Fractal, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the starting base range is: $225,000. In addition, you may be eligible for a discretionary bonus for the current performance period."
We need to include Pay section only if real specific content. It gives a starting base range estimate $225,000 and mentions discretionary bonus. That's specific enough. So we include Pay heading with maybe
prose.
- Schedule: No mention of schedule (e.g., full-time, hours). Not present. So we omit Schedule section.
- Also we might need to include "About the role" section with company description and role overview. Let's craft that.
Company description paragraph: "It's fun to work in a company where people truly BELIEVE in what they are doing! We're committed to bringing passion and customer focus to the business. Fractal is a strategic AI partner to Fortune 500 companies with a vision to power every human decision in the enterprise. Fractal is building a world where individual choices, freedom, and diversity are the greatest assets; an ecosystem where human imagination is at the heart of every decision. Where no possibility is written off, only challenged to get better. We believe that a true Fractalite is the one who empowers imagination with intelligence. Fractal has been featured as a Great Place to Work by The Economic Times in partnership with the Great Place to Work® Institute and recognized as a ‘Cool Vendor’ and a ‘Vendor to Watch’ by Gartner."
Then role overview paragraph: "We're looking for someone recognized as a subject matter expert on the Google Cloud Platform, with deep roots in Data Engineering and a sharp eye for AI/ML-driven solutions. This is not a purely advisory role you'll own architecture, drive delivery, and be the technical anchor clients trust when the stakes are high. If you've spent 12+ years building large-scale data platforms on GCP, know BigQuery and Vertex AI inside out, and thrive at the intersection of strategy and hands-on execution read on."
We can combine into About the role section with two
paragraphs.
Now we need to output only HTML fragment, no /, no markdown fences.
Thus final HTML:
About the role
It's fun to work in a company where people truly BELIEVE in what they are doing! We're committed to bringing passion and customer focus to the business. Fractal is a strategic AI partner to Fortune 500 companies with a vision to power every human decision in the enterprise. Fractal is building a world where individual choices, freedom, and diversity are the greatest assets; an ecosystem where human imagination is at the heart of every decision. Where no possibility is written off, only challenged to get better. We believe that a true Fractalite is the one who empowers imagination with intelligence. Fractal has been featured as a Great Place to Work by The Economic Times in partnership with the Great Place to Work® Institute and recognized as a ‘Cool Vendor’ and a
- for each bullet point. Could also have subheadings? Not required but we can keep plain list.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each bullet point from those sections.
Let's extract bullet points:
Architecture & Strategy:
- Define short- and long-term technology vision for clients, evaluating their current landscape and charting a path forward.
- Lead end-to-end architecture for Data Engineering, Data Warehousing, and AI/ML solutions on GCP.
- Design scalable, secure, future-proof solutions using GCP-native services BigQuery, Dataflow, Cloud Composer, Vertex AI, Dataproc, Cloud Storage, and more.
- Build foundational architectures: microservices, event-driven systems, event streaming, and online ML systems.
- Champion data governance, data management best practices, and platform maintainability.
Delivery Leadership:
- Act as Delivery Lead on large-scale programs owning timelines, quality, risk, and client satisfaction end to end.
- Drive program governance across workstreams, keeping cross-functional and cross-geography teams aligned.
- Step in hands-on during critical delivery phases architecture validation, performance tuning, production issue resolution.
- Bridge the gap between architecture decisions and execution realities, ensuring long-term scalability is never sacrificed for short-term speed.
- Mentor delivery teams, instilling strong engineering practices, accountability, and a culture of continuous improvement.
Client Engagement:
- Become a trusted thought partner to senior client leaders understanding their pain points and translating them into actionable technical strategies.
- Proactively identify client needs and align them with innovative, business-impacting solutions.
- Communicate complex technical concepts clearly across executive, business, and engineering audiences.
- Build lasting relationships with senior stakeholders and cross-functional teams.
Community & Enablement:
- Contribute to best practices, reference architectures, and technical content that elevate the broader practice.
- Collaborate with data engineers and data scientists to co-develop architecture that serves both analytical and operational needs.
Thus responsibilities list.
- Requirements / Qualifications / Skills: The posting has "Must-Have" and "Nice to Have". Must-Have includes: 12+ years in Data Engineering and Cloud-native technologies, with deep GCP expertise. Hands-on mastery of: BigQuery, Dataflow, Cloud Composer, Vertex AI, Dataproc, Cloud Storage, GCP serverless infrastructure. Proven delivery of end-to-end Data Engineering, Data Warehousing, or Analytics platforms at scale. Strong programming skills in Python and/or Java. Experience with Agile, CI/CD, DevOps, and MLOps pipelines. Track record leading large, complex, client-facing delivery programs. Ability to manage cross-functional, cross-geography teams with clarity and accountability. Prior Google with direct exposure to first party tooling. Write and optimize queries using PLX to support data analysis and product features Proficiency in PLX or similar structured querying languages (e.g. SQL, Dremel/Spanner). Nice to Have: Docker & Kubernetes experience. DevOps on GCP. AWS experience, especially in hybrid cloud contexts. Google Cloud Professional Cloud Architect Certification.
We need to decide sections: Requirements, Qualifications, Skills. The instruction says we can use those headings. We need to avoid filler. We have substantive content for Must-Have and Nice to Have. Could combine into Requirements (must-have) and Skills (nice-to-have) or Qualifications. But we need to avoid thin sections. Perhaps we can have one section "Requirements" containing must-have, and another "Skills" containing nice-to-have. Or "Qualifications" for must-have and "Skills" for nice-to-have. Let's see typical: Requirements often list must-have; Skills list nice-to-have. We'll do that.
Thus:
Requirements
with- items for each must-have bullet.
Skills
with nice-to-have bullets. - Benefits: The posting has a Benefits paragraph: "As a full-time employee of the company or as an hourly employee working more than 30 hours per week, you will be eligible to participate in the health, dental, vision, life insurance, and disability plans in accordance with the plan documents, which may be amended from time to time. You will be eligible for benefits on the first day of Employment with the Company. In addition, you are eligible to participate in the Company 401(k) Plan after 30 days of employment, in accordance with the applicable plan terms. The Company provides 11 paid holidays and 12 weeks of Parental Leave. We also follow a “free time” PTO policy, allowing you the flexibility to take the time needed for either sick time or vacation." We need to output as list? Could be prose. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. Benefits is a list of items; we could make
- . But we can also keep as prose. Safer to use
- for benefits list. Let's extract each benefit: - health, dental, vision, life insurance, and disability plans - eligibility on first day of employment - Company 401(k) Plan after 30 days - 11 paid holidays - 12 weeks of Parental Leave - “free time” PTO policy (flexible sick/vacation) We'll list each as
- .
- Pay: The posting has Pay section: "The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Fractal, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the starting base range is: $225,000. In addition, you may be eligible for a discretionary bonus for the current performance period."
We need to include Pay section only if real specific content. It gives a starting base range estimate $225,000 and mentions discretionary bonus. That's specific enough. So we include Pay heading with maybe
prose. - Schedule: No mention of schedule (e.g., full-time, hours). Not present. So we omit Schedule section. - Also we might need to include "About the role" section with company description and role overview. Let's craft that. Company description paragraph: "It's fun to work in a company where people truly BELIEVE in what they are doing! We're committed to bringing passion and customer focus to the business. Fractal is a strategic AI partner to Fortune 500 companies with a vision to power every human decision in the enterprise. Fractal is building a world where individual choices, freedom, and diversity are the greatest assets; an ecosystem where human imagination is at the heart of every decision. Where no possibility is written off, only challenged to get better. We believe that a true Fractalite is the one who empowers imagination with intelligence. Fractal has been featured as a Great Place to Work by The Economic Times in partnership with the Great Place to Work® Institute and recognized as a ‘Cool Vendor’ and a ‘Vendor to Watch’ by Gartner." Then role overview paragraph: "We're looking for someone recognized as a subject matter expert on the Google Cloud Platform, with deep roots in Data Engineering and a sharp eye for AI/ML-driven solutions. This is not a purely advisory role you'll own architecture, drive delivery, and be the technical anchor clients trust when the stakes are high. If you've spent 12+ years building large-scale data platforms on GCP, know BigQuery and Vertex AI inside out, and thrive at the intersection of strategy and hands-on execution read on." We can combine into About the role section with two
paragraphs. Now we need to output only HTML fragment, no /, no markdown fences. Thus final HTML:
About the role
It's fun to work in a company where people truly BELIEVE in what they are doing! We're committed to bringing passion and customer focus to the business. Fractal is a strategic AI partner to Fortune 500 companies with a vision to power every human decision in the enterprise. Fractal is building a world where individual choices, freedom, and diversity are the greatest assets; an ecosystem where human imagination is at the heart of every decision. Where no possibility is written off, only challenged to get better. We believe that a true Fractalite is the one who empowers imagination with intelligence. Fractal has been featured as a Great Place to Work by The Economic Times in partnership with the Great Place to Work® Institute and recognized as a ‘Cool Vendor’ and a
- . But we can also keep as prose. Safer to use
- for any list of duties/requirements/benefits, and
- items for each must-have bullet.