Starting a new job at Apple soon. Any one have tips, advice or recommendations on best practices for computer and account setup, work habits, benefits and perks, getting to know the team and technology, WFH culture, RTO culture, etc.
All helpful comments are welcome!
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
Enjoy your weekend and you’ll have time to ramp up once you join.
Bow your head, do as you are told, don’t ask too many questions, don’t questions decisions made by others, especially any decision coming from top. Think about a military structure. Orders come from top, you are there to execute. Not to improve, not to fix broken things. Just to execute someone else’s dream.
Good luck.
But since you asked specific questions, here you go:
1. Computer setup - the best practice is to follow the documentation on how to set it up. If there’s no documentation, ask your on-boarding buddy.
2. Work habits - think toxic culture, apple embodies so many aspects of it. A few habits I have seen: people are afraid to be self-critical, managers often hint at working weekends or late because they planned poor. That’s fine if it’s a critical launch, every team will have crunch time. But here’s the catch: all these deadlines are flexible and often postponed.
3. Benefits - well you got your offer letter and there’s a benefits page on the internal wiki.
4. Getting to know people - hard in one word. The standard way to ask questions is slack. There’s no job level on directory, so if you want to reach out to a Staff engineer for some context, you don’t know who to reach out to. So you hop from person to person till you reach somebody who can answer your question. The second issue is people are often busy with random deadlines, so your slack question may go unanswered or you may get time several days down the line. And then there’s the secrecy, people (even within the same team) may have different disclosures, so often you have no idea about what the guy next to you is working on.
5. WFH - 😂. Starting a pilot for 3 days in office. My guess is despite enough evidence of employees preferring flexibility, it will morph to 5 days in office.
6. See WFH
Culture: as much as you can, try to write some docs about what you work on for the next person. You probably won't have many docs and will need to ask around to find people who know things to learn what's going on, but at least in my org there's an opportunity to shift this culture (secrecy?) to having more docs. The lack of docs and this ask-around culture have been the most challenging aspects of working here for me.
Getting to know your team: do at least an intro meeting with people under your same manager, and probably people adjacent to your team under your manager's manager. I've tended to work with several nearby managers and/or their reports rather than just my team. Your manager should be your go-to resource for all of your questions, btw.
Work approach: focus on delivering something each week - especially if you have deadlines - but also make sure you keep some room to think about the larger picture. Sometimes things that would take a ton of work need to be rebalanced or redesigned/negotiated with larger teams before being executed.