Career Guides
MNC InsiderMNC Insider
Career Guides

Promotion kits · free preview

Prepare for your next level with evidence.

Role-specific preparation, starting with Android SDE1 → SDE2. Use this preview to organise the work you have done and the questions you need to ask.

This is a starter checklist, not a finished paid kit. It is not an employer’s promotion rubric and has not yet been reviewed by an Android promotion-panel expert. Your team’s expectations come first.
Read the Android preview ↓

First track

Android SDE1 → SDE2

Use each point as a prompt for a manager conversation. Titles and promotion requirements vary between teams; check which of these are relevant to yours.

  1. Agree on the bar

    Ask your manager which behaviours distinguish SDE2 in your team. Record the expectations, examples of work at that level, review date, and who makes the decision.

  2. Own a feature through delivery

    Choose a feature you can take from a written problem statement through implementation, testing, release and follow-up. Write down decisions you owned and where you needed help.

  3. Explain Android design decisions

    Use a project you actually shipped. Explain state ownership, lifecycle handling, data flow, failure handling and the trade-offs you made. Bring a diagram and links to the decisions.

  4. Make quality visible

    Collect evidence of tests, crash or ANR investigations, performance work and release checks. Record a baseline and measured outcome where available; do not invent improvement numbers.

  5. Show how you help the team

    Keep concrete examples of useful code reviews, documentation, mentoring and coordination with design, product or backend colleagues. Explain what changed because of your contribution.

  6. Turn work into an evidence packet

    For each project, write: problem → your responsibility → decision → result → evidence. Link the design, pull requests, release notes and feedback. Review gaps with your manager before a promotion conversation.

Start with one project

Fill in this short evidence note before your next one-to-one. Keep confidential project details in your company’s approved workspace.

Problem and scope
What needed to change, and what part did I own?
Decision and trade-off
What options did I consider, and why did I choose this approach?
Outcome and evidence
What happened? Which document, change, measurement or feedback supports it?
Gap and next action
What does my manager still need to see? What will I do next, and by when?

Make your work easier to understand.

Use your evidence notes to improve how you describe your projects and responsibilities.

Improve my resumeGet expert resume help