Hi ,
Please let me know if you have anyone for this role.
System Engineer
Client:: Milton Center Connecticut
Location:: Litchfield, Connecticut
MOI:: T + S
Start: ASAP
No H1B's
Must haves: Chef or Puppet….SCCM….Active Directory…Windows, Linux and VMware
- The L2 positions have been newly created as part of the operations (Run) group. There are three tiers of support roles:
- L2, L3, & Sustained Engineers
- The L2 roles are a second level support position (first tier is the Services Desk where an incident is logged)
- The L2 engineer will own the incident queue for a specific support area (block, NAS, Windows, UNIX, etc.)
- As the queue owner, the L2 will be responsible for the general health of the queue (resolving tickets/incidents, problem source identification, root cause analysis, recommending process/system changes to eliminate problem causes, optimizing the incident resolution process, and escalating to L3 for resolution where appropriate)
- The L2 person will also have project responsibilities and will own projects within their respective area.
- The position is for the primary day shift (8 – 10 hours per day). There may be some evening and weekend work needed but that would be planned time generally associated with project work where maintenance windows need to be observed.
- These are not low level positions given the ownership of the incident queue and project work required. The person will need a deep understanding of their respective areas. But this is a hands on operations position. Engineers that only want to do projects and/or design and architect solutions will not be happy with this role.
- For clarification purposes, the L3 would have broader engineering knowledge across multiple categories, more project work, be a point of escalation for L2, and participate in process engineering and optimization initiatives. Sustained Engineering is the highest level within operations and would be responsible for the design, upgrade, and optimization activities within the approved architecture for a category.
- The L2 roles were created to lessen the "cultural compatibility" challenges associated with the higher level positions.
Qualifications:
- Break/Fix, Provisioning & Decom, Patching, AD management, Permissioning, Documentation
- At least 5+ years of experience in relevant technologies.
- Hands on knowledge of key operating system environments including MS Windows, Red Hat Linux, and VMware
- Must be able to work well in an ambiguous and changing environment
- Skills/Technologies:
- Windows 2003, 2008, 2012
- Chef
- Active Directory
- SCCM
Key Responsibilities | -Break/Fix, Provisioning & Decom, Patching, AD management, Permissioning, Documentation - These are not low level positions given the ownership of the incident queue and project work required. The person will need a deep understanding of their respective areas. But this is a hands on operations position. Engineers that only want to do projects and/or design and architect solutions will not be happy with this role. |
Level of Experience | 5+ years of relevant experience |
Specific/Mandatory Technologies/Requirements | -MUST be strong in Active Directory (AD), SCCM, and Chef -MUST have a background in Windows, Red Hat Linux, and VMware |
Please send me below information to submit your resume to client.
Full Name:
Current location:
Contact number:
Email:
Skype ID:
DOB(MM/DD)
SSN( Last 4 Digit):
Face to face:
Legal visa:
Willing to relocate (Yes/No):
Availability:
--------
Thanks,
Bhanu Pratap Singh
Source InfoTech Inc.
W: 609-917-3310| F: 732-909-2282| Email: bhanu@sourceinfotech.com | Website: www.sourceinfotech.com |
You received this message because you are subscribed to the Google Groups "US Jobs: Requirements, Clients and Consultants" group.
To unsubscribe from this group and stop receiving emails from it, send an email to recruiters-r-us+unsubscribe@googlegroups.com.
To post to this group, send email to recruiters-r-us@googlegroups.com.
Visit this group at https://groups.google.com/group/recruiters-r-us.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment