Information about the offer
- Type of employment: b/d
- Offer ID: SK1806MRB
- Category: System Integrator
- Place: Bratislava , Slovakia
Requirements
- Minimal level of education:: b/d
- Minimal experience: Between 2 and 5 years
VACANCY DESCRIPTION
Migration Lead is responsible for all technical deliverables related to solutioning,
designing/planning, and executing a client’s IT migrations from point A to
Point B (includes migration across/within datacenters, server states, user
bases, operating systems, HW/SW versions, platforms, workplaces, delivery
teams, etc.). Provides overall design/engineering
direction and support for migration across all towers to ensure the program
meets the contractual obligations and operational standards, as well as the
client’s business imperatives.
Salary offer: min. 1000 EUR gross/ month; depends on seniority
The law requires to inform about the minimum salary for all advertised roles. In case of your successful candidacy we will consider all aspects of your experience, skills, competencies and qualification when defining final offer. We consider situation within labour market and provide competitive salaries to our employees.
DUTIES
- Manages the migration design/planning and oversees execution,
ensuring that all data required to plan/execute the migration is
collected, validated, and updated in the SSoT (Single-Source-of-Truth)
data repository to ensure all data is 3C-data (correct, current, complete)
for all Source workloads (apps/servers) at all times; all move-groups,
workload placement, migration methods, and migration tools are selected
correctly; and all technical resources are engaged and tasked for
execution- Ensures WAME (Workload Assessment & Migration Engine)
capabilities and best-practices are used to optimize the migration of
workload- Identifies changes/additions to Source environment, and triggers
scope-change-control when/where necessary- Ensures prerequisites are in-place, test-plans are in-place
(technical & UAT), technical resources are available, and technical
escalation paths are in-place for successful migration waves- Triggers and manages technical escalations to ensure the right
technical resources are brought-to-bear to resolve issues during the
window- Ensures workload migration occurs on-scope, on-schedule,
on-budget, on-quality and manages client/account communications as related
to the migration
REQUIREMENTS
- Detailed design/planning of migration scope, approach,
dependencies, risks, wave schedule, resources, and finances- Wave schedules to includeo
Validation of wave content, source/target mapping,
server groupings/dependencies, clustering, etc.o
All prerequisites (upgrades prior to migrations,
driver loads/updates, etc.)o
All components (servers, storage (local and
leveraged), applications, users, etc.)o
All participants (HP, client, 3rd party, etc.)o
Pre- and post- migration testing validation- All types of migrations in-scope
o
P2P,
P2V, P2C, V2V, V2C, SameBox/Lift-n-Shift, etc.
o
HW
and/or SW upgrades
o
Within
datacenter, across datacenters
o
Replication
via network, swing-gear, etc.
o
Etc.
- Validation of all dependencies
o
Hardware
build-out/configuration
o
Business/application
outage windows
o
Resource
allocations/commitments
o
Etc.
- Generation of detailed playbook/checklist
o
Key
milestones
o
Milestone
owners
o
Link
of key milestones to owners’ detailed playbooks/checklists
o
Expected
start/end date/time for each milestone
o
Dependencies
and durations
o
Critical-path
with cushion time to address unforeseen issues and back-out
o
Step-by-step
detailed technical instructions
o
Go/no-go
criteria
o
Critical-path
flagging, with rollback/back-out procedures
o
Severability
of wave components (i.e. components that can be backed-out, allowing remainder
of wave to complete successfully)
o
Change
requests
o
Steady-state
turnover criteria
o
Turnover
to steady-state
o
Release
of resources
o
Post-migration
validation/audit (monitoring, BUR, etc.)
Projecting demand of all key resources
o
All
key milestone owners (HP, client, 3rd party, etc.) for all roles (Engineers,
SAs, testers, etc.)
o
Contact
info for all participants
o
Backups
for all participants (turnover for windows > 8 hours, or successive)
o
Escalation
path for all participants
o
Hardware
o
Software
o
Tools
o
Outage/change
windows
o
Walk-through
playbook/checklist with all key milestone owners prior to execution