Envié una solicitud electrónica. Acudí a una entrevista en Under Armour
Entrevista
How a company interviews tell you a lot about it. Its not a tech company but guess they try to follow their pattern and fail. Coding round was initially designed to gauge a candidate's logical thinking. But guess the expectation has become to finish it. Expecting to finishing a medium/hard leetcode type problem in 25 mins is not reasonable after a candidate is grilled for 1 hr on architecture. These people also expect a certain/specific answer as well. There is no gap between system design and coding round. Everything is done in one stretch. On a real job am pretty sure you have more than 25 mins to think through a hard problem and no one context switches that fast from architecture to coding.
Envié una solicitud electrónica. Acudí a una entrevista en Under Armour (San Francisco, CA) en sept 2022
Entrevista
Standard process of interview containing multiple rounds, Mainly:
- Recruiter call
- Hiring Manager call
- Technical Phone round
- Final multi round interview
+ Data Structure Algorithm
+ Domain(Android or iOS )
+ System design
+ Behavioral - call with 3 Managers
And finally a call with HR for salary negotiations
Went through 7 interviews that varied from technical to situational questions.
After that many interviews thought I'd at least get a phone call if they decided to go with someone else, but instead got a one line email. Wish if they were leaning towards another candidate they would have stopped the process so I didn't waste so much of my time.
