|
| Definitions of competency levels |
|
| The following definitions give you an idea of what you can expect in each session at a particular level and are designed to help you attend sessions which are suitable for your level of competency. |
|
| Level 100 (introductory): |
|
| Overviews of product and technology features, functions and benefits |
| Details of new product features, how will they benefit customers and convince them that they need to buy this product |
| The functions of the product and an example of how they are used in a real world environment |
| The benefits of the product and any case studies that show how they assisted a customer |
| Product requirements and other integration information. |
|
| Level 200 (intermediate): |
|
| Specific product and technology technical information |
| Drilling into architecture, integration and configuration (what makes the feature tick) |
| Supportability reviews |
| Code samples |
| Best practices |
| High-level troubleshooting techniques |
| Known limitations and issues. |
|
| Level 300 (experienced): |
|
| Product migration, deployment, architecture, development |
| Drilling into how a product and its technology is designed to be deployed, migration, etc and focusing on how it is actually deployed |
| Real world examples as appropriate |
| Complex coding, known issues and work-arounds (sample code/examples) |
| Lessons learned, both positive and negative |
| Sample migration plans including sample project plans |
| Deployment case studies |
| Architecture design best practices and case studies. |
|
| Level 400 (advanced expert): |
|
| Custom code, scripts, application solution development, architect infrastructure designs and solutions |
| Advanced coding considerations and challenges |
| Design considerations and challenges |
| Architecture considerations and challenges |
| Troubleshooting techniques at the debugging level. |
|