Operations Supervisor - DAYS with Security Clearance
for section headings
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
- Preserve ALL substantive information
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- 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
- Output ONLY the HTML fragment — no /, no markdown code fences
Let me parse the content:
1. Benefits list at top: "Here's why we want you to consider LDRM:" with bullet points. This is a Benefits section.
2. Location requirement: "You must live within a 90-mile radius of the National Visa Center, located in Portsmouth, New Hampshire, to be considered." This could be part of Qualifications or a separate note.
3. Job Summary: paragraph.
4. Responsibilities: list of bullet points.
5. Qualifications: with subsections:
- Minimum Qualifications (bullet points)
- Minimum Knowledge, Skills and Abilities (bullet points)
- Physical Requirements (prose)
- Work Environment (prose)
6. Company description: "At LDRM, honesty and integrity..." This is company boilerplate. The rules say remove boilerplate, but this is company description. However, the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company description might be considered boilerplate? But it's substantive about the company. The rule says "Preserve ALL substantive information". I think we should include it as a Company Description section.
7. Job ID and Work Type: "Job ID 2026-24767 Work Type On-Site" - this is minor metadata, fold into a short
or drop. I'll include as a short paragraph.
8. Company Description again: "Work Where it Matters LDRM, a joint venture..." This is more company description. Might be duplicate. I'll combine.
Now, structure:
- Benefits section (since there is a list)
- Job Summary
- Responsibilities
- Qualifications (with subsections? The rule says use
for section headings. Should I use for each subsection? The rule says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't mention subsections. But we can use for main sections and maybe for subsections? However, the rule only mentions for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels, but to be safe, I'll use for main sections and maybe for subsections? But the output should be semantic HTML. I think using for main sections and for subsections is fine. However, the rule says "use for section headings". It doesn't say we cannot use other headings. But to keep it simple, maybe we can make Qualifications as one section with sub-lists. But the content has distinct subsections: Minimum Qualifications, Minimum Knowledge Skills and Abilities, Physical Requirements, Work Environment. They are distinct. I'll use for Qualifications and then for each subsection? But the rule says "use for section headings". It might be okay to use for subsections. However, the example only shows . I'll use for each major section, and for subsections, I'll use but the rule didn't specify. To be safe, I'll make each subsection a separate ? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications into one section with sub-lists.
Let's see: The posting has "Qualifications" heading, then "Minimum Qualifications:", "Minimum Knowledge, Skills and Abilities:", "Physical Requirements:", "Work Environment:". These are subsections. I'll create a Qualifications section with and then use for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
or drop it. I'll include a paragraph at the end: "Job ID: 2026-24767 | Work Type: On-Site".
Also, the location requirement appears twice: once at top, once in qualifications. I'll keep it in qualifications.
Now, remove boilerplate: The company description includes "At LDRM, honesty and integrity govern our activities..." and "Work Where it Matters...". This is company marketing. Might be considered boilerplate? But it's specific to the company. The rule says remove "cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is not that. It's company description. I'll include it as a Company Description section.
But note: The company description appears twice? Actually, there is a "Company Description" heading in the text? The text says "Company Description Work Where it Matters LDRM, a joint venture...". So it's a section. I'll include it.
Now, let's write HTML.
I'll start with Benefits:
Benefits
- Tuition reimbursement program
- Quarterly performance bonus up to $1,050
- 401(k), health, dental and vision plans, and other insurances
- Employee Assistance Plan
- Paid training and paid time off
Job Summary:
Job Summary
The Operations Supervisor supervises, directs, trains and assists staff in performing applicable support functions as it relates to the particular function assigned. The Operations Supervisor supervises employees and day to day operations ensuring that work performed in his/her functional area is performed to optimum quality standards and provides procedures and retraining to employees as needed.
Responsibilities:
Responsibilities
- Supervises, directs, trains and assists staff in performing applicable support functions as it relates to the particular function assigned. Supervises employees and the day-to-day operations ensuring that work performed in his/her functional area is performed to optimum quality standards and provides procedures and retraining to employees as needed.
- Uses independent judgement to assign work to employees based on site needs to meet production or quality requirements (objectives/goals).
- Assists Operations Managers and Assistant Operations Managers to ensure timely delivery of all deliverables as they relate to their functional area. Tracks progress of all activities in his/her functional area and may make adjustments to achieve objectives and reports the status to the Unit Manager or Assistant Operations Manager as appropriate.
- Manages the progressive discipline process within area of responsibility and makes recommendations for promotions and terminations.
- Initiates performance reviews for employees within area of responsibility.
- May interview and assess applicants and make recommendations for employee selection.
- Trains new employees and conducts refresher training for current employees.
- Ensures that the Standard Operating Procedures for his/her area of responsibility are used, understood and kept up to date.
Qualifications:
Qualifications
Minimum Qualifications
- Associates Degree and one (1) year of experience in visa operations support. One (1) year of supervisory experience may be substituted for visa operations support experience.
- An additional two years (2) of (similar) team management experience may be substituted for an Associates degree.
- Must be able to obtain and maintain a SECRET level security clearance; otherwise, an MRPT is required.
- Must live within 90 miles of Portsmouth, NH, and be a U.S. citizen.
Minimum Knowledge, Skills and Abilities
- Strong written and verbal command of the English language.
- Strong administrative and organizational skills. Basic Computer Skills.
- Excellent interpersonal and communication skills.
- Demonstrate a professional work ethic.
- Ability to work independently and collaboratively.
- Analytical skills and attention to detail to successfully analyze and evaluate trends, disseminate information to a wide audience.
Physical Requirements
While performing the duties of this job, the employee is occasionally required to stand; walk; sit; use hands and fingers to handle, or feel objects, tools or controls; use fingers and hands to type or write; reach with hands and arms; talk or hear; taste or smell. Specific vision abilities required by the job.
Work Environment
You will primarily work in an office environment but may be required to work in other work environments as well.
Company Description:
Company Description
At LDRM, honesty and integrity govern our activities. We fulfill our commitments, and we treat everyone with dignity and respect. As an Alaskan Native company, our mission is to improve the quality of life for our shareholders and our people by maximizing economic growth, protecting and enhancing our environment, and by promoting healthy communities with decisions, actions, and behaviors consistent with our core principles.
LDRM, a joint venture comprised of Lockwood Hills Federal, an Akima company, and DTSV, is not just another technical support contractor. As an Alaska Native Corporation (ANC), our mission and purpose extend beyond our exciting federal projects as we support our shareholder communities in Alaska. At LDRM, the work you do every day makes a difference in the lives of our 15,000 Iñupiat shareholders, a group of Alaska natives from one of the most remote and harshest environments in the United States. For our shareholders, LDRM provides support and employment opportunities and contributes to the survival of a culture that has thrived above the Arctic Circle for more than 10,000 years. For our government customers, LDRM provides technical, operational, and administrative support services to federal agencies, including Department of State and the U.S. Patent and Trademark Office. As an LDRM employee, you will be surrounded by a challenging, yet supportive work environment that is committed to innovation and diversity, two of our most important values. You will also have access to our comprehensive benefits and competitive pay in addition to growth opportunities and excellent retirement options.
Metadata:
Job ID: 20
for prose - Do NOT repeat job title as heading - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it - Preserve ALL substantive information - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - 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 - Output ONLY the HTML fragment — no /, no markdown code fences Let me parse the content: 1. Benefits list at top: "Here's why we want you to consider LDRM:" with bullet points. This is a Benefits section. 2. Location requirement: "You must live within a 90-mile radius of the National Visa Center, located in Portsmouth, New Hampshire, to be considered." This could be part of Qualifications or a separate note. 3. Job Summary: paragraph. 4. Responsibilities: list of bullet points. 5. Qualifications: with subsections: - Minimum Qualifications (bullet points) - Minimum Knowledge, Skills and Abilities (bullet points) - Physical Requirements (prose) - Work Environment (prose) 6. Company description: "At LDRM, honesty and integrity..." This is company boilerplate. The rules say remove boilerplate, but this is company description. However, the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company description might be considered boilerplate? But it's substantive about the company. The rule says "Preserve ALL substantive information". I think we should include it as a Company Description section. 7. Job ID and Work Type: "Job ID 2026-24767 Work Type On-Site" - this is minor metadata, fold into a short
or drop. I'll include as a short paragraph. 8. Company Description again: "Work Where it Matters LDRM, a joint venture..." This is more company description. Might be duplicate. I'll combine. Now, structure: - Benefits section (since there is a list) - Job Summary - Responsibilities - Qualifications (with subsections? The rule says use
for section headings. Should I use for each subsection? The rule says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't mention subsections. But we can use for main sections and maybe for subsections? However, the rule only mentions for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels, but to be safe, I'll use for main sections and maybe for subsections? But the output should be semantic HTML. I think using for main sections and for subsections is fine. However, the rule says "use for section headings". It doesn't say we cannot use other headings. But to keep it simple, maybe we can make Qualifications as one section with sub-lists. But the content has distinct subsections: Minimum Qualifications, Minimum Knowledge Skills and Abilities, Physical Requirements, Work Environment. They are distinct. I'll use for Qualifications and then for each subsection? But the rule says "use for section headings". It might be okay to use for subsections. However, the example only shows . I'll use for each major section, and for subsections, I'll use but the rule didn't specify. To be safe, I'll make each subsection a separate ? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications into one section with sub-lists.
Let's see: The posting has "Qualifications" heading, then "Minimum Qualifications:", "Minimum Knowledge, Skills and Abilities:", "Physical Requirements:", "Work Environment:". These are subsections. I'll create a Qualifications section with and then use for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
for main sections and maybe for subsections? However, the rule only mentions for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels, but to be safe, I'll use for main sections and maybe for subsections? But the output should be semantic HTML. I think using for main sections and for subsections is fine. However, the rule says "use for section headings". It doesn't say we cannot use other headings. But to keep it simple, maybe we can make Qualifications as one section with sub-lists. But the content has distinct subsections: Minimum Qualifications, Minimum Knowledge Skills and Abilities, Physical Requirements, Work Environment. They are distinct. I'll use for Qualifications and then for each subsection? But the rule says "use for section headings". It might be okay to use for subsections. However, the example only shows . I'll use for each major section, and for subsections, I'll use but the rule didn't specify. To be safe, I'll make each subsection a separate ? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications into one section with sub-lists.
Let's see: The posting has "Qualifications" heading, then "Minimum Qualifications:", "Minimum Knowledge, Skills and Abilities:", "Physical Requirements:", "Work Environment:". These are subsections. I'll create a Qualifications section with and then use for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels, but to be safe, I'll use for main sections and maybe for subsections? But the output should be semantic HTML. I think using for main sections and for subsections is fine. However, the rule says "use for section headings". It doesn't say we cannot use other headings. But to keep it simple, maybe we can make Qualifications as one section with sub-lists. But the content has distinct subsections: Minimum Qualifications, Minimum Knowledge Skills and Abilities, Physical Requirements, Work Environment. They are distinct. I'll use for Qualifications and then for each subsection? But the rule says "use for section headings". It might be okay to use for subsections. However, the example only shows . I'll use for each major section, and for subsections, I'll use but the rule didn't specify. To be safe, I'll make each subsection a separate ? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications into one section with sub-lists.
Let's see: The posting has "Qualifications" heading, then "Minimum Qualifications:", "Minimum Knowledge, Skills and Abilities:", "Physical Requirements:", "Work Environment:". These are subsections. I'll create a Qualifications section with and then use for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
for main sections and maybe for subsections? But the output should be semantic HTML. I think using for main sections and for subsections is fine. However, the rule says "use for section headings". It doesn't say we cannot use other headings. But to keep it simple, maybe we can make Qualifications as one section with sub-lists. But the content has distinct subsections: Minimum Qualifications, Minimum Knowledge Skills and Abilities, Physical Requirements, Work Environment. They are distinct. I'll use for Qualifications and then for each subsection? But the rule says "use for section headings". It might be okay to use for subsections. However, the example only shows . I'll use for each major section, and for subsections, I'll use but the rule didn't specify. To be safe, I'll make each subsection a separate ? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications into one section with sub-lists.
Let's see: The posting has "Qualifications" heading, then "Minimum Qualifications:", "Minimum Knowledge, Skills and Abilities:", "Physical Requirements:", "Work Environment:". These are subsections. I'll create a Qualifications section with and then use for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
for main sections and for subsections is fine. However, the rule says "use for section headings". It doesn't say we cannot use other headings. But to keep it simple, maybe we can make Qualifications as one section with sub-lists. But the content has distinct subsections: Minimum Qualifications, Minimum Knowledge Skills and Abilities, Physical Requirements, Work Environment. They are distinct. I'll use for Qualifications and then for each subsection? But the rule says "use for section headings". It might be okay to use for subsections. However, the example only shows . I'll use for each major section, and for subsections, I'll use but the rule didn't specify. To be safe, I'll make each subsection a separate ? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications into one section with sub-lists.
Let's see: The posting has "Qualifications" heading, then "Minimum Qualifications:", "Minimum Knowledge, Skills and Abilities:", "Physical Requirements:", "Work Environment:". These are subsections. I'll create a Qualifications section with and then use for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
for section headings". It doesn't say we cannot use other headings. But to keep it simple, maybe we can make Qualifications as one section with sub-lists. But the content has distinct subsections: Minimum Qualifications, Minimum Knowledge Skills and Abilities, Physical Requirements, Work Environment. They are distinct. I'll use for Qualifications and then for each subsection? But the rule says "use for section headings". It might be okay to use for subsections. However, the example only shows . I'll use for each major section, and for subsections, I'll use but the rule didn't specify. To be safe, I'll make each subsection a separate ? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications into one section with sub-lists.
Let's see: The posting has "Qualifications" heading, then "Minimum Qualifications:", "Minimum Knowledge, Skills and Abilities:", "Physical Requirements:", "Work Environment:". These are subsections. I'll create a Qualifications section with and then use for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
for each subsection? But the rule says "use for section headings". It might be okay to use for subsections. However, the example only shows . I'll use for each major section, and for subsections, I'll use but the rule didn't specify. To be safe, I'll make each subsection a separate ? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications into one section with sub-lists.
Let's see: The posting has "Qualifications" heading, then "Minimum Qualifications:", "Minimum Knowledge, Skills and Abilities:", "Physical Requirements:", "Work Environment:". These are subsections. I'll create a Qualifications section with and then use for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
for subsections. However, the example only shows . I'll use for each major section, and for subsections, I'll use but the rule didn't specify. To be safe, I'll make each subsection a separate ? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications into one section with sub-lists.
Let's see: The posting has "Qualifications" heading, then "Minimum Qualifications:", "Minimum Knowledge, Skills and Abilities:", "Physical Requirements:", "Work Environment:". These are subsections. I'll create a Qualifications section with and then use for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
for each major section, and for subsections, I'll use but the rule didn't specify. To be safe, I'll make each subsection a separate ? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications into one section with sub-lists.
Let's see: The posting has "Qualifications" heading, then "Minimum Qualifications:", "Minimum Knowledge, Skills and Abilities:", "Physical Requirements:", "Work Environment:". These are subsections. I'll create a Qualifications section with and then use for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications into one section with sub-lists.
Let's see: The posting has "Qualifications" heading, then "Minimum Qualifications:", "Minimum Knowledge, Skills and Abilities:", "Physical Requirements:", "Work Environment:". These are subsections. I'll create a Qualifications section with and then use for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
for each subsection. That's semantic.
But the rule says "use for section headings". It doesn't say we cannot use . I'll do that.
Now, Benefits: The list at top is benefits. I'll create a Benefits section.
Job Summary: one paragraph.
Responsibilities: list.
Qualifications: with subsections.
Company Description: maybe include as a section.
Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
. I'll do that. Now, Benefits: The list at top is benefits. I'll create a Benefits section. Job Summary: one paragraph. Responsibilities: list. Qualifications: with subsections. Company Description: maybe include as a section. Job ID and Work Type: include as a short paragraph at the end or beginning? The rule says fold minor metadata into a short
or drop it. I'll include a paragraph at the end: "Job ID: 2026-24767 | Work Type: On-Site". Also, the location requirement appears twice: once at top, once in qualifications. I'll keep it in qualifications. Now, remove boilerplate: The company description includes "At LDRM, honesty and integrity govern our activities..." and "Work Where it Matters...". This is company marketing. Might be considered boilerplate? But it's specific to the company. The rule says remove "cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is not that. It's company description. I'll include it as a Company Description section. But note: The company description appears twice? Actually, there is a "Company Description" heading in the text? The text says "Company Description Work Where it Matters LDRM, a joint venture...". So it's a section. I'll include it. Now, let's write HTML. I'll start with Benefits:
Benefits
- Tuition reimbursement program
- Quarterly performance bonus up to $1,050
- 401(k), health, dental and vision plans, and other insurances
- Employee Assistance Plan
- Paid training and paid time off
Job Summary
The Operations Supervisor supervises, directs, trains and assists staff in performing applicable support functions as it relates to the particular function assigned. The Operations Supervisor supervises employees and day to day operations ensuring that work performed in his/her functional area is performed to optimum quality standards and provides procedures and retraining to employees as needed.
Responsibilities:Responsibilities
- Supervises, directs, trains and assists staff in performing applicable support functions as it relates to the particular function assigned. Supervises employees and the day-to-day operations ensuring that work performed in his/her functional area is performed to optimum quality standards and provides procedures and retraining to employees as needed.
- Uses independent judgement to assign work to employees based on site needs to meet production or quality requirements (objectives/goals).
- Assists Operations Managers and Assistant Operations Managers to ensure timely delivery of all deliverables as they relate to their functional area. Tracks progress of all activities in his/her functional area and may make adjustments to achieve objectives and reports the status to the Unit Manager or Assistant Operations Manager as appropriate.
- Manages the progressive discipline process within area of responsibility and makes recommendations for promotions and terminations.
- Initiates performance reviews for employees within area of responsibility.
- May interview and assess applicants and make recommendations for employee selection.
- Trains new employees and conducts refresher training for current employees.
- Ensures that the Standard Operating Procedures for his/her area of responsibility are used, understood and kept up to date.
Qualifications
Minimum Qualifications
- Associates Degree and one (1) year of experience in visa operations support. One (1) year of supervisory experience may be substituted for visa operations support experience.
- An additional two years (2) of (similar) team management experience may be substituted for an Associates degree.
- Must be able to obtain and maintain a SECRET level security clearance; otherwise, an MRPT is required.
- Must live within 90 miles of Portsmouth, NH, and be a U.S. citizen.
Minimum Knowledge, Skills and Abilities
- Strong written and verbal command of the English language.
- Strong administrative and organizational skills. Basic Computer Skills.
- Excellent interpersonal and communication skills.
- Demonstrate a professional work ethic.
- Ability to work independently and collaboratively.
- Analytical skills and attention to detail to successfully analyze and evaluate trends, disseminate information to a wide audience.
Physical Requirements
While performing the duties of this job, the employee is occasionally required to stand; walk; sit; use hands and fingers to handle, or feel objects, tools or controls; use fingers and hands to type or write; reach with hands and arms; talk or hear; taste or smell. Specific vision abilities required by the job.
Work Environment
You will primarily work in an office environment but may be required to work in other work environments as well.
Company Description:Company Description
At LDRM, honesty and integrity govern our activities. We fulfill our commitments, and we treat everyone with dignity and respect. As an Alaskan Native company, our mission is to improve the quality of life for our shareholders and our people by maximizing economic growth, protecting and enhancing our environment, and by promoting healthy communities with decisions, actions, and behaviors consistent with our core principles.
LDRM, a joint venture comprised of Lockwood Hills Federal, an Akima company, and DTSV, is not just another technical support contractor. As an Alaska Native Corporation (ANC), our mission and purpose extend beyond our exciting federal projects as we support our shareholder communities in Alaska. At LDRM, the work you do every day makes a difference in the lives of our 15,000 Iñupiat shareholders, a group of Alaska natives from one of the most remote and harshest environments in the United States. For our shareholders, LDRM provides support and employment opportunities and contributes to the survival of a culture that has thrived above the Arctic Circle for more than 10,000 years. For our government customers, LDRM provides technical, operational, and administrative support services to federal agencies, including Department of State and the U.S. Patent and Trademark Office. As an LDRM employee, you will be surrounded by a challenging, yet supportive work environment that is committed to innovation and diversity, two of our most important values. You will also have access to our comprehensive benefits and competitive pay in addition to growth opportunities and excellent retirement options.
Metadata:Job ID: 20