Skip to content
Three Questions I Asked a CTO in 2023 to Decide Whether to Join

Three Questions I Asked a CTO in 2023 to Decide Whether to Join

In 2023, after a three-month break, the author interviewed with a catering company's CTO and evaluated him through three key questions: business expertise, business architecture knowledge, and management style, ultimately deciding to join based on the CTO's strong answers and a mutual two-way selection process.

samdeepthink
samdeepthink
samdeepthink

In 2023, after leaving my job and spending three months at home, I grew bored and browsed Maimai, a professional networking platform. I discovered a catering company's CTO posting a hiring notice for a technical manager to lead a development team. Since I had relevant industry experience, I contacted him on Maimai, and after reviewing my work history, he immediately scheduled an interview.

The interview lasted about an hour, and by the end I had already decided to join the company. My decision hinged on evaluating the CTO across three dimensions.

First, whether he truly understood the business. From previous experience, I knew that CTOs who lack business understanding are often challenged by business leaders or the CEO, leading to instability — typically lasting only six months to a year. Since CTO stability directly affects my own stability, I needed to assess this. I asked him about difficult chain-store problems I had encountered, phrasing them as requests for advice. He answered exceptionally well, even detailing implementation and operational strategies. Later I learned he was a seasoned expert in the chain-store domain.

Second, whether he understood business architecture — not technical architecture. This means viewing the business from perspectives such as online segments, offline segments, and new business launches, and being able to connect the company's end-to-end business flows. This is a weak area for me, so I hoped my future superior could complement it. He immediately outlined the supply-chain business flow, finance business flow, store operations flow, and the systems required for each. He genuinely understood this area.

At this point I was largely convinced; even if his technical skills were lacking (though they were strong), I could handle the technical side. Still, for caution, I asked one more question.

Third, his management style. I had previously worked under micromanaging bosses, which was painful. I prefer a delegating leader who clarifies the problem and lets me handle execution. This is hard to gauge in a single meeting, but his response was: "I occasionally throw out a one-sentence requirement, and the team figures out the rest." That matched exactly what I wanted — both operational autonomy and delegation.

After these three questions, I felt confident about joining. Some might wonder why I, as the interviewee, asked so many questions. The reason is mutual selection: my background includes big-company experience and years of deep involvement in the chain-store industry, so the fit had to work both ways. Finding a suitable superior is rare, and the company finding a candidate like me is equally a matter of luck. It is absolutely a two-way process.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

business architecturebusiness understandingtechnical managermanagement stylecareer decisioncatering industryCTO interviewtwo-way selection
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.