Data & AI Governance Insights
Practical insights on AI governance, responsible AI, regulations, and building trustworthy AI systems.
Breaking Into AI Governance: Why Confidence Comes From Taking Action
On breaking into AI governance when everyone at the table seems more qualified than you.
I once sat on a panel where I was the last of seven people to speak. The six before me were accomplished, and as each of them answered the question in front of us, I did the worst possible thing: I stopped listening to them and started rehearsing myself. My only thought was a question that probably sounds familiar if you’re job-hunting right now: what could I possibly add that these people haven’t already said?
My nerves climbed with every confident answer that wasn’t mine. Then I remembered a piece of advice I’d been given years earlier: stop preparing your response and actually listen. So I moved my attention off myself and onto what was being said. The nerves settled almost immediately, and when the question reached me, I answered calmly, from my own experience. Nothing about me had changed in those few minutes. What changed was where I was pointing my attention.
I’m convinced that small shift contains almost everything a transitioner needs to hear about the AI governance job market. Not because it’s a clever trick, but because it quietly dismantles the belief that makes the search so painful: that you have to be the most qualified person in the room to deserve a place at the table.
The belief worth abandoning
Most people walk into a job search treating confidence as a prerequisite; something you’re supposed to feel before you apply, before you speak up, before you’re allowed to compete. If you don’t feel it, you assume you’re not ready.
That has it backwards. Confidence is an output, not an input. It’s what accumulates when you run a process a few times, not a personality trait you either possess or don’t. And the feeling of not having it is nearly universal right now: in one survey, fewer than one in six job seekers reported feeling confident about finding a role that fits. If your confidence is low, that isn’t a verdict on you. It’s the condition of the market.
So the question isn’t how to feel more qualified. It’s what small, repeatable things you can do at each stage of the search. There are three stages, and I’d give each of them exactly one move.
Stage one: narrow, don’t widen
The instinct when you start looking is to widen; dozens of tabs, hundreds of listings, the whole field sprawling out in front of you until it feels unknowable. The move I’d make is the opposite. Pick ten to fifteen roles that genuinely fit where you’re headed and read those closely instead of skimming a hundred.
Something useful happens when you do. The same language starts repeating: the NIST AI Risk Management Framework, the EU AI Act, ISO 42001, stakeholder communication, risk assessment; and the field shrinks from infinite to learnable. You also notice what these roles actually want. Job boards are full of AI governance postings asking for someone comfortable explaining AI governance in plain language, with the most-listed skills being stakeholder management and communication. You do not need to be a machine learning engineer to belong here; as one career analysis puts it, if you can assess risk and translate technical concepts into business language, you already have transferable skills. Narrowing your list is how the target stops moving; and a target that holds still is the beginning of confidence.
Stage two: translate one real thing
The first screen- a recruiter or a system doing a quick fit check is where many people quietly quit. They send applications into silence and read the silence as a judgment. It isn’t one. Recruiters are candid that rejection and silence are simply part of the process, and that no single role defines a career.
The one move here is to take something you’ve genuinely done and translate it into a proof story: not a list of duties, but a situation, an action, and an outcome. That isn’t a gimmick; it’s precisely what recruiters say they want, results and outcomes rather than responsibilities. You’re not inventing experience. You already did the work; you’re learning to say it in the language of the role. (This is the same argument I made in my video on certifications: demonstrated capability beats credentials, and your sample work, public writing, and current-role involvement become the stories you tell here.)
Stage three: run SRM; and notice that listening is the job
The second-stage interview, where someone hands you a scenario and watches how you think, is where the panel comes back. The move that calmed me; listening before answering turns out to be the most important interview skill there is, and it has a structure. I call it SRM.
System knowledge comes first: you ask questions to understand what the system does, what data it uses, and who it affects, because you can’t govern what you don’t understand. Risk assessment follows: with the system understood, you identify the risks to the people who use it and the people it acts on. Management closes it: who owns the risk, what controls go in, how it’s monitored over time.
Here is the part worth sitting with. That first letter; System knowledge is listening. It’s the panel move, turned into a discipline. Which means that when you open an interview by getting curious about the system instead of rushing to impress, you aren’t performing the job. You’re doing it, live, in the room. The interview stops being an audition you might fail and becomes the first time you get to do the work. (If you’ve seen my NIST video, SRM is the portable cousin of GM³; Govern, Map, Measure, Manage. SRM is the lens you carry into any question; GM³ is how you go deeper when they want the framework by name.)
Preparing for it is smaller than the fear suggests. Pick one AI system you already use, and run SRM on it out loud, once. That’s the rep. Structure beats brilliance; and the recruiters agree that the more interviews you do, the better you get at them.
Why the discomfort is the point
None of this makes the search comfortable.
Applying when you’re unsure, speaking up among people who seem further along, waiting in silence; it stays uncomfortable. But I’d reframe what that discomfort means. It isn’t evidence that you’re not ready. It’s the same discomfort the job itself requires, because AI governance is the work of being the person who asks the uncomfortable question; the one who says, wait, what is this system actually doing, and who could it harm? Everyone else is comfortable not asking. Getting comfortable being the one who does isn’t separate from the role; it is the role.
One career writer frames discomfort as data and argues you should let courage lead rather than wait for confidence to arrive. I’d put it more plainly: the people who get hired are usually not the most credentialed at the table, but the ones still running the process after others stopped.
So if you take one thing from this, let it be the thing the panel taught me. You’re not there to out-qualify the room. You’re there to listen well and answer from your own experience; and that turns out to be both how you steady your nerves and how you do the job. It's the same approach. The confidence shows up afterward.
Breaking Into AI Governance: Why Confidence Comes From Taking Action
On breaking into AI governance when everyone at the table seems more qualified than you.
I once sat on a panel where I was the last of seven people to speak. The six before me were accomplished, and as each of them answered the question in front of us, I did the worst possible thing: I stopped listening to them and started rehearsing myself. My only thought was a question that probably sounds familiar if you’re job-hunting right now: what could I possibly add that these people haven’t already said?
My nerves climbed with every confident answer that wasn’t mine. Then I remembered a piece of advice I’d been given years earlier: stop preparing your response and actually listen. So I moved my attention off myself and onto what was being said. The nerves settled almost immediately, and when the question reached me, I answered calmly, from my own experience. Nothing about me had changed in those few minutes. What changed was where I was pointing my attention.
I’m convinced that small shift contains almost everything a transitioner needs to hear about the AI governance job market. Not because it’s a clever trick, but because it quietly dismantles the belief that makes the search so painful: that you have to be the most qualified person in the room to deserve a place at the table.
The belief worth abandoning
Most people walk into a job search treating confidence as a prerequisite; something you’re supposed to feel before you apply, before you speak up, before you’re allowed to compete. If you don’t feel it, you assume you’re not ready.
That has it backwards. Confidence is an output, not an input. It’s what accumulates when you run a process a few times, not a personality trait you either possess or don’t. And the feeling of not having it is nearly universal right now: in one survey, fewer than one in six job seekers reported feeling confident about finding a role that fits. If your confidence is low, that isn’t a verdict on you. It’s the condition of the market.
So the question isn’t how to feel more qualified. It’s what small, repeatable things you can do at each stage of the search. There are three stages, and I’d give each of them exactly one move.
Stage one: narrow, don’t widen
The instinct when you start looking is to widen; dozens of tabs, hundreds of listings, the whole field sprawling out in front of you until it feels unknowable. The move I’d make is the opposite. Pick ten to fifteen roles that genuinely fit where you’re headed and read those closely instead of skimming a hundred.
Something useful happens when you do. The same language starts repeating: the NIST AI Risk Management Framework, the EU AI Act, ISO 42001, stakeholder communication, risk assessment; and the field shrinks from infinite to learnable. You also notice what these roles actually want. Job boards are full of AI governance postings asking for someone comfortable explaining AI governance in plain language, with the most-listed skills being stakeholder management and communication. You do not need to be a machine learning engineer to belong here; as one career analysis puts it, if you can assess risk and translate technical concepts into business language, you already have transferable skills. Narrowing your list is how the target stops moving; and a target that holds still is the beginning of confidence.
Stage two: translate one real thing
The first screen- a recruiter or a system doing a quick fit check is where many people quietly quit. They send applications into silence and read the silence as a judgment. It isn’t one. Recruiters are candid that rejection and silence are simply part of the process, and that no single role defines a career.
The one move here is to take something you’ve genuinely done and translate it into a proof story: not a list of duties, but a situation, an action, and an outcome. That isn’t a gimmick; it’s precisely what recruiters say they want, results and outcomes rather than responsibilities. You’re not inventing experience. You already did the work; you’re learning to say it in the language of the role. (This is the same argument I made in my video on certifications: demonstrated capability beats credentials, and your sample work, public writing, and current-role involvement become the stories you tell here.)
Stage three: run SRM; and notice that listening is the job
The second-stage interview, where someone hands you a scenario and watches how you think, is where the panel comes back. The move that calmed me; listening before answering turns out to be the most important interview skill there is, and it has a structure. I call it SRM.
System knowledge comes first: you ask questions to understand what the system does, what data it uses, and who it affects, because you can’t govern what you don’t understand. Risk assessment follows: with the system understood, you identify the risks to the people who use it and the people it acts on. Management closes it: who owns the risk, what controls go in, how it’s monitored over time.
Here is the part worth sitting with. That first letter; System knowledge is listening. It’s the panel move, turned into a discipline. Which means that when you open an interview by getting curious about the system instead of rushing to impress, you aren’t performing the job. You’re doing it, live, in the room. The interview stops being an audition you might fail and becomes the first time you get to do the work. (If you’ve seen my NIST video, SRM is the portable cousin of GM³; Govern, Map, Measure, Manage. SRM is the lens you carry into any question; GM³ is how you go deeper when they want the framework by name.)
Preparing for it is smaller than the fear suggests. Pick one AI system you already use, and run SRM on it out loud, once. That’s the rep. Structure beats brilliance; and the recruiters agree that the more interviews you do, the better you get at them.
Why the discomfort is the point
None of this makes the search comfortable.
Applying when you’re unsure, speaking up among people who seem further along, waiting in silence; it stays uncomfortable. But I’d reframe what that discomfort means. It isn’t evidence that you’re not ready. It’s the same discomfort the job itself requires, because AI governance is the work of being the person who asks the uncomfortable question; the one who says, wait, what is this system actually doing, and who could it harm? Everyone else is comfortable not asking. Getting comfortable being the one who does isn’t separate from the role; it is the role.
One career writer frames discomfort as data and argues you should let courage lead rather than wait for confidence to arrive. I’d put it more plainly: the people who get hired are usually not the most credentialed at the table, but the ones still running the process after others stopped.
So if you take one thing from this, let it be the thing the panel taught me. You’re not there to out-qualify the room. You’re there to listen well and answer from your own experience; and that turns out to be both how you steady your nerves and how you do the job. It's the same approach. The confidence shows up afterward.
Breaking Into AI Governance: Why Confidence Comes From Taking Action
On breaking into AI governance when everyone at the table seems more qualified than you.
I once sat on a panel where I was the last of seven people to speak. The six before me were accomplished, and as each of them answered the question in front of us, I did the worst possible thing: I stopped listening to them and started rehearsing myself. My only thought was a question that probably sounds familiar if you’re job-hunting right now: what could I possibly add that these people haven’t already said?
My nerves climbed with every confident answer that wasn’t mine. Then I remembered a piece of advice I’d been given years earlier: stop preparing your response and actually listen. So I moved my attention off myself and onto what was being said. The nerves settled almost immediately, and when the question reached me, I answered calmly, from my own experience. Nothing about me had changed in those few minutes. What changed was where I was pointing my attention.
I’m convinced that small shift contains almost everything a transitioner needs to hear about the AI governance job market. Not because it’s a clever trick, but because it quietly dismantles the belief that makes the search so painful: that you have to be the most qualified person in the room to deserve a place at the table.
The belief worth abandoning
Most people walk into a job search treating confidence as a prerequisite; something you’re supposed to feel before you apply, before you speak up, before you’re allowed to compete. If you don’t feel it, you assume you’re not ready.
That has it backwards. Confidence is an output, not an input. It’s what accumulates when you run a process a few times, not a personality trait you either possess or don’t. And the feeling of not having it is nearly universal right now: in one survey, fewer than one in six job seekers reported feeling confident about finding a role that fits. If your confidence is low, that isn’t a verdict on you. It’s the condition of the market.
So the question isn’t how to feel more qualified. It’s what small, repeatable things you can do at each stage of the search. There are three stages, and I’d give each of them exactly one move.
Stage one: narrow, don’t widen
The instinct when you start looking is to widen; dozens of tabs, hundreds of listings, the whole field sprawling out in front of you until it feels unknowable. The move I’d make is the opposite. Pick ten to fifteen roles that genuinely fit where you’re headed and read those closely instead of skimming a hundred.
Something useful happens when you do. The same language starts repeating: the NIST AI Risk Management Framework, the EU AI Act, ISO 42001, stakeholder communication, risk assessment; and the field shrinks from infinite to learnable. You also notice what these roles actually want. Job boards are full of AI governance postings asking for someone comfortable explaining AI governance in plain language, with the most-listed skills being stakeholder management and communication. You do not need to be a machine learning engineer to belong here; as one career analysis puts it, if you can assess risk and translate technical concepts into business language, you already have transferable skills. Narrowing your list is how the target stops moving; and a target that holds still is the beginning of confidence.
Stage two: translate one real thing
The first screen- a recruiter or a system doing a quick fit check is where many people quietly quit. They send applications into silence and read the silence as a judgment. It isn’t one. Recruiters are candid that rejection and silence are simply part of the process, and that no single role defines a career.
The one move here is to take something you’ve genuinely done and translate it into a proof story: not a list of duties, but a situation, an action, and an outcome. That isn’t a gimmick; it’s precisely what recruiters say they want, results and outcomes rather than responsibilities. You’re not inventing experience. You already did the work; you’re learning to say it in the language of the role. (This is the same argument I made in my video on certifications: demonstrated capability beats credentials, and your sample work, public writing, and current-role involvement become the stories you tell here.)
Stage three: run SRM; and notice that listening is the job
The second-stage interview, where someone hands you a scenario and watches how you think, is where the panel comes back. The move that calmed me; listening before answering turns out to be the most important interview skill there is, and it has a structure. I call it SRM.
System knowledge comes first: you ask questions to understand what the system does, what data it uses, and who it affects, because you can’t govern what you don’t understand. Risk assessment follows: with the system understood, you identify the risks to the people who use it and the people it acts on. Management closes it: who owns the risk, what controls go in, how it’s monitored over time.
Here is the part worth sitting with. That first letter; System knowledge is listening. It’s the panel move, turned into a discipline. Which means that when you open an interview by getting curious about the system instead of rushing to impress, you aren’t performing the job. You’re doing it, live, in the room. The interview stops being an audition you might fail and becomes the first time you get to do the work. (If you’ve seen my NIST video, SRM is the portable cousin of GM³; Govern, Map, Measure, Manage. SRM is the lens you carry into any question; GM³ is how you go deeper when they want the framework by name.)
Preparing for it is smaller than the fear suggests. Pick one AI system you already use, and run SRM on it out loud, once. That’s the rep. Structure beats brilliance; and the recruiters agree that the more interviews you do, the better you get at them.
Why the discomfort is the point
None of this makes the search comfortable.
Applying when you’re unsure, speaking up among people who seem further along, waiting in silence; it stays uncomfortable. But I’d reframe what that discomfort means. It isn’t evidence that you’re not ready. It’s the same discomfort the job itself requires, because AI governance is the work of being the person who asks the uncomfortable question; the one who says, wait, what is this system actually doing, and who could it harm? Everyone else is comfortable not asking. Getting comfortable being the one who does isn’t separate from the role; it is the role.
One career writer frames discomfort as data and argues you should let courage lead rather than wait for confidence to arrive. I’d put it more plainly: the people who get hired are usually not the most credentialed at the table, but the ones still running the process after others stopped.
So if you take one thing from this, let it be the thing the panel taught me. You’re not there to out-qualify the room. You’re there to listen well and answer from your own experience; and that turns out to be both how you steady your nerves and how you do the job. It's the same approach. The confidence shows up afterward.
Breaking Into AI Governance: Why Confidence Comes From Taking Action
On breaking into AI governance when everyone at the table seems more qualified than you.
I once sat on a panel where I was the last of seven people to speak. The six before me were accomplished, and as each of them answered the question in front of us, I did the worst possible thing: I stopped listening to them and started rehearsing myself. My only thought was a question that probably sounds familiar if you’re job-hunting right now: what could I possibly add that these people haven’t already said?
My nerves climbed with every confident answer that wasn’t mine. Then I remembered a piece of advice I’d been given years earlier: stop preparing your response and actually listen. So I moved my attention off myself and onto what was being said. The nerves settled almost immediately, and when the question reached me, I answered calmly, from my own experience. Nothing about me had changed in those few minutes. What changed was where I was pointing my attention.
I’m convinced that small shift contains almost everything a transitioner needs to hear about the AI governance job market. Not because it’s a clever trick, but because it quietly dismantles the belief that makes the search so painful: that you have to be the most qualified person in the room to deserve a place at the table.
The belief worth abandoning
Most people walk into a job search treating confidence as a prerequisite; something you’re supposed to feel before you apply, before you speak up, before you’re allowed to compete. If you don’t feel it, you assume you’re not ready.
That has it backwards. Confidence is an output, not an input. It’s what accumulates when you run a process a few times, not a personality trait you either possess or don’t. And the feeling of not having it is nearly universal right now: in one survey, fewer than one in six job seekers reported feeling confident about finding a role that fits. If your confidence is low, that isn’t a verdict on you. It’s the condition of the market.
So the question isn’t how to feel more qualified. It’s what small, repeatable things you can do at each stage of the search. There are three stages, and I’d give each of them exactly one move.
Stage one: narrow, don’t widen
The instinct when you start looking is to widen; dozens of tabs, hundreds of listings, the whole field sprawling out in front of you until it feels unknowable. The move I’d make is the opposite. Pick ten to fifteen roles that genuinely fit where you’re headed and read those closely instead of skimming a hundred.
Something useful happens when you do. The same language starts repeating: the NIST AI Risk Management Framework, the EU AI Act, ISO 42001, stakeholder communication, risk assessment; and the field shrinks from infinite to learnable. You also notice what these roles actually want. Job boards are full of AI governance postings asking for someone comfortable explaining AI governance in plain language, with the most-listed skills being stakeholder management and communication. You do not need to be a machine learning engineer to belong here; as one career analysis puts it, if you can assess risk and translate technical concepts into business language, you already have transferable skills. Narrowing your list is how the target stops moving; and a target that holds still is the beginning of confidence.
Stage two: translate one real thing
The first screen- a recruiter or a system doing a quick fit check is where many people quietly quit. They send applications into silence and read the silence as a judgment. It isn’t one. Recruiters are candid that rejection and silence are simply part of the process, and that no single role defines a career.
The one move here is to take something you’ve genuinely done and translate it into a proof story: not a list of duties, but a situation, an action, and an outcome. That isn’t a gimmick; it’s precisely what recruiters say they want, results and outcomes rather than responsibilities. You’re not inventing experience. You already did the work; you’re learning to say it in the language of the role. (This is the same argument I made in my video on certifications: demonstrated capability beats credentials, and your sample work, public writing, and current-role involvement become the stories you tell here.)
Stage three: run SRM; and notice that listening is the job
The second-stage interview, where someone hands you a scenario and watches how you think, is where the panel comes back. The move that calmed me; listening before answering turns out to be the most important interview skill there is, and it has a structure. I call it SRM.
System knowledge comes first: you ask questions to understand what the system does, what data it uses, and who it affects, because you can’t govern what you don’t understand. Risk assessment follows: with the system understood, you identify the risks to the people who use it and the people it acts on. Management closes it: who owns the risk, what controls go in, how it’s monitored over time.
Here is the part worth sitting with. That first letter; System knowledge is listening. It’s the panel move, turned into a discipline. Which means that when you open an interview by getting curious about the system instead of rushing to impress, you aren’t performing the job. You’re doing it, live, in the room. The interview stops being an audition you might fail and becomes the first time you get to do the work. (If you’ve seen my NIST video, SRM is the portable cousin of GM³; Govern, Map, Measure, Manage. SRM is the lens you carry into any question; GM³ is how you go deeper when they want the framework by name.)
Preparing for it is smaller than the fear suggests. Pick one AI system you already use, and run SRM on it out loud, once. That’s the rep. Structure beats brilliance; and the recruiters agree that the more interviews you do, the better you get at them.
Why the discomfort is the point
None of this makes the search comfortable.
Applying when you’re unsure, speaking up among people who seem further along, waiting in silence; it stays uncomfortable. But I’d reframe what that discomfort means. It isn’t evidence that you’re not ready. It’s the same discomfort the job itself requires, because AI governance is the work of being the person who asks the uncomfortable question; the one who says, wait, what is this system actually doing, and who could it harm? Everyone else is comfortable not asking. Getting comfortable being the one who does isn’t separate from the role; it is the role.
One career writer frames discomfort as data and argues you should let courage lead rather than wait for confidence to arrive. I’d put it more plainly: the people who get hired are usually not the most credentialed at the table, but the ones still running the process after others stopped.
So if you take one thing from this, let it be the thing the panel taught me. You’re not there to out-qualify the room. You’re there to listen well and answer from your own experience; and that turns out to be both how you steady your nerves and how you do the job. It's the same approach. The confidence shows up afterward.
Join the AI Governance Insider
Weekly insights on regulations, career moves, and what's actually working in responsible AI.
Helping professionals build meaningful careers in AI, AI Governance, and organizations build AI systems people can trust.
Resources
Services
Connect
© 2026 Obi Ogbanufe. All rights reserved.