The Two Gradients You Should Be Tracking from Day One

Every ML Engineer or Data Scientist knows that feeling quite well. Whenever you look at a problem proposal or a target to achieve, it hooks you immediately. Maybe it’s an opportunity to work on very complex architecture and make it work at scale to affect millions of users, it might be a core business challenge that genuinely matters, or it’s a well-known problem that can save millions of Euros/Dollars per year if addressed correctly. Thus, you get instantly excited about the main cause, and your brain immediately starts mapping out the pipeline.

But if experience teaches us anything, it’s that technical excitement is not a significant covariate in the career satisfaction equation.

Those feelings are very important only during the interview or the proposal phase. Unfortunately, there isn’t enough data to decide whether this project is a good step forward for you. The real challenge in my eyes is the ability to “read the room” early on. You need to evaluate the true potential of where you are landing, without dragging your feet and wasting months, but also without rushing into premature conclusions.

There are exactly two things I’ve learned to track instead. Gradient 1: How the team is deciding on their milestones, how they plan for them, and more importantly, how they react when they fail to deliver. This signals the team’s engineering maturity. Gradient 2: What’s actually in it for you, professionally? Not compensation (assume you negotiated that already).

The Failure Dynamics & The 60-Day Convergence Rule

Gradient 1: The Maturity Baseline

I can’t emphasize how important it is to understand the project’s power structure. Who is defining priorities, and based on what? Is that transparent enough for all the team members? How do the priority conflicts get resolved? These questions matter before you even get to milestone dynamics, because the answers tell you whether planning is a real process or a ritual. Delivery failures are not edge cases in high-pressure environments. Scope shifts, estimates were wrong from the start, and dependencies moved. What actually separates a healthy team from a dysfunctional one has nothing to do with whether they miss a milestone. It’s what the room looks like the day after. I’ve been in both rooms. The difference is not subtle. A team that handles this well gives you something harder to quantify but implicitly noticeable: you stop second-guessing whether your work is landing. That stability compounds fast, especially when you’re paving your way into the team’s structure.

Gradient 2: Defining Your Personal ROI

For Gradient 2, you need to be calculating your career optimization function long before day one. The expectation has two sources. One is internal: what do you want to have shipped, learned, or led in two years that you couldn’t have done in your previous role? The other is external: what did the team tell you the role would be? What’s your impression of the scope, ownership, and technical influence? This is like your compass during your time with the team, whether you are moving towards your destination or not.

Both gradients go hand-in-hand; they might differ in magnitude, but the sign must always be the same.

The 60-Day Boundary Condition

In my eyes, never run into premature conclusions, especially in the first two weeks. You are just getting to understand the team dynamics, which is more important than filing your first PR in that period. You also do not need a massive sample size or months of observation to see which way the wind is blowing. Sixty days are more than enough to have a better understanding of your current environment. In which you at least attended quarter planning, milestones’ hiccups, retros, and many reviews. These are very valuable inputs in the first months of every new team. In this period, try to maximize your learning, touch on different parts of the project, and ask as many questions as possible, as long as they help you better understand. I also highly recommend reading the team’s documentation for their current processes or their bottlenecks. A team that writes things down and keeps them current is signaling something about itself.

If you have done your job completely, asked the right questions, and pushed for clarity, then you are well-prepared to conclude here. Never underestimate your own judgment if you’ve done your homework. Don’t let the fear of taking a bold decision paralyze you. In 90% of the cases, making a decisive move based on clear data is a winning decision for your career. The people I’ve seen regret their timing almost always waited too long, not too short. They observed clearly, formed a view, and then held on for another quarter, hoping something would shift. It rarely did. The window where leaving is clean and the cost is low, closes faster than it feels like it will.

What If the Pace Is the Problem?

That’s an alarming signal. Suppose the pace is so high that you can’t have enough time to understand the team culture and structure. Or it might feel like firefighting all the time under the slogan of just deadline pressure, then it will be back to normal again. That’s not a good signal for inclusion for new joiners. A team that treats new joiners as headcount before treating them as people who need to understand what they’re actually working on will keep doing so. On the other side of the river, you might not feel work pressure, but still, your questions are also not being answered. It’s always next week, or you’ll get more context next quarter, or that’s something we’re still figuring out. And that window keeps moving. Chances are, they really do not have a clear answer for your questions, or they are just not transparent enough. Both are negative signals.

The Decision is Yours

If you have done all you can to quantify the progress on both gradients, talk with all team members, ask uncomfortable questions, and understand the team’s power structure. Then you just need to believe that your conclusion is not premature, it’s earned.

Act on it.