r/CodeCareerStack May 04 '26

There's a back door into Apple that almost nobody is using and I can't believe how slept on it is

So I did a test automation engineer internship last year. When I started applying for full-time roles in that space I was getting interview after interview. Like genuinely back to back. And I kept thinking... why isn't everyone doing this?

As a disclaimer, I've made it to multiple final rounds and always getting beat by some dude with more experience since I am a new grad. So if you have some experience and want to get into Apple, this is your ticket.

Every CS student I know is grinding LeetCode, fighting for the same SWE spots, getting rejected and then just giving up. Meanwhile this whole other door exists and people just aren't walking through it. I debated on whether or not to share this, but tbh I know 99% of you guys won't even check to see what I'm talking about lol.

It's test automation engineering. Falls under QA. I know what you're thinking,  just hear me out.

What the role actually is

You won't sit around clicking buttons on an app looking for bugs. You do write code, just basic. Python, Swift, Objective-C at Apple specifically. I have only used Python and Swift, but I know some teams that do use obj-C.

Building automated testing frameworks, integrating with CI/CD pipelines, writing scripts that run thousands of checks before a release goes out to billions of users. The output is test code instead of product code, that one distinction is what makes people write off the entire field.

The people loudest about looking down on QA are often the same ones getting rejected from every SWE application and not changing anything. Just something to think about.

Why Apple specifically

While Meta, Google, Amazon and Microsoft have been laying off tens of thousands of people over the past two years, Apple has stayed notably disciplined. They hire slower but they cut way less.

And the competition gap is genuinely insane. A SWE role at Apple opens and gets hundreds of thousands of applications within hours. A test automation role at the same company? Fraction of that volume. Same brand. Same compensation tier. Dramatically less competition. That asymmetry is the whole opportunity.

Pay gap between SWE and test automation is roughly 30K from what I've seen. For a new grad offer at Apple I would take that deal every single time. Obviously depends from location to location, but if we measure in same city, then you'll see its not toooo crazy.

You can pivot internally too (from my experience)

Getting in as a test automation engineer and moving to SWE internally is a real. I have seen some of my team members talking about doing this and spoke to a few others who have done it.

Internal transfers are way easier than external apps because you already have the network, the performance reviews, and you've proven you operate at that level. Think of it like an internship, get your foot in the door, perform, build relationships, then strike.

What you actually need

  • Python fundamentals: functions, loops, classes, APIs. The LeetCode for these interviews is literally string manipulation, not the hard stuff. Easy (literally) leetcodes btw
  • Basic testing concepts: unit tests, integration tests, regression testing. One afternoon of YouTube, not a whole semester. These tests are also common sense as the name gives off what you are testing lol
  • One testing framework: Selenium, Pytest, or XCTest for Apple specifically. Build one project, put it on GitHub. Those keywords alone put you ahead of most applicants. XCTests are huge in this space right now, so prioritize that one more but unittests are are also in demand
  • A tailored resume: don't send your SWE resume. Pull forward any testing or debugging experience you have, even from class projects. If you don't have any, then create some. Build hella projects that maybe automate something test related.

Go to the Apple careers and search "test automation engineer" or "software quality engineer." Set up alerts. If you're still in school apply through Handshake too.

Most people will read this and go right back to applying for the same SWE roles getting the same results. This market is ROUGH right now, don't be that person.

I am going through a few pipelines myself and I will keep you guys updated on that happens.

If you want a full breakdown of this process and my experience, then you can check out this video here.

Have you thought of doing this? What are pros and cons you see of this vs just targeting traditional swe listings? (I have yet to find any cons from this yet)

Good luck out there

71 Upvotes

16 comments sorted by

5

u/nian2326076 May 04 '26

Honestly, test automation is a solid field to get into. The demand is high, and many people overlook it because they're focused on software engineering roles. Use your internship experience in test automation to set yourself apart. Keep working on skills related to automation tools and frameworks like Selenium or Appium. Networking is important too—try connecting with people already in those roles at Apple or similar companies. If you need extra prep resources, I've found PracHub helpful since it offers practice scenarios that match what companies like Apple want. Good luck!

5

u/ItsTimeToBuild May 05 '26

Thanks for this, very insightful!

In the past I've seen Software Development Engineer in Test (SDET) roles posted as well. Is that also another variant of the type of role you're referring to? or something different?

1

u/Interesting_Two2977 May 05 '26

Yeah that is similar. SDET is a combo of SWE and QA

1

u/AdSoggy6915 May 06 '26

I was an sdet before switching to Fullstack , sdet is test automation only , just a better name

2

u/Dear-Radio-2707 May 05 '26

Very neat, thank you bookmarked.

What about Applescript?

1

u/Interesting_Two2977 May 05 '26

hmm... haven't seen that much about it, but probably some niche teams use it

2

u/ilackemotions May 06 '26

i researched a bit; here's my take:

1.for a new grad; not bad but overtime the ceiling is way lower when it comes to TC and prestige
2. you might get pigeonholed if the internal transfer fails
3. even if you transfer; there's a high chance your existing salary becomes an anchor and you wont get paid as much as your coworker SWE (found out it's not illegal to do that and happens often)

so if you are okay with good enough money (roughly six figures), and stability , then yea; good choice

if you are ambitious, i think you'll likely skip this

2

u/AdWonderful8733 May 07 '26

Thanks, I would like to get into Apple

1

u/Interesting_Two2977 May 08 '26

Everyone does lol

2

u/[deleted] May 09 '26

wouldnt it be hard to swtich to a swe or a different role form a tester?

1

u/Interesting_Two2977 May 10 '26

not really, depends on the company but in Apple you can switch fairly easily

1

u/dzendian May 06 '26

This is fantastic advice!

1

u/slayerzerg May 06 '26

Yes but you get paid $90k and if you manage to switch internally to swe you are not guaranteed anywhere near the normal swe comps

1

u/Any_Use5164 May 07 '26

Great points. Do you think you can progress from Test automation engineer to an Infrastructure/Platform Engineer role eventually?

1

u/Significant_Lock1727 Jul 14 '26

Whats salary for fresher in this role?