Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Avyy7523yMy thought process while solving interview coding bs is as follows -
- Read and understand the problem and constraints/edge cases
- Which data structure should I store the data in?(Stack, queue, tree, heap, graph matrix/list)
- What kind of algorithm is required. dynamic programming, divide and conquer, recursive or iterative?, backtracking
- Run test cases. Most of the time there will be some bs cases. (input = 0, or some other invalid value)
Some of the problems have predefined set of optimized algo, so you'll need to reduce your problem into a standard one -
@Avyy thanks bro.
Not sure if you know or not, but I am not a dev and my problem questions are different with no right or wrong answer.
It's more about framework, structure, reasoning, and creativity.
I am lacking in last two. -
nitnip18153yNever had to deal with such complex questions/problems in interviews. What position are you applying to? Framework?
-
@Nanos true.
Interviewers love to hire themselves. It's all about how you make them feel. -
@Nanos lmao not that way.
It's about overall experience and I wouldn't blame you because devs are not good at sales anyway which also has been a key topic of discussion in the industry since sometime now. -
@Nanos I just came back practicing some mocks.
My friend who is super smart gave me some god feedback on these lines.
Engaging the interviewer is one way, telling stories while explaining is another, keeping it conversational than one sided is one more way.
And many more ways to do so.
Related Rants
Ugh! I feel so low and less motivated because I am unable to solve the interview practice questions really well.
This is fucking annoying. I am not sure what is that that I am lacking.
I got the framework. I have problem statements. I am practicing mocks. I got the feedback and I implemented it.
I have spent ~30 hours on this till now. Solved around ~20 cases, 10 of each category.
Should I now purely bet on luck? Maybe I'll take a break and submit the other companies case assignment to divert my mind.
I need to crack the interview and land the offer at all cost. There is no chance or scope for failure.
rant
learnings
interview
success
practice
mocks