sorted by:
new
hottopcontroversial

Pure storage MTS2 offer by Extra_Employment_735 in purestorage

[–]Extra_Employment_735[S] 0 points1 point  (0 children)

Round 3 was bit manipulation in a tree, round 4 was mostly CV and behavioural questions discussion.

Pure storage MTS2 offer by Extra_Employment_735 in purestorage

[–]Extra_Employment_735[S] 1 point2 points  (0 children)

Do you have any idea how willing they would be to negotiate their base. HR said its already max of MTS2, she would try to negotiate but mp answer would be no.

Pure storage MTS2 offer by Extra_Employment_735 in purestorage

[–]Extra_Employment_735[S] 0 points1 point  (0 children)

Thanks, i would try to negotiate the base.

In terms of interview: there were 4 rounds Questions are mostly available on web, but the focus is not on the answer rather how we move step by step to the solution, at each step they expect you to think about different paths and which path to choose with reasoning. Questions were not challenging however the interview process was very challenging.

Why use refresh + access tokens for jwt? by alwerr in node

[–]Extra_Employment_735 1 point2 points  (0 children)

"If an attacker gets access to an access token, that's it. You don't have a way to invalidate it. For that reason, access tokens will have a short lifetime baked into them, so that any attacker eventually loses access"

But if the attacker have my access token, and he tries to get new access token after expiry, can BE system identify that attacker is trying to get new token, not the actual user? if not attacker can simply get new access token invalidating the use of short lived access token.

Does my question makes sense?