In the late 1800s, a young man named Charles Schwab took a job as a day laborer in one of Andrew Carnegie's steel plants. The work was unglamorous. Nobody was watching him closely and certainly nobody expected anything from him beyond the narrow list of tasks tied to his wage.

Schwab did the work anyway, and then he did more. He stayed late without being asked. He learned parts of the operation that had nothing to do with his job description. He carried a good attitude into work that most people would have treated as beneath them and Carnegie noticed.

Over the following years, Schwab was promoted again and again, until he became the first president of United States Steel, the company Carnegie built into an empire. Carnegie eventually paid him a salary of a million dollars a year, an almost unthinkable sum for someone who started out sweeping floors and hauling material. When people asked Carnegie why Schwab was worth that kind of money, his answer was simple: no one else in the business went further than what was asked of them, as consistently, or with as little complaint.

Where This Breaks Down for Engineers

Most engineers do not think of themselves as under-delivering. They close their tickets, hit their sprint commitments, show up to standup and say the right words. By the letter of the job, they are doing everything asked of them but there is a difference between meeting the specification and shaping the outcome, and that difference is where most engineering careers quietly stall.

Picture the engineer who fixes exactly the bug in the ticket, notices a second related issue three functions away, and closes the ticket without mentioning it because flagging it isn't their job. Observe the senior engineer who has the context to mentor a struggling junior colleague but stays heads-down in their own backlog because helping someone else doesn't show up in their own velocity metrics. Remember the person who refuses to touch documentation, onboarding, or the messy parts of a legacy system because none of it was assigned to them by name.

Each of these choices is defensible in isolation. Nobody gets fired for staying exactly inside their lane but the quiet cost of staying inside the lane is also how you become forgettable. When growth conversations happen, when leadership is deciding who gets the harder, more visible project, when a team is trying to figure out who to trust with ambiguity, the engineers who only ever did what was asked rarely come to mind first. Technical competence gets you tolerated. Going beyond it is what gets you remembered.

The strange irony buried in this is that the engineer who protects their time by doing only the minimum feels like they're playing it safe. In reality, they are trading a small short-term convenience for a much larger long-term cost which becomes capped trust, capped visibility, and a career that grows in a straight line instead of compounding.

Ralph Waldo Emerson wrote about this kind of deferred payoff long before anyone had heard of sprint velocity. His argument, in essence, was that effort given without an immediate return doesn't disappear. It accrues quietly, like interest on interest, and eventually it gets repaid, often from a direction you didn't expect. The extra hours Schwab put in as a laborer were not charged against a specific paycheck. They were an investment that eventually returned a fortune, and more importantly, a level of trust that no title alone could have earned him.

What to Actually Do With This

This isn't a call to work more hours or take on everyone else's job for free. It's a call to change what you do with the hours you already have.

Start with one recurring task this week, something you already own, and do it slightly better than what's expected.

Find one thing that sits just outside your direct ownership, something you've noticed but never mentioned because it wasn't technically yours, and raise it before your next 1:1.

Treat the extra effort as a deposit in your own skill account, not just an act of goodwill toward your team. Keep a private note of what you learned each time you stretched past the ticket. That record becomes the evidence you'll need when you eventually ask for the bigger project, the promotion, or the raise.

And reframe what this work actually is. You are not doing free labor for an employer who may or may not notice. You are purchasing experience, trust, and range, three things no manager can hand you directly and no title can substitute for.

Schwab never asked Carnegie for the million-dollar salary because he never had to. The habit itself built the case for him, one unrequired hour at a time.

The compounding starts the same way for you; quietly, and long before anyone else notices.

Until next time,

Kayode