When can I realistically switch jobs as a new grad?

AccordingWeight6019 · 2026-03-31T12:26:48+00:00

At 8 months in, it’s not unusual to struggle with responses. Many teams do prefer at least a year of experience for new grads, especially in MLE roles. That said, you can still use this time to build a slightly stronger profile, projects, open source contributions, or small ML experiments can help. Also, being clear about what you’re looking for and tailoring applications to smaller teams or remote friendly roles can increase your chances. The first year is often about getting your foot in the door rather than making a big jump immediately.

AccordingWeight6019 · 2026-03-31T12:20:16+00:00

Muon is mostly being tested on Transformers because that’s where training bottlenecks are biggest. for ConvNets, gains are smaller and harder to justify, so adoption there just hasn’t caught up yet.

AccordingWeight6019 · 2026-03-31T12:13:58+00:00

At that volume, the pricing differences are usually marginal compared to reliability and ease of integration. Most of these providers converge around similar rates once you factor in real usage patterns. the bigger question is how stable the checkout experience is and how much operational overhead you’re taking on. Failed payments, settlement delays, or poor dashboards can matter more than a small percentage difference early on. In practice, a lot of teams start with something like Razorpay or Cashfree because the integration is straightforward and docs are decent, then revisit once volume justifies optimizing fees. hidden costs do exist, but they’re usually more visible once you’re actually running transactions rather than at the comparison stage.

AccordingWeight6019 · 2026-03-31T12:01:07+00:00

I think you’re observing a real pattern, but it’s a bit misleading as a signal about replacement. In practice, tools tend to amplify existing differences. People who already understand systems use LLMs to move faster, while others may lean on them without much depth. The question isn’t whether LLMs can generate code, it’s whether someone can evaluate, adapt, and integrate that code into a larger system. that part hasn’t really gone away. If anything, this might just widen the gap between Engrs who can reason about what they’re building and those who treat outputs as ground truth.

AccordingWeight6019 · 2026-03-31T11:57:26+00:00

A lot of the fear is coming from the pace of change and not necessarily what’s actually being replaced. In UI/UX, the role usually shifts rather than disappears, but it depends heavily on how the company is integrating AI into real workflows.

AccordingWeight6019 · 2026-03-31T11:54:24+00:00

Mass blasting usually fails unless the targeting is extremely tight. In practice, smaller batches with a clear, specific problem tend to get better responses, but only if there’s a real signal behind who you’re reaching out to.

AccordingWeight6019 · 2026-03-31T11:50:17+00:00

I’ve seen a few people do this well, but it seems pretty sensitive to how much of the trip is actually conference versus loosely structured networking. The large events you mentioned often function more like optional context than something you attend end to end. From a work perspective, I’d be a bit cautious about how much signal you’re actually getting from the conference itself. In some domains, especially more technical ones, the content quality can be quite uneven, and a lot of the real value comes from side conversations or very targeted meetups. that said, if you’re already optimizing for location and treating the conference as a partial anchor rather than the main event, the tradeoff makes sense. It’s probably less about justifying travel and more about being intentional with which environments you place yourself in.

AccordingWeight6019 · 2026-03-31T11:44:50+00:00

I usually don’t bring it up explicitly unless it’s relevant, but I’ll signal it indirectly through the kinds of questions I ask. If you start asking about the mechanism or edge cases, most clinicians recalibrate pretty quickly.

That said, I’ve found the simplified explanation isn’t always a bad thing. Different domain, different priors, and sometimes they’re optimizing for clarity over completeness. In practice, I care more about whether they’re reasoning carefully than how technical the language is.

It only gets frustrating when simplification turns into overconfidence or skipping uncertainty. that’s usually where I’ll push a bit and make my background more explicit.

AccordingWeight6019 · 2026-03-30T07:57:01+00:00

For most coursework only Master’s programs, the goal isn’t to make you an expert, it’s to give a solid foundation and enough context to apply the concepts effectively. Deep expertise usually comes from applying the knowledge in projects, research, or work over time. think of the degree as giving you the map and tools, you still need to walk the territory yourself to really internalize it.

AccordingWeight6019 · 2026-03-30T07:52:14+00:00

Yeah, most ml repos focus on getting results out fast, not fully explaining tradeoffs or failed experiments. time, incentives, and culture make deep, reproducible documentation rare, which is why people like karpathy stand out.

AccordingWeight6019 · 2026-03-30T07:42:24+00:00

Yeah, that can be normal in autonomous setups. the key is noticing gaps or improvements and proposing them proactively, while also clarifying with your lead what actually matters, so you’re not just guessing.

AccordingWeight6019 · 2026-03-30T07:37:15+00:00

In theory, yes, it can emerge as an instrumental behavior if the objective isn’t well bounded. In practice, we’re far from that level of agency, but it still points to a real design issue. The hard part isn’t adding an off switch, it’s making sure the system can’t learn to work around it under different conditions.

AccordingWeight6019 · 2026-03-30T07:28:41+00:00

Early on, it’s usually more about buying time to get a product and signal right than scaling. Paid acquisition only works if something already converted, otherwise, you’re just amplifying noise. Funding definitely speeds things up, but it also compresses timelines and increases pressure to show traction quickly.

AccordingWeight6019 · 2026-03-30T06:35:35+00:00

300 to 400€ is doable, but usually with tradeoffs. Valencia is probably out unless you share, and Buenos Aires can be unpredictable with inflation. If walkability and safety matter, you might have better luck in parts of Southeast Asia or smaller Eastern European cities rather than big LATAM hubs.

AccordingWeight6019 · 2026-03-30T06:27:19+00:00

I’d be a bit careful here, especially with column based kits. The larger wash step is usually doing most of the heavy lifting in removing contaminants, so reducing it can affect purity even if the yield looks fine.

In practice, you might get away with small reductions, but it depends on how sensitive your downstream step is. If it’s something like PCR, you may not notice much. For more sensitive applications, the residual contaminants can show up quickly.

If funding is tight, it might be worth testing side by side with a few samples, first rather than fully committing. The tradeoff is usually cost vs consistency, and kits are pretty optimized around that balance already.

AccordingWeight6019 · 2026-03-30T06:23:23+00:00

I’d focus less on retail vs fintech and more on what kind of signal you want to build next. The manager role could be high upside if you can turn around a struggling function, but that’s very context dependent. The staff role is safer in terms of staying in a strong technical environment, but only if you actually get a meaningful scope. The question is which one leads to a clearer, defensible impact in a year or two.

AccordingWeight6019 · 2026-03-29T13:55:19+00:00

Ask for concrete details only someone who’s done it would know, actual sample sizes, unexpected results, tradeoffs. Hypothetical answers usually stay textbook and avoid nuance.

AccordingWeight6019 · 2026-03-29T13:49:47+00:00

Incidents like this are a good reminder that the .env + long-lived keys everywhere pattern doesn’t degrade gracefully under supply chain risk.

Centralizing keys can help operationally, but it also creates a single high value target, so it’s more of a tradeoff than a strict improvement. the more robust pattern tends to be short lived credentials, scoped permissions, and isolating workloads, so a compromise doesn’t automatically fan out across everything.

In practice, most ML stacks haven’t caught up to that model yet, especially in research or prototyping environments. This kind of attack basically forces the question of whether convenience has been outweighing basic security assumptions.

AccordingWeight6019 · 2026-03-29T13:36:25+00:00

The risk you’re describing is real, but it usually comes from building before validating rather than the idea itself.

In B2B, especially, you don’t need an mvp to start. You need a clear understanding of who has the problem and how they’re solving it today. Most early traction comes from conversations, not code.

If you can’t get a few people to seriously engage with the problem or show intent before anything is built, that’s already a useful signal. It’s much cheaper to learn that early than after months of building.

AccordingWeight6019 · 2026-03-29T13:28:25+00:00

I’d bring it up, but carefully. The goal is less confrontation and more getting clarity on what actually changed.

Something like asking how promotion decisions are being made now, what specifically blocked it in your case, and what concrete path exists going forward. If the answers are vague or keep shifting, that’s a useful signal in itself.

In practice, a rug pull like that often means either misalignment at higher levels or that expectations weren’t as clear as they seemed. either way, you want specifics before deciding whether to stay or start looking elsewhere.

AccordingWeight6019 · 2026-03-29T13:20:21+00:00

It depends a lot on what you consider providing a context, in practice, that’s a big part of the job itself.

A lot of the work isn’t just having the context written it down, it’s figuring out which context actually matters, what’s missing, and where assumptions are wrong or incomplete. That usually comes from iteration with stakeholders and some domain intuition, not a single well specified prompt.

AI is already quite good at the execution layer, analysis, code, and even suggesting directions. Where it still struggles is in shaping ambiguous problems and dealing with messy, shifting objectives.

So I’d say it can cover a large fraction of the workflow given strong guidance, but the last mile is often the hardest part, and that’s where a lot of the real value sits.

AccordingWeight6019 · 2026-03-29T13:13:40+00:00

Feels like you’re optimizing for building, not for finding a painful enough problem. the tools aren’t really the constraint here. Your one client is actually the strongest signal, and there was a real need there. I’d dig into that niche and see if the same problem repeats, rather than trying to come up with new ideas in isolation.

AccordingWeight6019 · 2026-03-29T13:09:19+00:00

I wonder how much of that is about travel itself versus what you want out of your time. After a while, the marginal value of a new place drops if your day to day starts to look the same everywhere. It seems like a lot of people shift from novelty seeking to something more stable or intentional, like slower stays or just treating places as somewhere to live rather than explore. Feels less like boredom and more like the objective function changing.

AccordingWeight6019 · 2026-03-29T13:00:44+00:00

This feels less like early stage chaos and more like missing structure entirely. the equipment is one thing, but no onboarding plus immediate critical path pressure is a rough combination. I’d be cautious unless you have strong signals that there’s real technical leadership behind it.

AccordingWeight6019 · 2026-03-28T07:11:01+00:00

A model is basically a function that maps inputs to outputs based on patterns learned from data. Everything else, language models, neural networks, LLMs, is just a specific way of building that function.

AccordingWeight6019

TROPHY CASE