SNOWFLAKE Platform Admin
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate (EEO, disclaimer, etc). Also remove navigation, cookie, legal, duplicated lines, application instructions.
We need to parse the posting.
Let's extract content:
Role Description SNOWFLAKE Platform Admin Raritan NJ Onsite Good handson EXP in Snowflake utilities SnowSQL Snowpipe Design and implement effective database solutions and models to store and retrieve retail data Assess database implementation procedures to ensure they comply with internal and external regulations Oversee the migration of data from legacy systems to new solutions Recommend solutions to improve new and existing database systems Realtime experience working in OLAP OLTP database models Dimensional models Comprehensive understanding of Star schema Snowflake schema and Data Vault Modelling Design and develop data extraction and integration code modules Partner with the data engineers testing practitioners to strategize ingestion logic consumption patterns testing Build data warehouse data marts on Snowflake while performing data profiling and quality analysis Use version control to maintain versions of data models Enthuse to coach team members collaborate with various stakeholders across the organization and take complete ownership of deliverables Works closely with all business units and engineering teams to develop data strategy for long term data platform architecture Providing technical expertise in data storage structures data mining and data cleansing Good understanding of SNOWFLAKE Architecture and its application for different kinds of Business use case across Retail Domain
Other Details Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity. Benefits/perks listed below may vary depending on the nature of your employment with LTIMindtree (“LTIM”): Benefits And Perks Comprehensive Medical Plan Covering Medical, Dental, VisionShort Term and Long-Term Disability Coverage401(k) Plan with Company matchLife InsuranceVacation Time, Sick Leave, Paid HolidaysPaid Paternity and Maternity Leave The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations. Within the range, individual pay is determined by work location and job level and additional factors including job-related skills, experience, and relevant education or training. Depending on the position offered, other forms of compensation may be provided as part of overall compensation like an annual performance-based bonus, sales incentive pay and other forms of bonus or variable compensation. Disclaimer: The compensation and benefits information provided herein is accurate as of the date of this posting. LTIMindtree is an equal opportunity employer that is committed to diversity in the workplace. Our employment decisions are made without regard to race, color, creed, religion, sex (including pregnancy, childbirth or related medical conditions), gender identity or expression, national origin, ancestry, age, family-care status, veteran status, marital status, civil union status, domestic partnership status, military service, handicap or disability or history of handicap or disability, genetic information, atypical hereditary cellular or blood trait, union affiliation, affectional or sexual orientation or preference, or any other characteristic protected by applicable federal, state, or local law, except where such considerations are bona fide occupational qualifications permitted by law.
We need to remove boilerplate: EEO, disclaimer, etc. Also remove "Other Details" maybe not needed as heading. We'll keep substantive content.
We need sections:
- About the role: maybe a short paragraph summarizing role: "SNOWFLAKE Platform Admin based in Raritan, NJ (Onsite). Requires hands-on experience with Snowflake utilities, SnowSQL, Snowpipe." That's from first line.
- Responsibilities: list of duties: Design and implement effective database solutions and models to store and retrieve retail data; Assess database implementation procedures to ensure they comply with internal and external regulations; Oversee the migration of data from legacy systems to new solutions; Recommend solutions to improve new and existing database systems; Realtime experience working in OLAP OLTP database models Dimensional models Comprehensive understanding of Star schema Snowflake schema and Data Vault Modelling; Design and develop data extraction and integration code modules; Partner with the data engineers testing practitioners to strategize ingestion logic consumption patterns testing; Build data warehouse data marts on Snowflake while performing data profiling and quality analysis; Use version control to maintain versions of data models; Enthuse to coach team members collaborate with various stakeholders across the organization and take complete ownership of deliverables; Works closely with all business units and engineering teams to develop data strategy for long term data platform architecture; Providing technical expertise in data storage structures data mining and data cleansing; Good understanding of SNOWFLAKE Architecture and its application for different kinds of Business use case across Retail Domain.
We need to ensure we don't duplicate. Some sentences are run-on; we can split into list items.
- Requirements: maybe "Good hands-on EXP in Snowflake utilities SnowSQL Snowpipe" etc. But many of those are also responsibilities. The posting doesn't separate requirements explicitly. Could treat "Good hands-on EXP in Snowflake utilities SnowSQL Snowpipe" as requirement. Also maybe "Realtime experience working in OLAP OLTP database models Dimensional models Comprehensive understanding of Star schema Snowflake schema and Data Vault Modelling". But that seems more like skill.
We need to decide sections: Since the posting doesn't have explicit headings, we need to infer. We can create sections based on content grouping.
We could do:
About the role: brief intro.
Responsibilities: list of duties (design, implement, assess, oversee, recommend, partner, build, use version control, coach, collaborate, works closely, providing expertise, good understanding).
Requirements: maybe "Good hands-on experience with Snowflake utilities, SnowSQL, Snowpipe". Also maybe "Experience with OLAP/OLTP, dimensional modeling, star/snowflake schema, data vault". But that overlaps with skills.
Qualifications: maybe not explicit; could omit if no specific.
Skills: list of technical skills: Snowflake utilities, SnowSQL, Snowpipe, OLAP/OLTP, dimensional modeling, star schema, snowflake schema, data vault, data extraction/integration, data profiling, quality analysis, version control, data storage structures, data mining, data cleansing, Snowflake architecture, retail domain.
Benefits: list as given.
We must not invent details; we must preserve all substantive information. So we need to include everything from the posting, but we can reorganize into sections. Must not lose any info.
Let's extract all substantive sentences (excluding boilerplate). We'll list them:
1. SNOWFLAKE Platform Admin Raritan NJ Onsite
2. Good handson EXP in Snowflake utilities SnowSQL Snowpipe
3. Design and implement effective database solutions and models to store and retrieve retail data
4. Assess database implementation procedures to ensure they comply with internal and external regulations
5. Oversee the migration of data from legacy systems to new solutions
6. Recommend solutions to improve new and existing database systems
7. Realtime experience working in OLAP OLTP database models
8. Dimensional models
9. Comprehensive understanding of Star schema Snowflake schema and Data Vault Modelling
10. Design and develop data extraction and integration code modules
11. Partner with the data engineers testing practitioners to strategize ingestion logic consumption patterns testing
12. Build data warehouse data marts on Snowflake while performing data profiling and quality analysis
13. Use version control to maintain versions of data models
14. Enthuse to coach team members collaborate with various stakeholders across the organization and take complete ownership of deliverables
15. Works closely with all business units and engineering teams to develop data strategy for long term data platform architecture
16. Providing technical expertise in data storage structures data mining and data cleansing
17. Good understanding of SNOWFLAKE Architecture and its application for different kinds of Business use case across Retail Domain
18. Benefits And Perks Comprehensive Medical Plan Covering Medical, Dental, VisionShort Term and Long-Term Disability Coverage401(k) Plan with Company matchLife InsuranceVacation Time, Sick Leave, Paid HolidaysPaid Paternity and Maternity Leave
Also there is compensation info but we cannot create Pay section because no specific numbers. However we could include a short paragraph about compensation under About the role? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation info but not specific numbers. It says "Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity." That's still compensation info but not a specific range. Should we include a Pay section? The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation info (though vague). But also says: "Prefer a few substantive sections over many thin ones." And "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The compensation info is vague but not exactly placeholder like "commensurate with experience". It says "Actual compensation within the range will be dependent upon...". That is still vague but not a placeholder phrase. However they also say "The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations." That's still not giving numbers. This could be considered filler. Safer to omit Pay section because no concrete numbers. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated concretely, so we include Benefits. Pay is not stated with numbers, so we omit.
Schedule not stated, omit.
Now we need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to allocate each piece of info to appropriate section without losing any.
Let's try:
About the role: SNOWFLAKE Platform Admin Raritan NJ Onsite. Good hands-on experience in Snowflake utilities SnowSQL Snowpipe.
Responsibilities: list of duties (items 3-7, 10-16 maybe). Actually many items are responsibilities.
Requirements: maybe "Good hands-on experience in Snowflake utilities SnowSQL Snowpipe" could be requirement, but we already used in About the role. Could move to Requirements.
Qualifications: maybe not present; we could omit.
Skills: list of technical skills: Snowflake utilities, SnowSQL, Snowpipe, OLAP/OLTP, dimensional modeling, star schema, snowflake schema, data vault, data extraction/integration, data profiling, quality analysis, version control, data storage structures, data mining, data cleansing, Snowflake architecture, retail domain.
But some of these overlap with responsibilities. We need to ensure we don't duplicate info. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay? It says do not repeat lines? It says "removed duplicated lines". So we should avoid duplicating the same sentence. But we can rephrase? Probably better to allocate each piece to one section only, to avoid duplication.
Let's list each distinct piece:
- Role title and location: SNOWFLAKE Platform Admin Raritan NJ Onsite
- Hands-on experience in Snowflake utilities SnowSQL
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate (EEO, disclaimer, etc). Also remove navigation, cookie, legal, duplicated lines, application instructions. We need to parse the posting. Let's extract content: Role Description SNOWFLAKE Platform Admin Raritan NJ Onsite Good handson EXP in Snowflake utilities SnowSQL Snowpipe Design and implement effective database solutions and models to store and retrieve retail data Assess database implementation procedures to ensure they comply with internal and external regulations Oversee the migration of data from legacy systems to new solutions Recommend solutions to improve new and existing database systems Realtime experience working in OLAP OLTP database models Dimensional models Comprehensive understanding of Star schema Snowflake schema and Data Vault Modelling Design and develop data extraction and integration code modules Partner with the data engineers testing practitioners to strategize ingestion logic consumption patterns testing Build data warehouse data marts on Snowflake while performing data profiling and quality analysis Use version control to maintain versions of data models Enthuse to coach team members collaborate with various stakeholders across the organization and take complete ownership of deliverables Works closely with all business units and engineering teams to develop data strategy for long term data platform architecture Providing technical expertise in data storage structures data mining and data cleansing Good understanding of SNOWFLAKE Architecture and its application for different kinds of Business use case across Retail Domain Other Details Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity. Benefits/perks listed below may vary depending on the nature of your employment with LTIMindtree (“LTIM”): Benefits And Perks Comprehensive Medical Plan Covering Medical, Dental, VisionShort Term and Long-Term Disability Coverage401(k) Plan with Company matchLife InsuranceVacation Time, Sick Leave, Paid HolidaysPaid Paternity and Maternity Leave The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations. Within the range, individual pay is determined by work location and job level and additional factors including job-related skills, experience, and relevant education or training. Depending on the position offered, other forms of compensation may be provided as part of overall compensation like an annual performance-based bonus, sales incentive pay and other forms of bonus or variable compensation. Disclaimer: The compensation and benefits information provided herein is accurate as of the date of this posting. LTIMindtree is an equal opportunity employer that is committed to diversity in the workplace. Our employment decisions are made without regard to race, color, creed, religion, sex (including pregnancy, childbirth or related medical conditions), gender identity or expression, national origin, ancestry, age, family-care status, veteran status, marital status, civil union status, domestic partnership status, military service, handicap or disability or history of handicap or disability, genetic information, atypical hereditary cellular or blood trait, union affiliation, affectional or sexual orientation or preference, or any other characteristic protected by applicable federal, state, or local law, except where such considerations are bona fide occupational qualifications permitted by law. We need to remove boilerplate: EEO, disclaimer, etc. Also remove "Other Details" maybe not needed as heading. We'll keep substantive content. We need sections: - About the role: maybe a short paragraph summarizing role: "SNOWFLAKE Platform Admin based in Raritan, NJ (Onsite). Requires hands-on experience with Snowflake utilities, SnowSQL, Snowpipe." That's from first line. - Responsibilities: list of duties: Design and implement effective database solutions and models to store and retrieve retail data; Assess database implementation procedures to ensure they comply with internal and external regulations; Oversee the migration of data from legacy systems to new solutions; Recommend solutions to improve new and existing database systems; Realtime experience working in OLAP OLTP database models Dimensional models Comprehensive understanding of Star schema Snowflake schema and Data Vault Modelling; Design and develop data extraction and integration code modules; Partner with the data engineers testing practitioners to strategize ingestion logic consumption patterns testing; Build data warehouse data marts on Snowflake while performing data profiling and quality analysis; Use version control to maintain versions of data models; Enthuse to coach team members collaborate with various stakeholders across the organization and take complete ownership of deliverables; Works closely with all business units and engineering teams to develop data strategy for long term data platform architecture; Providing technical expertise in data storage structures data mining and data cleansing; Good understanding of SNOWFLAKE Architecture and its application for different kinds of Business use case across Retail Domain. We need to ensure we don't duplicate. Some sentences are run-on; we can split into list items. - Requirements: maybe "Good hands-on EXP in Snowflake utilities SnowSQL Snowpipe" etc. But many of those are also responsibilities. The posting doesn't separate requirements explicitly. Could treat "Good hands-on EXP in Snowflake utilities SnowSQL Snowpipe" as requirement. Also maybe "Realtime experience working in OLAP OLTP database models Dimensional models Comprehensive understanding of Star schema Snowflake schema and Data Vault Modelling". But that seems more like skill. We need to decide sections: Since the posting doesn't have explicit headings, we need to infer. We can create sections based on content grouping. We could do: About the role: brief intro. Responsibilities: list of duties (design, implement, assess, oversee, recommend, partner, build, use version control, coach, collaborate, works closely, providing expertise, good understanding). Requirements: maybe "Good hands-on experience with Snowflake utilities, SnowSQL, Snowpipe". Also maybe "Experience with OLAP/OLTP, dimensional modeling, star/snowflake schema, data vault". But that overlaps with skills. Qualifications: maybe not explicit; could omit if no specific. Skills: list of technical skills: Snowflake utilities, SnowSQL, Snowpipe, OLAP/OLTP, dimensional modeling, star schema, snowflake schema, data vault, data extraction/integration, data profiling, quality analysis, version control, data storage structures, data mining, data cleansing, Snowflake architecture, retail domain. Benefits: list as given. We must not invent details; we must preserve all substantive information. So we need to include everything from the posting, but we can reorganize into sections. Must not lose any info. Let's extract all substantive sentences (excluding boilerplate). We'll list them: 1. SNOWFLAKE Platform Admin Raritan NJ Onsite 2. Good handson EXP in Snowflake utilities SnowSQL Snowpipe 3. Design and implement effective database solutions and models to store and retrieve retail data 4. Assess database implementation procedures to ensure they comply with internal and external regulations 5. Oversee the migration of data from legacy systems to new solutions 6. Recommend solutions to improve new and existing database systems 7. Realtime experience working in OLAP OLTP database models 8. Dimensional models 9. Comprehensive understanding of Star schema Snowflake schema and Data Vault Modelling 10. Design and develop data extraction and integration code modules 11. Partner with the data engineers testing practitioners to strategize ingestion logic consumption patterns testing 12. Build data warehouse data marts on Snowflake while performing data profiling and quality analysis 13. Use version control to maintain versions of data models 14. Enthuse to coach team members collaborate with various stakeholders across the organization and take complete ownership of deliverables 15. Works closely with all business units and engineering teams to develop data strategy for long term data platform architecture 16. Providing technical expertise in data storage structures data mining and data cleansing 17. Good understanding of SNOWFLAKE Architecture and its application for different kinds of Business use case across Retail Domain 18. Benefits And Perks Comprehensive Medical Plan Covering Medical, Dental, VisionShort Term and Long-Term Disability Coverage401(k) Plan with Company matchLife InsuranceVacation Time, Sick Leave, Paid HolidaysPaid Paternity and Maternity Leave Also there is compensation info but we cannot create Pay section because no specific numbers. However we could include a short paragraph about compensation under About the role? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation info but not specific numbers. It says "Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity." That's still compensation info but not a specific range. Should we include a Pay section? The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation info (though vague). But also says: "Prefer a few substantive sections over many thin ones." And "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The compensation info is vague but not exactly placeholder like "commensurate with experience". It says "Actual compensation within the range will be dependent upon...". That is still vague but not a placeholder phrase. However they also say "The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations." That's still not giving numbers. This could be considered filler. Safer to omit Pay section because no concrete numbers. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated concretely, so we include Benefits. Pay is not stated with numbers, so we omit. Schedule not stated, omit. Now we need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to allocate each piece of info to appropriate section without losing any. Let's try: About the role: SNOWFLAKE Platform Admin Raritan NJ Onsite. Good hands-on experience in Snowflake utilities SnowSQL Snowpipe. Responsibilities: list of duties (items 3-7, 10-16 maybe). Actually many items are responsibilities. Requirements: maybe "Good hands-on experience in Snowflake utilities SnowSQL Snowpipe" could be requirement, but we already used in About the role. Could move to Requirements. Qualifications: maybe not present; we could omit. Skills: list of technical skills: Snowflake utilities, SnowSQL, Snowpipe, OLAP/OLTP, dimensional modeling, star schema, snowflake schema, data vault, data extraction/integration, data profiling, quality analysis, version control, data storage structures, data mining, data cleansing, Snowflake architecture, retail domain. But some of these overlap with responsibilities. We need to ensure we don't duplicate info. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay? It says do not repeat lines? It says "removed duplicated lines". So we should avoid duplicating the same sentence. But we can rephrase? Probably better to allocate each piece to one section only, to avoid duplication. Let's list each distinct piece: - Role title and location: SNOWFLAKE Platform Admin Raritan NJ Onsite - Hands-on experience in Snowflake utilities SnowSQL