So far in my (admittedly fairly short, at 7--8 years experience) professional life, I've always entered employment as a software engineer.
However, I study a lot of things outside of this: leadership, economics, site reliability engineering, writing, queuing theory, product development, extreme value theory, lean, survival analysis, etc. This means when I find the right employer, my job often extends well beyond the programming I was hired to do, into things like:
- statistical analysis of customer health,
- cross-functional KPIs for alignment on current priorities over a diverse set of departments,
- improving development methodologies and workflows,
- adjusting on-call compensation to improve join rates and employee satisfaction, and more.
Over and over I encounter the advice to "come up with and practise the elevator pitch of what you do". I struggle with this. In an ideal environment, I do so many things I have trouble summing it up -- and if I do, it ends up being something too abstract like "I optimise all your systems".
I realise the things I do are basically the job of a CTO, but with my short professional experience it would be ridiculous if I said that's what I wanted to work as -- I know I lack a lot side skills that would be necessary for that job. (And I don't think everyone would appreciate the joke "assistant to the regional CTO".)
I can sell myself as a software engineer and hope that I end up in a crowd that appreciates the other things I do, but I would like to try to find a good summary of what I do to begin with.
How have you approached this?
Be careful not to be seen a presumptuous dabbler. For example, if you've studied a field but not done much of it, when you meet someone who has real experience in that, you're impressed and curious to learn from them; don't try to impress them with what you've read. (Maybe briefly take a clinical look at Reddit /r/iamverysmart top posts for some examples of what not to do; but briefly, since I suspect that dwelling in online forums focused on anger/derision/mockery/etc. isn't a great mode to be in.)
With different people, and in different contexts, you'll talk abotu different facets of your experience and interests, using different language. If some of your interests get into MBA-space, you might talk differently with MBAs than you will with engineers. For example, some of your phrasing above would make a lot of technical ICs think you want a manager job.
Outside of elevator pitches, you can cram a lot of examples into a 1-page or 2-page resume, which people will see in non-elevator contexts.
And articulating examples in a resume that you can skim occasionally might help remember examples, so they're on the tip of your tongue as followups when someone responds to your elevator pitch in some direction.
(Warning: I'm not great at business networking, so pinch of salt. For myself, my current professional self-image is something like "straight-shooter creative engineer, with battle scars, who cares", because that's natural and genuine for me, and it works for a lot of roles. Find what's natural for you, and how that matches with what people need, and whether you want to evolve your interaction styles in some direction.)
Imagine you're trapped in an elevator with the CEO of your company:
CEO: What department do you work in?
You: I'm a software engineer--but don't hold that against me.
CEO: Heh! Truth is I really value software engineers. [Ed: What else is she going to say?]
You: Of course, but I'm sure you've had your frustrations too. Some of us are better with machines than people.
CEO: You know, one thing that's hard is getting reliable estimates. One week I hear that everything is on track and the next week I'm told we're going to miss our deadlines. It's hard to know the reality.
You: Yeah, I get that. I think there some things with our development process that we could improve. If we had more visibility on the customers that sales is targeting, we might be able to anticipate new requirements. If we had known that we were going to sell to [CUSTOMER X], then we would have worked on [FEATURE A] sooner.
CEO: Interesting! Set up a meeting and we can talk about how to implement something like that.
Obviously, this is just a (lame) example. But the point is that no one cares that you're a polymath in the abstract. They only care about how you can solve a problem that they have.
The more you do this, the more people will remember you as "the person who solved problem X". Eventually you might even be known as the "expert in problem X." And if you end up solving lots of different and unrelated problems, eventually you'll get a reputation as a general problem solver, and people will seek you out.
Talk about what you have done, in what capacity. This is valuable and should be presented, so "technical lead for transformation of HR systems" or perhaps list "Business transformation manager & soft eng" whatever and let the questions work the detail out, presenting each as a project of sorts. As it stands, doing lots of odd jobs is not always helpful to your branding as a person, as it tends to work against the "elevator pitch" quick summary.
In my experience, there are two kinds of "CTO" titles in the industry: the kind given to a principal cofounder who doesn't want to manage people, and the kind given to a principal of any sort when they have their git access taken away and are asked take calls with big customer prospects all day. If you want to be the former kind, start a company; the latter, reevaluate.
It's like you're trying to say you want to have your cake and eat it too, but you don't have the cake yet.
Yeah, sounds harsh, but I'm just repeating what you are saying.
It’s a generalist role. You solve problems/generate insights with an analytical or technical approach. I’d call you an analyst from what I’ve read. Nothing particularly sounded like any CTO I’ve worked with. Maybe CTO of a 20 person company, but realize that’s largely title inflation.
The extent to which this is true should affect your answer quite a bit. Look at yourself honestly and decide whether you study these things or if you’ve just read a book on each of them (or maybe just a New Yorker article). Have you received intense critique and feedback from a true expert in those fields?
I’d lean towards never mentioning your study unless it’s actual study and not just self-learning of whatever catches your fancy. Dilettante isn’t often used as a compliment.
The elevator pitch you give should be tailored to the job you want. Do you want to be CTO? If so, learn what that job is and where you fall short and where you don’t. Maybe something like, “I’m an experienced full-stack engineer. In addition to X,Y,and Z, I’ve often found myself improving systems like A,B,C - that you have at your company. I’m looking for a CTO role where I can D,E,F and work on building skills in G,H,I.”
This might resonate with you: https://wildcardpeople.com/what-is-a-wildcard-person
If your job title isn't CTO, leave this behind. Unless the elevator is stuck between floors and we are waiting on an emergency crew to rope down sandwiches through the escape hatch, it's not going to work in an elevator. Too many syllables versus "I am a CT0."
2. Tell people who you are. You are more than what you do. If you are a leader, say "I am a leader." Lean in. Tell people what you can stand behind.
Good luck.
If I were staying in software, then I think my strategy would be to identify what 'boxes' there are and try to fit my experience into those 'boxes' for the different jobs I apply to. It gets really grueling having to make multiple resumes, and some of them can get a little thin, but maybe take this as a first approach. As an example of 'boxes' I mean
- Web developer - Embedded firmware developer - Devops engineer - Data scientist/data engineer
You know your experience best so modify as appropriate, but also maybe try to lean into the box where you "fit" the best. I know it might be a little depressing to try to reduce yourself to "web developer" box, but I see the goal as trying to stick to a career path/industry with the goal of building a network and building off opportunities. Not sure if that makes sense, good luck.
Second would be try to find appropriate metaphors -- how about "I'm a meta full stack developer" and if that piques interest go into your multidisciplinary talents there.
Third, plain old confidence.
CTOs primarily solve people problems, not technical problems. The focus is much more on organizational, market, and customer issues in a strategic context. Being technical provides necessary context to do that job competently but the skills required are not primarily technical per se. What you are describing is a technical generalist and Swiss Army knife. Outside of a garage-stage startup, a CTO should not be spending much time deep in the weeds of technical execution.
I think you'll find that you are better off presenting yourself as a very well-rounded specialist, which is highly desirable from an employment perspective, than as a generalist.
- statistical analysis of customer health,
- cross-functional KPIs for alignment on current priorities over a diverse set of departments,
- improving development methodologies and workflows,
- adjusting on-call compensation to improve join rates and employee satisfaction, and more.
"Technical and business problem solver" or "Applied Senior Scientist", perhaps?
Be careful that your pitch is not read as "Jack of all trades and master of none".(CTOs, at least in larger companies, work at a higher level e.g. installing governance structures, setting strategy etc. - which you do not mention)
I think a bit of a mystery is nice. You are a SW engineer, tell them you are a geek and will find yourself involved in the details of XXXX. If they probe, deliver, but keep a little mystery. When you surprise them, you will build a solid and well earned reputation.
do you typically work directly with the CTO of companies you've been with?
you could maybe self describe as a "CTO in training"
this would have even more credibility if the real CTO is mentoring you
What is wrong with that? If you want a better description then you can say "I work at the CXO's office." Replace X with whatever career path you want e.g. CEO, CTO, COO, CMO etc.
There are companies that specifically have career paths for young employees where an employee is deliberately put into various departments/divisions of the company to groom that employee for a future leadership position. Search for companies like these. Most big companies have these types of programmes.
If you can do the things you claim then you will be an indispensable asset to any Company. You can pitch something like "Problem Solver who can bring Cross-Disciplinary Knowledge to implementing a Computer-based Solution" followed by actual examples to drive home the point. Don't be constrained by the format (i.e. short elevator pitch, one-page resume etc.) but provide a good summary first followed by longer details via document/email.
If they need somebody who brings in a vision and holistic view then you might be that person they are looking dor
In those environments, it's just normal. You have the headline job you were hired to do, but everybody else knows the list of 15 other things where you're the go-to guy.
Most people here don't see your value and think you must just be puffing. Ditto employers. You won't convince them no matter what. You're from Mars as far as they can tell. They're sleepwalking, you're not.
Finding one employers who does know what you're all about is the hard part, not convincing them of the value of polymaths/interdisciplinary peeps. They know.