Active in 3 subreddits · 100 items · first seen 2 May 2026, last seen 24 Jun 2026. Most active in r/datascience and around 09:00 UTC.
Based on 100 items. Data may lag slightly behind Reddit.
* Hour, weekday, over-time and common-word patterns are based on a recent sample of activity, so they may not cover the full history. The item count and top subreddits cover everything we have.
Coverage may be incomplete. Search Reddit directly for the most recent activity ↗
Note: searching Reddit directly will NOT show deleted or removed posts/comments.
honestly a lot of these genai roles are going to quietly rediscover why your skillset exists. the demos all work. the thing that kills them in quarter two isn't the model, it's that nobody owns the messy edge of the real inputs. a source quietly changes a field, a timestamp gets …
yellowflexyflyer nailed the real risk, it's the pipeline not the work. one thing to add from the other side of the table, i'm the kind of person who actually buys small AI shops' services, and the brand is doing way more of your selling right now than it feels like from the insid…
yeah that's the part that surprised me too, the skill transfers but the life version is way harder. at work you usually have something to point at, a number that isn't moving or a deadline you keep blowing. with the personal stuff there's no clean signal telling you it's over, so…
one thing worth adding, almost everything here tests that the code gives the same answer on a fixed reference dataset. that catches env and compiler drift, which is real, especially with fortran and blas. but it says nothing about the inputs changing. the stuff that actually bit…
the most reliable signal i've found isn't how smart you feel in the room, it's whether you can kill your own work. juniors prove themselves by shipping something and defending it. the people i trust most will tell you the thing they spent two months on isn't worth finishing. if …
The classical stats stuff isn't going away, it's getting repriced. Once everyone's shipping RAG and agents, the scarce person becomes the one who can actually tell whether any of it works, and that's an eval and measurement problem, which is exactly your background. Most teams bo…
honestly from the hiring side the label matters way less than you'd think. most of what i'm actually paying for isn't the next shiny model, it's someone who notices when the thing that's been running fine for a year quietly starts drifting and just fixes it. that's the muscle you…
most of these answers are about problems inside a project, but for me the bigger one sits upstream, it's deciding which requests should even become a project. a huge chunk of what hits a data team is ad hoc questions and dashboard asks that feel urgent but aren't tied to a decisi…
yeah if you actually like the budget fights then up is the right ladder for you, that's kind of the whole tell. the thing that compounded most for me at that level wasn't the modeling, it was getting good at saying no. a huge chunk of what hits a data leader's desk is someone wan…
the part that doesn't get said enough is that director to vp or c-suite isn't a bigger version of the same job, it's a different job. as a director you still get judged on whether the data and the models actually work. one level up you get judged on p&l and on whether the other e…
the thing i'd add from the hiring side is you're not really reacting to the webcam, you're reacting to the judgment behind it. you said you figured the camera stuff was coachable, but what you're actually seeing is that they decided a paid interview wasn't worth sitting at a desk…
the frame-around-decisions advice is right, but honestly nobody gets pulled into transformation work off a cert. the people who land those roles already took the cross-team thing everyone else was avoiding and got it unstuck. your comms background helps less for the strategy theo…
the worst ones for me were never really about the hours, it was that nobody could tell me what "done" actually looked like, so every day felt like effort with no way to score whether i was getting closer. what helped was forcing that into writing early, even a mediocre definition…
the part i'd push on is calling it "lack of domain knowledge." that's honestly the cheap part, you pick up enough healthcare context in a few months on the job. the scarce thing is having shipped something where being wrong had real consequences, and you already have that from fi…
the internet comparison holds up better than people think, but what it actually changed was who inside the firm got commoditized, not whether consulting survived. once information got cheap, the person whose whole value was gathering it stopped being worth much, and the money pil…
The trap is that clustering metrics will happily answer the wrong question. Silhouette can tell you GMM fits the feature space better than K-Means while both produce player comps a scout would laugh at, because nothing in those scores knows what similar actually means in your dom…
Been on the staffing side of this a lot in financial services. Nobody on that banking project will remember that you rolled off. What sticks is the unexplained version, where the project was scoped wrong but the only visible fact is that you left. So before you go, put one short …
The part nobody warns you about is that what you had at year 17 wasn't context, it was being known. Your judgment showed up in the room before you did, so you never had to prove anything. Consulting resets that to zero every time and no first weeks template gives it back. What m…
the thing i'd weight heavier than the 20% is the stagnant stack. a great manager and flexible pto are real but they're invisible the moment you're job hunting. i've screened a lot of DS resumes and i can't see that your boss was kind or that you took your vacation, i just see wha…
usually secondhand. someone who was actually in the room mentions it after, like the cfo brought up your retention number in board prep. or it shows up downstream, your exact framing or metric ends up in a deck you didn't build, or an exec repeats your own phrasing back to you we…
yeah the counterfactual feedback is the part that quietly wrecks you. you only ever get labels on what you let through, the stuff you blocked never gets a ground truth, so the model is grading its own homework. we ended up forcing a tiny random slice past the rules unscored just …
yeah you're basically describing it. agile is the software version but the core idea isn't tech specific, you show work in small chunks and get a thumbs up before building the next chunk. in consulting people just call it phasing or staging the work. same move, keeps you from pol…
the ones that blow up early at least get noticed. the quieter killer in my experience is the project that technically succeeds. the model works, people even use it, and somehow nothing downstream changes because no actual decision was ever attached to the output. i ended up aski…
honestly the thing that separates this from normal DS isnt the algorithms, it's two domain truths. your labels are garbage, you only ever see the fraud you already caught, so your training data is biased toward what you're already good at catching and blind to the rest. and your …
one thing that makes it land better, hand it over like you're asking not presenting. something like "before we build this out, is this the right direction" lets him redirect without feeling like he's trashing finished work, which is the part he actually likes doing. if it looks p…
honestly the sign-off advice works with real clients but it won't save you here, the thing that keeps changing is his brain not the scope. approving a format costs him nothing, he didn't actually think about it until 3 days of work was sitting in front of him. so put something u…
this isn't really a strategy problem, it's a who-controls-the-checkbook problem. you can obviously see the fix, you've probably mapped it out a dozen times. but you don't own the capital call and the people who do have quietly decided to harvest the firm instead of reinvest in it…
yeah that's the catch, nobody says out loud that they ignored the analysis. so i never frame it as "did you use the data," i ask whether it changed their direction, confirmed it, or didn't factor. "confirmed it" is usually the polite version of ignored, and the real tell is when …
the part that jumps out is you said it's not one thing, it's everything. that's actually your answer. when it's one skill you coach it. when it's attention to detail and ownership and communication and structured thinking all at once, that's not a development plan, it's a fit pro…
the prepare vs wing it thing is the actual trap, and what worked for me was preparing the structure, not the words. if you script real sentences then any deviation feels like a mistake and you freeze trying to find your place again. just lock in the 3 things you want them to walk…
i think the part that gets missed is it's not just the switching, it's that none of those threads actually close. a fire drill at least ends, it resolves and leaves your head. a normal day you touch fifteen things and every one of them is still half-open when you log off, so your…
the thing nobody's saying here is that "upward mobility" doesn't have to mean climbing the ds ladder. from the hiring side what actually looks bad is a flat title with no story behind it, not the absence of promotions. you're describing the exact profile that makes a great pm / s…
most of the answers here are about the stats, drop vs impute, which matters, but you asked about presenting and that's a different question. how you handle missing data in a deck depends way more on who's in the room than on the method. technical audience, show the missingness a…
the stack ranking fear is the right instinct but it's not really about which company, it's about whether the seat owns something visible. the people who get ranked out are almost always the ones doing fungible analysis nobody can attach a name to. own a model or a product surface…
from the manager side, reputation lags reality by like 6-12 months, and a visible bug turns into a sticky mental tag way out of proportion to what it actually cost. the PO isn't tracking your defect rate, they're remembering one bad feeling, and you can't argue someone out of a f…
the part that gets missed in these threads is that imbalance gets treated as a training-time decision, when in prod the thing that actually bites is that the positive rate and the cost ratio don't sit still. ran fraud models for years and the base rate would move week to week as …
having sat on the manager side of this for a while, both camps here are half right. the reason 'i automated it' backfires usually isn't the automation, it's that you reported a capacity gain without reframing your role. when someone tells leadership 'i cut this to half the time,'…
the 'swe without the pay' read is the part i'd push back on, but use it as a filter instead of a worry. on the hiring side, where a company sets the SRE band tells you exactly how it thinks about reliability. pay it below swe and they see keeping prod alive as a cost to minimize.…
two different things are getting mixed together in that job description. part of it is wishlist inflation, a hiring manager and a recruiter each pile on their must-haves and nobody trims the list, so the posted req asks for a mid-level engineer because that's the fantasy hire. yo…
speaking from the other side of the table, the part that should take some pressure off: at 6 YOE the interview almost never comes down to whether you prepped the optimal answer. it comes down to whether you can think clearly in a live conversation, and exhaustion is the one thing…
having sat on the management side of this for a while, the thing that separates the legit version of these from the weaponized version is almost always whether the person saying it can actually evaluate the work. "low hanging fruit" and "take this offline" are normal prioritizati…
the delay by itself I wouldn't panic over, comp cycles slip for boring reasons too, budget reforecast, a comp band review, sometimes M&A diligence freezes everything. the part that would worry me is the "couldn't or wouldn't explain it." a manager who knows the reason is benign u…
12 years on the hiring and firing side of financial services. Most of the indicators here are real, but they're all visible after the planning has already started. A few earlier signals that come from inside the planning room: Finance starts asking for "cost per employee" or "re…
12 years in financial services. The reports about cleanliness here are mostly true, but for an underrated reason: it's regulation, not industry. SOX, SR 11-7, model governance, OCC exam prep, all of it forces the org to keep definitions stable and auditable. The fight already hap…
12 years writing python pipelines in financial services and the single biggest thing nobody tells you upfront: the code that survives isn't the code with the best architecture, it's the code written for the analyst who's going to be debugging it at 11pm on a Tuesday six months fr…
The technical side will work fine. The thing nobody warns you about is what gets lost organizationally. Twelve years in fintech, I've watched this exact handoff happen probably 8-10 times. The pattern: DS owns the end-to-end app, business gives DS the credit for "the tool." D…
The hiring-side version of this matches what you're seeing. Twelve years in fintech and the funnel has restructured around what AI output you can't trust without senior eyes on it. What's shifted: the people we hire most aggressively now aren't generators, they're reviewers. …
That progression is the giveaway. Once you've gone direct to PMs and designers a few times, you've effectively rerouted information flow around your manager. It looks unintentional but it's structural, the people making decisions start coming to you first because you're closer to…
12 years across financial services and this exact problem is what most of those years felt like. The thing that helped me land the platform decision wasn't winning the SDLC argument, it was reframing the request. Instead of asking IT for an exception, give them what they actu…
This is the most common structural complaint I see from analysts, and it's real. The "we'll tell you what we need" pattern means leadership has framed your function as a service desk, not a partner. Asking nicely doesn't change that. You change it by changing how you show up. …
12 years hiring side in financial services, the patterns that show up over and over: Mid-levels solve the problem in the ticket, seniors solve the problem behind the ticket. Junior PR fixes the bug as described. Senior PR fixes the bug and asks why this code path existed in t…
Fair question, you don't measure it perfectly. You measure it well enough to defend the team in a budget meeting. Three lightweight things worked for us. Quarterly stakeholder retro. Pull the 5-10 major decisions the business made that quarter and ask each owner "did the anal…
Hiring side, 12 plus years in financial services. The honest answer is the layoffs matter less than the headcount math implies, but in a way that's worse for some candidates and better for others. A Meta DS who spent the last four years doing analytics on a single product sur…
Twelve plus years on the hiring side in financial services, all three observations match what we're seeing in our pipeline. The salary compression is structural, not cyclical. The generalist DS role that paid 180-220K from 2019 to 2022 is being unbundled into two narrower lan…
Twelve plus years on the hiring side in financial services, the million-dollar-band signal is louder than the announcement reads at first glance. The math companies are doing right now isn't "fewer engineers because AI is productive." It's "fewer engineers because AI is productiv…
Twelve plus years running data and ML teams in financial services, this pattern is showing up in every shop right now and it's worth being precise about what's actually happening. The staff engineer who used to whiteboard for hours hasn't gotten dumber. He's gotten quieter. Somew…
Hiring-side honest take from twelve plus years running data and ML teams: at the SWE 2 level, in interviews I genuinely cannot reliably tell a senior from a senior+LLM anymore. That is the underlying force pushing the bar up. It is not about whether to use LLMs, it is that the fl…
Twelve plus years on the hiring side, mostly in financial services data and ML. The take-homes ballooned for a reason that isn't really about your skill. A ten hour assignment isn't measuring whether you can build the pipeline. It's three things at once: a self-selection filter …
Twelve plus years running data and ML teams in financial services, this pattern was the single thing that changed how I scoped projects. The structural lever is being in the room when the question gets framed, not in the room when results get presented. Most "ignored" insights a…
Twelve plus years hiring and managing engineering teams on the fintech side. OP's edit gets close but inverts the actual mechanism. Companies are not replacing seniors with juniors-plus-AI. They are keeping the seniors and cutting juniors because each senior now absorbs the work …
Twelve plus years building data pipelines in financial services, this exact scenario lands about twice a year. The part nobody wants to hear up front: AI on top of data chaos fails the same way every time. Model produces output that looks plausible because LLMs are excellent at c…
your follow-up to super-pretty-kitty has the actual diagnosis in it: workload is fine, boredom is the structural problem. that's a different prescription than burnout-from-overwork and most of this thread is answering the wrong question. 8 years at one non-tech company on full-st…
hiring-side angle that surfaces less often than it should: at the final-round stage, the variable being optimized usually isn't candidate performance, it's pipeline composition that cycle. you can deliver a strong loop and lose to a candidate who had a referrer advocating harder …
Confirming the same pattern from the hiring side in fintech. Through 2024 and most of 2025 our recs were sitting open for 5-6 months at the senior MLE level because we were running ourselves through a freeze, and what looked like a candidate scarcity problem from the outside was …
RandomThoughtsHere92 hit the structural reason and it's worth pulling on. A lot of pod-style hedge funds (and increasingly the bigger investment firms following suit) run continuous talent benchmarking pipelines that look identical to a hiring process from the candidate side. The…
The pattern OP describes is real but it's environment-shaped, not talent-shaped. FAANG hires for a specific failure mode (consistently strong fundamentals so any person can swap into any seat) because the surrounding infrastructure is mature enough that what differentiates senior…
Fair pushback and the agile-at-scale piece is well-said. Coordination tax across 6-8 dependent teams in 2-3 week sprints is the failure mode that scaled-agile frameworks pretend to solve and don't. The consolidation move you describe is the actual unit-of-work fix, the SOX/FINRA …
Don't fabricate numbers. That breaks the second a hiring manager asks one follow-up and you pause for a beat. But you have more real numbers available than you think, you just don't have them in front of you. Three recovery exercises that have worked for people I've coached throu…
From hiring side this is in the normal-bad band for 2025-26 Toronto senior backend, not the "something is wrong with you" territory it feels like at month four. 3% interview rate at 11 YOE is what the market is producing right now for the cell you targeted. Toronto hybrid-only fi…
LikesAlgae's read on the resume is the right one and it's the part that hurts to hear. From hiring side I see 200+ frontend resumes per backfill role at this level, and 5 YOE frontend with mostly feature-shipping bullet points reads as 1 year repeated 5 times. Not because you're …
Hiring manager voice from the other side, 12yr in fintech. The structural read on your situation: your tech lead left, your manager has no plan, and you're the catch-fall they're betting will absorb the ambiguity until they backfill or until you burn out and provide them a clean …
Infrastructure-vendor cuts hit downstream pricing differently than product-company cuts. Fintech runs through Cloudflare's edge for ddos, waf, dns. When an edge vendor cuts senior infra engineers and tries to backfill with interns plus AI, customer-side incident response timeline…
Hiring side, 12 years building ML at a fintech, helped two senior PMs close exactly this gap last year. None of them did Andrew Ng or any general AI course because it doesn't transfer to defending a model choice in a real meeting. What worked, in order of leverage: Build an eval…
Fintech-side perspective on what the bundle actually signals. "Scrap agile" in regulated financial services almost never means dropping coordination. It usually means moving control of release cadence and change approval up a level, which is what regulators have been quietly push…
Most useful framing for a junior here is that your manager has stopped doing scope work. The "architecture doc that changes daily" isn't documentation overload, it's a manager who has outsourced thinking to a prompt that produces plausible artifacts but doesn't commit to anything…
From the F500 hiring side, the part most comments miss is what's actually being signaled here. CFO comp at MSFT is heavy stock and "headcount down" is the cleanest narrative line to push efficiency ratios on the next earnings call. $101B net income on 228k people doesn't read the…
Senior leader, 12yr in fintech. The silo culture you're hitting in big finance isn't broken process, it's compliance posture. Cloud team owns AWS because the bank carved that out as a separately-audited risk surface. You won't change it. That's not a 'this place is bad' signal, t…
Hiring manager side, 12yr fintech. The shape isn't process drift, it's risk-distribution. Every additional round adds one more stakeholder whose name goes on the hire. Eight rounds means eight people who 'approved' the candidate. If the hire underperforms, blame is diffused, not …
Hiring side, 12 years building DS loops: the 24.9 number isn't process bloat in isolation, it's risk-budget allocation that crystallizes when nobody owns the loop end-to-end. A 4-round loop costs about 15 hours of interviewer time across team. At F500 the budget exists, what'…
From 12 years on the management side in fintech: the cleanest signal of whether "AI cuts" are real productivity vs cover story is what happens to the saved budget. Real productivity story, the headcount budget gets reinvested into adjacent revenue or risk projects. Engineering th…
frogchris is right and the harder version of his point is that fintech splits cleanly into two markets right now and the gap is widening. Companies extending the rails (Visa, Stripe, Apple Pay, Adyen) are still hiring senior infra and risk talent because their growth is operatio…
7 YOE MSCS in financial services plus an "AI first team" rebrand right after layoffs is the most dangerous combination in tech right now. Not because AI is bad, but because the leadership move that gets you to "AI first" is the same one that defunds incident review, code review, …
12 years in financial services ML, managed teams with people exactly like the architect you described. The trait is mostly downstream of two operational habits, not personality. First: routinely ask dumb questions in meetings where juniors are present. Even questions you know th…
Take it. From the F500 hiring side, an MLE loop is structurally different from DS even when day-to-day work overlaps. Expect more system design rounds (model serving, batch vs online inference, latency/throughput tradeoffs) plus probable rollout and eval questions (A/B framework,…
12yr fintech hiring manager. couple things from the other side of the table: the 1-year gap isn't the problem people make it out to be at 6 YOE. but how it shows up on the resume changes how the gap reads. "Independent product (100 DAU, $300/mo)" with caregiving context in th…
F500 fintech hiring manager 12yrs in. Both styles measure something narrow and both have known failure modes. living\_david\_aloca has the structural reason FAANG goes generic right, but the failure mode of each side is worth naming. FAANG IQ-style overweights stats theory be…
\+1 to the company-size framing. F500 fintech here, your read matches mine. The thing your friend's startup gets that big-company senior engineers don't is AI failure tolerance. In a 5-person company shipping fast, an agent that's right 80% of the time saves time, and the 20% get…
Hiring side: this format gets the right things (judgment, debugging when AI is wrong, communication) but it's harder than LC to keep calibrated. With LC there's a shared rubric, even if it's a flawed one. With "build something with AI and explain it," the bar drifts session to se…
Hiring manager side: yes, but the volume is brutal. F500 fintech, our DS roles get 400+ applicants in the first 48 hours. By the time most cold apps reach me, the recruiter has filtered to 8-12 from the first 100 or so. Apply after that and the math is against you, not the role b…
Still very much a thing in fintech and anywhere model output gets audited. Credit decisioning, fraud, AML, capital reserve modeling. Explainability and reproducibility make a black-box LLM call a non-starter for the actual decision layer. Every model needs an MRM write-up and "we…
Hiring manager from the F500 side: this describes most of my best hires from the last decade. The pattern that gets people promoted at companies that are not FAANG is exactly this. Translating ambiguity into a question someone can act on, picking the dumbest model that solves the…
Hiring manager side, this lines up with what I have watched on three teams over the last 18 months. The cost of deleting the bottom rung does not show up on a productivity dashboard. It shows up 14 to 18 months later, when the senior who would have organically grown out of that r…
Senior management lens here, 12 years on the management side of fintech. The supply-side argument is right but the 2-year timeline is optimistic. Companies aren't 'bracing' for the shitshow, they're externalizing the cost: offshore contractors, MSPs, and AI tooling that papers ov…
Hiring manager perspective on this. Google DS Research is one of the more academic DS roles in tech, the bar there reflects a research-heavy mandate that most industry DS roles don't have. Writing MLE equations on a whiteboard isn't a typical industry DS expectation. The typical …
Hiring manager side, 12 years in financial services. Almost never malice. Usually the loop is technically still open (waiting on the chosen candidate to accept, headcount approval frozen, hiring committee debating between two finalists), and there is no internal process for telli…
Hiring manager, 12 years in financial services ML. This is the core problem and very few companies are actually planning for it. The "AI augments seniors" framing is true and also a comfortable trap, because it lets leadership defer the question of how seniors get made. The s…
Hiring manager from 12yr fintech management. The recruiter asked the wrong question but you also gave the wrong answer. They're not measuring tool use, they're filtering for whether you'll friction-block their AI rollout. "I like writing code" reads as "I'll resist the new workfl…
Hiring manager perspective from 12yr fintech management. The missing middle is structural, not random. Mid-tier roles ($80-110K seniors) made sense when the budget included 12-18 months of ramp-up time. When budgets get tight, companies stop funding ramp. So they hire senior (pro…
Senior of 12 years, manage teams that hire seniors. The skills your AI listed are real but they're table stakes. What actually saves people in your situation is operating like a senior, not coding like one. Show up to ambiguous meetings with a 1-paragraph framing of the problem …
Fellow DS hiring manager, 12 years in fintech. The cheating section matches what we're seeing word for word. Crotch-glancing is real. We've also started watching for inconsistent typing rhythm. Someone who can solve a leetcode-medium in four minutes but spends thirty seconds typi…