Submission Guideline - Microsoft
This guideline covers Microsoft’s unique submission process, including required templates, candidate approval steps, compliance checks, and VMS usage. It helps recruiters follow Microsoft's structured hiring workflow and maintain accuracy.
1. “Which phase of the SDLC will this role focus on?”
This question helps you pinpoint whether the job is centered on requirements (Analysis), architecture (Design), coding (Implementation), quality (Testing), or support and improvements (Evaluation). Knowing the primary phase allows you to target candidates with the correct experience and prevents confusion when roles have overlapping responsibilities.
2. “Is this mostly new development or maintenance?”
New development roles focus on building new systems or features, which usually requires strong coding, architecture, and innovation skills. Maintenance roles focus on bug fixes, enhancements, optimization, and production support. Asking this question helps you distinguish between builders (developers, architects) and fixers/support roles (support engineers, DevOps, maintenance teams).
3. “Is the environment Agile, Waterfall, or Hybrid?”
The delivery methodology directly impacts how teams work and what tools or processes they use.
-
Agile roles emphasize sprints, stand-ups, story grooming, and collaboration.
-
Waterfall roles require documentation-heavy, structured, phase-by-phase execution.
-
Hybrid environments blend aspects of both.
Knowing the methodology helps you find candidates who can easily integrate into the team's workflow.
4. “Which tools or tech stacks are required at each phase?”
Different SDLC phases rely on different tools:
-
Analysis: Jira, Confluence, Visio
-
Design: Figma, Lucidchart, UML tools
-
Implementation: Programming languages, frameworks, Git, CI/CD
-
Testing: Selenium, Postman, JMeter, TestRail
-
Evaluation: ServiceNow, Dynatrace, Splunk, monitoring tools