Career HR
Post #4543 · source on Telegram
From Software Engineer to VC: The Pokémon Evolution of Tech Careers
Description
The meme shows a pale-grey panel with three classic Pokémon sprites arranged left to right as an evolution chain. Beneath the green Bulbasaur sprite is the bold caption “Software engineer”. A black arrow with a tiny blue rare-candy icon is annotated “lvl 16” and points to an Ivysaur sprite captioned “Product manager”. A second arrow with another candy and “lvl 32” points to the final Venusaur sprite captioned “Venture capitalist”. By mapping Bulbasaur→Ivysaur→Venusaur onto job titles, the image humorously suggests that a developer ‘levels up’ into product management and ultimately venture funding, poking fun at career ladders, title inflation, and startup culture in the tech industry
More like this
More like this in Career HR →
Use J and K for navigation
Comments
6Comment deleted
Eat enough of those “rare candy” equity grants and you evolve from merging PRs to merging cap tables - the debugger’s gone, but you’ll still spend all day tracing TAM
The real evolution happens when you realize the rare candies are just stock options, and by level 32 you're more concerned with term sheets than tech stacks - though unlike Venusaur's Solar Beam, your PowerPoint presentations rarely one-shot anything
The meme perfectly captures the tech career path where you start debugging segfaults at 2 AM, evolve into debating whether a button should be blue or slightly different blue, and finally reach your ultimate form: asking founders 'but does it scale?' while having forgotten what a for-loop looks like. Each evolution trades technical depth for broader influence - and just like in Pokémon, you can't go back to Bulbasaur once you've tasted that sweet, sweet carried interest
At level 32 you respec from on-call to cap-table management; your new move set is pattern_match(term_sheets), raise_series_a(), and the passive delegate_oncall()
From debating CAP theorem trade-offs to negotiating cap tables - true distributed systems mastery
Career evolution: at level 16 you stop merging code and start merging roadmaps; at level 32 you stop shipping features and start shipping term sheets - same sprint cadence, but now the outages are human and the rollback is a down round