How to Get Promoted from ICT2 to ICT3 Software Engineer at Apple
Building your promotion case?
Get AI coaching on what to document and how to present it.
You're a few months into Apple. You shipped your first feature, survived your first code review (Apple reviews are thorough), and your manager seems satisfied with your ramp. But nobody has explained what ICT3 actually means, what the promotion process looks like, or whether you're on track. Apple doesn't publish rubrics. There's no promotion packet to study. ICT levels aren't even visible to your coworkers. You're navigating a system designed to be opaque.
The ICT2 to ICT3 jump is the first real promotion at Apple. It's the transition from "new grad figuring things out" to "engineer who can own real work independently." Apple expects most ICT2 hires to make this move within roughly two years. The total compensation increase is meaningful -- about $80K at the median according to Levels.fyi -- and ICT3 is Apple's first terminal level, meaning there's no implicit pressure to keep climbing once you get there. But the entire process runs through one person: your manager. If they don't bring your name up, nothing happens.
What Changes from ICT2 to ICT3
ICT2 is Apple's entry-level engineering role for new grads and junior hires. ICT3 is where Apple considers you a fully capable, mid-level engineer. The expectations shift in concrete ways.
| Dimension | ICT2 (Junior / New Grad) | ICT3 (Mid-Level) |
|---|---|---|
| Independence | Works on defined tasks with guidance from senior engineers | Owns features end-to-end with minimal direction |
| Scope | Individual tasks within existing systems | Full features or modules, including design input |
| Quality | Writes correct code, learning Apple's standards | Consistently meets Apple's quality bar without heavy review rework |
| Debugging | Solves bugs with help | Debugs complex issues independently, including in unfamiliar areas of the codebase |
| Communication | Asks good questions, absorbs feedback | Communicates proactively with manager and cross-functional partners (design, QA, PM) |
| Mentoring | N/A | Helps onboard new ICT2 engineers, answers questions, shares team knowledge |
| Ownership | Completes assigned work reliably | Identifies problems before being asked, proposes solutions, drives them to completion |
The core shift: at ICT2, someone scopes the work and hands you pieces. At ICT3, your manager hands you a problem and you figure out how to break it down, build it, ship it, and verify it works in production. You stop being the person who executes the plan and start being the person who makes the plan for your feature.
How Promotions Work at Apple
Apple runs a manager-driven promotion process. There is no committee packet like Google's. No written promo doc like Amazon's. Your manager is simultaneously the advocate, the evaluator, and the gatekeeper.
Here's how the cycle works:
- Your manager decides you're ready based on sustained ICT3-level work over multiple months
- Your manager presents your case during calibration discussions with peer managers and their director
- The calibration group aligns on who gets promoted across the org
- Promotions are finalized during the annual review cycle -- reviews happen in late May/June, and compensation changes take effect in October
There's also a path that surprises some engineers: the calibration committee can promote someone even without an explicit manager nomination, if the engineer's work is visible enough to other managers in the discussion. This is rare at the ICT2-to-ICT3 level, but it underscores why cross-team visibility -- even within Apple's siloed culture -- isn't wasted effort.
Key differences from other Big Tech companies:
- One cycle per year. Apple's promotion window is annual, tied to the fall review. Google and Amazon run two cycles. If you miss Apple's window, you wait a full year.
- No self-nomination. You cannot submit yourself for promotion. Your manager initiates it.
- Titles are hidden internally. Apple deliberately doesn't expose ICT levels to your peers. Your coworkers don't know whether you're ICT2 or ICT3. Only your manager and their reporting chain see your level.
- No published rubric. The promotion criteria live in your manager's judgment and the calibration group's expectations. There is no document you can study to figure out the bar.
The implication is stark: your relationship with your manager matters more at Apple than at almost any other tech company. At Google, a committee reads your packet and can override a lukewarm manager assessment. At Apple, if your manager isn't fully bought in, the conversation about you doesn't happen.
How Long ICT2 to ICT3 Should Take
| Pace | Timeline | What it looks like |
|---|---|---|
| Exceptional | ~12 months | Rare; strong prior experience, immediate ICT3-scope project, manager actively advocating early |
| Standard | 18-24 months | Solid ramp, steady ownership growth, building manager confidence over two review check-ins |
| Slow (worth a conversation) | 2.5-3+ years | Something structural is off -- wrong team, disengaged manager, unclear expectations, or skill gaps not being addressed |
ICT2 is not a terminal level. Apple expects competent engineers to advance past it. Staying at ICT2 for more than about two and a half years is unusual and should prompt a direct conversation with your manager about what gaps they see and what specifically needs to change.
Based on Levels.fyi data, median total compensation moves from roughly $180K at ICT2 to $260K at ICT3 -- about an $80K increase driven primarily by base salary growth and larger annual RSU grants. Apple RSUs vest over four years in equal annual increments. Every cycle you miss is real money left on the table.
What Actually Gets You Promoted
Own a feature from problem to production
The single clearest signal that you're ready for ICT3 is shipping a feature where you drove the whole lifecycle. Not a system redesign. Not a massive project. Something reasonably scoped where you understood the user problem, proposed an approach, handled the implementation, navigated code review, shipped it, and confirmed it works.
If your current workload is entirely tasks broken down and assigned by a senior engineer, have the conversation with your manager. Ask for a project where you own the full cycle -- from understanding the requirements through verifying the outcome. This conversation itself signals growth, and a good manager will find something appropriate.
"I got my ICT3 promo after owning the notification preferences redesign end-to-end. It wasn't a huge project, but I scoped it, built it, coordinated with the design team, and shipped it. My manager used that as the anchor for my case."
Keep a brag journal and surface your wins
Apple's secrecy culture creates a documentation problem. Your manager has six to ten direct reports and their own deliverables. They are not tracking every PR you merge, every bug you squash, or every time you unblocked a teammate. If you don't surface your contributions, your manager's calibration narrative will reflect what they remember -- not what you actually did.
Keep a running document of your wins. Update it weekly. In your 1:1s, mention the things that matter:
- Features shipped -- what you built, what it does, and what the impact was
- Problems you found proactively -- bugs or design issues you caught before they became incidents
- Scope you took on voluntarily -- times you stepped up without being asked
- Mentoring moments -- helping a new ICT2 get unblocked, onboarding someone onto your area of the codebase
This is not bragging. This is giving your manager the raw material they need to build your promotion case during calibration. They will use your words. Make it easy for them.
Build the manager relationship deliberately
At Apple, your manager IS the promotion process. Every move toward ICT3 runs through them.
- Ask about ICT3 directly. After your first review cycle, ask: "What does ICT3 readiness look like for me specifically? What gaps do you see?" This gives you a concrete target and tells your manager you're thinking about growth.
- Request feedback on specific work. Not "how am I doing?" but "I just shipped X -- was the approach what you'd expect from an ICT3 engineer, or would you have handled it differently?"
- Understand the timeline. Ask your manager when they think you'll be ready and what the remaining gaps are. If they're vague, push for specifics. A manager who can't articulate what's missing is a red flag you should address early.
Adapt to Apple's quality bar
Apple is obsessive about quality. Code review feedback tends to be more detailed and more exacting than at most companies. ICT3 engineers produce code that consistently passes review without major rework -- well-tested, handles edge cases, meets the team's style and architecture standards without the reviewer doing the thinking for them.
If you're getting the same types of review comments repeatedly (missing tests, not handling error paths, inconsistent naming), that's the highest-signal feedback Apple will give you about your readiness. Fix the pattern, not just the individual comments.
Mistakes That Keep Engineers at ICT2
Staying in task-execution mode. You've gotten fast at the kind of tickets you were assigned during onboarding. But completing more tasks at the same scope doesn't build an ICT3 case. Your manager is evaluating scope growth -- whether you can own a full feature, not whether you can close Jira tickets faster. Volume at ICT2 scope is not the same as readiness for ICT3 scope.
Not adapting to Apple's engineering culture. Apple's expectations around code quality, testing rigor, and attention to detail are specific and high. Engineers who arrive from startups or less structured environments sometimes struggle with the review process and mistake review feedback for criticism. Treat code review as the single most useful signal for what Apple expects at your level. If your PRs consistently come back with substantive comments, that's your roadmap.
Assuming your manager sees everything. Your manager has their own work, their own deadlines, and multiple other reports. They are not cataloging every contribution you make. When the calibration conversation happens, your manager will advocate based on what they can remember and articulate. If you haven't been surfacing your work in 1:1s, the narrative they build will be thinner than it should be.
Avoiding the promotion conversation. Apple has no rubric you can study independently. The criteria live in your manager's understanding of what the calibration group expects. If you don't ask what ICT3 looks like for your specific situation, you are guessing at a target you cannot see. The question is not awkward -- it's how Apple's system is designed to work.
Waiting for a high-profile project. Some ICT2 engineers delay pushing for promotion because they haven't landed a flagship feature. At this level, you don't need a company-defining project. A cleanly executed improvement to an internal tool, a well-shipped component within a larger initiative, or a reliability fix that you identified, scoped, and landed -- any of these is enough, as long as you owned it end-to-end.
Frequently Asked Questions
How long does it take to get promoted from ICT2 to ICT3 at Apple?
Most engineers spend 18-24 months at ICT2 before promotion. Strong performers with good project fit can do it in about 12 months, though that pace is uncommon. ICT2 is not a terminal level, so Apple expects capable engineers to advance. If you've been at ICT2 for more than two and a half years, it's worth having a direct conversation with your manager about what's holding things up.
What's the compensation difference between ICT2 and ICT3?
Based on Levels.fyi, median total compensation increases from roughly $180K at ICT2 to $260K at ICT3 -- about an $80K jump. The increase is driven primarily by base salary growth and larger RSU grants. Apple RSUs vest annually over four years.
Does Apple have a promotion committee like Google?
No. Apple's process is manager-driven. Your manager presents your case in calibration discussions with peer managers and their director. There is no written promotion packet that a separate committee evaluates. The calibration group can promote someone without explicit manager nomination, but at the ICT2-to-ICT3 level, your manager's advocacy is the primary path. This makes the manager relationship the most important factor in your promotion outcome.
Can I get promoted faster by switching teams?
Switching teams resets your context. Your new manager doesn't know your work, and Apple's siloed culture means your reputation doesn't transfer easily. Only switch if your current team genuinely lacks ICT3-scope work or if your manager relationship is broken beyond repair. If the problem is project fit, ask your current manager for different work on the same team first -- that conversation is faster and lower-risk than an internal transfer.
How do I know what ICT3 looks like if Apple doesn't publish a rubric?
Ask your manager directly. The criteria exist in your manager's understanding of what the calibration group will accept. A good opening: "What would make you confident bringing my name up for ICT3 in the next cycle?" Your manager should be able to give you specific, actionable gaps. If they can't articulate what's missing, that's worth noting -- and possibly worth raising with a skip-level manager or mentor.
CareerClimb tracks your wins at Apple, maps them to what your manager needs for calibration, and shows you exactly what evidence is missing. When promotion decisions happen, your case is already built. Download CareerClimb