Of Counsel -- Bilingual Immigration Attorney
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat the job title as a heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a short `
` or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Analyze the Input Text:**
The input is a job posting for "Of Counsel - Bilingual Immigration Attorney Partnership Track | Alexandria, VA". Let me extract the relevant sections and content.
Structure in the input:
- Position: Of Counsel - Bilingual Immigration Attorney
- Employment Type: Full-Time, Exempt
- Location: Alexandria, VA
- About The Firm: paragraph
- Position Overview: paragraph (actually seems like a block of text, but has structure)
- Key Responsibilities: list of duties (bullet points)
- Qualifications: list of requirements (bullet points, but formatted as paragraphs with bold-like text? Actually they're separated lines starting with "Active license...", "Fluent bilingual...", etc. I'll treat them as a list)
- Compensation & Growth Opportunity: paragraph with specific info
- Ideal Candidate: paragraph
- Important: paragraph
Let me list out all the content carefully:
**Position/Metadata**:
- "Of Counsel - Bilingual Immigration Attorney Partnership Track | Alexandria, VA"
- Position: Of Counsel - Bilingual Immigration Attorney
- Employment Type: Full-Time, Exempt
- Location: Alexandria, VA
**About The Firm**:
"A growing boutique immigration law firm is seeking a senior-level bilingual immigration attorney to join its leadership team. This position is designed for an experienced attorney who is already operating at a partner level and is interested in a clearly defined path toward ownership and partnership. The firm focuses on providing high-quality immigration representation while leveraging technology and streamlined processes to improve the client experience."
**Position Overview**:
"The attorney will have significant autonomy and will work directly with firm leadership. This role is focused on family-based and humanitarian immigration matters, with a strong emphasis on removal defense. The attorney will be responsible for developing case strategy, conducting client consultations, managing complex matters, and providing guidance to associate attorneys who handle the day-to-day execution of cases."
**Key Responsibilities**:
(List items)
- Conduct consultations with current and prospective immigration clients.
- Develop case strategies based on each client's circumstances and objectives.
- Manage matters from initial consultation through resolution.
- Handle complex family-based and humanitarian immigration cases.
- Provide representation at: Master Calendar Hearings, Bond Hearings, Individual Hearings
- Evaluate and respond to Requests for Evidence (RFEs) and changes in case circumstances.
- Advise clients and internal teams on changes in legal strategy.
- Work closely with associate attorneys to ensure effective case execution.
- Provide mentorship and guidance to junior and mid-level attorneys.
- Help contribute to the continued development and growth of the immigration practice.
- Build and maintain strong client relationships.
**Qualifications**:
(List items, but in the text they're formatted as separate lines with bold-like starts. I'll make them list items)
- Active license to practice law and in good standing in at least one U.S. state.
- Fluent bilingual proficiency in English and Spanish, both written and spoken - required.
- 10+ years of immigration law experience.
- Significant experience handling family-based and humanitarian immigration matters.
- Strong experience with removal defense and immigration court proceedings.
- Demonstrated ability to independently conduct client consultations and develop complex case strategies.
- Strong courtroom and advocacy experience.
- Excellent judgment and ability to handle high-stakes matters with professionalism and empathy.
- Demonstrated leadership and attorney-development experience.
- Current or previous partner-level experience preferred, or clear evidence of operating at a partner level.
- Strong client-service skills and professional reputation.
- Interest in taking on greater leadership responsibility and progressing toward partnership.
**Compensation & Growth Opportunity**:
"$145,000-$190,000 base salary, depending on experience. Compensation may be negotiable above the stated range for candidates bringing a significant book of business or strong partner-level experience. Defined path toward partnership and profit participation. High level of autonomy and direct access to firm leadership. Opportunity to help shape and grow an expanding immigration practice."
**Ideal Candidate**:
"The ideal candidate is a senior bilingual immigration attorney with substantial experience in family-based immigration, humanitarian relief, and removal defense. The firm is particularly interested in attorneys who already operate at a partner level and are looking for a genuine opportunity to progress toward ownership and partnership."
**Important**:
"This is primarily a family-based, humanitarian, and removal-defense immigration practice. Candidates whose experience is primarily in business/corporate immigration will not be the target profile."
Now, I need to map these to the requested sections using `
`. The allowed headings examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Rules about sections:
- Include a section ONLY when the posting has real, specific content for it
- Never emit a heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Do NOT repeat the job title as a heading
- Do NOT put Job ID / requisition numbers as headings
Let's decide on sections based on the content:
1. "About the role" or "Position Overview"? The prompt says use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The input has "About The Firm" and "Position Overview". I need to map these appropriately. I think "About the firm" could go under a section, but the example says "About the role". However, the input has a distinct "About The Firm" block and a "Position Overview" block. I need to be careful not to create thin sections. Let's see what substantive content we have.
Possible sections:
- About the firm (or "About the role" could encompass firm description, but the prompt's examples list "About the role" as a heading example. I'll use "About the Firm" or maybe "About the Role"? The prompt says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It's not exhaustive, but I should follow the spirit. I think I can use "About the Firm" as an h3, or maybe "Role Overview". But I need to check if the content justifies a section. Yes, there's a solid paragraph about the firm.
- Responsibilities: definitely, has a list of duties.
- Qualifications: definitely, has a list of requirements.
- Skills: maybe overlapping with qualifications. The prompt lists "Skills" as an example heading. But the input doesn't have a separate "Skills" section; qualifications include skills. I might skip "Skills" if it's redundant, or I could fold it into Qualifications. The rule says "Prefer a few substantive sections over many thin ones." So I should avoid creating a "Skills" section if there's not distinct content beyond Qualifications. I'll see.
- Pay: the input has "Compensation & Growth Opportunity" with specific salary range and details. So I should include a "Pay" section with that content. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, so I can include Pay. I should not include "commensurate with experience" etc. It has specific numbers and negotiability, so it's substantive.
- Schedule: the input has "Employment Type: Full-Time, Exempt" and location. No specific schedule details beyond that. The rule says never create Schedule section unless the posting actually states them. It doesn't really state a schedule, just employment type. I could fold employment type into a short
or metadata. The rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can put employment type and location in a short
.
- Benefits: the input has "Compensation & Growth Opportunity" which includes some benefit-like items (path toward partnership, profit participation, autonomy, etc.), but not traditional benefits like health insurance, etc. The rule: never create Benefits section unless the posting actually states them. It doesn't really state "benefits" in the traditional sense. I'll skip a Benefits section. The compensation section covers the growth opportunity part.
Let's plan the structure:
I need to output ONLY the HTML fragment, no /, no markdown code fences.
I'll use these headings (as h3):
- About the Firm (or "About the Role"? The input says "About The Firm". I'll use "About the Firm" as h3, but the example says "About the role". I think it's fine to use "About the Firm" or maybe "Firm Overview". To stay close to the examples, I could use "About the Role" but that might misrepresent the content which is about the firm. Actually, the prompt says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It's giving examples of valid headings. I can use "About the Firm" or "Role Overview". I'll decide based on content. The input has "About The Firm" and "Position Overview". I'll combine or separate? I think I'll do "About the Firm" as h3, then "Position Overview" might not be needed if I have Responsibilities and Qualifications. But the input has distinct content. Let's map carefully.
Let's list all content blocks and decide headings:
1. Metadata: Position, Employment Type, Location. I'll put these in a short
at the top or bottom, not as headings.
2. About The Firm: paragraph. I'll use `
About the Firm
` or `About the Role
`. The prompt's example says "About the role" but the content is about the firm. I'll use `About the Firm
` as it's accurate. Wait, the prompt says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't restrict me to exactly those; they're examples. I'll use "About the Firm" as it's substantive.
3. Position Overview: paragraph. Could this be part of "About the Firm" or separate? I'll consider if it's substantive enough for its own section. It describes the role's focus
` for prose - Do NOT repeat the job title as a heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a short `
` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Text:** The input is a job posting for "Of Counsel - Bilingual Immigration Attorney Partnership Track | Alexandria, VA". Let me extract the relevant sections and content. Structure in the input: - Position: Of Counsel - Bilingual Immigration Attorney - Employment Type: Full-Time, Exempt - Location: Alexandria, VA - About The Firm: paragraph - Position Overview: paragraph (actually seems like a block of text, but has structure) - Key Responsibilities: list of duties (bullet points) - Qualifications: list of requirements (bullet points, but formatted as paragraphs with bold-like text? Actually they're separated lines starting with "Active license...", "Fluent bilingual...", etc. I'll treat them as a list) - Compensation & Growth Opportunity: paragraph with specific info - Ideal Candidate: paragraph - Important: paragraph Let me list out all the content carefully: **Position/Metadata**: - "Of Counsel - Bilingual Immigration Attorney Partnership Track | Alexandria, VA" - Position: Of Counsel - Bilingual Immigration Attorney - Employment Type: Full-Time, Exempt - Location: Alexandria, VA **About The Firm**: "A growing boutique immigration law firm is seeking a senior-level bilingual immigration attorney to join its leadership team. This position is designed for an experienced attorney who is already operating at a partner level and is interested in a clearly defined path toward ownership and partnership. The firm focuses on providing high-quality immigration representation while leveraging technology and streamlined processes to improve the client experience." **Position Overview**: "The attorney will have significant autonomy and will work directly with firm leadership. This role is focused on family-based and humanitarian immigration matters, with a strong emphasis on removal defense. The attorney will be responsible for developing case strategy, conducting client consultations, managing complex matters, and providing guidance to associate attorneys who handle the day-to-day execution of cases." **Key Responsibilities**: (List items) - Conduct consultations with current and prospective immigration clients. - Develop case strategies based on each client's circumstances and objectives. - Manage matters from initial consultation through resolution. - Handle complex family-based and humanitarian immigration cases. - Provide representation at: Master Calendar Hearings, Bond Hearings, Individual Hearings - Evaluate and respond to Requests for Evidence (RFEs) and changes in case circumstances. - Advise clients and internal teams on changes in legal strategy. - Work closely with associate attorneys to ensure effective case execution. - Provide mentorship and guidance to junior and mid-level attorneys. - Help contribute to the continued development and growth of the immigration practice. - Build and maintain strong client relationships. **Qualifications**: (List items, but in the text they're formatted as separate lines with bold-like starts. I'll make them list items) - Active license to practice law and in good standing in at least one U.S. state. - Fluent bilingual proficiency in English and Spanish, both written and spoken - required. - 10+ years of immigration law experience. - Significant experience handling family-based and humanitarian immigration matters. - Strong experience with removal defense and immigration court proceedings. - Demonstrated ability to independently conduct client consultations and develop complex case strategies. - Strong courtroom and advocacy experience. - Excellent judgment and ability to handle high-stakes matters with professionalism and empathy. - Demonstrated leadership and attorney-development experience. - Current or previous partner-level experience preferred, or clear evidence of operating at a partner level. - Strong client-service skills and professional reputation. - Interest in taking on greater leadership responsibility and progressing toward partnership. **Compensation & Growth Opportunity**: "$145,000-$190,000 base salary, depending on experience. Compensation may be negotiable above the stated range for candidates bringing a significant book of business or strong partner-level experience. Defined path toward partnership and profit participation. High level of autonomy and direct access to firm leadership. Opportunity to help shape and grow an expanding immigration practice." **Ideal Candidate**: "The ideal candidate is a senior bilingual immigration attorney with substantial experience in family-based immigration, humanitarian relief, and removal defense. The firm is particularly interested in attorneys who already operate at a partner level and are looking for a genuine opportunity to progress toward ownership and partnership." **Important**: "This is primarily a family-based, humanitarian, and removal-defense immigration practice. Candidates whose experience is primarily in business/corporate immigration will not be the target profile." Now, I need to map these to the requested sections using `
`. The allowed headings examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Rules about sections:
- Include a section ONLY when the posting has real, specific content for it
- Never emit a heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Do NOT repeat the job title as a heading
- Do NOT put Job ID / requisition numbers as headings
Let's decide on sections based on the content:
1. "About the role" or "Position Overview"? The prompt says use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The input has "About The Firm" and "Position Overview". I need to map these appropriately. I think "About the firm" could go under a section, but the example says "About the role". However, the input has a distinct "About The Firm" block and a "Position Overview" block. I need to be careful not to create thin sections. Let's see what substantive content we have.
Possible sections:
- About the firm (or "About the role" could encompass firm description, but the prompt's examples list "About the role" as a heading example. I'll use "About the Firm" or maybe "About the Role"? The prompt says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It's not exhaustive, but I should follow the spirit. I think I can use "About the Firm" as an h3, or maybe "Role Overview". But I need to check if the content justifies a section. Yes, there's a solid paragraph about the firm.
- Responsibilities: definitely, has a list of duties.
- Qualifications: definitely, has a list of requirements.
- Skills: maybe overlapping with qualifications. The prompt lists "Skills" as an example heading. But the input doesn't have a separate "Skills" section; qualifications include skills. I might skip "Skills" if it's redundant, or I could fold it into Qualifications. The rule says "Prefer a few substantive sections over many thin ones." So I should avoid creating a "Skills" section if there's not distinct content beyond Qualifications. I'll see.
- Pay: the input has "Compensation & Growth Opportunity" with specific salary range and details. So I should include a "Pay" section with that content. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, so I can include Pay. I should not include "commensurate with experience" etc. It has specific numbers and negotiability, so it's substantive.
- Schedule: the input has "Employment Type: Full-Time, Exempt" and location. No specific schedule details beyond that. The rule says never create Schedule section unless the posting actually states them. It doesn't really state a schedule, just employment type. I could fold employment type into a short
or metadata. The rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can put employment type and location in a short
. - Benefits: the input has "Compensation & Growth Opportunity" which includes some benefit-like items (path toward partnership, profit participation, autonomy, etc.), but not traditional benefits like health insurance, etc. The rule: never create Benefits section unless the posting actually states them. It doesn't really state "benefits" in the traditional sense. I'll skip a Benefits section. The compensation section covers the growth opportunity part. Let's plan the structure: I need to output ONLY the HTML fragment, no /, no markdown code fences. I'll use these headings (as h3): - About the Firm (or "About the Role"? The input says "About The Firm". I'll use "About the Firm" as h3, but the example says "About the role". I think it's fine to use "About the Firm" or maybe "Firm Overview". To stay close to the examples, I could use "About the Role" but that might misrepresent the content which is about the firm. Actually, the prompt says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It's giving examples of valid headings. I can use "About the Firm" or "Role Overview". I'll decide based on content. The input has "About The Firm" and "Position Overview". I'll combine or separate? I think I'll do "About the Firm" as h3, then "Position Overview" might not be needed if I have Responsibilities and Qualifications. But the input has distinct content. Let's map carefully. Let's list all content blocks and decide headings: 1. Metadata: Position, Employment Type, Location. I'll put these in a short
at the top or bottom, not as headings. 2. About The Firm: paragraph. I'll use `