GeeksforGeeks Question · Sep 2017 · San Francisco

Interview Experience at Swaniti Initiative | Set 1 (For Internship)

SWE Phone Screen Intern

Question Details

In the last summer, I got an opportunity to intern at Swaniti Initiative as a software developer. The hiring process was as followed:1.) Shortlisting done on the basis of ...

Full Details

In the last summer, I got an opportunity to intern at Swaniti Initiative as a software developer. The hiring process was as followed: 1.) Shortlisting done on the basis of resume 2.) Online coding round: In this round, we were given a problem statement , and we had to submit our solution in maximum three hours. I was given a web game to develop. 3.)

Phone interview This was the final interview round. Questions were asked on the projects I did in the college, Data structures and algorithms. Having a strong grip on algorithms and data structures will help you sail through this round , so I would suggest go through geeksforgeeks and cover ds ,algorithms from there. It has rich content for interviews preparation.

Free preview — 6 questions shown. Unlock all Swaniti Initiative questions →

About Swaniti Initiative Interview Reports

This question was reported by a candidate who interviewed at Swaniti Initiative. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Swaniti Initiative are the higher-signal extractions to take from this report.

For broader preparation context, the Swaniti Initiative interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Swaniti Initiative reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Swaniti Initiative Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in Swaniti Initiative reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.