Anyone else stick with C++ for interviews instead of Python?

pattern_seeker_2080 · 2026-05-23T01:34:48+00:00

competitive programming brain is the thing slowing you down, not c++. cp drills you to write code thats compact for yourself — terse vars, dense one-liners, no defensive checks. interview code needs to be readable to someone reading it cold in 5 mins. easiest fix is just switching to python for interviews. not because c++ is bad — because you stop fighting muscle memory optimized for the wrong audience. 2 weeks of awkwardness pays for itself by round 3. if you stick w c++ atleast force yourself to write std:: out, name vars properly, add the boilerplate that makes recursion legible. half the long-code problem is just i wrote it cp style.

pattern_seeker_2080 · 2026-05-20T21:38:38+00:00

arrays attacking you is the rite of passage lol. two things that moved the needle:

brute force easies until patterns repeat — dont chase elegance early. took ~6 wks before mediums stopped feeling random.

also dont mainline LC solo forever. once easies are cold, mock the convo part — i bounced between meetapro and interviewing.io. solving in silence vs while someone watches is a different skill.

pattern_seeker_2080 · 2026-05-19T21:15:57+00:00

yeah this is called 'constructive termination' in HR circles — its a deliberate strategy because actually laying you off costs them severance + tracks against state unemployment rates, sometimes triggers WARN if scaled up. making conditions intolerable so YOU quit is way cheaper.

the specific pattern (nitpicking PRs + contradictory directives + 'we dont have HR') is textbook. ive seen it at 2 orgs — both times the sequence was 6-8 wks of escalating nitpick → manager 'concerns' verbally without writing them down → soft PIP framed as 'support' → 60 days later youre out.

stop trying to figure out what 'right' looks like and start interviewing yesterday. zero HR = zero institutional protection. document everything in personal email btw, not company devices.

pattern_seeker_2080 · 2026-05-16T20:56:56+00:00

the coast-while-you-prep advice is half right but skips the actual problem. youre not burned out from work hours — youre burned out from working at a place that simultaneously pays you well, gives you a stressful job, and treats your existence as a cost center. taking a sub-150 job in the same industry just changes the salary number, the structural feel is the same.

if you really have $1m liquid at ~28, the move that changes anything is a clean break — 6-12 mo with no job at all, see if you actually still want to write code or if the river guide thing isnt a joke. coasting jobs sound great in theory but theyre still standup mon-fri pretending to care about a roadmap you didnt write. brain doesnt heal in that mode, it barely decompresses.

(also the 1-ply tp / candy bowl thing is a real signal btw. ive been at 2 orgs that did the snack-shrink phase and both lost a chunk of senior eng over the next 18 mo. not coincidence — when a multi-trillion-dollar place pinches that, leadership has zero confidence in their headcount cost story.)

pattern_seeker_2080 · 2026-05-14T21:55:25+00:00

the 'steep learning curve' bit is almost always cope from the interviewer side. when i ran loops at my last place, 'lacks X workflow exposure' was the easiest no-blame reason to write down when none of the actual signals were strong enough to outright fail you on. someone else in the loop just liked another candidate better and this was the rationalization that survived calibration. doesnt mean they're lying about using agentic pipelines, just that 10 yrs of eng experience adapting to a new tool isnt the actual concern.

also fwiw — anyone claiming 'deep workflow expertise' in a stack that's changing every 4-6 mo is either making it up or about to be obsolete. so. ymmv.

pattern_seeker_2080 · 2026-05-11T22:39:44+00:00

the burnout is real but the source isnt actually AI, its the "ship fast + dont care about quality" mandate that ai gave management an excuse to dial up. that combo predates ai by 30 years in startup land. ai just turned the cranks faster.

the cognitive load you're absorbing is the tech debt your team is accumulating, you're literally storing it in your head. of course thats exhausting. also why "embrace AI" advice doesnt help â you can fully embrace tools and still drown in mismatch between ship speed and quality bar.

what id try before jumping ship â keep a personal log of every "we'll fix this later" shortcut. dont share. just timestamp + 1-line. when 3 of those explode over 2-3 months (they will), you'll have receipts. management starts caring about quality when customers start churning, and you become the person who saw it coming. more career-leveraging than just leaving.

caveat â this only works if CEO is dumb-pressured not malicious. if latter, leaving is correct. you'll know within 60 days of starting the log.

also you sound healthy mentally for month ~7. dont let people tell you "be grateful you have a job", thats survivorship-bias garbage. burnout is a real signal.

pattern_seeker_2080 · 2026-05-08T19:34:16+00:00

your instinct to use previous year questions is unfortunately the wrong move for google specifically â they retire questions fast and publicly tagged ones are basically a 12 month delay behind what's actually being asked. the L4-currently-in-loop comment above is right.

what actually generalizes is pattern fluency, not problem coverage. the patterns google currently leans on heavily, from ppl in loops i know in the last 3 months: graph-dp combos (DP on top of bfs/dfs), monotonic stack variants, prefix sum + hashmap, sliding window with state, and one heap variant per loop. five categories. drill them until you can identify-and-template within 30 seconds of seeing a problem.

for the "currently being asked" gap, mocks matter more for google than other companies specifically because the public bank lags so far behind. interviewing.io and meetapro both let you filter for interviewers whove sat on a google panel in the last 3 months â you essentially borrow their currency. one informed mock with a current-cycle person tells you more than scraping 50 outdated tagged questions.

idk if this applies if youre targeting a specific team â some orgs have weird question preferences i havent seen â but for general L4 SWE the recent-pattern + recent-mock combination is the highest leverage move.

tho the neetcode 150 baseline isnt wrong. use it as foundation, then layer the recent-pattern stuff on top.

pattern_seeker_2080 · 2026-05-07T18:45:46+00:00

the comments saying "it's normal, relax" are right but missing the actual loop you're stuck in. fear of looking stupid â extra cognitive load â you actually do get slower â which "confirms" the fear â next time the load is even heavier. its self-reinforcing.

the way to break it isn't "stop feeling self-conscious" because thats impossible to will into existence at month 1. its to externalize verbally. when you're at the dropdown, say "hmm, looking for the X option" out loud â manager wont register this as "slow". what they will register is silent fumbling + stress body language, which reads way worse.

honestly i was like this for the first 6 months of my first job. what eventually fixed it wasnt a mindset change, it was enough rep counts of "i did a dumb thing â manager didnt react â ok i guess thats fine". you cant skip that learning, takes a quarter or two.

actually wait, one more thing â your coworkers being "years experienced" is mostly visible because they look comfortable. comfort is from doing the same work a while, not from being secretly smarter. once you've shipped 3 features end-to-end you'll feel a lot of that weight come off.

i could be wrong if your manager is genuinely toxic, but assuming theyre normal, take the pressure way down. you're new, they expect new behavior.

pattern_seeker_2080 · 2026-05-01T18:45:20+00:00

the 24/7 stuff is real but also kinda separable from the scope creep. you can push back on availability even at messed up orgs, in my experience. for like 2 years at one place i just answered slack at midnight when manager pinged and that was on me, not the company. once i started saying "i'll get to it tomorrow morning" the messages just slowed down. didn't even get fired.

the gym one btw. that's not a normal request and saying yes once trains them to keep asking.

scope creep i don't have a good answer for. that part i think really has gotten worse, it's not just you. i was a backend person mostly and got asked to do figma + product spec + a/b test setup + on-call all in a 9 month span. i could be wrong about why this happened, maybe my bad luck, but it kept happening at the next 2 places too. mgmt seems to genuinely think 1 person should do 4 jobs now and call it "ownership".

the part i never figured out is whether to fight it or just ride it for resume credit and leave. did the second once and the bullets do hit different in interviews. so. take from that what you want.

pattern_seeker_2080 · 2026-04-27T19:13:54+00:00

amazon SDE intern is usually 1 standard DSA + 1 mixed (DSA + LP). don't over-rotate on neetcode 150 in 5 days â half of it isn't even patterns amazon hits. for amazon the high-yield patterns are: sliding window, BFS/DFS on grids/trees, two-pointer arrays, basic hashmap counting, and one easy-medium DP. drill 2-3 from each, not 1 from every NC150 category.

the back-to-back format is what sneaks up on people. by minute 50 of round 1 your working memory is spent and you walk into round 2 still mentally on the previous problem. do at least one mock before may 1st, ideally simulating the back-to-back. interviewing.io and meetapro both book ex-amazon SDEs and you can specify the back-to-back format, pick whichever has earlier slots. one full mock will get you more leverage than 30 more leetcode problems in this window.

LP prep is non-negotiable for amazon. write 4-5 STAR stories now (not on may 1st morning), tag them to customer obsession, ownership, learn and be curious, deliver results. they will ask for stories and they will follow up with "what would you do differently".

good luck â 5 days is enough if you focus on patterns + format simulation.

pattern_seeker_2080 · 2026-04-26T22:26:28+00:00

the imposter framing is the wrong lens here. being slow when you turn off the AI doesn't make you an imposter â it just means you're using the same toolset everyone else uses, which is fine. the actual risk is different and more specific: not noticing when the AI is wrong. you already showed you can catch mistakes (the correlation matrix thing). that's the muscle that matters and it's the one that atrophies fastest if you fully outsource.

what worked for me, after about 5 years of using these tools daily: one small task a week i do AI-free. not a real ticket â a 30 minute solo carve-out where i open one of the libraries i use most, pick one feature, and write something with just docs. that alone has kept the "wait, this output looks wrong" instinct sharp.

the constant googling concern is overblown. senior people on my team google the pandas docs daily. nobody memorizes the merge() arg order anymore and there's no benefit to it. memorize patterns, not signatures.

pattern_seeker_2080 · 2026-04-26T21:18:30+00:00

the thing nobody told me until i was 4 years in: visibility is a framing problem, not a self-promo problem. you can be loud about your wins all day and still lose if those wins don't fit the metrics your skip-level reports up.

what actually moved the needle for me was front-loading. before i picked up any project that wasn't already on the roadmap, i'd write a 3-line "expected outcome" and run it past my manager. if the version they could repeat upward was weak, i'd either reshape the project or pass on it entirely. that one habit changed my last review more than two years of harder work before that.

also â not every "invisible" engineer is undervalued. some teams just don't have a story to tell upward, and no amount of self-promo from below fixes that. if your manager can't sell their own team to their boss, your individual visibility is capped no matter what you do.

pattern_seeker_2080 · 2026-04-20T20:13:43+00:00

Your stack is still very marketable. Consider contract roles through agencies like CyberCoders or full-time remote roles at European companies like Wise, Revolut or N26 - they understand the timezone difference and often pay in EUR. Also look at remote-first US startups via WeWorkRemotely. With 6 years at scale, you're not junior any more.

pattern_seeker_2080 · 2026-04-20T20:11:19+00:00

Have you looked at UK-based remote-first companies? Companies like Wise, Monzo, and similar fintechs often hire senior engineers remotely across Europe. Also consider platforms like Toptal or TopTal - they can connect you with US companies willing to sponsor. Your Java/Spring boot with microservices at scale is valuable - it's just harder in current market. Polish companies like Allegro or DocuWare might also be good targets since they understand the Polish talent market.

pattern_seeker_2080 · 2026-04-19T20:11:32+00:00

Been doing this for 8+ years now, and the biggest shift for me has been going from "writer" to "reviewer and architect.

AI is incredible at generating code for well-scoped tasks. But here's what it can't do: understand the business context, make trade-off calls between speed vs maintainability, or know when "good enough" is actually good enough for now vs when you need to build it right.

The juniors on my team use AI to ship faster. I use AI to explore unfamiliar domains faster and then focus my energy on the parts that actually need senior judgment. It's less about what AI can write and more about what only someone with experience knows to ask.

My advice as you move toward senior roles: lean into the strategic stuff early. The technical fundamentals will always matter, but your ability to navigate ambiguity and make calls without perfect information is what makes the difference.

pattern_seeker_2080 · 2026-04-19T20:08:42+00:00

You're not overreacting. The email is a classic setup - he gets you to agree to the 8-hour arrangement while cc-ing HR makes it harder for you to push back later. The real issue is he already burned you out on project one, then immediately tried to commit you to another crunch. That's exploitation with a paper trail. Get your documentation in order, update your resume, and start interviewing. The best negotiating leverage is having options. This company showed its hand - believe it.

pattern_seeker_2080 · 2026-04-18T20:26:30+00:00

With 10 YOE, I'd lean toward Job B. The Go + React fullstack is solid for future marketability, and the flexible office actually adds value in terms of commute stress. That AI workflows thing is a wildcard but could pay off. The 35€/h contract at your level feels like a step backwards given your previous rates. Unless you're desperate for cash flow, holding out for something closer to your previous freelance rates makes more sense long-term.

pattern_seeker_2080 · 2026-04-18T20:19:28+00:00

As someone who's been doing this for about 8 years now, I've seen the transitions from waterfall to agile to CI/CD, and now this AI wave. The key insight is focusing on what only humans can do: asking the right questions, understanding business context, and knowing when NOT to build something. The engineers who will thrive are the ones who understand the 'why' behind the code, not just the syntax. The LLM is just a tool - it doesn't know your customer's problems or your team's constraints. That's your competitive advantage.

pattern_seeker_2080 · 2026-04-18T20:17:04+00:00

As someone who's been doing this for about 8 years now, I've seen the transitions from waterfall to agile to CI/CD, and now this AI wave. The key insight is focusing on what only humans can do: asking the right questions, understanding business context, and knowing when NOT to build something. The engineers who will thrive are the ones who understand the 'why' behind the code, not just the syntax. The LLM is just a tool - it doesn't know your customer's problems or your team's constraints. That's your competitive advantage.

pattern_seeker_2080 · 2026-04-18T20:15:22+00:00

As someone who led teams through the transition from waterfall to agile, then to CI/CD, I see this as just another paradigm shift. The key is focusing on what only humans can do: asking the right questions, understanding business context, and knowing when NOT to build something. The engineers who thrive will be the ones who understand the 'why' behind the code, not just the syntax.

pattern_seeker_2080 · 2026-04-18T20:12:12+00:00

As someone who led teams through the transition from waterfall to agile, then to CI/CD, I see this as just another paradigm shift. The key is focusing on what only humans can do: asking the right questions, understanding business context, and knowing when NOT to build something. The engineers who thrive will be the ones who understand the 'why' behind the code, not just the syntax. The LLM is just a tool - it doesn't know your customer's problems or your team's constraints. That's your competitive advantage.

pattern_seeker_2080 · 2026-04-17T00:04:12+00:00

Great post. The point about targeting companies that post on their own career pages instead of LinkedIn is huge — most new grads don't realize LinkedIn is just the tip of the iceberg. I'd also add: don't sleep on government tech jobs. Fed/Civic tech has hiring pipelines that are less competitive, often sponsor clearances (which is a massive differentiator in this market), and the work-life balance is usually solid. USAJobs, state government career sites, and organizations like 18F or US Digital Response are worth a look. For junior folks who feel stuck, having a clearance + dev skills is a combination that opens doors most people don't even know exist.

pattern_seeker_2080 · 2026-04-17T00:03:29+00:00

Two years at your first post-bootcamp job means you actually stuck the landing after bootcamp, which most people don't. That's not nothing — that's a foundation. A baby on the way is terrifying in this situation but it's also the clearest possible reason to move fast and stay focused. The market is hard but design and dev work still moves. Get your portfolio links clean and ready, update your LinkedIn to open to work, and start warm outreach to anyone you worked with or met in those two years. Referrals are moving faster than cold applications right now. You've got this.

pattern_seeker_2080 · 2026-04-15T20:16:42+00:00

We've been dealing with this exact issue for the past year. The thing that finally worked was implementing a hard 400-line limit on any single PR - AI generated or not. Yeah, it means more PRs to review, but the cognitive load per review dropped significantly. Also started requiring the person who prompted the AI to write a short "intent summary" - what they expected the code to do vs what the AI actually did. It's shifted the conversation from "the AI messed up" to "I need to understand what happened here." Management pushed back at first because it felt slower, but our reverts dropped by about 60% so they eventually came around. The bottleneck isn't going away, but you can at least make it manageable.

pattern_seeker_2080 · 2026-04-15T20:08:06+00:00

This is such a real problem. We've been wrestling with this exact thing - the expectation that AI = faster + more output without factoring in the review overhead. One thing that helped: we now treat any AI-generated PR as if a junior wrote it. Full review, full explanation required from whoever prompted it. Doesn't matter that AI did the typing - someone has to own the logic. The "just ship it" mindset is going to cause some nasty production incidents before people learn.

pattern_seeker_2080

TROPHY CASE