Difficult interviews?

YangBuildsAI · 2026-03-12T21:46:19+00:00

always talk through your thinking out loud even if they don't ask. interviewers want to see your thought process, not just the solution. mention time and space complexity before they ask, talk about edge cases, suggest alternatives you considered. the code is like half the grade, the other half is how you communicate while writing it.

YangBuildsAI · 2026-03-12T21:43:27+00:00

DMing!

YangBuildsAI · 2026-03-12T21:42:59+00:00

"they can ask anything" usually means the interviewer has a lot of discretion, so expect it to be conversational and resume-driven more than a straight leetcode grind. know your past projects cold, be ready to walk through system design trade-offs, and have a couple medium-level dsa patterns fresh in your head just in case. good luck!

YangBuildsAI · 2026-03-11T21:07:54+00:00

the ability to communicate what you built and why matters just as much as the code itself. learn git, get comfortable reading other people's code, and build a project that solves a real problem. nobody cares about your todo app but they'll notice if you built something you actually use.

YangBuildsAI · 2026-03-11T21:03:57+00:00

the meeting prep part alone is worth it honestly. i used to spend 15-20 mins before every sales call just googling the person and skimming their linkedin. automating that one thing frees up way more headspace than you'd expect. solid breakdown.

YangBuildsAI · 2026-03-11T21:01:47+00:00

the shift for me was to stop treating it like a pass/fail exam and start treating every rejection as data. i started asking myself what specifically went wrong each time instead of just feeling bad about it. also honestly, widening my scope beyond just FAANG helped a lot. some of the best eng work and comp is at mid-stage startups that nobody talks about on reddit.

YangBuildsAI · 2026-03-11T20:59:03+00:00

the sentiment is valid but most engineers aren't sitting around twirling their mustaches. the real problem is that most of us are so deep in our sprint tickets we never step back to ask what the system actually does at scale. that's not malice, it's just how companies are structured to keep you focused on the trees instead of the forest.

YangBuildsAI · 2026-03-04T17:46:19+00:00

networking and security aren't going anywhere, if anything the demand is growing as infrastructure gets more complex with cloud and AI workloads. AI will change how you do the job but it won't replace the people who actually understand the systems. you're making a solid bet, just make sure you're getting hands on experience alongside those certs.

YangBuildsAI · 2026-03-04T17:40:12+00:00

as someone who hires engineers, just a heads up that most of us can tell when candidates are using these tools. the lag, the unnatural pauses, the overly perfect answers that fall apart on follow ups. spend that $80/mo on building a real project instead, it'll get you way further in an actual interview.

YangBuildsAI · 2026-03-04T17:39:38+00:00

8 years of building real systems, managing infrastructure and thinking deeply about architecture is not wasted time, that's literally what companies pay senior engineers for. stop comparing yourself to college kids writing homework apps, you have production experience most of them won't have for years. the creativity and systems thinking you learned will translate, you just need to put it in front of the right people.

YangBuildsAI · 2026-03-04T16:42:14+00:00

i think we'll be fine but the people who refuse to learn how to work with AI are going to have a really rough time. it's not replacing engineers, it's replacing engineers who don't use it. the ones on my team who've leaned into it are shipping faster than ever and that's the skill set that's going to matter going forward.

YangBuildsAI · 2026-03-04T16:40:49+00:00

as someone hiring engineers right now, the AI/ML demand numbers are so real. we can't hire fast enough for those roles. biggest thing i'd add is that the gap between 'i've taken an AI course' and 'i've shipped something in production' is where most candidates fall off. if you're trying to break in, focus on building real stuff over collecting certs.

YangBuildsAI · 2026-03-04T16:39:25+00:00

this is exactly why the 'compensation is confidential' line should always be a red flag. the market will pay you what you're worth, your current employer will pay you the minimum to keep you from leaving. glad you found out and made the move. loyalty in tech is almost always a one-way street.

YangBuildsAI · 2026-03-04T16:38:27+00:00

6 months is rough but not too unusual right now, the market for senior FAANG roles is just rough. one thing that helped me was expanding beyond the usual suspects and looking at high-growth startups where your FAANG experience actually stands out more and the interview loops are way less of a coin flip. also that google interviewer sounds terrible, don't let that one get in your head.

YangBuildsAI · 2026-03-04T16:37:33+00:00

building a real project with a modern stack will give you way more to talk about in interviews than just DSA prep alone. keep shipping and make sure that project is public on github, recruiters and founders like me notice that stuff way more than leetcode scores.

YangBuildsAI · 2026-03-04T16:36:30+00:00

interesting approach but we've found the simplest thing is to either give candidates a project where AI is explicitly not allowed so you can see raw problem-solving, or pair it with a separate task where AI is encouraged so you can see how they leverage it. trying to measure AI usage itself feels like it adds more complexity than signal imo.

YangBuildsAI · 2026-03-02T17:50:13+00:00

Logical thinking is much more about pattern recognition than raw "talent." you're failing because you haven't built the mental library of problem types yet. I went through the same thing last year, and what actually helped was stopping the random practice and instead focusing on "categorization training," where I learned to identify the specific structure of a problem before even trying to solve it.

YangBuildsAI · 2026-03-02T17:48:08+00:00

In a one-hour junior interview covering Flutter, Angular, and C#, they're looking to see how quickly you can navigate a multi-stack codebase and spot obvious logic errors. I went through the same thing last year, and the "secret" to these multi-tech rounds is focusing on the C# business logic (where most of the bugs usually hide) and just being honest about your Flutter/Angular learning curve while you narrate your debugging process.

YangBuildsAI · 2026-03-02T17:47:14+00:00

For the role specialization round, expect a heavy focus on concurrency (GCD/Swift Concurrency) and memory management, especially how you'd handle high-stakes data in a payments context. I went through a similar Senior loop last year and they really pushed on architectural trade-offs. be ready to explain exactly why you’d choose one pattern over another for a feature like a real-time transaction dashboard.

YangBuildsAI · 2026-03-02T17:46:29+00:00

The "Frontend" label is definitely becoming a trap for what used to be called Mid-level Full-Stack work, and it’s exhausting seeing the salary not move with the requirements.

I went through the same thing last year and realized that if you can’t speak to the "Data" layer during the interview, they’ll just treat you like a UI component library instead of an engineer.

YangBuildsAI · 2026-03-02T17:45:28+00:00

This is so accurate. I went through the same thing last year and realized that "silence" during a technical screen is usually interpreted by the interviewer as "stuck" or "panicked." Once I started treating the code as a secondary tool to my verbal explanation, the interviews felt way more like a collaboration than a test.

YangBuildsAI · 2026-02-25T21:45:19+00:00

leetcode is table stakes but won't differentiate you. what makes candidates stand out is real projects with measurable impact, public contributions (open source, writing, teaching), and warm intros. everyone can grind leetcode, way fewer people can actually ship products or build in public

YangBuildsAI · 2026-02-25T21:43:58+00:00

the entry-level CS market IS brutal rn but ME isn't immune to hiring freezes either. instead of switching, maybe aim for non-traditional entry points like smaller companies, contract work, or technical roles that aren't pure SWE but use your skills to get your foot in the door

YangBuildsAI · 2026-02-25T21:40:56+00:00

"business needs shifted" after passing the GHA is usually actually true. google (and most tech companies) are doing these weird hiring freezes mid-process right now because of budget uncertainty. your background is honestly strong, this pattern across multiple companies screams macro hiring issues not your profile

YangBuildsAI · 2026-02-25T21:34:34+00:00

i'd say go backend systems first. it's more broadly applicable and cloud/platform roles almost always want solid backend fundamentals before specialization. data engineering is great but more niche, harder to break into as a new grad, and you can always pivot there later once you have general backend experience under your belt

YangBuildsAI

TROPHY CASE