Maybe it was because you weren't able to find the right data structures.

Or are you gonna misty using a problem quickly in this video?

I'm gonna show you how to find the optimal answer in according interview quickly.

Just as an example, let's consider this maximum sub array problem.

Now.

What's a subway?

A sub arrays, basically an array within.

All right, so an example of a sub array would be to one.

Or it could be just one element negative three.

Or it could be the whole array that's also separate.

But if we had instead NATO three on, let's say, one, that's not a separate because these air not contiguous elements.

So a sub array is a set of continuous elements within the given.

All right now, the problem here is finding the sub array with the maximum some.

Here's what I mean, if we look at this separate to one, the Selma is two plus one equals three on If we look up this sub array with Justine Berry three.

The Psalm is negative.

Three on.

We're trying to find the one with the maximum, some on in this example.

It's actually 21 with the Psalm three, and you can check it yourself, too.

Let's say you're given this problem in your interview on you don't know how to solve it on.

You can't figure out the solution right away.

What did you do about it?

There are four tips I want to give you here for finding the right solution very quickly.

Tip number four is just say, Can I think for a second?

Whenever you start thinking, you know, most candidates become completely silent when they start thinking on it.

Could be really awkward for the interviewer because they don't know what you're doing.

So you should really clarify whenever you start thinking tip number three's Think aloud.

Once you said that phrase, can I think for a second you should start thinking out loud instead of silently?

I know for some people, it's easier to think silently, but you don't have to overdo this.

You just need to let the interviewer know where you are in your thought process.

On the way I would do it might be something like this, I would say.

Okay, I noticed that their policy of members here in this example on also negative numbers on If we only had positive numbers, let's say 1 to 1, then the problem would be much easier, because then the maximum sub array would just be the whole rape.

So what makes a hard is the fact that we have negative numbers.

So maybe we can do something separate to the negative numbers on the positive numbers in there, Ray.

And when you say something like that, the interview is gonna say either okay, you're going in the right direction or in the wrong direction, and that's gonna be really helpful for figuring out what the right solution ISS.

So you shouldn't think of the interview as a monologue or a solo problem solving session.

You should think of it as more of a collaborative thing as a conversation, so you shouldn't have to solve everything by yourself.

When the average Canada is given a problem, they just start writing code.

But you shouldn't do that.

You should first think through examples and think of a few more examples than that.

Just give him one.

So in this problem, I might say, Okay, this is a, of course, a given example, but I can think of a few more examples.

What about all postive numbers?

On what about maybe all negative numbers.

When you start thinking through examples, you be able to think in a much more concrete way than trying to think of everything in an abstract way.

Let's say you start thinking through examples and you come up with a solution, then, Ah, you should ask, Does this seem like a good strategy?

Unless you're 100% sure that your solution is optimal on the way I would do in this example might be something like this.

I would say.

Okay, my solution would be compare all the sub Uh oh, the possible separates.

So the ones starting at the first thing next and then the ones starting at the second index and I will compute the sum for each sub array on.

I was just picked along with the maximum some.

So it's a boot for strategy.

And then I would ask to the interviewer thous, this seemed like a good strategy when you say that you're essentially giving some space duty interviewer so they can give you feedback as to if you're going in the wrong direction.

or if your solution is really optimal.

And this way you don't have to waste time writing code because you didn't write code in the first place.

You don't have to waste time writing code for a solution that doesn't work or that's not optimal.

So just to recap say, Can I think for a second when you start thinking, Think I allowed instead of Simon Lee?

You don't have to overdo this.

You just need to let the interview and nowhere you're thinking from time to time.

And don't start writing code right away.

Use examples first.

And finally, when you come up with a solution, just ask.

Does it seem like a good strategy?

And these are more four tips for finding the optimal solution in according interview quickly.

I hope you like the video.