r/InterviewHackers

bit of backstory first. i spent months grinding leetcode, hundreds of problems, could solve most mediums alone no stress. then i kept bombing actual interviews, and for the longest time i assumed it meant i just wasnt good enough technically.

eventually it clicked that the technical part usually wasnt even the issue. i could solve the thing. i just couldnt perform it, going quiet at the wrong moments, rambling, blanking on follow ups i actually knew, falling apart the second the interviewer asked me something. solving alone and doing it live while someone watches and expects you to talk are completely different skills, and nothing i was doing trained the second one.

the annoying part was there wasnt a great way to practice it. interviewing. io is like $150+ a session, peer mocks mean scheduling around someone elses life and hoping they show up. so i ended up building the thing i wished existed, an AI that runs full live mock interviews (coding out loud, system design, behavioral), pushes back on your approach mid-problem, and tells you where you actually fumbled after.

im at the stage now where it works but i genuinely need people to break it and tell me whats bad about it. so a few honest questions:

if youve struggled with the "i know it but cant show it live" thing, does an AI interviewer sound like something you'd actually use, or does it feel like it'd miss the point vs a real person?

whats the one thing that would make or break it for you?

and honestly, would you trust AI feedback on your interview performance, or is that the part that feels off?

not trying to sell anything here, its free and i mostly just want to know if im building something people actually want or if im too close to it to see the obvious flaw. full disclosure obviously, its mine. Let me know if anyone is interested and wants to check it out.

I've received an email for the Software Project Engineer written test at CDAC Bengaluru.

Has anyone appeared for this exam before? I'd like to know what kind of questions are typically asked, the difficulty level, and which topics I should focus on for preparation.

Any insights or preparation tips would be greatly appreciated.

Backend dev, been putting InterviewMan through a CodeSignal practice GCA this week to see how it handles the speed. I cant share a screen recording sorry, but I sat a few throwaway questions just to feel out the timing before I have to lean on it for an actual one.

Initial thoughts: the speed is really impressive for the price. The answers start streaming in while the prompt is still loading and its a one liner on screen in maybe two or three seconds in my testing. Those two things alone make it the one I'd want on a GCA in my opinion. Its becoming increasingly hard to find a helper that keeps pace under a clock that tight these days. So its interesting that the part I was most scared of, the timer, is the part it handles best.

Its a real desktop app and not a browser tab too (I tested this with CodeSignal locking the page down) and it works pretty well. But I'll have to test more to get a better idea of how it holds up late in a run. The detection is set to medium and the answer length to Short. Which is good and I quite like it because it means I get a quick nudge instead of a paragraph I have no time to read.

The screenshot capture grabs the problem diagram fast when the GCA wording is a mess. Theres a question detection sensitivity in there too which I found perfect for stopping it firing on every sentence. The answers on the harder problem are a touch slower but still in time. So I'll have to test more how it does when my brain is fried 50 minutes in.

So far it feels like the answer actually arrives in time to use and I love how quick it is. Feels well built and has the settings that make the speed work for a GCA specifically. Anyone here actually run it on a real CodeSignal GCA under the timer, would love a sanity check before tuesday.

bit of a rant/lesson, bear with me.

i used to treat interview prep like a grind counter. do enough problems, hit some number, youre ready. so i did, neetcode, blind 75 a few times over, could knock out most mediums alone without much drama.

then i sat in a real interview and it fell apart, but not in the way i expected. i didnt totally blank or anything dramatic. what actually happened was messier. i solved it, mostly, but i couldnt explain what i was doing as i went. went quiet at the wrong moments, then over-explained tiny stuff nobody cared about, fumbled a follow up i definitely knew the answer to, needed the interviewer to nudge me toward a line i'd have caught instantly on my own. walked out having "solved it" and still got rejected.

took me way too long to get why. knowing how to solve a problem and being able to perform it live while someone watches and expects you to talk are just two totally different skills. leetcode only trains the first. i had loads of the first and almost none of the second, and grinding more problems was never gonna fix a gap that had nothing to do with problems.

and its not just "freezing" btw, thats what i assumed at first. its a whole spread of stuff:

• going quiet and making them dig your thinking out of you
• the opposite, rambling and turning your answer into a monologue
• blanking on follow ups you actually know
• not knowing how to structure the answer out loud
• falling apart the second they give a hint instead of using it

all different symptoms, same root thing, you can do the work, you just cant show it under pressure. and you cannot practice ANY of that alone in a leetcode tab, because the whole problem only shows up when theres another person in the room.

stuff that actually helped once the penny dropped:

• record yourself solving out loud like its real. painful to watch back but you hear every silence and every ramble
• do real reps with a human watching, even a friend. the nerves show up less on the day if youve felt them a few times
• narrate BEFORE you type not after. "im weighing two approaches, let me talk through the tradeoff." feels awkward, works

anyway wasted a lot of hours on the wrong thing. genuinely curious where other people land, was it the actual algorithms that failed you in interviews, or was it this, knowing your stuff but not being able to get it across live?? for me the problems were never the problem.

I have the apple interview next thursday for ICT4 SWE on the platform group but i tested interviewman over three days, two practice calls on zoom with a friend who used it for his own apple interview last cycle and one solo webex run just to see the share dialog. Not much to write home about as a test set. My friend got the offer in december and showed me his setup, the overlay was invisible on his screenshare even when i was actively scanning the corner he said it was in. I bombed an amazon virtual final last cycle on a sliding window problem i had solved fifteen times in prep, just froze on the first sentence. Apple specifically because the offer math is bigger than the company i'm at now and i cant afford to freeze again, the recruiter said five rounds with webex for three and zoom for two depending on who's free. Tested the tool and first impressions are good, just want real confirmation from someone who walked into the apple thursday and walked out with the offer. Should i commit to the annual for the full day or is the suggestion box too aggressive across five rounds back to back? Or does the box hold up the whole interview and i should just go for it.

I'm about to have my first ever Amazon SDE2 interview, and it's running on Chime. As such, i'm not very familiar with how InterviewMan behaves on that specific platform yet.

Edit: Forgot to mention i did a dry run with a coworker the night before on Zoom to confirm the overlay didn't show on screen share, and it was totally clean. Chime is the one i'm worried about though since it's the actual round.

Is Chime any different from Zoom in terms of how the screenshare works? As in does the desktop overlay get caught the same way? Or is there any behavioral difference i should know about? If so, what is the expected layout for the share dialog?

I've been preparing by doing Easy/Mediums out of Blind 75 and LC Amazon tagged problems, prewriting STAR examples for the LPs, and i think i'm decently ready on the content. Really focusing on the LPs because the Amazon interview process is half LP-based and that's the part where InterviewMan's behavioral prompt is supposed to shine.

Any information about how InterviewMan behaves specifically on Chime and how the LPs work in practice with the tool is appreciated. Thank you!

prepping mbb round 2 at one of the three. tested interviewman with my casebook partner last week, two cases. prompts pulled some MECE-ish framework right when the case opened, kept me from blanking minute one (which is the part i actually do blank on).

so the question is. during the case itself, how much do they actually care about structure being visible on screen vs all in your head? like if my analysis is solid but im glancing at a scaffold on a side monitor, does a consultant who does this every week clock the glance, or is it just thinking time

I need some help in practicing some of the interviews. I have an upcoming on site interview at Capital One for the lead senior software engineer.

Even though I have a lot of notes from the recruiter, I don't know how to prepare for a coding and a case study interview. Can someone please share their experiences?

I feel I badly need guidance on these 2 interviews. The reason is that,

1. Whenever I've given any technical assessments which are non leetcode style, they've gone bad because I don't know how to practice. Like leetcode, if I could practice on a small codebases where I would have to extend it and probably work on a small feature or find bugs, it would be great. Most of the time, the only thing I needed is time.

2. I've never given a case study interview. It would be great to get some examples and answers so that I can learn and practice.

They have mentioned 4 rounds

1. Coding

- Leetcode style? - NO

- It would be more focused on building API, security, database schema, scalability

- They would ask 3 level based questions

• Solve all of questions
• For Design and Style, the interviewer will check if the solution is easily understandable by an engineer
• For a Function or a class in the solution, the interviewer'll check if the problem at hand is solved or not.
• For Technical communication, the interviewer'll check how the candidate is communicating.
• Need to ask clarifying questions and thats how capital one gauges your abilities
• Need to produce optimized, scalable and resilient solution
• The solution needs to be modular, extensible, and demonstrating modern tooling and best practices. Also, need to use the coding language that is best for 2026

2. System Design

- Primary focus will be on architecture. Probably banking related or credit card related system design question

- The interviewer will be focussed on 3 areas

• Designing style
• Technical concepts
• Technical communication

- No need to have any banking experience.

- Need to

• Ask Clarifying questions
• Gather
  • Technical Requirements
  • Non-technical Requirements

- The solution needs to be thorough and have deep dives about a few things atleast

- Need to make sure about (Not limited to)

• Resiliency
• Scalability
• Reliability
• Authentication
• Security

- For authentication, authorization, the interviewer might talk about API operations

- The solution also needs to address failures

3. Behavioral

- The interviewer can be anyone. Not necessarily a person from the technical background (any line of business from capital one)

- This kind of interview will be a standard behavioral interview

- Need to make sure able to answer in STAR method and break down systematically

- They'll focus on 2 main areas

- Overall communication

- Questions might be asked related to the Capital One values

• Handling conflicts --> Need to make sure that conflicts internal/external
• Learning continuously --> The candidate needs to be the initiator in the story. For example, the candidate found and issue or a problem on their own and fixed it.
• Delivered results --> Make sure to quantify results, how you got the job done (very important)
• Influence (Huge important) --> As a senior lead, something you did which was positively impactful or you've influenced and how you swayed people positively
• Team collaboration --> Ability to cross-team (functional) collaboration
• Embracing change --> How you went with the change happened around you. Capital one like to talk about failure --> Make sure that you don't end on failure (regular STAR method) --> Talk about
  • What went wrong,
  • What you learnt since then,
  • The change(s) that you made,
  • The success you've seen since then.

4. Case Study

- It will be graded in 3 areas

• Quantitative Analysis
• Technical Problem Solving
• Technical Communication

- There will be a coding element, but not going to be a coding from scratch

• Ability to review and optimize existing code
• Going to get real world business scenario. It could be anything --> any business problem
• Need to solve a simple mathematical using code signal

- Going to have a back story to the business problem

- The interviewer will continue to feed the candidate information

- Implement solutions out of the box, make callouts,

- Goal is to provide solution and in the end explain what your finding is and provide recommendation

• Think out of the box --> Provide diff processes while working through the problem

- Hint: Watch a youtube video - Ace your capital ones case interview -- > Business analyst case.

i passed mbb round 1 at one of the three and round 2 is wednesday. did a dry run with my casebook partner on three rounds to check the tech before wednesday. framework scaffold loaded fast, math prompts felt clean.

round 2 interviewers are partners or senior partners who've done this for years. easy to be polished on round 1 and fall apart on round 2. the scaffold helped during my dry run but i'm not sure if a partner would clock the glance to the side monitor as a tool or just thinking. anyone done mbb round 2 with the tool and walked out with the offer?

i got a hackerrank OA in few days, im thinking of playing a looped 1-2 hour video of me pretending to give the test through the virtual camera, would hackerrank detect or flag the usage of virtual camera?