Applied via portal.
Got OA link: Did not remember the format, solved both problems

Phase 1 of interviews:

Interview 1:
Explained about IS & T team

1. Leetcode medium question
2. class LongIterator implements Iterator {long val = 0; long max = 1000000; public boolean hasNext() {return val < max;} public long next() {return ++val;}}
   Write a driver funtion to calculate all values sum.
   Now parallellize it to calculate using two threads. I used CompletableFuture, AtomicLong and ExecutorService, interviewer seems happy with this.
3. If after deployment your service goes down every 2 hours, what will you do.
4. SOLID principles.
5. Some basic questions on spring, like MVC vs Boot, IoC... also why ExecutorService, why not threads...

Interview 2:

1. Deep discussion around my projects in resume
2. HLD of rate limitter, with some basic coding of the algoriths, where to fit this, when considering distributed env of API gateway, how to handle cache, and what to do if cache goes down, partioning, and static configs for rate limitting vs dynamic configs, how can we achieve this.

Both interviewers seems technically very good, enjoyed the conversation.

Verdict: cleared.

Next:
3 more rounds in person on Hyderabad office.

Coding + Java

• Given two employees, you need to merge them into single DS, which DS to use and why. I used HashSet and explained how hashset works internally and how writing equals and hashcode will help in identifying the unique elements. Also while creating the hashset a comparator.
  interviewer said you could have used addAll, I wrote a for loop
  Questions asked if i have used auth> - No here
  4 threads producing cars parallelly, they need to place them in a warehouse, warehouse has slots. in each slot, only one can be placed. write code for this, I used executorservice for this purpose to produce and place car in slots, and each ReentrantLock for each slot. whoever gets the lock, will place the car.
  Interviewer feedback: could have implemented runnable for car producers directly.
  What all types of objects will ExecutorService will expect - Callable and Runnable.
  Mentioned, SpringBoot is in learning stage for me, so no more deep dive questions on this.
  Let's say you are designing a cofee vending machine and you have steps to execute, pour milk, add sugar, add water, ..... finally coffee is made, which design principle you use, and code for it. If I want to replace sugar with coffee, it should be done easily. I coded for this in two ways, not sure on the names, interviewer still needed exact design it seems.

High level Design round:
Deep discussion on my projects, interviewer seems technically sound, wanted me to design a backup system, keeping in mind

1. Data Integrity.
2. scalable
3. Multi region replication
4. Observability
5. Reseliency

Had a good discussion on each and every point I made in the interview.

**Hiring Manager round: **
started with small questions like Tell me about your self,
what is the technical disagrement that you and your peer had on?
what is the one disagreement that you and your manager has, how did you handle this.
Java21 questions, I was unaware of (virtual threads, how they are represented, how they are different from regular threads..) mentione I am not fully familiar with java21
ReactiveProgramming experience: none
worked on rest apis? yes
OAuth and JWT
Why Apple, what made you excite when you read the JD.
Questios on my projects, ever worked with team in non indian hours as well, are you fixated on location or open to relocation
This work we do here is different than the work that you do at your current org, is that okay?

Verdict: No hire (probably) no response from recruiter after interviews, from my end All interviews seems went well.