14-Day Company PYQ Plan for Campus Placement Coding Rounds

Read the current job or campus notice and the employer’s official careers information. Reported assessment patterns can change by role, batch, location, and hiring partner.

Choose one target company and role. Record the allowed languages, likely environment, time limit if known, and the fundamentals named in the role description. Treat third-party question reports as practice material rather than official policy.

Attempt a small mixed set without hints and under a reasonable time limit. Record whether each failure came from understanding, choosing an approach, implementing it, handling edge cases, or managing time.

Build a gap list by pattern: arrays and strings, hashing, two pointers, sliding window, sorting, stacks and queues, trees, graphs, dynamic programming, or basic mathematics. Your plan should follow evidence from the baseline.

Spend each day on one or two recurring patterns. Review the concept, solve one guided example, then attempt two related questions without looking at the solution.

After every problem, write the input assumptions, approach, time and space complexity, and one edge case. If you cannot explain why the approach works, the problem is not finished.

Combine questions into timed sets that resemble the reported mix without assuming an exact repeat. Decide in advance when to move on from a blocked problem and return later.

Review wrong answers the same day. Classify the cause and re-solve from a blank editor after a gap. Copying a solution can create familiarity without recall.

Practice stating a brute-force approach, improving it, testing an example, and naming complexity. Interviewers may care about your reasoning even when the final code is incomplete.

Use one mock session to explain a solved PYQ and one to debug a deliberately broken solution. This connects coding-round preparation with technical interview communication.

Run one final timed set in your chosen language and environment. Review your checklist: input parsing, empty and boundary cases, overflow where relevant, output format, and a final sample test.

Use the remaining time to revisit notes and sleep normally. The plan cannot guarantee a particular question or result; it gives you a repeatable way to use reported questions without mistaking memorization for preparation.