Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / Bootcamp Grads Transitioning Into AI Prompt Engineering
Transcript
- Lucas: So you graduated from a coding bootcamp — maybe six months ago, maybe two years ago — and the job you thought you'd line up isn't materialising the way you hoped. Front-end roles are hyper-competitive, data analyst postings ask for three years of experience. There's a emerging niche that's tailor-made for bootcamp grads, and it's not on most people's radar: AI prompt engineering. Luna: I keep hearing that term thrown around, but I don't think most people actually know what it entails. Is it just typing clever questions into ChatGPT? Lucas: That's the $64,000 misconception. Prompt engineering is closer to software testing than to creative writing. You're systematically probing a large language model — an LLM — to understand its failure modes, then crafting prompts that reliably steer it toward correct, useful outputs. It's an applied debugging skill. Luna: So bootcamp grads are actually well-positioned here — they've spent months debugging code, edge cases, unexpected behavior. Lucas: Exactly. Let me give you a concrete example. A bootcamp grad I know, let's call her Priya, joined a mid-size SaaS company as a customer success associate — not a tech role. But she noticed the support team was drowning in repetitive tickets about account settings. She spent a weekend building a prompt chain that walked a support rep through structured troubleshooting steps. Within a month, average resolution time dropped by 40 percent. Luna: And management noticed, I'm guessing. Lucas: They promoted her to a 'customer operations engineer' — effectively her company's first internal prompt engineer. She now designs prompt templates for the whole support org. No formal AI training, just a bootcamp background and a willingness to treat the model like a flaky piece of software. Luna: So what are the actual skills a bootcamp grad needs to develop to move into this? Lucas: Three things. First: understanding model behavior. That means spending time with different LLMs — GPT-4, Claude, Llama — and noticing patterns. When does a model hallucinate? When does it get too verbose? When does it refuse a perfectly reasonable request? You build an intuition for its quirks. Luna: That sounds a lot like learning the quirks of a programming language or a framework. Lucas: It's almost identical. Second skill: iterative testing. You treat each prompt like a unit test. You write a hypothesis — 'if I phrase the instruction this way, the output should be a one-paragraph summary' — then you run it against ten different inputs, observe failures, refine. It's a tight feedback loop, exactly like test-driven development. Luna: And the third? Lucas: Domain-specific vocabulary. The best prompt engineers aren't generalists — they're experts in a particular field who learn to translate that expertise into prompts. Priya knew customer support terminology inside out. A prompt engineer at a legal tech company needs to know 'motion to dismiss', 'discovery', 'privilege log'. The model needs that context to produce relevant outputs. Luna: So the advice is: don't just learn prompting in the abstract. Pick an industry you already understand, or are willing to study deeply. Lucas: Right. And bootcamp grads often have an edge there because many career-changers bring prior domain experience from their old field — healthcare, education, finance. That combination of coding logic and real-world domain knowledge is exactly what companies want. Luna: One thing I'm wondering: do you need to understand the underlying machine learning math to do this well? Lucas: No. And I say that carefully. You don't need to know backpropagation or transformer architectures. But you should understand what a token is — roughly — and that the model has a context window. That's fifteen minutes of reading. The rest is empirical tinkering. Luna: So bootcamp grads shouldn't feel intimidated by the AI hype. This is a skill they can build with the tools they already have. Lucas: Exactly. And here's the thing that makes this path particularly viable right now — July 2026 — is that companies are still figuring out how to staff this function. They don't have established job ladders. Many postings call it 'AI operations specialist' or 'conversation designer' or 'machine learning prompt engineer'. The role is fluid enough that a bootcamp grad with a strong portfolio can define the job themselves. Luna: How do you build a portfolio for prompt engineering? It's not like you can show a GitHub repo of code. Lucas: You absolutely can. Start a public log on GitHub or a personal blog where you document prompt experiments. For example: 'I tested five different prompt structures for summarising medical research papers. Here's what I learned.' Then show before and after outputs. That's your portfolio. It demonstrates systematic thinking and communication skills — exactly what the job requires. Luna: That's smart. And it's low-friction — you don't need a company API key or expensive tools. Just a free tier of an LLM and a willingness to document. Lucas: Totally. And if you're looking for a specific starting point, try this: pick a dataset of fifty customer support emails — there are public ones on Kaggle — and design a prompt that automatically categorises them into 'billing', 'technical issue', 'account management'. Then iterate until your accuracy hits 90 percent. That's a project you can walk into any interview with. Luna: I want to push back on one thing though. Some people argue that prompt engineering is a passing fad — that as models get better, you'll just be able to say what you want in plain English and get the answer. Lucas: I hear that argument a lot. And I think it misunderstands what prompt engineering really is. Even as models improve, you still need to constrain outputs for production systems. You need reliability. You need to prevent the model from going off the rails. A company integrating an LLM into its customer-facing chatbot needs someone who can write prompts that are robust against adversarial inputs and edge cases. That's not going away. Luna: So it's more like quality assurance for AI than a creative writing gig. Lucas: Exactly. And QA has been a stable career path in tech for decades. The skills are transferable, too — if you later want to move into product management or AI product design, prompt engineering gives you direct experience with user-model interaction. Luna: Let's talk about the job market. What kinds of companies are hiring for this right now, and what are they paying? Lucas: It's still early. I've seen roles at ai native startups, big consulting firms building internal tools, and enterprise SaaS companies adding AI features. Salaries range widely — from seventy thousand at a small startup to well over one hundred fifty thousand at a tech giant for a senior role. But the median for someone with two to three years of experience seems to be around ninety-five to one hundred ten thousand. Luna: And how does that compare to a typical entry-level software engineering role? Lucas: It's comparable, maybe slightly lower at the entry level. But the bar to entry is lower — you don't need a computer science degree or a LeetCode grind. And you can often transition from prompt engineering into a broader AI product role, which pays even more. So it's a viable on-ramp. Luna: One concern bootcamp grads might have: is this role going to be automated away by better models? Isn't that ironic? Lucas: It is ironic. And it's a fair question. But look at it this way: as models get better, the number of applications increases. Companies find new ways to use AI. Each new application creates demand for someone who understands the model's strengths and weaknesses in that context. The job evolves, but it doesn't disappear. It's like how search engine optimization didn't disappear when Google got better — it just got more sophisticated. Luna: Good analogy. So for a bootcamp grad listening right now, what's the single most actionable thing they can do this week? Lucas: One thing: find a problem you care about — something small and tangible — and build a prompt-based tool that solves it. It could be a study guide generator, a meal planner, a meeting note taker. Use it yourself for a week. Then write about what broke. That experience is worth more than any certification. Luna: And if they're not in a position to do that — maybe they're still job hunting and short on time — what's a smaller step? Lucas: Read the documentation. Every major LLM provider publishes guidelines on prompt design — OpenAI's prompting guide, Anthropic's prompt engineering resources. Read those with the same attention you'd give to a coding tutorial. They're short, practical, and full of examples you can adapt. Luna: I think that's a solid plan. And honestly, this episode has been really helpful for me too — I've been curious about this field but never knew where to start. Lucas: Glad to hear it. And if today's conversation saved you some time or gave you a clear direction, that's exactly why we do this show ad-free. We keep it that way thanks to listeners who support us — if it was worth a coffee to you, you know the link: buy me a coffee dot com slash fexingo. No pressure, just a way to keep the show going. Luna: Yeah, it genuinely helps. And it keeps us independent — no sponsors telling us what to cover. Lucas: Right. So back to that prompt project idea — if you build one, tag us online. We'd love to see what you create. Luna: I want to add one more resource. The subreddit r/PromptEngineering has a weekly thread where people post their experiments and get feedback. It's a great place to learn and to show your work. Lucas: Good call. And one thing I'd emphasise: don't compare yourself to people who've been in AI for years. You're bringing a different toolkit — you understand user needs, you can iterate fast, you're not afraid to break things. That's exactly what the field needs right now. Luna: So the takeaway is: prompt engineering is a real, accessible career path for bootcamp grads. It leverages your coding foundation and your ability to communicate and test systematically. Lucas: And it pays well, it's growing, and you can start building a portfolio today with zero budget. If you've been feeling stuck in your job search, this might be the niche that unlocks your next move. Luna: I'm sold. I might start that experiment tonight. Lucas: Do it. And let us know how it goes. For Fexingo's Career Change Podcast, I'm Lucas. Luna: And I'm Luna. See you next time.