Explore Intuit on Taro

As part of my story or task, often times I have to understand and contribute to other codebases or solve bugs that involve understanding flow of other codebases. What is the best way to navigate this when you are suppose to solve an issue where you have to understand an external codebase in order to contribute or fix an issue?

I am a frontend focused full-stack engineer with 7 years of relevant experience in the frontend engineering space and a total of 12 years of experience. I am not able to decide where should I invest my time when working on side projects. Should I start picking up mobile(Android/iOS) or continue to sharpen my skills in the frontend development space? To put it another way, should I invest my time in going depth in my current domain or should I invest time learning mobile UI development as that has gained more traction and is viewed as more valuable skill?

I think I am unable to decide whether to go about developing my skills in breadth or depth.

I'm in the onboarding phase. I was assigned a starter task and have been working on it. I haven’t done the work of asking questions on design choices (that part is pending).

I want to be ramped up after a week and am wondering how to spend the time. Should I go in-depth on overall architecture? Or spend time working on the codebase? Or is there something else I should do?

I'm on the earlier side of mid-level with around ~2 years of experience. I just wanted to get some overall thoughts from senior engineers that are more seasoned than me: What are the main things to grow from mid-level to senior?

I feel like everyone's talking about getting into FAANG all the time, and I've been thinking about it as well since I haven't worked at a FAANG company yet. I see people with really short stints on their resume - Is that really okay? Overall, it's all a lot to take in and I'm just wondering how to best think about my career and get away from all this job switching noise.