Having changed two teams, I've found a team that:
has a lot of freedom in product decisions
allows us to choose what technology we are allowed to use
has a generally accepting culture, where people genuinely try to be less biased
offers good benefits
Sometimes it is better to focus less on the process and more on the product/people. TFS will still be there when we are done creating. No need to manage us like we are a construction company. Agile means sometimes we don't know what the cost is three months in advance.
Screening call followed by three technical interviews and one behavioral interview. All technical interviews started with one values question, and then we jumped into LC-style problem-solving. The process is language-agnostic. Design questions might
I applied online. The process took 3 weeks. There were 4 rounds in total: - 3 coding rounds: Behavioral questions and diving deep into my resume, with 1 or 2 coding questions (LeetCode Easy-Medium). - 1 System Design round: Started off with behavior
Standard intro to CS material, algorithms analysis, and rough systems design. A lot of interview questions will test your CS fundamentals for intro-level jobs. There's nothing about big system design or architecture except in rare cases. Know your
Screening call followed by three technical interviews and one behavioral interview. All technical interviews started with one values question, and then we jumped into LC-style problem-solving. The process is language-agnostic. Design questions might
I applied online. The process took 3 weeks. There were 4 rounds in total: - 3 coding rounds: Behavioral questions and diving deep into my resume, with 1 or 2 coding questions (LeetCode Easy-Medium). - 1 System Design round: Started off with behavior
Standard intro to CS material, algorithms analysis, and rough systems design. A lot of interview questions will test your CS fundamentals for intro-level jobs. There's nothing about big system design or architecture except in rare cases. Know your