《职位评价体系》doc版.doc

DevelopmentDevelopers are responsible for constructing software that delights customers and adds strategic value to Microsoft. Developers evaluate requirements, estimate development costs, design and implement the software, review the design and implementation, improve the development process, perform unit testing, communicate status, manage risks and compromises, integrate software into a larger system, and diagnose and resolve issues.Career Stage ProfilesIC2: Software Development EngineerWorks on a specific feature or section of code. SDEs at this stage typically require supervision and are concerned with building basic development experience and expertise appropriate for the discipline. IC3: Software Development Engineer 2Works on a specific feature area or component. SDE2s work autonomously and make broad contributions to the product and demonstrate emerging technical leadership. IC4: Senior Software Development EngineerActs as a leader within his or her feature team. This leadership may come from deep understanding of a specific technical area, or it may come from demonstrated leadership in an engineering practice and in the Development discipline. IC5: Principal Software Development EngineerActs as a technical leader across an entire product. This leadership may come from deep understanding of a specific technical area, or it may come from leadership in an engineering practice.IC6: Partner Software Development EngineerWorks at business group- or Microsoft-wide scope. At Microsoft-wide scope, he or she may be the representative of the product line or technology to members of the community outside of Microsoft.IC7: Distinguished EngineerThe Distinguished Engineer (DE) is not a career stage per se but a title and set of responsibilities conferred to recognize individuals at the highest level of nonexecutive technical achievement. DE work is detailed within a specific business group and product line, but the contribution is influential Microsoft-wide. IC8: Technical FellowThe Technical Fellow is recognized internally and externally as a world-class expert. Leads technological innovation with industry-wide effects.Software Development EngineerJump to: Scope and ImpactCompare Scope and Impact Across This Discipline Design and architecture tradeoffs: Makes appropriate design trade-offs for a feature Risks & dependencies: Identifies risks and dependencies in the schedule for a feature Code quality: Writes unit test and fully leverages the automatable system for a feature Customer & partner quality resolution: Solves customer/partner problems in a timely manner; accounts for the performance, operation, and serviceability of the featureCSP User Guide Expand AllCollapse AllBusiness: Design includes results related to enabling scenarios, quality, extensibility, and the basics; compatibility and flexibility; maintenance across the life cycle; compromises; innovations; performance and serviceability; implementation standards; and architectureFull 1. Designed a robust, scalable, secure, efficient, and globalized feature that enabled scenarios and met customer/partner requirements 2. Made appropriate design compromises between functionality, performance, dependencies, quality, and reliability for a feature 3. Took into consideration the performance, operation, and serviceability of a feature in his/her designs 4. Chose the right technology and target domain to implement a feature, which resulted in high-quality, stable, and efficient code 5. Ensured that his/her feature fit into the overall product architecture Exceptional 1. Wrote specifications for a feature that incorporated input from multiple feedback sources (such as newsgroups, customers, partners, and project managers), which resulted in an on-schedule and high-quality implementation 2. Anticipated dependencies and needs of related features; ensured that his/her designs and code were aligned to dependencies and needs 3. Provided insights on feature designs that led to more effective and complete customer scenarios 4. Understood the overall product and system architecture and aligned feature designs to it, which ensured that the approach was optimal and extensible and that it could be maintained Developing 1. Learning to design scalable features 2. Learning to create feature designs that fit into the overall system architecture and learning to adapt to changes that are necessary for the success of the architecture 3. Learning to create designs that are adequately scalable or that appropriately enable scenarios 4. Learning to clearly define design goals and milestones Business: Implementation includes results related to schedule of work, communicating status, risk and dependency management, implementation standards and best practices, documentation, code quality, and code improvement Full 1. Made a schedule for a feature that took dependencies into account and provided clear and informative status updates that helped others plan their work 2. Implemented a feature in conformance with group coding standards, was consistent with product design and architecture goals, did not repeat mistakes, and met schedule milestones and quality expectations 3. Provided clear comments on specifications, design, and code, and worked to resolve issues and conflicts 4. Delivered stable and secure code for a feature, as scheduled, that contained minimal bugs, and outlined next steps to resolve them where appropriate 5. Implemented design, code, and process optimizations that enabled significant improvements in performance, scalability, security, and/or reliability Exceptional 1. Kept his/her work on schedule despite changes in project scope or the introduction of new variables; demonstrated his/her understanding of the impact of these changes by negotiating a new schedule 2. Identified hidden dependencies and security risks in designs 3. Helped to define new group practices and conventions for coding and for implementing code, and provided input that was adopted Developing 1. Learning to create accurate feature schedules that do not need revision 2. Learning to create code that stabilizes quickly in builds 3. Learning to create stable features that do not require last-minute rewriting 4. Learning to proactively provide status updates 5. Learning to provide updates to others that are clear, concise, and complete Business: Quality includes results related to: unit tests order, leveraging automation, identifying trends, process improvement, resolving bugs, resolution understanding, completeness and compatibility, triage, and debugging proficiency and methodologyFull 1. Wrote unit tests for each function for a feature that effectively exercised the code; identified bugs or design issues 2. Optimized the automatable system to make implementation and testing of code efficient 3. Used existing tools to effectively debug his/her code, which resulted in thorough fixes that did not introduce new bugs 4. Made sure bug fixes for his/her code did not introduce problems for other features 5. Found most bugs and other quality issues in his/her assigned feature before the code was integrated into the main build 6. Responded to high-priority bugs quickly, and remained involved to ensure an appropriate resolution or triage Exceptional 1. Was considered a primary resource for solving debugging problems for a feature; often recommended feature or process improvements that were adopted 2. Understood the effects of fixing a bug on the overall system, sought out other occurrences, and suggested alternatives to mitigate potential problems 3. Contributed to decisions about whether a QFE or hot fix was needed, partnered with Sustained Engineering and CSS (as appropriate), and proactively communicated with customers/partners to notify them of issue resolution Developing 1. Learning to create code that does not break the build 2. Learning to proactively develop automation tools or techniques to test his/her code 3. Learning to submit complete bug fixes 4. Learning debugging techniques and tools Business: Sound Engineering Practices includes results related to: code review, design review, team standards, and process improvement Full 1. Incorporated feedback from code reviews into code 2. Modified code when necessary to meet team standards Exceptional 1. Conducted code reviews with other developers that they viewed as value-added 2. Conducted design reviews that added insight to the product design 3. Suggested ways to improve engineering and coding processes within his/her team that were adopted Developing 1. Learning to clearly articulate comments on code, specifications, or design so that others can adequately review work 2. Working to consistently follow group standard practices 3. Working to consistently prioritize participation in code reviews 4. Working to consistently create maintainable code that follows standards Leadership includes results related to technical leadership and discipline excellence: removing blocking issues, anticipating key issues, ship-cycle experience and leadership, artifacts, acquiring talent, mentoring, championing vision and strategy, new tools and technology, and identifying dependencies across teamsFull 1. Participated in the interview process and gave considered, high-quality feedback on candidates 2. Effectively contributed to patent documentation 3. Identified areas of dependency and overlap with other teams and disciplines in specifications, code, and test plan reviews for a feature; provided constructive input so that the feature was integrated efficiently and the project remained on schedule 4. Was knowledgeable about his/her own code and informed peers when needed, which resulted in better decisions regarding design, feasibility, and time or schedule estimates Exceptional 1. Effectively resolved blocking issues for others, which allowed the team to remain on schedule 2. Gave proactive reviews with other disciplines and teams that revealed areas of dependency and overlap, which enabled higher-quality features 3. Mentored new hires on using the necessary tools, which helped them to successfully meet project requirements Developing 1. Learning to prioritize interviewing and selection and to provide quality feedback on candidates 2. Learning to fully participate and provide input in feature reviews with other developers or teams Customer/Partner includes results related to improving customer experiences, understanding customer needs, customer advocacy, and representing Microsoft Full 1. Addressed customer and/or partner issues with existing features that enabled their timely resolution 2. Used all appropriate tools at his/her disposal, including code reviews, to isolate and solve customer/partner problems Exceptional 1. Resolved difficult or non-obvious problems for customers/partners, which resulted in positive feedback 2. Spotted trends and potential customer/partner issues through participation in online communities; incorporated this information to improve his/her designs and resolve bugs Developing 1. Working to consistently prioritize customer/partner or support requests 2. Working to address customer/partner feedback that requires significant work, rather than dismissing reported issues as not reproducible Software Development Engineer 2Jump to: Scope and ImpactCompare Scope and Impact Across This Discipline 1. Design and architecture tradeoffs: Makes appropriate design trade-offs for a feature area 2. Risks & dependencies: Identifies risks and dependencies in the schedule for a feature area 3. Code quality: Has code reviews with other developers to surface design and implementation issues 4. Customer & partner quality resolution: Proactively identifies and resolves customer/ partner and quality issuesCSP User Guide Expand AllCollapse AllBusiness: Design includes results related to enabling scenarios, quality, extensibility, and the basics; compatibility and flexibility; maintenance across the life cycle; compromises; innovations; performance and serviceability; implementation standards; and architectureFull 1. Designed a robust, scalable, secure, efficient, and globalized feature area that enabled customer/partner scenarios that were clearly described 2. Created designs for a feature area that ensured that code could be diagnosed and maintained, that it was testable, discoverable, and extensible to other feature areas 3. Proactively ensured that the overall user experience was compatible with design objectives 4. Designed and implemented reusable code for a feature area, which resulted in increased efficiency and quality 5. Balanced functionality, performance, dependency, quality, and reliability in designs for a feature area 6. Provided insights about feature area designs that enabledeffective and complete customer/partner scenarios 7. Provided feedback about technology and work processes that enabled management to improve them 8. Considered the performance, operation, and serviceability of a feature area in his/her designs 9. Chose appropriate technology and target domains with no unnecessary abstraction layers to implement a feature area, which resulted in high-quality, stable, efficient, and secure code 10. Conveyed a clear understanding of the overall product architecture in the design and implementation for a feature area Exceptional 1. Designed a robust, scalable, secure, efficient, and globalized feature area that enabled new scenarios, needed no additional explanation or revision, and exceeded requirements 2. Anticipated feature-area enhancement needs and worked to incorporate them into designs 3. Contributed insights into the overall product architecture Developing 1. Working to ensure that designs address all requirements, consider all assigned features, account for all dependencies, and fit into the overall architecture Business: Implementation includes results related to schedule of work, status updates, risk and dependency management, implementation standards and best practices, documentation, code quality, and code improvement Full 1. Created schedules for a feature area that accounted for all dependencies and communicated status updates across disciplines and teams, which allowed for on-time deliverables, meeting milestones, and better coordination among groups 2. Identified dependencies and risks for a feature area in a timely manner, which resulted in no surprises during the project 3. Implemented a feature area in conformance to group coding standards, product design and architecture goals, and quality expectations 4. Completed design documentation before implementation, which resulted in accurate scheduling and consistent implementation 5. Delivered stable and secure code for a feature area on schedule and that contained minimal bugs; outlined next steps where appropriate 6. Implemented design, code, and process optimizations that enabled significant improvements in performance, scalability, security, and/or reliability Exceptional 1. Kept his/her assigned feature area on schedule despite changes; created a schedule that anticipated changes and provided proper mitigation for dependencies; met schedule milestones 2. Identified and mitigated dependency and security risks in designs 3. Advocated coding standards and helped to define them, which improved standards across the team 4. Created code for a feature area that was considered exemplary and a best practice for the product Developing 1. Learning to identify all dependencies to avoid milestone delays 2. Learning to identify and fully consider all risks Business: Quality includes results related to: unit tests order, leveraging automation, identifying trends, process improvement, resolving bugs, resolution understanding, completeness and compatibility, triage, and debugging proficiency and methodologyFull 1. Wrote unit tests for each function of the feature area that effectively exercised the code, identified bugs or design issues, and integrated well with those used by Test, in accordance with group practices 2. Made full use of the automatable system, adapting or enhancing the system as needed to make implementation and testing of a feature area efficient 3. Identified process improvements (such as new tools, new work methods, or new debugging techniques) that other developers adopted 4. Used debugging and stabilization tools to effectively debug code, and found the root cause of bugs and fixed them, which ensured that no new bugs were introduced and that fixes were backwards compatible 5. Evaluated risks and costs of fixing bugs and developed sound alternatives to resolve the problem, when appropriate 6. Found most bugs and other quality issues in his/her assigned feature area before code was handed off to Test 7. Triaged bugs to appropriately prioritize fixes, which kept the project on schedule while meeting quality standards Exceptional 1. Developed a best practice for writing and checking for errors in code 2. Acted as a subject matter expert (SME) for a feature area; was sought out by others for advice about resolving design and debugging issues 3. Worked with Test to ensure that appropriate feature-area testing strategies were in place, which resulted in less duplicate work Developing 1. Learning to create components or features that do not require last-minute revision 2. Learning how to prioritize bugs 3. Learning to take appropriate and sustained steps to resolve bugs and quality issues Business: Sound Engineering