Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / Bootcamp Grads in Creative Tech Roles
Transcript
- Lucas: If we've helped you think through a career move or decision, you know that most of our advice leans heavily toward the structural side of tech: backend systems, data pipelines, security protocols. But today, I want to talk about the other half of the equation. The creative half. Specifically, the roles that sit right at the intersection of code and visual storytelling. Luna: Right, because everyone talks about becoming a full-stack developer, but very few people discuss how to actually make things look good while they work. It is a huge blind spot in the bootcamp curriculum. Lucas: Exactly. And it is a blind spot that costs companies money. When I was prepping for this episode, I looked at job postings for Technical Artistry and UX Engineering. The requirement lists are bizarre. They want someone who can write clean Python scripts but also understand color theory and spatial awareness. It is not just about making pretty pictures. It is about building tools that help designers and developers speak the same language. Luna: I have seen this in my own network. A friend of mine switched from graphic design to technical production. She learned enough JavaScript to automate her workflow, and now she earns forty percent more than she did as a pure designer. Lucas: That is the key metric we need to focus on today. The premium for hybrid skills. In September of twenty twenty-six, the market is saturated with junior coders who can build a basic API. But there is a shortage of people who can take a creative brief and translate it into a functional, beautiful digital experience without needing three engineers to fix the implementation details. Let us look at one specific role: Technical Artistry in gaming and immersive media. Luna: Wait, so you are saying the entry point isn't just writing code, but understanding the software pipeline? Like Unreal Engine or Unity? Lucas: Precisely. In gaming, a Technical Artist does not just model characters. They write shaders. They optimize rendering pipelines. They solve the problem where an artist makes something that looks amazing but crashes the frame rate. If you can do both, you become indispensable. I remember when I first tried to explain this to a recruiter. She asked me what my favorite programming language was. I told her it was whatever language made the graphics engine render faster. Luna: That is a great answer. It shows you care about the output, not just the syntax. But how does a bootcamp grad actually break into that? You cannot just sign up for a 'Learn Shaders' course. Lucas: You are right. The path is messier. It usually involves starting in a generalist frontend role and then aggressively pivoting your projects. I built my portfolio by taking simple UI components and adding complex animation libraries to them. I didn't just build a button. I built a button that responded to physics simulations. It was overkill for a standard website, but it proved I understood the underlying math and the visual result simultaneously. Luna: So the project needs to be demonstrably harder than what a typical bootcamp graduate produces. It needs to show friction management. Lucas: Friction management is exactly the right term. You are removing the friction between human creativity and machine execution. Another area growing fast is in advertising tech. Brands are no longer satisfied with static banners. They want interactive, real-time personalized experiences. That requires engineers who understand consumer psychology and designers who understand DOM manipulation. The roles are often titled 'Creative Technologist' or 'Interactive Producer'. Luna: I have heard those titles before. But they often sound like buzzwords. How do you know if it is a real engineering role versus just managing vendors? Lucas: Good question. The trick is in the job description keywords. If they mention WebGL, Three.js, or custom CMS integrations, it is likely a hands-on role. If they only mention 'client liaison' or 'project management', it is probably not. You want a role where you are touching the codebase. I once interviewed for a position that turned out to be purely sales. The interviewer spent ten minutes asking me about my networking skills instead of my git history. I walked out immediately. Luna: Smart move. Wasting time on misaligned roles is the biggest trap for career switchers. What about salary expectations? Are these roles paying more than standard web development? Lucas: Generally, yes. Because the talent pool is smaller. A standard web developer competes with thousands of bootcamp grads. A Creative Technologist competes with maybe a hundred people who truly understand both sides. In the current market, that scarcity drives compensation up. I am seeing base salaries for mid-level creative technologists ranging from one hundred and ten thousand to one hundred and thirty thousand dollars, depending on location and seniority. Luna: That is a significant jump. But it assumes you already have some design background. What if someone comes from a pure backend background and wants to pivot? Lucas: Then you lean into the tooling side. Backend engineers often struggle with frontend aesthetics, but they excel at logic. You can specialize in 'Design Systems Engineering'. You build the component libraries that designers use. You write the documentation. You ensure consistency across products. It is a highly respected role because it requires discipline and architectural thinking. You are not painting the walls; you are building the blueprint for the entire house. Luna: So you are essentially the bridge. You translate the architect's vision into buildable instructions. That sounds like a lot of responsibility for someone who might not consider themselves 'creative'. Lucas: It is a myth that you need to be an artist to work in creative tech. You need to be curious. You need to enjoy looking at why something works visually. I used to hate design. I thought it was subjective nonsense. Then I realized that good design is just efficient communication. Once I started viewing pixels as data points, it clicked. The emotional response of a user is a measurable outcome of layout choices. Luna: That reframing is powerful. It takes the fear out of the creative process. So, practically speaking, what should a listener do tomorrow morning if they want to start this pivot? Lucas: Start by auditing your current projects. Do you have any side projects that are purely functional? Pick one and add a layer of polish. Add micro-interactions. Improve the typography. Make it feel alive. Then, document the process. Write a blog post about how you solved the technical challenge of implementing that animation. That blog post becomes part of your portfolio. It shows you can articulate the 'why' behind the 'how'. Luna: Documentation is such an underrated skill. It proves you can communicate complex ideas to non-technical stakeholders. Which is basically the whole job. Lucas: Absolutely. And do not underestimate the power of open source. Contribute to creative coding libraries. Even small fixes to documentation or bug reports in projects like p5.js or D3.js get noticed. Recruiters in this space hang out in GitHub repositories, not just LinkedIn. They look for contributors who engage with the community. Luna: That is a concrete action item. Go to GitHub, find a library you use, and submit a pull request. It is low risk, high reward. But Lucas, what about the imposter syndrome? How do you deal with feeling like you are pretending to be a designer when you are really a coder? Lucas: You embrace it. You say, 'I am a coder who cares about design.' That is a strength, not a weakness. Designers often lack the rigor to build scalable systems. Engineers often lack the empathy for the user interface. You bring both. When you walk into an interview, do not apologize for your background. Frame it as a unique perspective. 'Because I come from engineering, I build designs that are robust and performant.' Luna: I love that framing. It turns a potential weakness into a value proposition. It shifts the conversation from 'what you don't know' to 'what you offer that others don't'. Lucas: Exactly. And let us talk about the interview itself. Creative tech interviews are different. You will likely have a practical test. You might be asked to recreate a landing page or animate a dataset. Do not rush to code. Ask questions about the user experience first. Show that you are thinking about the end goal before you start typing. Interviewers watch how you approach ambiguity. If you stare at the screen for five minutes in silence, you fail. If you talk through your thought process, even if you get stuck, you pass. Luna: Communication during the test is critical. It shows you are collaborative. No one hires a lone wolf, especially in a role that requires bridging teams. Lucas: Correct. And finally, let us address the remote aspect. Many of these roles are fully remote. You might be working with a team in London, San Francisco, and Tokyo. This requires strong asynchronous communication skills. You need to leave clear comments in your code. You need to record Loom videos explaining your design decisions. You need to be proactive in updating status channels. Remote creative work relies heavily on trust and clarity. Luna: So you are building a reputation as much as you are building a portfolio. The online footprint matters just as much as the GitHub repo. Lucas: It does. I recommend maintaining a personal site that acts as your hub. Link to your GitHub, link to your case studies, link to your blog. Keep it simple. Clean typography. Fast load times. Your personal site is your first technical art piece. If it is slow or broken, no one will believe you can fix theirs. Luna: That is a great metaphor. Your website is your proof of concept. If you cannot manage your own digital presence, how can you manage a client's brand? Lucas: Right. It is all connected. Now, before we wrap up, I want to touch on the financial sustainability of this path. Some people worry that creative tech is a niche market. But look at the broader trend. Every company is becoming a media company. Banks have apps. Retailers have immersive shopping experiences. Healthcare providers have patient portals. The demand for people who can build these interfaces is not going away. It is expanding. Luna: It is shifting from luxury to necessity. Good user experience is now a baseline requirement for customer retention. Companies cannot afford to ignore it anymore. Lucas: Exactly. And that brings me to a quick note about support. We produce these episodes every day to help you navigate these changes. A couple of dollars a month is genuinely what keeps these going. If you have gotten something out of this conversation, consider supporting us at buy me a coffee dot com slash fexingo. It helps us keep the lights on and the research deep. Luna: Yeah, your support directly impacts the quality of the data and the guests we can bring on. It makes a real difference. Lucas: Thanks for listening. So, if you are sitting on the fence about switching fields, ask yourself this: are you willing to learn the language of both logic and beauty? Because that is where the future of work is heading.