- Company Name
- Appfabs Incorporation
- Job Title
- Reporting Data Analyst
- Job Description
-
<think>
Okay, let's tackle this. The user wants a concise job profile for a Reporting Data Analyst based on the provided description. First, I need to parse the original job description and extract the key elements.
The job title is clear: Reporting Data Analyst. The role summary mentions partnering with business groups in P&C insurance, acting as an SME on data warehouse and systems. Key responsibilities include being an SME on P&C areas like policy, claims, financials, collaborating with stakeholders, translating business concepts into data logic, working with source systems like Guidewire and SAP, validating SQL queries, reviewing reports, documenting definitions, supporting UAT, and educating users.
Technical qualifications specify 8+ years as a hands-on IT reporting data analyst, 4+ years in P&C insurance, 3+ years with tools like MicroStrategy or Power BI, knowledge of source systems, strong SQL skills, and understanding of dimensional modeling. General qualifications are about self-management, communication, and working with senior stakeholders. Education is a bachelor's in CS, MIS, or related.
I need to structure this into the required sections: Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, Education & Certifications. The user wants it factual, concise, ATS-friendly, globally neutral. No fluff, company details, location, benefits.
Role Summary should be a brief overview. Expectations can be the technical qualifications. Key Responsibilities are the main bullets. Required Skills include the tools, SQL, etc. Education as stated.
I need to make sure to use neutral language, avoid any markdown, and keep under 500 words. Also, translate if needed, but the original is in English. Ensure it's all in English. Remove any company or location info. Make sure the summary is a concise one-liner. Check for required education and certifications, and note that certifications aren't mentioned except the bachelor's degree. The technical qualifications list Certifications separately? Wait, in the original, it's "General Qualifications," but they don't mention certifications. So maybe "Required Education & Certifications" just has the Bachelor's. The user says to exclude fluff and include only specified sections. Let me make sure all required sections are there and nothing extra. Also, avoid any explanations or extra text. Use bullet points appropriately but only as per the example. The example uses bullet points for Role Summary, Key Responsibilities, but the user's output example might not. Wait, looking back at the user's instructions: the output should only include the specified sections. The original example uses bullet points for some items. Wait, the user's example shows that the output should be in the specified format with bullet points where appropriate. For example, Key Responsibilities is in bullet points. The user provided an example output in the query history. Let me check. The user wants the output to be:
Job title,
Role Summary,
Expectations,
Key Responsibilities,
Required Skills,
Required Education & Certifications.
Each section should be formatted appropriately. The user's example shows bullet points for Key Responsibilities, but for other sections, maybe just a paragraph. The user says to "exclude company details, location, benefits, or fluff." Also, make it ATS-friendly, so keywords important. Keep it factual and concise. Let me start drafting each section.
Role Summary: Partners with business groups in P&C insurance to define and deliver reporting. SME on data warehouse and source systems.
Expectations: The technical qualifications are under "Technical Qualifications" and "General Qualifications" in the original. But the user wants "Expectations" which might refer to the job requirements from the candidate's perspective. So, the required experience years and skills. So, "Expectations" here would likely be the experience and skills required, but grouped under the technical qualifications and general qualifications. The user's example in their query history might have "Expectations" as the experience level, e.g., 8+ years experience. So, in the output, the "Expectations" section should include the years of experience and possibly the industry experience.
Wait, looking at the original job description, Technical Qualifications include:
- 8+ years as a hands-on IT Reporting data analyst.
- 4+ years in P&C reporting/analysis.
- 3+ years with specific tools.
- Knowledge of source systems.
- SQL skills, etc.
General Qualifications include self-management, communication, working with senior stakeholders.
But the user wants to exclude fluff and present in the structure: Expectations, Key Responsibilities, Required Skills, etc. So "Expectations" likely refers to the candidate's experience, education, certifications. Let me see the example in the user's history. Wait, in the user's own example in the first query, they have:
Role Summary: Short paragraph.
Expectations: bullet points with experience and skills.
But maybe in this case, "Expectations" is not a standard section. Wait, the user's original instruction says:
Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications.
So, "Expactations" is likely a typo and should be "Expectations". The user wants a section called "Expectations". How should that be interpreted? Maybe the candidate's expectations, but that's not the case. It's more likely part of the job requirements. Maybe the user intended it as part of the qualifications, but the original structure might not have an "Expectations" section. This could be a confusion between sections. Alternatively, maybe the user intended "Expectations" as the job's requirements, similar to "Requirements".
Given the original job description has both Technical and General qualifications, perhaps "Expectations" here refers to the experience and qualifications the candidate is expected to have. So, in the original, Technical Qualifications include years of experience, industry experience, tool experience, etc. General Qualifications include soft skills.
But the user wants to split into sections as per instruction: Role Summary, Expectations, Key Responsibilities, Required Skills, Education & Certifications.
Therefore, "Expectations" would include the technical qualifications (experience years, industry experience, tools) and perhaps the general qualifications, but the user wants it split between sections. For example, "Required Skills" would include SQL, dimensional modeling, knowledge of systems like Guidewire, etc. The "Expectations" would be the years of experience and industry experience. The "Required Skills" would be the tools and technical abilities. So let me map accordingly.
"Expectations" could be the required years and domain experience. Then "Required Skills" includes the technical skills, tools, etc.
So in the original, the Technical Qualifications have:
- 8+ years hands-on IT Reporting data analyst
- 4+ years P&C insurance
- 3+ years with Strategy, Power BI, etc.
- Knowledge of Guidewire, Genius, SAP
- SQL skills, dimensional modeling, etc.
So "Expectations" would be the years of experience, domain experience. Then "Required Skills" would be the tools, knowledge of systems, SQL, etc.
Thus:
Expectations:
- 8+ years IT reporting data analysis experience
- 4+ years in P&C insurance industry; reinsurance a plus
- 3+ years using MicroStrategy/Power BI
Key Responsibilities as per original.
Required Skills: SQL, dimensional modeling, enterprise data warehouse experience, insurance systems (Guidewire, SAP), data validation, documentation, UAT support.
Education: Bachelor's in CS, MIS, etc.
I need to make sure that the sections are correctly mapped without overlap. Also, the user wants to exclude fluff. For example, the "General Qualifications" mention self-management, communication, etc. Should these be included in "Required Skills"? Possibly under professional skills. However, the user's instruction says to exclude non-essential details. Since "Excellent Communication skills..." is part of the job, it should be included in Required Skills. However, the user wants it concise and ATS-friendly. ATS systems often prioritize keywords like SQL, Power BI, etc.
But the user's instruction is to include what's necessary. So maybe include the soft skills under Required Skills. Alternatively, maybe the user wants them in a separate section, but the output structure does not have a specific place for soft skills. The user's listed sections are Role Summary, Expectations, Key Responsibilities, Required Skills, Education & Certifications.
So, the General Qualifications include communication and senior stakeholder experience. Since the user said to exclude "fluff" but these are required skills, they should be included. How to fit them?
Possibly under Required Skills: "Excellent written and verbal communication skills. Proven experience working with senior stakeholders."
Yes. So include that in Required Skills.
So putting it all together, ensuring that the sections are properly filled without duplication.
Also, the user says "global neutral," so avoid any region-specific terms if necessary. But the example uses Guidewire, SAP which are global, so okay.
Now, check the word count. The original is 500 words, so need to be concise.
Final check for each section:
Job Title: Reporting Data Analyst
Role Summary: Partners with P&C business groups to define/deliver reporting. SME on data warehouse and source systems. Ensures accurate data interpretation and reliable reporting.
Expectations: Experience numbers, industry experience.
Key Responsibilities: The bullets from the original.
Required Skills: Technical and soft skills.
Education: BSc in CS/MIS.
Now, structure each section with bullet points where needed, as per user's example. The example output uses bullet points for Key Responsibilities but not for others. Wait, the user's instruction says to output only the specified sections, but the example in the user's query history (previous interaction) might have bullet points in the Role Summary, but perhaps