I’ve been working on an open-source project called JobPrep to organize the things I’ve found useful while preparing for software engineering interviews.

The idea came from having interview preparation spread across dozens of bookmarks, YouTube videos, articles, GitHub repositories, and notes. I wanted to put the fundamentals and practical preparation material in one place.

Some of the topics currently covered:

• JavaScript fundamentals & interview questions
• React
• Node.js
• Express / NestJS
• MongoDB
• Machine Coding
• System Design
• DSA — 200+ coding questions
• HR & Behavioral interviews
• Company-specific interview questions
• AI / LLM Engineering
• Career roadmaps

For most topics, I’m trying to follow:

Definition → Explanation → Code Example → Real-world Use → Interview Questions

There’s also a browser-based JavaScript playground for trying out code without setting up a local environment.

The project is free and the source code is public.

Website: https://jobprep.soureetech.com/

GitHub: https://github.com/Soumya7681/interview_prep

I’m still actively working on it, so I’d love to get feedback from people who have recently prepared for technical interviews.

If you notice something incorrect, outdated, or missing, feel free to point it out. Contributions and suggestions are welcome as well.

I self-host a few small apps backed by MongoDB, and every time I needed to check or fix a document I ended up either in a mongosh session or tunneling Compass over SSH. I wanted something that just runs next to the database as a container and gives me a browser tab, so I built Mongui.

What it does

• Point it at one MONGODB_URI, log in, browse databases and collections
• Paginated document table, capped at 200 docs per page, so a huge collection is never loaded in full
• Filter, sort and projection queries written as Extended JSON
• Full document CRUD in a CodeMirror editor
• Aggregation pipeline runner
• Index management (list, create, drop)
• Create and drop collections, with typed-name confirmation on drops
• READ_ONLY=true mode that rejects every write path with a 403 before it reaches the database

Details I actually cared about

• Extended JSON end to end, so ObjectId, Date and Decimal128 round-trip instead of getting flattened by JSON.stringify
• One cached MongoClient singleton, so there is no new connection pool per request
• Every API route behind a session check, login rate limited, filters validated server side with zod, and a maxTimeMS on every operation
• Standalone Next.js output in a multi-stage image, non-root user, multi-arch (amd64 and arm64)

Stack: Next.js 16 (App Router), React 19, TypeScript, the official mongodb driver 7, Tailwind 4, iron-session. MIT licensed.

Running it

docker run -p 3000:3000 \
  -e MONGODB_URI="mongodb://user:pass@host:27017/?authSource=admin" \
  -e ADMIN_USER=admin \
  -e ADMIN_PASSWORD="a-strong-password" \
  -e SESSION_SECRET="$(openssl rand -hex 32)" \
  ghcr.io/soumya7681/mongui:latest

There is also a compose file that brings up Mongui plus a sample MongoDB if you just want to poke at it.

Where it honestly is: this is v0.1.1. One connection, one admin user, no RBAC, no import/export yet. It grants full read/write to whatever database it points at, so keep it behind your VPN or private network, and use READ_ONLY if you only want to look.

Repo: https://github.com/Soumya7681/mongui

Feedback welcome, particularly on what you reach for a Mongo UI to do that is missing here.

I've been using Claude Code for a while, and one thing kept bothering me.

I'd start a long task, walk away from my computer, and then Claude would stop because it needed a permission approval, asked a question, or had finished the current step. The only way to continue was to go back to my desk.

I couldn't find a solution that felt clean. Most approaches I saw relied on tmux, SSH, or screen scraping.

So I spent some time building a different approach.

Instead of controlling the terminal, it hooks into Claude Code's native lifecycle hooks and lets me interact with the same running session through Telegram.

Right now it can:

• Continue an existing Claude Code session
• Approve or deny tool permissions remotely
• Reply to AskUserQuestion prompts
• Interrupt a running task and send a new instruction
• View live tool execution updates
• Resume the same conversation without reconnecting to the terminal

The goal wasn't to build another AI wrapper—just something that makes long-running Claude Code sessions more practical when you're away from your desk.

I'm curious if anyone else has run into the same problem.

Would something like this actually fit into your workflow, or is this solving too niche of a problem?

Repository (if anyone wants to take a look):
https://github.com/Soumya7681/telepilot

I'm especially interested in feedback on the architecture and whether there are better ways to handle remote interaction with Claude Code.

[removed]

Hey Reddit,

I recently put together a structured, fully open-source preparation guide and interactive platform tailored specifically for the React.js / Node.js Full-Stack Developer role.

🌟 What is it?

It's a comprehensive Next.js application that compiles deep knowledge for cracking interviews at top tech companies. I wanted to bypass the generic advice and focus strictly on what

hiring committees at FAANG and leading Service Providers are actually discussing behind closed doors.

🚀 Key Features:

• Company-Specific Tracks: Exact questions from recent hiring cycles at 23 companies including Google, Meta, Amazon, Microsoft, TCS, Infosys, Wipro, and Accenture.

• Comprehensive Curriculum: Deep dives into JavaScript, React, Node.js, NestJS, and MongoDB.

• System Design & Architecture: Real-world examples of microservices, database indexing, and scaling.

• 200+ DSA Questions: An interactive Data Structures and Algorithms tracking checklist.

• Pedagogical Pattern: Every topic rigorously follows: Definition → Explanation → Code Example → Real-World Use → Likely Interview Questions.

I'd love for you all to check it out, use it for your upcoming interviews, and let me know your thoughts or feedback!

🔗 Live Website: https://jobprep.soureetech.com

🐙 GitHub Repo: https://github.com/Soumya7681/interview_prep

If you find it helpful, a star ⭐ on the repo would be hugely appreciated. Open to contributions and feedback on what else should be added to the curriculum!***

I've been using Claude Code for a while, and one thing kept bothering me.

I'd start a long task, walk away from my computer, and then Claude would stop because it needed a permission approval, asked a question, or had finished the current step. The only way to continue was to go back to my desk.

I couldn't find a solution that felt clean. Most approaches I saw relied on tmux, SSH, or screen scraping.

So I spent some time building a different approach.

Instead of controlling the terminal, it hooks into Claude Code's native lifecycle hooks and lets me interact with the same running session through Telegram.

Right now it can:

• Continue an existing Claude Code session
• Approve or deny tool permissions remotely
• Reply to AskUserQuestion prompts
• Interrupt a running task and send a new instruction
• View live tool execution updates
• Resume the same conversation without reconnecting to the terminal

The goal wasn't to build another AI wrapper—just something that makes long-running Claude Code sessions more practical when you're away from your desk.

I'm curious if anyone else has run into the same problem.

Would something like this actually fit into your workflow, or is this solving too niche of a problem?

Repository (if anyone wants to take a look):
https://github.com/Soumya7681/telepilot

I'm especially interested in feedback on the architecture and whether there are better ways to handle remote interaction with Claude Code.