Recently left the company to pursue a new opportunity. Happy to answer questions about culture, job, career advice, etc. Won’t talk about unreleased/secret stuff. #software #swe #career #engineering
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
The first team I joined was full of mid to late career professionals. This came with a lot of benefits: deep knowledge to draw from, professional pragmatism, and a somewhat defensive posture when it came to management and schedule. Over time I moved to work on more high profile projects with a lot less flexibility and more visibility. The latter definitely helped my career, but wasn’t necessarily well run.
This is not always the case—I know people who got burned out and left within 3 years. The closer you are to hardware the more pressure there is—this is a fact of life.
Everyone is willing to help—especially for junior engineers—but don’t expect them to hold your hand. I was given a lot of autonomy from the get go, and essentially delivered a (small) feature by myself in the first release I joined as a full time employee.
Overall, I recommend Apple as a place for new grads (hard to argue with success.) It will give you a mark on your resume that pretty much guarantees you a phone screen/first round with anyone. However it’s hard to know how transferable the knowledge you gain truly is. (Most of) Apple works on a very different type of technology than much of the industry, with its own (insane) processes (or lack there of.)
1) How feasible is it to get into Apple with 1 YOE. Obviously I’d be going for ICT3 but is the process just as it is for anywhere else, that is to say is it just the Leetcode grind & luck?
2) How’s WLB? I ask this because I always thought if/when I get into Apple, I’d stay for a long time (maybe even be a career man). I know I’d be giving up hefty TC bumps by not switching often but as long as wlb is good and there are decent raises/promos then I’d certainly be happy there. Apples been a dream for as long as I can remember.
Interviews are entirely owned by the team and hiring manager. Some might look for leetcode skills but in my experience that is not emphasized in Apple interviews. I never asked leetcode questions in interviews I gave, but I also never did first round interviews. FWIW I ask questions about past projects to get a sense for technical competency and technical communication ability, as well as design questions.
2) WLB is team, project and schedule dependent. Some teams are constantly slammed or subject to bad project management decisions. Some are not. Some people (such as myself) are consummate procrastinators and find themselves with loads of time until 2 weeks before the deadline.
Overall, most people I know at Apple are there for the long haul. I stayed for 10ish years! Not sure how much TC I missed out on in the process but I don’t think I did too poorly.
The aforementioned aside, hardware/build teams have terrible schedules. I would not recommend a HW TPM role at any TC.
Of course if you break the build, the scheduler stops scheduling, or something else Really Bad, all bets are off.
New TC 850.