The IC ladder is a constant work-in-progress due to over-titling created by the merger of many corporate acquisitions over the years.
Legacy Bell roles remain but are gated behind stack-rank rules designed in 1980 for long tenure employment, which drops morale, causes career stagnation, and creates consistent talent churn as senior ICs "wait their turn" in a sponsorship queue.
Multiple management roles exist within every band, generally 1-2 IC roles above band 7. Frequent in-band role changes do not translate across the industry.
Due to headcount and excessive ladder rungs, titles are highly organizationally dependent. The criterion for the same role is largely dependent on your skip-level and will change frequently as restructuring occurs.
There are minimal employee safeguards in performance reviews. If a restructuring creates a management battle above your head, your contributions can quickly disappear within the politics. It's essential to keep your own record and create opportunities on your timescale, not the company's.
Business transformation initiatives create a legacy of "dead end" roles which either lack executive sponsorship or were never consolidated post delivery. Orgs survive beyond their tenure on mythical "phase 2". These roles can be launchpads into headquarters roles (planning, PMO, finance, etc.) but decay beyond a 1-2 year tenure.
"Standards" teams can form from initiatives which have exhausted funding or sponsorship, generally creating office politics and early/mid-career traps. Avoid these roles if you value meritocracy or your sanity.
"Quiet Trimming". Senior management tends to use the org chart to sunset initiatives versus collapsing these groups. This is evident in the flow of resources but never directly acknowledged due to optics.
Due to sheer enterprise scale, you will be vortexed into turf wars you didn't start. You will need sponsors across business units to lean on in these moments; leverage is the best defense.
The opportunity to build deep technical skills is increasingly rare, and the internal growth plan often pits deeply technical and managerial employees against one another for the same positions. Bias exists towards management due to the operational business model.
I remain appreciative of the many growth opportunities and lessons, and the intention of this section is solutions-oriented.
Verizon provides a smooth growth plan for managers at the expense of engineers. Fine if this is the intended culture, but the available opportunities are rarely transparent.
Scale unlocks capital‑B “Big” projects, but it also scatters accountability across too many ladder rungs. This tension must be proactively managed within any telco.
Do not penalize ICs for problematic, disillusioned, or retiring managers. If someone’s career is scaling down, their employees should be provided resources for lateral transition or sign a written acknowledgement to remain in the org. The water cooler is not sufficient.
Attrition occurs due to the skeletal remains of 3G/4G dual career ladders which persist in the 5G, but funnel one direction. Morale and recognition complaints are symptoms of professionals who join technology company marketing and ultimately manage annual budget cycles instead of pursuing their passions and potential Verizon IP.
I challenge you to deeply examine, define, and broadcast the intention of your senior IC roles. Across wider industry, role requirements are public domain and progress on merit-based artifacts (IP, patents, standards contributions, source contributions). Verizon's are highly subjective.
Verizon is one of few "technology" companies executing a generalist strategy within specialist roles, and is building a reputation for over-titling employees that are re-leveled at their next opportunity (VZ Fellow → NVIDIA Principal).
Performance goals should be generated by an employee's manager and approved by their skip level to avoid "bottom-up" politics. Drama is inevitable, but it's crucial to minimize the damage to individual careers and not penalize an employee for their manager. An employee seeking career growth and individualized performance feedback is going to become disillusioned if it is blocked by battles above their head.
Stack ranking is a management reality but needs far more governance.
Automate these notifications with written justification directly to the employee. Forget feelings, stick to facts. Do not rely on a manager to pass the message verbally, as front line managers frequently fight for their own people and rarely transparently pass directives they disagree with, which is unfair to the impacted employee.
Escalation paths should exist where organizational design creates stack ranking rather than performance. Nothing is more valuable than high output, cross-functional collaboration, and preserving high performing teams is a strategic imperative.
If two peers are compared for the same promotion slot, they should be notified in advance, and executives should work with the non-selected high performer to re-assign them into an org with an aligning opportunity. When someone feels their peer became their superior in an equal merit, headcount-limited scenario, they find new opportunities and leave. Nobody wants to damage their relationship with a peer they respect or care for over promotion politics. Failing to be proactive in these scenarios hurts both sides, as well as the efficacy of the promoted leader and business unit.
Phone with in-person follow-up. The phone interview was approximately 1 hour. The second follow-up interview was in-person with the hiring manager and one of their peers. A mock project and presentation was assigned and then had to be delivered a wee
The interview process is very good and friendly. It started with basic technical questions and then proceeded slowly to architect scenarios and accept challenges. It involves multiple rounds, including a technical phone screen, online assessments, an
One interview! No video. Phone conversation that included a review of my background, a few clarifying questions on skills, and 5 or so "tell me a time" questions. Lasted less than an hour. Interviewer was focused and had a clear understanding of the
Phone with in-person follow-up. The phone interview was approximately 1 hour. The second follow-up interview was in-person with the hiring manager and one of their peers. A mock project and presentation was assigned and then had to be delivered a wee
The interview process is very good and friendly. It started with basic technical questions and then proceeded slowly to architect scenarios and accept challenges. It involves multiple rounds, including a technical phone screen, online assessments, an
One interview! No video. Phone conversation that included a review of my background, a few clarifying questions on skills, and 5 or so "tell me a time" questions. Lasted less than an hour. Interviewer was focused and had a clear understanding of the