Adapt or Fade: Interviewing for Developers in the Age of AI Assisted Coding
In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub explore the evolving landscape of interviewing for programmer positions in the age of AI-assisted coding. They discuss the relevance of traditional leetcode questions, best practices for evaluating skills when interviewees may use AI, and the importance of higher-level thinking in interviews. The conversation covers interview techniques such as pair programming and code reviews, possible IP concerns, and whether interview questions are designed to catch engineers or just coders. They also share insights on designing effective interview loops, the kinds of interview questions Microsoft asks, and the implications of using AI models for specific tasks like spell checking.
Resources:
- How Many CTOs Pod: https://howmanyctospod.com
- Scott Porad: https://www.linkedin.com/in/scottporad/
- Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/
#TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIinterviewing #HiringTrends #ArtificialIntelligence #AIAssistedCoding #AIAssistedInterviews #CodingInterviews #AIRevolution #FutureOfWork #AIinTech #AIAssistance #PairProgramming #CodeReviews #HiringPractices
Articles from this episode
Brad: I want you to operate at the level of understanding and designing systems.
And so I want you to use AI.
Welcome to another episode of the How Many CTOs Does It Take podcast.
I'm Brad Hefta-Gaub, and this is my co-host.
Scott: Scott, all right.
Brad: All right, Scott,
welcome back.
What do you want to talk about this week?
Scott: Brad,
only our loyal listeners might remember.
A recent episode I talked about how I had been an interview,
I've been interviewing somebody who was wearing a baseball cap.
Brad: Yeah, I felt seen or being called out.
Scott: It really threw me for a loop. And this is not about workplace fashion any longer. This is actually about a more modern problem,
which is interviewing in the age.
of AI-assisted coding.
Brad: Yeah.
Scott: And it actually takes on two dimensions.
There's interviewing in person,
and there's interviewing remotely.
And even a lot of in-person companies now are still interviewing remotely because it is much more efficient.
I'm curious to discuss with you best practices, so to speak, if there are best practices yet,
for how to interview in an AI.
assisted coding era and i think it's two parts of it one is interviewing for the ai skills meaning do you know how to use the tools and
Brad: Yeah.
Scott: the other part is well if somebody knows how to use the tools and get the ai to do it for them do they actually know the fundamentals right and so i'm just curious to know if how you're doing it these days if you're doing it or how you would hypothesize to do it if you're not doing
Brad: Well,
this I love this topic. This is a great topic.
I think that, yeah, there's lots to lots to kind of dig in here.
And I don't know that we can cover everything in a single podcast episode,
but I think it's worth starting the conversation.
Let me start by saying that I always thought that like leap code style interview questions were not a very constructive and useful interview technique.
And I think that.
One of the things about like the age of AI is that like that just like a remote, you know, remote call interviews where you ask lead code questions are just going to be a waste of time because every person would be able to just have their, you know, HUD overlay of heads up display overlay of,
you know, the AI chatbot helping answer your lead code questions. In fact, there's like a.
like a company that's like an Andreessen Horowitz funded startup of some engineering students from Columbia or something like that that got kicked out of Columbia because they they built a thing I think it's called Cluzi or something like that it's AI assisted lead code programming thing
Scott: And I know that we have a few non-technical listeners to this podcast.
So what is lead code?
Brad: Yeah, elite code is basically like you stump you stump the interviewer stumps the interviewee by asking to perform,
you know, coding gymnastics,
you know, like a classic,
a simple classic example is please implement in.
the language of your choice, or maybe I give you specifically the language of Python,
you know, or the language of JavaScript reverse a string in fastest possible time or something
Scott: So
Brad: like that.
Scott: just some coding trick.
Brad: Coding tricks.
There's like leetcode.com or something like that has, you know, hundreds of leetcode tests and like score your test is like performance and memory usage.
et cetera,
right?
Scott: So what do you think is a good interview?
Brad: Well,
I mean,
my...
My preferred interview technique is to get somebody to talk in depth technically about a project that they specifically worked on.
Right.
Scott: Mm-hmm.
Brad: You know, I mean, I've been writing code for more than 40 years.
So it's like I you can you'd better be able to explain any project you ever worked on to me in a way that you can make it clear to me what you actually did, what the architecture actually was.
what the challenging problems of it were,
what your technical choices were,
and we ought to be able to have a conversation there that gives me a lot of information about what you actually know how to do as an engineer.
That's how I typically interview people.
Scott: In an AI coding world,
that would get around one of the topics, which is, do people really know what they're talking about?
If they had the AI robot write all the code,
if they could then just describe what was happening there to you, then they would.
That would illustrate that.
Brad: Yeah, exactly.
I'm a huge believer in like,
show me your GitHub account,
right?
Scott: Yeah.
Brad: And even if you only worked on private projects,
right?
Like your GitHub view still shows your activities across private projects and public projects,
you know?
And so, you know, okay,
wow,
this person has 78% commits,
you know, of, you know, this big, huge green bar of work they've been doing.
been doing on all these private projects you know now i know you're you're doing a bunch okay cool tell me about i don't want you to disclose anything that's confidential but let's
Scott: Mm
Brad: talk
Scott: -hmm.
Brad: about a pick a project pick a project you want to talk to me about and tell me about it and yeah to your point like you have to be able to understand the technology you'd be able to to handle that interview question um it can go a lot of different directions i find that it helps it should help people kind of like
like get away from their nervousness like i mean some people are going to be naturally nervous but but like i don't care if you i'm not going to ding you because you're doing some lead code programming thing and you put a semicolon in the wrong place like compilers tell us that i don't need you to be a compiler compilers do that i want you to operate at the level of of understanding and designing systems and so
I want you to use AI.
Scott: Yeah, now what's your opinion?
I think in an AI-assisted world,
my opinion on this is changing.
What is your opinion on the sample coding project?
Brad: I mean,
I think there's value in that still.
I think that there certainly was a time like you and I were at a health tech company together and that was a big thing that they had. They kind of sent off people with go do the sample coding project.
There's pros and cons to that. Like in a in a in a buyer's market,
then.
right where you're where you're you know or a hirer's market an employer market where employees are looking for work they're more willing to sort of like jump through hoops to prove that that they're worth hiring um in a in an employee sided market where there's a lot of um demand for employees i think that that kind of like do a coding project or i think you lose good candidates because they're just like i'm
i'm i don't have time to write that code for you so to me i feel like it's like it can give you good information but it can cut both ways like sometimes it kind of gets in you it gets in your way
Scott: Yeah, I was for a long, long time a big fan of the.
the coding project um because i felt and i would say this even to the recruiters because the recruiters would always say oh this is really slow and step down we're losing candidates and i would sort of say look you could take away all the interviews and just give if i have the choice between no interviews and only coding project or interviews only and no coding project i take the coding project because i want to just see what somebody can do like i don't want to hear what they can do i want to see what they can do
um and i sound that it was not the case that somebody who did a good coding project always got hired but it was almost always the case that when there was wasn't a great coding project and then we interviewed someone we ended up not wanting to hire them it
Brad: Right.
Scott: was so it was a really good signal um but it was a burden for people and i think that became an impediment but i do think that where my mind is changing is now in an ai coding world i mean
We would basically would send someone a spec and say code this up and now you can just give it to a cursor and say, well, this company wants this thing. Can you make this for them?
Brad: Well, but I, okay,
so 100% agree with you on that. I have a couple of reactions to that. The first one is,
well,
isn't that how I'd want them to code it if they worked for me? Because I'd want them to go as fast as, like, if you're wasting your time pressing the enter key and the tab key and the bracket key,
like,
that's, you're slowing yourself.
yourself down i want you to move faster than that anyway so you absolutely use the ai agent to solve this problem but then i need you to come back and you need to code review it you need to prove that it's working you need to have you need to have implemented your unit test you need to have written your your your er description and you need to come to me and tell me and and defend your code in front of me right like tell me how what was hard about that why was that a challenging question why was that challenging what
And how did you solve that?
What did you?
Scott: So I have two questions,
two comments leading into a question or something like that.
One is something you also said on a previous podcast, and I agree with it, which is increasingly what's required when working with the AI coding assistance is like tech lead and engineering manager type skills,
which is true. And I've always felt in interviewing, even interviewing for, you know, entry level and mid level IC engineers evaluating their sort of those types of skills is really important.
So I guess my question is, if you were designing an interview loop,
you're at a new company,
you're going to hire some people,
you're going to design an interview loop in this AI assisted coding world,
how would you do it these days?
How would you introduce this piece to it?
Brad: Well,
I already told you that I would I tend to lean away from like.
code questions anyway
Scott: Yeah.
Brad: and I want to lean towards higher level thinking anyway right which I think lends itself to what I'm saying is the the better model to use AI agents anyway right
is
Scott: So is that like, tell me, you know, is it basically tell me, is it a star question?
Tell me about a time where you developed something with an agent.
What was the problem?
It was, you know, star situation, task,
action result.
Is that basically,
is it those kind of questions with
Brad: Sure.
Scott: an AI agent?
Brad: I think you could totally make a bunch of star questions around how do you use AI agents, how do you use them to solve specific problems.
uh you know and you could certainly use star like questions around all kinds of things like building new software refactoring old software finding a particularly challenging bug right um i do think that like you know we had one of our one of our early episodes uh last season was uh with ted neward where we talked about interviewing in general i thought that was there were some really great great nuggets that came out of that that conversation and one of the
Points that I think Ted made that I 100% agree with is that, you know, you really have to have a very clear expectations for the role and your interviewers need to evaluate the person's fitness for those expectations of the role.
Scott: Hmm
Brad: Right.
And so I think more and more the role of being a software engineer in the AI assisted coding world is all about,
are you good at evaluating code written by another developer,
aka the agent?
Are you good at evaluating the code?
So one thing that might be useful would be like,
you know, I can imagine this being an interview loop thing,
design an interview loop that includes like.
We have a bunch of pull requests,
a bunch of code written.
Do a code review.
Scott: Code review interview.
I was thinking about just earlier this week was telling me about that I work with.
We had some code written in Ruby and we wanted a TypeScript version and one person was bellyaching about it and the other person was like, well, let's just see if an agent can do it.
And it was basically a hole in one, you know, they had to rework the prompt a little bit, it took them about an hour,
which sidebar, I think that's one of the key things that people miss with this AI stuff is sometimes it takes a while to get the prompt right,
you know, you have to iterate.
But after a while, they got it.
And so I wonder if that's an interesting thing to just almost,
you know, here is, I don't know, something written in one language.
Maybe we can sit down and pair together and you can just tell your AI of choice like to make it in this other language.
And then we can look through it together and you can tell me if you think it's right.
Brad: That has been a technique that I've used to varying degrees of success in interviews in the past,
and I would like to get this to work well consistently,
and that is a pair programming interview.
You know, VS Code does support this, like, shared remote mode where you can basically,
like.
turn on like basically open up vs code in a way that you using your vs code can connect to my vs code and i literally can watch you type and follow your cursor around and you're looking at the code base which is my little sample code base and you're changing it directly right think cursor has this mode yet hey cursor team like let's turn this on like pair programming uh agents where we both are able to look at the same agent
agent and type into it and chat with the agent together and I would love to basically see how you use the agent you know so here's some code it's got a bug in it or here's some old code in one language tell me how you use tell me how you use the agent to to implement this feature right
Scott: I got a lot of questions in there.
First to comment company I was at like a long time ago now we did this cool thing a pair programming interview.
This is how it worked. I'm the interviewer.
you are the interviewee and we're working on the same code and it starts like okay i'm going to write a test and it was a basic thing like we're going to make a calculator or something you know one of these we're going to make the elevator algorithm or the calculator i don't know what it was something basic like that right i'm going to write a test now you make a pass okay cool we did that one sweet now you write this test
that person does it okay now i'm going to make that pass right back and forth back and forth ping pong and we sort of had a script to like escalate
Brad: Yeah.
Scott: it and make it go on and on for whatever this thing was we were building but it was a cool way of just
working with somebody you see we've got to see like how do they write tests how they write code what is it like to work with them he was just sitting next to him sitting on the same computer sharing it that was a fun way to interview okay so here's the question about this agent thing I'm giving you some code I want you to make the agent make it do something different would you give them some good clean code or would you give them some really dinky code
Brad: I like I've done this most recently literally with the code base.
base of the enterprise that we're interviewing for so like like
Scott: Okay.
Brad: here's here's like a real project that needs to happen did exactly that project and it didn't like there were there were mechanical problems logistical problems with it that i think kind of got in the way of it so that's why i'm sort of saying like like i feel like it's a a very straightforward problem to say literally here's a ticket here's the ticket here's the code tell me how you solve this problem
right
Scott: Yeah.
Brad: because that's what's going to happen on day one anyway and if the code base is big enough i mean i just fixed some bug today in some code base where it's like fuck i haven't looked at that file i have no i didn't write that code some other yahoo on the team wrote this code right or like i get dropped in as a fractional cto like when we were talking to uh scott bradley you know he's like his his firm like it's dropped into places and it's like their whole job is unfucking code bases right
right it's like so you're dropped in on some random code and it's just like it's a mess well guess what that's the job like that's the job and i'm more certain that with ai coding like we said uh you know i think we said this in a couple episodes ago where i'm like i think 2026 is all going to be about this case-shaped economy for like the haves and the have-nots around understanding uh ai-assisted coding so i for the people that are good at ai coding
There's going to be more and more work for them to do to go unscrew up code bases that were messed up by humans and AI,
right?
So expect that you're going to randomly be dropped in some code you've never seen before, and it's a real test to your ability as an engineer to be able to like quickly figure that out.
Right.
Scott: I create any intellectual property issues.
You got interview candidates looking at your real code.
Brad: Maybe.
Obviously, you have to solve that as appropriate.
I'm less I mean, most the average the companies companies I tend to work with are startups that are moving so fast that they that's not a problem to have them sign an NDA.
Scott: Or I was thinking the other way around,
which is we
Brad: Oh, I'm not going to actually use the code, right?
Like, besides,
maybe I do.
I don't know.
Like, you mean like work for hire,
intellectual property,
Scott: Yeah,
Brad: work for hire?
Scott: yeah
Brad: Yeah, okay.
We're trying to evaluate their ability as a, yes,
granted,
solve that problem,
have the legal team come up with something, but there's no reason why you can't solve that problem.
Maybe you don't actually have them.
you don't commit the code right like in the in the example that I am thinking of I knew it was a very doable project because literally a developer had just done it and
Scott: Mm
Brad: that developer
Scott: -hmm.
Brad: told me oh yeah that took me like you know 20 minutes
Right.
So I know it's a do so that's an example where it's like it's a real example of the code that they'd be in.
It's a project that I know is a solvable problem.
Right.
And so really we're just testing that we're directly testing the engineer's ability to do exactly the types of problems that we need to have them do. And.
It tells it shows me how they solve problems,
right?
The tools that they reach for.
Scott: And you're just looking for all the normal stuff you kind of look for which is are they breaking it down into small tasks?
Brad: Yeah.
Scott: Are they normal kind of things interesting?
Brad: So it's interesting.
I just I literally just did this interview with a candidate for another firm and it was like, to be fair,
the person was relatively junior.
And,
you know, I asked my,
you know, talk to me about a project you've worked on.
John and this person had very very limited experience and what was really interesting is effectively they said man I I thought you were going to be grilling me on react native and and so they were kind of like this interview is a lot easier than I thought it would be you know and you know at the same time I was like
if you're not really experienced enough for the role that we're trying to hire so but keep up the good work and talk to us in the future you know um but i just think that these like coding quiz questions are a waste of everybody's time
Scott: There was a trend.
I'd say it was about seven, eight years ago of companies that, you know, made online platforms for sort of coding quiz questions.
You know, you'd screen a resume and someone passed that, then you'd say, OK,
go do these coding tests and then it would give you a score kind
Brad: Yep.
Scott: of thing.
And we tried that and it was OK.
I mean, it certainly it was these it was as you say,
it was these leak questions,
right?
and got to see if there was some proficiency. But I think that assumes that there's something on the other side, which is, for lack of a better way of describing it,
that there are perfectly well-described tickets that you want someone to do,
right?
Brad: Yeah, exactly.
Scott: And in at least in the realities I've lived in, there are never perfectly well described tickets,
despite our best efforts.
In fact, I would actually say differently, there are never perfectly well described tickets because there hasn't been a lot.
Brad: it's like i'm going to detour a little bit i was talking with one of our engineering managers yesterday um we don't use we most of the people i work with use a tool called augment code which is a competitor to cursor Yep we bought an enterprise license and at the time we did is because they had a bigger context
window uh i think chris has probably pulled ahead but that's beside the point anyway uh this engineering manager he is uh he's plugged our github our confluence our jira our company objectives all sorts of stuff into this thing he essentially he refers to it as a problem brief but like you know he was showing yesterday there's like this one new error showing up in the log and it's like what is this and someone might
i file a ticket which just has the street of the air like hey we started getting these on tuesdays
Scott: Right.
Brad: and you know some engineer would go well i guess i'm gonna go start digging into this and he said he sent an agent about it and wrote like i don't know like two or three pages of like information and context of like where this was coming from and might be what might be causing it and
yeah potential ways to fix it and all
Scott: Yeah.
Brad: sorts of things like that and so ultimately you get a much more robust ticket which potentially you could handle hand to an engineer say now let now fix this or now let the robot fix this I'm not actually sure why you wasn't just coming up with answers to those things
When I say answers, I mean solutions, but it might be that there were some choices that had to be made. I don't know what I've digressed a ton from those leak code questions or those coding platforms assume that there's like these very rote code things on the other end and those days are gone with the agents. If there are,
the agents are doing them.
Scott: Well,
one,
those days are gone.
And two,
I think the teams that hired those types of engineers are just focused on that.
that for hiring engineers they weren't really they were getting they were getting uh coders they weren't getting engineers they were getting people that would clickety clack on a keyboard that's not the same as like actually thinking about the business problem understanding it you know understanding how to solve the business problem and and how to understand the business description like there's i mean like
That's the hardest part about being an engineer is translating the non-technical description that you inevitably get that is not very useful into something that's actionable and testable and implementable.
Brad: I've thought about this so many times on this podcast and elsewhere.
That is the value.
If you can translate something from an idea to action.
Scott: So let's go full circle back to the original question you asked.
In the day, in the age of AI coding,
how do we interview for engineers?
And I feel like the answer is we have to lean that much more heavily on how good are you at understanding.
vaguely describe business problems and then describing them in you know describing them in a manner that allows them to be broken down into sufficiently executable tasks by an agent and then that you can evaluate the quality of the plan and ultimately the implementation done by that agent
Brad: Mm-hmm.
Scott: That's what matters.
Brad: That's it. That's the interview loop right there.
Scott: That's the interview.
And so tell me examples of that.
Star questions that relate to that.
Brad: We're going to have four sessions and focus on each one of them.
Scott: I love it.
Brad: I interviewed at Microsoft once.
Scott: Uh-huh. Did they ask you leak code questions or ask you how many ping pongs it takes to fill up the Smith Tower?
Brad: They did not.
I remember a question that was asked of me though.
Scott: Okay.
Brad: you are designing a key fob for a car what do you need to know and it was pretty interesting because i knew nothing about key fobs and i was a i was applying for a job working on the visual studio team actually so like i had nothing to do at all with what they were doing and it was a little bit of a trick interview question but it was you know just one of those questions that they were getting at trying to understand how do you think and
Scott: Yeah, totally.
Brad: It only comes to mind now because I think actually in these days, that's actually might be kind of a handy question.
Somebody comes to you and asks you to build them a key fob and you know you can get the agent to build the key fob, but you got to ask all the right questions so
Scott: Exactly.
Brad: you can tell the agent the right thing to do.
What do you need to know?
First question is, what is this key fob opening?
Scott: Right.
Right.
Brad: What's the key fob for?
Scott: Right.
Brad: Um,
so maybe those kinds of questions, which I think sometimes can be a little bit of a trick question.
I was also asked the question,
how many gas stations are there in the United States, you know, but maybe some of those questions are a little bit more relevant these days.
Scott: Yeah,
I feel like some of those kind of are just a little bit around trickery and just like estimations and strategies for estimations. But I agree with you that that that there's like it does.
If you explain your answer to me, then I get.
I get to see how you think the problem through.
I just would like to turn those into questions that are more relevant to the task at hand,
right?
Brad: Yes,
Scott: So
Brad: I agree
Scott: I like
Brad: with your you.
Scott: key fob questions a better one than how many ping pong balls will fill Smith Tower or how many gas
Brad: That's stupid.
Scott: stations are there in the United States.
You know, like to me,
Brad: Gas station ping pong are stupid, but I think the key fob is closer, but key fobs have a stretch with its visual studio.
studio if somebody said to me we want to add spell checking in visual studio doesn't believe it or not it doesn't have spell checking right
Scott: Yeah,
Brad: now
Scott: there are some plugins for it.
Brad: so someone's put it in a ticket put out of the spell checker what
Scott: Yeah, how do we do it?
Brad: what do you need to know
Right.
Scott: Yeah.
Brad: That would probably be kind of maybe irrelevant this question.
I don't know.
Scott: By the way, I only because, you know, I'm a big believer in like if you're going to like have coding standard rules,
then if, you know, make sure you can codify them into your linting and your and your static analysis toolset. And I had a developer on a team that was like really adamant about like he would like refuse pull requests that had like spelling mistakes in the comments or.
grammatical mistakes in the comments and stuff like that and i was just like oh this is driving me crazy so i installed like a linting plugin that does spell checking and
it was it's pretty good but it's surprising how many technical words it doesn't or how many times you would like like even if you kind of like are anti-abbreviation there's still times where it's like so this c spell thing just has like this extra extra thing to add your ignored words or your special words you know it's just like man so spell checking that's a fun that's a fun one
Brad: So
Scott: i
Brad: not a good one.
Scott: mean no it's a good one it's it's got some it's
some it's got some uh it's got some sharp edges to it so you know yeah
Brad: Yeah, that's an obvious edge,
right? You're going to get all these non-English words.
Scott: so i actually like that one that's a that that right there does sound like a good example like if you if someone for if someone was interviewing for you know
VS code or something like that or any kind of an editorial product then say oh yeah we're going to add a spell checker what do we need to do what do we need to know what are the what are the shapes and what are the boundaries of this thing how are you going to prompt your AI coding agent to build this etc
Brad: Very relevant.
I could use that in TaskRabbit. When you go to create a task,
there's a message box where you can type in a free text description of what you want.
And, yeah, hey, we want to add, there is no spell checker in there now.
We want to add a spell checker button or actually I led the witness.
We want to add, I said spell checker button.
We want to add spell checking
Scott: Yeah.
Brad: in there.
Scott: Yeah.
Brad: because it minimizes confusion and if we can minimize confusion we can increase conversion and as we've talked about on a recent episode decrease conversion increases customer conversion which lowers CAC and
Scott: Yep.
Yep.
Love it. There you go.
There's the business reason.
Now tell me how you're going to build it.
Or
Brad: you build
Scott: feel free to tell me your favorite AI tool that you're going to use to do it.
Yeah.
I love it. There you go.
Brad: Do you think for this specific,
I'm going to interview you for a second,
Scott: Okay.
Brad: for this specific implementation,
I'm really just getting at a pet peeve I have lately,
which is people using AI models for things which AI models are not appropriate
Scott: Oh,
Brad: for.
Scott: wait,
should you use like an AI LLM to be your spell checker?
Brad: Yes.
Scott: No,
not at all.
That's a bad idea.
Why is it a bad idea?
I'd say that's a bad idea.
Brad: Because I think spell checking is fairly deterministic.
Scott: Yes, and it's a well-solved problem that can be done in a like there are various spell checking libraries that are compete on speed and performance.
Brad: Oh boy, yeah.
So we did an AI hackathon,
lots of cool stuff,
but there were a handful of things where I was watching the demos and I was like, that's not a good use of AI.
That's a deterministic problem.
Scott: Exactly. You don't want a probability machine solving a determinant. I don't know.
Sometimes strawberry does have two R's in it and sometimes it has three R's in it. It depends.
Brad: Well, this actually begs a different question. Now we're way off of the interviewing topic.
This is bonus episode for the listeners who stayed to the end of this thing.
This has to do with the perfect is the enemy of good.
Scott: Yeah
Brad: Now maybe in spellchecking it's not,
but for other solutions where it's like,
well,
maybe probabilistic is good enough because you know why?
They could build it fast.
It would have taken them more time to go figure out what these different libraries were and then to get a license for them and to figure out how to get it into the build blah, blah, blah, blah, blah, blah, blah, blah.
Like, look, we had an opening eye token already.
It was really easy.
Scott: I don't know. If they gave me that answer,
then I would sort of be like, it's spell checking.
I'm not sold on that one.
Brad: Fair enough, fair enough.
Well,
Brad,
I feel like I learned something today.
Scott: Well,
thanks for playing.
Brad: It's not a podcast.
Scott: Unless we say rate
Brad: Smash that subscribe button.
Scott: and review.
All right.
Brad: Thanks for playing along.
Scott: Until next week.
Brad: Until next week.
Scott: Good
Brad: Bye,
Scott: to
Brad: everyone.
Scott: see you, Scott.
Bye, everybody.
This episode of How Many CTOs Does It Take Podcast was edited by Saffron Epigal.
Our theme song was AI generated by Brad.
Please follow us on all the social media platforms at at How Many CDOs Pod.
You can find us on YouTube,
LinkedIn,
Instagram,
Facebook,
Threads, X,
TikTok,
and Patreon or at our website at HowManyCDOsPod.com and remember to rate,
review,
and subscribe on the podcast platform of your choice.
Thanks for listening.