1. Strengths
1.1. Linux
1.2. Scripting
1.3. User support
1.4. Social/People skills
2. Experience
2.1. Support in remote offices
2.1.1. Dealing with new colleagues/customers
2.1.2. Investigation of unknown systems
2.1.2.1. Network layout
2.1.2.2. Server structure
2.1.2.3. User workflows
2.1.3. Team communication
2.1.3.1. Informing team about what I've learned
2.1.3.2. Managing tasks across timezones
2.1.3.3. Managing tasks across demand scope
2.1.3.3.1. Users in remote office work differently
2.1.3.3.2. Users expect different levels of responsiveness
2.1.3.3.3. There will likely be backlog due to lack of regular IT support
2.1.4. Analysis
2.1.4.1. Finding things that could be improved
2.1.4.1.1. Pro-actively improving them!
2.2. Managing company mobile phone contracts
2.2.1. Coverage assessment
2.2.2. Handset
2.3. Changing the backup tape
2.3.1. Managing security of tapes
2.3.2. Remembering to do it
2.3.3. Daily check of server room
2.3.3.1. Validate security of room
2.3.3.2. Check for server faults
2.3.3.3. Check temperature
2.3.4. Managing the cycle through tape set
2.3.4.1. Storing of logs
2.4. Cloud architecture (Puppet)
2.4.1. Users
2.4.1.1. How do they use services?
2.4.1.1.1. Any special provisions?
2.4.1.1.2. Do we need to scale up to meet demand?
2.4.1.1.3. Is it transparent?
2.4.1.2. How do they receive support?
2.4.1.3. Will they need instructions?
2.4.2. Developers
2.4.2.1. How do they test the infrastructure?
2.4.2.1.1. Local testing
2.4.2.1.2. Automated testing
2.4.2.2. How do they deploy?
2.4.2.3. How do they debug (logging?)
2.4.3. Security
2.4.3.1. Data
2.4.3.1.1. Where do we store it?
2.4.3.1.2. How do we transfer it?
2.4.3.1.3. How do we keep it up to date?
2.4.3.2. User access
2.4.3.2.1. Who can do what?
2.4.3.2.2. How do applications do things?
2.4.3.2.3. Where can you access things from?
2.4.3.2.4. Are there potential attack vectors we might be missing?
2.4.3.2.5. Password policy?
2.4.3.2.6. Multi-factor authentication?
2.4.3.3. Host access
2.4.3.3.1. Do we log in manually?
2.4.3.3.2. Communications between each other
2.4.4. Avalability
2.4.4.1. Disaster recovery
2.4.4.1.1. How do we deal with damaged hosts?
2.4.4.1.2. How do we recover data?
2.4.4.2. Monitoring
2.4.4.2.1. What metrics are we interested in?
2.4.4.2.2. Can we use any as capacity indicators?
2.4.4.2.3. How do we report?
2.4.4.3. Uptime
2.4.4.3.1. Should there be an SLA?
2.4.4.3.2. What metric measures uptime?
2.4.4.4. Load
2.4.4.4.1. How do we measure it?
2.4.4.4.2. How do we balance it?