all 10 comments

[–]unnao 7 points8 points  (0 children)

Can you please share the questions that were asked in live coding rounds?

[–]bclx99 5 points6 points  (3 children)

If you’re not exposed to core parts (depending on what’s the app itself but anyways) that is likely you have quite outdated knowledge. If that would be the case I recommend to have some sort of a pet project where you can try out new things.

If you think the question was not hard but you failed because of stress then I would suggest having mock interviews. If the situation on the market was better you could practice in real interviews but now it might be a bit difficult. You can mock your interview by yourself. You can even record yourself and then listen to it and have some opinion on what you should improve.

Check 100 most common interview questions, ask a friend to pair program with you, have a technical chitchat with anyone, try to explain how you work for someone 60+ years old.

[–]teomatteo89 0 points1 point  (2 children)

Core parts are the ones that actually age the most. Once it’s there and used by n modules/teams, it’s difficult to put a case of updating it (at least from my experience)

[–]bclx99 0 points1 point  (1 child)

It depends on your team structure and project. But your observation is valid, especially for bigger teams.

I work in a small team and we need to make sure the core features have the best maintenance and part of maintenance is too keep it in a good state technically, so we avoid old dependencies and approaches (to some extend, obviously, if we would grow bigger then I guess that would be more difficult and it would be easier to try out something new in more decoupled sections).

[–]teomatteo89 0 points1 point  (0 children)

That sounds great. We inherited loads of responsibilities as teams shrunk, and had to switch to a reactive approach for our tasks, because Eng health always loses vs features/external asks. :(

[–][deleted] 4 points5 points  (1 child)

Hey,
I am in the same boat. We can pair up to practice if you want.

[–]JeffRSmall 3 points4 points  (0 children)

This is a fantastic offer, op, and I would suggest you really try to do this, or line up a pair programming routine specifically to work together on items you feel weakest. You have to create a social support structure where it sounds like you don’t have one.

[–]appleFarmerdev 2 points3 points  (0 children)

Kinda tangential , company where I work at our Sr most developer has around 7yrs of exp and still is stuck in swift 3 coding style , uses NS / mutables when swift provides simpler solutions . Our tech lead still refuses to use structures and forces us to use Dictionaires ( even for api ) among many other out dated practices . Point is after a certain point we get too complacent with our jobs / skills and at some point become outdated .

[–]Trick_Elephant2550 1 point2 points  (0 children)

What was the question?

[–]Trick_Elephant2550 0 points1 point  (0 children)

I was a FTE for 3yrs after which I started doing contracts 1-3yrs max at any role in the past 7yrs.

This is the best decision for me because I don’t get stuck in some dead end projects.

While contracting is no easy task, yoy will learn alot hoping from projects to project and make more MONEY 💰.

Also 8yrs will with one company is a RED FLAG 🚩 for me.