Insurance Defense Associate Attorney
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate. Must preserve all substantive info.
Let's parse the posting:
"The Miami office of Kubicki Draper is seeking an Associate Attorney with 5+ years of civil litigation experience. Experience in insurance defense and premises liability is highly desired. Hospitality and retail background a plus."
That's about the role.
Then "Requirements" block: "Previous experience in litigation, particularly in the areas of Insurance Defense strongly preferred Licensed member of the Florida Bar and in good standing Drive for Success: Possess an unyielding drive to climb the hierarchical ladder, aspiring to leadership roles and leaving a mark Client-Centric Approach: Our clients are our compass—your unwavering commitment to exceptional client service Organizational Mastery: An organized mind paired with the ability to communicate succinctly and effectively is crucial"
Then "Your Day-to-Day:" list: "Draft/review and respond to substantive pleadings, motions, and discovery Attend/chair hearings, depositions, mediations, and meetings with clients, as well as negotiate settlements Must be competent & proficient in the use of Word, Microsoft Office, PowerPoint & Excel Communicate in a highly effective manner with team members and clients Ability to work in a fast-paced, evolving environment"
Then "Benefits": "We offer competitive pay, top-tier medical insurance, 401(k) with matching, and much more."
Then "Why Join Us?" with subpoints: Opportunity to Grow..., Work-Life Balance..., Long-Term Value..., Inclusive Culture..., At Kubicki Draper..., etc. Also mention "No matter where you are in your legal journey—from your first case to your hundredth—you'll find the support, challenge, and opportunity to succeed."
Also "Kindly note: Direct applicants only. No phone calls or recruiters, please." That's application instruction, should be removed.
We need sections: About the role (maybe "About the role" heading). Responsibilities (Your Day-to-Day). Requirements (maybe "Requirements" heading). Qualifications? Could combine with Requirements? The posting has "Requirements" and also "Licensed member of the Florida Bar". That's qualification. Could put under Requirements. Skills: maybe mention proficiency in Word, etc. Could be under Skills. Benefits: we have benefits. Pay: they mention competitive pay but not specific amount; we should not create Pay section unless posting actually states them. It says "competitive pay" but that's vague; rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "competitive pay" which is a statement about pay, albeit not specific. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive pay". So we could include a Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might combine Pay into Benefits? But they said separate sections for Benefits, Pay, Schedule. Since we have Benefits and Pay mentioned, we could include both. Schedule: not mentioned, so omit.
We need to avoid filler like "commensurate with experience". Not present.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info; do not invent or summarize away detail.
We need to remove boilerplate: EEO etc. Not present.
We need to not repeat job title as heading.
We need to not put Job ID.
We need to output only HTML fragment.
Let's craft sections:
- About the role (prose)
- Responsibilities (list)
- Requirements (list maybe)
- Skills (list maybe)
- Benefits (list)
- Pay (maybe prose)
But we need to decide what goes where.
The posting includes:
About the role: first paragraph.
Requirements: includes "Previous experience in litigation, particularly in the areas of Insurance Defense strongly preferred", "Licensed member of the Florida Bar and in good standing", then some soft skills: "Drive for Success: ...", "Client-Centric Approach: ...", "Organizational Mastery: ...". Those could be considered Requirements or Qualifications. We'll treat them as Requirements.
Your Day-to-Day: responsibilities list.
Skills: proficiency in Word, Microsoft Office, PowerPoint & Excel; communicate effectively; ability to work in fast-paced environment.
Benefits: "We offer competitive pay, top-tier medical insurance, 401(k) with matching, and much more." Actually includes pay. So maybe Benefits includes pay. But we could separate Pay: "competitive pay". Benefits: "top-tier medical insurance, 401(k) with matching, and much more." However the sentence lumps them together. To avoid splitting incorrectly, maybe keep Benefits section with that whole sentence, and not create Pay section because it's not separate specific pay details. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits and pay together. Could we create Benefits section and include the whole sentence? That would satisfy. Pay section would be redundant. So we will not create Pay section.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
Check if any other sections like Qualifications: we could merge Requirements and Qualifications but we already have Requirements. Could also have Qualifications for Florida Bar etc. But we can keep Requirements covering that.
Now we need to format.
About the role:
The Miami office of Kubicki Draper is seeking an Associate Attorney with 5+ years of civil litigation experience. Experience in insurance defense and premises liability is highly desired. Hospitality and retail background a plus.
Responsibilities: Responsibilities
- Draft/review and respond to substantive pleadings, motions, and discovery
- Attend/chair hearings, depositions, mediations, and meetings with clients, as well as negotiate settlements
- Must be competent & proficient in the use of Word, Microsoft Office, PowerPoint & Excel
- Communicate in a highly effective manner with team members and clients
- Ability to work in a fast-paced, evolving environment
But note that some of those items are actually skills; but we can keep them under Responsibilities as they are day-to-day. However we also have a Skills section maybe for proficiency etc. To avoid duplication, we could split: Responsibilities: drafting pleadings, attend hearings, negotiate settlements. Skills: proficiency in Office, communication, fast-paced environment. Let's see.
The "Your Day-to-Day:" includes all those bullet points. So we could treat all as Responsibilities. Then Skills section maybe not needed. But we have also "Drive for Success", etc. Those are soft skills but could be under Requirements.
Thus we can have:
- About the role
- Responsibilities (list of duties)
- Requirements (list of qualifications and soft skills)
- Benefits (list)
We need to ensure we use - for any list.
Let's extract Requirements list:
- Previous experience in litigation, particularly in the areas of Insurance Defense strongly preferred
- Licensed member of the Florida Bar and in good standing
- Drive for Success: Possess an unyielding drive to climb the hierarchical ladder, aspiring to leadership roles and leaving a mark
- Client-Centric Approach: Our clients are our compass—your unwavering commitment to exceptional client service
- Organizational Mastery: An organized mind paired with the ability to communicate succinctly and effectively is crucial
We could keep each as
- .
Benefits list: The sentence: "We offer competitive pay, top-tier medical insurance, 401(k) with matching, and much more." Could be a
- Competitive pay
- Top-tier medical insurance
- 401(k) with matching
- And much more
but "and much more" is vague; maybe keep as prose? But rule: Use - for any list of duties/requirements/benefits. So we should list them. However "and much more" is not specific; but we could still include as a list item. Might be considered filler? It's not "N/A" etc. It's vague but still part of the posting. I'd include it.
Now we need to ensure we don't include boilerplate like "Kindly note: Direct applicants only. No phone calls or recruiters, please." Remove.
Now produce HTML fragment:
About the role
The Miami office of Kubicki Draper is seeking an Associate Attorney with 5+ years of civil litigation experience. Experience in insurance defense and premises liability is highly desired. Hospitality and retail background a plus.
Responsibilities
- Draft/review and respond to substantive pleadings, motions, and discovery
- Attend/chair hearings, depositions, mediations, and meetings with clients, as well as negotiate settlements
Requirements
- Previous experience in litigation, particularly in the areas of Insurance Defense strongly preferred
- Licensed member of the Florida Bar and in good standing
- Drive for Success: Possess an unyielding drive to climb the hierarchical ladder, aspiring to leadership roles and leaving a mark
- Client-Centric Approach: Our clients are our compass—your unwavering commitment to exceptional client service
- Organizational Mastery: An organized mind paired with the ability to communicate succinctly and effectively is crucial
Benefits
- Competitive pay
- Top-tier medical insurance
- 401(k) with matching
- And much more
Check if any other substantive info: "Why Join Us?" sections: Opportunity to Grow, Work-Life Balance, Long-Term Value, Inclusive Culture, At Kubicki Draper..., etc. Those are substantive and should be included. We missed them. Indeed we need to preserve all substantive info. So we need a section for "Why Join Us?" maybe heading "Why Join Us?" but the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not list "Why Join Us?" as an allowed heading. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but we should likely stick to those headings. However we could still create a heading not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might be interpreted that we should use those headings for sections; but we could also use other headings if needed? The examples are given, but not exclusive. However to be safe, we could incorporate that content under existing sections like Benefits or Requirements? But they are not exactly benefits or requirements. Could be under "About the role" or maybe a separate section like "Why Join Us?" but not in list. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect us to use those headings when appropriate. If we have content that doesn't fit, we might need to create a heading like "Why Join Us?" but it's not in the list. However the instruction says "e.g." meaning for example, not exhaustive. So we can use other headings if needed. But they also say "Pre
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive info; do not invent or summarize away detail. We need to remove boilerplate: EEO etc. Not present. We need to not repeat job title as heading. We need to not put Job ID. We need to output only HTML fragment. Let's craft sections: - About the role (prose) - Responsibilities (list) - Requirements (list maybe) - Skills (list maybe) - Benefits (list) - Pay (maybe prose) But we need to decide what goes where. The posting includes: About the role: first paragraph. Requirements: includes "Previous experience in litigation, particularly in the areas of Insurance Defense strongly preferred", "Licensed member of the Florida Bar and in good standing", then some soft skills: "Drive for Success: ...", "Client-Centric Approach: ...", "Organizational Mastery: ...". Those could be considered Requirements or Qualifications. We'll treat them as Requirements. Your Day-to-Day: responsibilities list. Skills: proficiency in Word, Microsoft Office, PowerPoint & Excel; communicate effectively; ability to work in fast-paced environment. Benefits: "We offer competitive pay, top-tier medical insurance, 401(k) with matching, and much more." Actually includes pay. So maybe Benefits includes pay. But we could separate Pay: "competitive pay". Benefits: "top-tier medical insurance, 401(k) with matching, and much more." However the sentence lumps them together. To avoid splitting incorrectly, maybe keep Benefits section with that whole sentence, and not create Pay section because it's not separate specific pay details. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits and pay together. Could we create Benefits section and include the whole sentence? That would satisfy. Pay section would be redundant. So we will not create Pay section. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. Check if any other sections like Qualifications: we could merge Requirements and Qualifications but we already have Requirements. Could also have Qualifications for Florida Bar etc. But we can keep Requirements covering that. Now we need to format. About the role:
The Miami office of Kubicki Draper is seeking an Associate Attorney with 5+ years of civil litigation experience. Experience in insurance defense and premises liability is highly desired. Hospitality and retail background a plus.
Responsibilities:Responsibilities
- Draft/review and respond to substantive pleadings, motions, and discovery
- Attend/chair hearings, depositions, mediations, and meetings with clients, as well as negotiate settlements
- Must be competent & proficient in the use of Word, Microsoft Office, PowerPoint & Excel
- Communicate in a highly effective manner with team members and clients
- Ability to work in a fast-paced, evolving environment
- for any list. Let's extract Requirements list: - Previous experience in litigation, particularly in the areas of Insurance Defense strongly preferred - Licensed member of the Florida Bar and in good standing - Drive for Success: Possess an unyielding drive to climb the hierarchical ladder, aspiring to leadership roles and leaving a mark - Client-Centric Approach: Our clients are our compass—your unwavering commitment to exceptional client service - Organizational Mastery: An organized mind paired with the ability to communicate succinctly and effectively is crucial We could keep each as
- .
Benefits list: The sentence: "We offer competitive pay, top-tier medical insurance, 401(k) with matching, and much more." Could be a
- Competitive pay
- Top-tier medical insurance
- 401(k) with matching
- And much more but "and much more" is vague; maybe keep as prose? But rule: Use
- for any list of duties/requirements/benefits. So we should list them. However "and much more" is not specific; but we could still include as a list item. Might be considered filler? It's not "N/A" etc. It's vague but still part of the posting. I'd include it.
Now we need to ensure we don't include boilerplate like "Kindly note: Direct applicants only. No phone calls or recruiters, please." Remove.
Now produce HTML fragment:
About the role
The Miami office of Kubicki Draper is seeking an Associate Attorney with 5+ years of civil litigation experience. Experience in insurance defense and premises liability is highly desired. Hospitality and retail background a plus.
Responsibilities
- Draft/review and respond to substantive pleadings, motions, and discovery
- Attend/chair hearings, depositions, mediations, and meetings with clients, as well as negotiate settlements
Requirements
- Previous experience in litigation, particularly in the areas of Insurance Defense strongly preferred
- Licensed member of the Florida Bar and in good standing
- Drive for Success: Possess an unyielding drive to climb the hierarchical ladder, aspiring to leadership roles and leaving a mark
- Client-Centric Approach: Our clients are our compass—your unwavering commitment to exceptional client service
- Organizational Mastery: An organized mind paired with the ability to communicate succinctly and effectively is crucial
Benefits
- Competitive pay
- Top-tier medical insurance
- 401(k) with matching
- And much more
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but we should likely stick to those headings. However we could still create a heading not in list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might be interpreted that we should use those headings for sections; but we could also use other headings if needed? The examples are given, but not exclusive. However to be safe, we could incorporate that content under existing sections like Benefits or Requirements? But they are not exactly benefits or requirements. Could be under "About the role" or maybe a separate section like "Why Join Us?" but not in list. The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect us to use those headings when appropriate. If we have content that doesn't fit, we might need to create a heading like "Why Join Us?" but it's not in the list. However the instruction says "e.g." meaning for example, not exhaustive. So we can use other headings if needed. But they also say "Pre