Think About Your Career in Phases, Not a Straight Line
The audience for this topic includes people who have built up some career experience but aren’t confident their current work is leading anywhere, or who, if anything, would rather be doing something else entirely. I also think this concern applies broadly, not just to engineers.
To talk about this, I first need to look back at my own career by breaking it into “phases.”
I joined the workforce after graduate school, and in my early twenties I was basically an errand boy learning the basics. I arranged procurement for prototype parts, swapped candidate parts over and over while taking waveform data, and gathered up datasheets to organize them into documents presentable to my seniors and veteran engineers. Once I learned how to use CAD, I spent my time building PCBs to meet the specs and change requests my seniors had decided on, calculating tolerances, then measuring waveforms again. My development skills were probably terrifyingly weak compared to many engineers my age who’d graduated from technical colleges or had robotics competition experience. But I treated this whole period simply as a “study phase.”
My late twenties were an “independence phase.” I made a point of thinking through and executing everything on my own judgment. That got me into trouble again and again, and my working hours were black-company level at their worst. But without that period of stumbling and nearly dying over and over, I don’t think I could have gained confidence in my own technical ability. You can’t properly evaluate anything without trying it. That’s a basic principle of engineering. I was very grateful, during this period, for an environment that let me operate with that kind of stance in the first place. The senior engineer who had been my OJT mentor happened to be promoted to department head around that time, and he pulled me into his department. That coincidence made things go very smoothly.
My early thirties were, in contrast, a “team management phase.” Once I could see to some extent what I could do on my own, the next stage was to expand that further by moving a team. Some of my peers viewed taking on that kind of management role around age 30 negatively — “too early,” “I’d rather keep developing” — but in practice I was a playing manager in all but title (my position hadn’t actually risen), so it was a very fruitful period of riding on someone else’s coattails, my boss’s, and turning it into my own experience. I did product planning, persuaded people around me, secured budgets, ran the team, wrote schematics, reviewed source code, handled EMC countermeasures, sorted out legal matters, managed the development budget, coordinated schedules, adjusted specs, occasionally got yelled at by the manufacturing plant, arranged promotions, and did whatever was needed, whether that meant giving a talk or doing sales on the floor at Yodobashi. In the end, I think I was blessed with good bosses in this period too. Mr. A was my mentor as a salaryman. He’s an eternal mentor who taught me the ultimate life skill of how to achieve self-realization and live an interesting, amusing life even while holding the position of a salaryman.
My early thirties after changing jobs were purely a “challenge phase.” That was the point when I crossed over to Silicon Valley with confidence, having picked up a full set of skills. Would I actually measure up? What kind of ability did the people who’d built careers at Apple and Google after graduating from MIT actually have? How well could I compete with them? As I’ve touched on elsewhere, the shift in my values over those few years was enormous. Even now I sometimes find myself suddenly recalling various scenes from that time. It was a wonderful period. I had decided my late thirties would be a “phase of serving as a CxO,” but during that time, for reasons I couldn’t fully explain even to myself, a feeling welled up that I wanted to contribute to Japan, a country I’d more or less thought I’d given up on (laughs). Doing a startup in Japan seemed like a great way to act on that, so I decided to go back.
I wasn’t earning nearly enough to become an angel investor, and I thought it was still too early to shift into advisory or support-type work. And if I wanted to live as a working engineer, Silicon Valley was without question the happier choice. But the idea of building a company that could itself serve as a reference point fit my motivation at the time far better. As it turned out, I ended up serving as CTO, and seeing it from the inside was completely different from watching it from outside. Back in my Miselu days, I had plenty of complaints and things I wanted to say to my boss J, but I feel like now we could understand each other far more deeply and share a good bottle of wine.
My forties are, to some extent, a matter of how things turned out, but I’d call this the “phase of diversifying activities.” I didn’t end up on the path I’d originally imagined — making a startup wildly successful in my late thirties and retiring early (laughs) — but as it happens, this seems to be a phase where I’m working through, one by one, the things I was vaguely thinking about around the time I returned to Japan. In Silicon Valley, it’s said that “if you throw a rock, one in two people you hit will be an entrepreneur,” and those entrepreneurs are your high school classmates, the guy who lived down the street, your parents, your relatives, people close to you. That lets young people see entrepreneurship as something very familiar, and lets them hear all kinds of useful stories about it from a young age. Japan’s biggest weakness is that it lacks this kind of social infrastructure, and I’d been thinking there might be something I could do about that.
These days, the weight of my work has shifted away from pure engineering and toward activity as a manager, and even further toward something like social activity. Engineering obviously still matters — I still read schematics, still subscribe to Transistor Gijutsu, still buy and take apart sketchy gadgets from China, and sometimes carve out focused blocks of time to code. But for me, that’s like a pro athlete’s jogging or strength training: doing it alone earns you no praise, nothing to be proud of, it’s simply a given. What matters is the additional step beyond that: properly putting out social value. And the critical tool for doing that is management. These days I support a variety of startups, from technical strategy through fundraising to hiring plans. I’ve also been given opportunities to give talks, and even to teach students at universities. In that sense, I feel like I’m carrying out, in changed form, what I originally envisioned.
The phases keep going. Right after I stepped down from TripleW, an angel investor gave me some advice: “Your late thirties and beyond are prime time, you know.” The idea being that your technical skill is solid by then, you’ve tasted plenty of hardship, and you still have plenty of physical stamina, drive, and ambition. That’s the kind of age range it is. But when it comes to “career,” I think prime time, in fact, always exists, then as now, and going forward too. Succeeding once doesn’t let you coast through the rest of your career. People who sell the startup they founded, make a fortune, and then vanish from the world are actually quite rare. Everyone keeps engaging with society afterward. A career doesn’t end, it just puts you at the starting line of the next phase.
Now, about the “foresight” I mentioned at the start: honestly, how far ahead I was actually thinking, at any given point, was maybe one or two phases out. I wasn’t reading that far ahead or building a long-term plan.
For example, the big decision to go to the US was already on my mind during the “independence phase” I mentioned earlier, but back when I was a student, I honestly hadn’t thought about it at all. And during the period when I was running around doing team management as a salaryman, the idea of starting a company and going independent was already fully present in my mind. But since the path to get there was unclear from where I stood on my own growth curve, I figured it was best to first just get in and try. Because I held that view, I could say yes without a second thought when an opportunity rolled my way, but it’s true that I was taking the optimistic stance of “I’ll think about what comes after once I get there.”
Around my third year as a working adult, I had the chance to speak at my old high school, and I remember telling the third-years, “Please try to form an image of yourself five years from now.” The number five didn’t carry any special meaning at the time; it was just a message to those soon-to-be college students to think about what they’d become, or want to become, “after graduating college.” But looking back now, it strikes me as a remarkably well-chosen number. Looking too far ahead when it comes to the future usually means your predictions fall apart. In terms of phases, one or two ahead is plenty. In terms of years, something like three to five is plenty.
As a general statement, it’s safe to say that seeing far into the future is basically impossible. If you look back through the history of the global economy, it’s said that there wasn’t really anything you could call economic development until around the year 1600. Of course there was some development day by day even before that, and it wouldn’t be reasonable to think there was no growth at all. But I think what that claim really means is that, compared to the development of the past few decades or even few years, growth before 1600 was practically nothing. And this pace is, if anything, only likely to get faster from here, not slower. If it were ever to slow down, it would probably happen alongside a sharp population decline and a great depression, so honestly, we should hope it doesn’t happen. So we should basically understand that the future is not something that can be predicted.
That said, I do think it’s good to hold a vague sense of your big-picture vision. I had a vague notion that, in the long run, I wanted to live by using “technology” as my passport. But I didn’t think I could get there in one leap; I’d been aware, since my student days, that I’d need to build up a great many things first. What matters is not letting yourself stagnate. There are organizational circumstances to consider, of course, but your life ultimately belongs to you. If you feel any sense of stagnation, your career plan is in serious trouble. Someone who can’t properly handle what’s right in front of them has no future. But if handling what’s in front of you doesn’t actually point toward your goal, then, from the standpoint of an individual career, there’s no need to force yourself to do it anyway. Balancing those two points properly is, I think, a good way to keep your career in view.
The content of this post is an excerpt (original text) from the following book. If you’re interested, please get a copy.
The Shape of a Happy IoT Startup
The Shape of a Happy IoT Startup
Originally published in Japanese at https://clazytech.com/2022/10/1081/. Translated with LLM assistance and reviewed before publication.