Amazon SDE Intern OA

The assessment consisted of four components:

1. Data Structures & Algorithms A problem centered on minimizing the total cost required to make an array non-decreasing, where costs are incurred by applying increments to contiguous subarrays. Solved using a greedy, prefix-difference approach: tracking the running maximum and accounting only for the incremental increase in required adjustment at each step. Achieved O(n) time and O(1) space complexity.

2. Full-Stack Debugging Given a MERN stack e-commerce application with a broken admin product management module, the task was to identify and resolve two issues:

  • Product creation was silently failing due to missing tag validation and an incorrect database call.
  • Product deletion was non-functional, as the query lacked the required identifier and the route was missing its parameter definition.

Both issues were traced to the controller and route layers and resolved accordingly.

3. Work Style Assessment A series of scenario-based questions designed to evaluate approach to ambiguity, collaboration, and decision-making, aligned with Amazon's Leadership Principles.

4. Behavioral Assessment Situational judgment questions assessing responses to workplace scenarios involving prioritization, conflict resolution, and accountability.

Overall, a well-rounded assessment combining technical problem-solving with reflective, judgment-based evaluation. A useful reminder that strong engineering extends beyond writing code, it includes debugging methodically, communicating clearly, and demonstrating sound judgment under ambiguity.

Now we wait.

reddit.com
u/nvmshivamk — 12 days ago
▲ 11 r/tcs_nqt+4 crossposts

TCS NQT PRIME [ACCPECTED] Experience:

First Round:

- Aptitude section : It was average, the numerical ability section was very difficult, none of my friends were able to do more than 2-3 questions and rest we guessed from the options. Rest sections were easy and very doable.

- Coding section : My shift was the hardest (the first shift of the first day), we were given 2 questions:

  • Kth Largest element in the binary search tree Link
  • First Missing Positive Link

I solved both of them, and you had to write the entire code not just the function.

Interview:

TR + MR: Was asked to introduce myself and then was immediately given a question to code,

questions were:

  • print the longest substring without repeating characters : Got a bit confused in the beginning and returned just the length of the longest substring but then modified the approach and got to the correct answer.
  • print the frequency of every vowel in a sentence : Did this instantly using HashMaps.

I was also explaining the code as I was writing it and was asked to dry run the code as well.

Then one interviewer went away (the one who was giving me the DSA questions) and the second one continued the interview, he showed me 3 tables made on the paper and asked me to write SQL queries for the questions he asked:

  • Print all employees whose name starts with 'A'
  • Print last 3 records
  • Print employees who joined between a date range
  • Print employees who are working in an array of departments
  • Print the employee who has the second largest salary

2-3 more questions were asked which I don't remember, I answered them all.

Then he asked if I know about AI and python, I said yes I am working on it and learning stuff. Then he started asking HR like questions:

  • Would you be open for relocation
  • Would you work long hours and on weekends
  • Thoughts about night shift

I answered everything diplomatically.

Best of luck to whoever is reading this !

u/nvmshivamk — 12 days ago
▲ 7 r/gsoc_2027+3 crossposts

Building a tool to rank open-source repos by "worth contributing to", looking for honest feedback before I build it

If you've tried to find a first open-source contribution (for GSoC, resume building, whatever), you've probably hit this: good-first-issue labels are everywhere, but the label tells you nothing about whether the maintainer actually reviews PRs, or whether the repo is dormant and the label's just stale. You end up manually digging through commit history and old PRs for every candidate repo, which doesn't scale.

I'm building a tool that scores repos on actual signals, maintainer response time, first-time-contributor merge rate, activity recency, pulled from the GitHub API, not just label presence. You'd filter by your stack/interests and get a ranked list with the score breakdown shown, not a black-box number.

Before I sink weeks into this: has this specific problem hit you? Would you actually use something like this, or do you have a workaround that already works fine? Genuinely want to know if I'm solving a real problem or a problem only I have.

reddit.com
u/nvmshivamk — 13 days ago
▲ 7 r/gsoc_2027+2 crossposts

Exploring open source programs

What are some other open source programs apart from GSoC or LFX ?

Programs that are nice and really contribute to meaningful projects and maybe offer stipend as well.

reddit.com
u/nvmshivamk — 2 months ago
▲ 3 r/gsoc_2027+2 crossposts

Open source project seeking contributors (good first issues + advanced tasks)

Looking for contributors and feedback on an open-source developer tooling project.

The project focuses on helping developers understand unfamiliar codebases by analyzing repository structure, dependencies, entry points, and architecture to generate a navigable view of the codebase.

Current stack:

  • TypeScript
  • Next.js
  • Express
  • PostgreSQL
  • Redis + BullMQ
  • React Flow

There are issues available across different experience levels:

For newer contributors

  • Documentation improvements
  • UI/UX refinements
  • Testing
  • Bug fixes
  • Small backend and frontend enhancements

For experienced contributors

  • Dependency graph generation
  • Repository analysis pipeline
  • Caching and performance optimization
  • Worker orchestration
  • System design discussions
  • AI-assisted codebase explanations

The project is structured as a monorepo with a clear separation between frontend, backend, workers, and the analysis engine, making it relatively easy to pick a specific area and contribute.

If you're interested in developer tooling, code intelligence, static analysis, architecture visualization, or simply looking for an open-source project to contribute to, feel free to take a look.

Feedback, feature suggestions, bug reports, and contributions are all welcome.

github.com
u/nvmshivamk — 2 months ago
▲ 6 r/gsoc_2027+1 crossposts

Looking for genuine JS/TS/Web-based open source projects to contribute to

Hey everyone,

​

I'm looking for active and genuine open-source projects built with JavaScript, TypeScript, React, Next.js, Node.js, or related web technologies.

​

I'm particularly interested in projects where contributors can work on actual features, bug fixes, architecture improvements, testing, developer tooling, or performance enhancements rather than only documentation changes.

​

A bit about me:

• Full-stack developer

• React, Next.js, TypeScript

• Node.js, Express, PostgreSQL, Prisma

• Redis, Docker, AWS

• Previous open-source contributions and internship experience

​

If you're maintaining a project or know of one that's actively looking for contributors, I'd love to take a look.

​

Feel free to drop links or recommendations below.

reddit.com
u/nvmshivamk — 2 months ago
▲ 14 r/gsoc_2027+1 crossposts

Stop chasing meaningless PR counts.

A lot of courses and influencers sell the idea that open source is just about getting as many PRs merged as possible.

So people end up spending months fixing README typos, correcting spelling mistakes, removing unused variables, or making tiny cosmetic changes across repositories.

There's nothing wrong with those contributions. They help. But if your goal is to get recognized by maintainers, grow as an engineer, or improve your chances of getting selected for programs like GSoC, internships, or contributor roles, those PRs alone won't get you very far.

The contributors who stand out are usually the ones who:

* Build and own features, even small ones.

* Fix bugs that nobody noticed.

* Improve developer experience.

* Understand the architecture and suggest meaningful improvements.

* Contribute in areas that align with the project's future roadmap.

To do that, you need actual development skills. You need to learn how to read large codebases, trace data flow, understand design decisions, debug issues, and communicate technical tradeoffs.

No shortcut, PR-count strategy, or "100 PR challenge" can replace that.

The uncomfortable truth is that maintainers don't remember you because you fixed 50 typos.

They remember you because you solved a problem that mattered.

reddit.com
u/nvmshivamk — 2 months ago
▲ 12 r/gsoc_2027+2 crossposts

A tool of easy onboarding of new contributors

I've seen a lot of people ask the same question: "How do I get started with a large codebase?"

And honestly, it's intimidating.

Tens of folders, hundreds of files, and you have no idea where to begin. You keep wondering:

* How does authentication work?

* Where does the application start?

* What files are important?

* If I change this, what else breaks?

I'm building a tool to solve this.

Just paste a GitHub repository URL, and it analyzes the codebase, builds a deterministic architecture graph, identifies modules, dependencies, entry points, and request flows, then answers questions grounded in the actual repository structure.

For example:

* "How do I get started with this repo?"

* "How does authentication work?"

* "Which files are affected by this issue?"

* "Show me the user registration flow."

The goal is to make onboarding into large repositories much easier for contributors, interns, and open-source developers.

Would love to know what feature you'd want in a tool like this.

reddit.com
u/nvmshivamk — 2 months ago
▲ 12 r/gsoc_2027+1 crossposts

Active Open Source Project Looking for Contributors (Good First Issues Available)

Hey everyone,

I'm maintaining Quelm, an open-source distributed workflow orchestration platform built with Next.js, Node.js, Redis, BullMQ, and PostgreSQL.

The project already has community contributions and several open issues ranging from beginner-friendly documentation/frontend tasks to larger backend and infrastructure features.

Areas open for contribution:

- Frontend

- Backend

- Documentation

- Performance optimization

Repo: https://github.com/SHIVAM-KUMAR-59/quelm

If you're looking for an active project where contributions get reviewed quickly, feel free to check it out.

u/nvmshivamk — 2 months ago

Gsoc' 27 PR maxxing

So I am seeing many people trying to "prep" flr GSOC or buying courses for it.. but that is just now how i works ! You do it for the love of open source and not the tag or money.

I have been contributing to an organization from the past 2 months and have ~20 PRs merged some of them were tiny mistakes and some fere full stack features.. so everyone trying to get int GSOC, jnderstand the significance of open source first !!

reddit.com
u/nvmshivamk — 2 months ago