**The problem:** Most interview prep is passive - read, memorize, hope you remember it under pressure. Nobody's built something that actually simulates the pressure itself, adapts to how you're really performing, and tells you where you're weak before an interviewer does. So I built one. **What it is:** Kiriti AI - an AI mock interviewer that runs a real adaptive interview based on your resume. Question difficulty shifts live depending on how you answer. It scores your body language along with your answers, generates a cheatsheet specific to your actual domain, and won't let you move to the next level until you've cleared your weak areas. **How it works:** * Upload your resume * It builds a personalized interview around your actual background and target role * You go through rounds that get harder or easier live, based on your answers * You get a score breakdown - technical accuracy, body language, communication * Daily quiz keeps terminology fresh between sessions **What makes it different from generic mock interview tools:** * Adaptive difficulty in real time, not a fixed question bank * Body language scoring, not just answer correctness * Domain-specific cheatsheets instead of generic prep material * Weak-area gating - you can't skip past what you're actually bad at **Where I am:** Solo-built, currently free to try, actively improving based on feedback. No paid users yet - this is early. **Why the name:** Kiriti is one of Arjuna's names in the Mahabharat. The whole product is built around the idea of consistent, deliberate practice before the real test - which felt like the right namesake. **What I'm looking for:** * Honest feedback from people who've actually done technical interviews recently * Anyone who's grown an early-stage SaaS in India and can share what worked * Placement cells / coordinators open to a pilot with their students Happy to answer questions or take...

Im seeing a pattern where my performance reviews are more and more becoming about being better at gathering, and confirming functional requirements. Historically I’ve been given functional reqs and focused on documenting and delivering on the non functional requirements (eg uptime, reliability, maintainability, extensibility, etc?), but I’m seeing a preference to just hand wave this now. More and more I’m asked to include functional requirements in my tech briefs and being asked did you check data, talk to the customer/operations to confirm? My tech briefs are starting to become project briefs with a side of tech. It’s kind of demoralizing because organizing functional requirements feels like an admin job, and then you start getting pinged for a bunch of data support issues because X isn’t Y etc. It all contributes to time away from understanding/staying abreast the underlying tech. Is this a trend, or something unique to my org? Edit: I get this mentality for a startup since everyone has to wear a bunch of hats, but I’m experiencing this at a large org where it’s a huge lift to understand systems end to end.

Interviewing for a new team in the same overall org at my big tech company. Previous manager who I worked with closely on launching one of the first AI large scale products reached out to me to ask me to join his team. A lot of previous team members. For compliance reasons have to interview the same as external candidates. 2/4 interviews done. Failed both easy style leetcode problems due to severe performance anxiety. I’ve done these problems before but not in a few years. Does anyone else have this issue? How do you deal with severe coding anxiety in interviews? For reference, 18 years of experience, top reviews and bonuses every year, built features millions of people use. Propranolol didn’t help.