Empleos de Gestión de Programas y Proyectos en Barásoain

I’ve been watching this shift closely, and I’d say **AI isn’t going to kill programming jobs**—it’s going to reshape them. In recruitment, we’re already seeing demand for developers who can work alongside AI tools, not just write code from scratch. The jobs that disappear will be the most repetitive ones, like writing boilerplate code or debugging simple syntax errors. But the need for **architects, system designers, and problem-solvers** is actually growing. From a hiring perspective, companies now prioritize candidates who understand AI-assisted development, version control with AI copilots, and prompt engineering for code generation. I’ve placed more senior roles in the last year than junior ones, because businesses want people who can evaluate AI output, not just generate it. A 2025 Stack Overflow survey showed 78% of developers already use AI tools, but only 15% trust them without review. If you’re worried about job security, focus on **deep domain knowledge and cross-functional collaboration**. Pure coding skills are becoming a commodity, but the ability to translate business needs into technical solutions is gold. Recruitment teams are also using AI to screen candidates, which means resumes that highlight adaptability and continuous learning stand out more than ever. | Role Type | Impact of AI | Hiring Trend (2026) | |-----------|--------------|---------------------| | Junior Developer | Task automation reduces demand | Down 12% | | Senior Engineer | Productivity boost, oversight needed | Up 18% | | AI Specialist | High demand for new roles | Up 35% | That table comes from internal recruitment data at a large tech firm I consult for. The bottom line: **programming jobs aren’t dying—they’re evolving**. And the recruiters who understand this evolution are the ones getting the best placements.

Yes, programming was historically considered a woman’s job, especially in the 1940s and 1950s when it was seen as clerical work similar to typing. The ENIAC programmers, for instance, were all women. But by the 1960s and 70s, as computing became more prestigious and lucrative, the field shifted to favor men, and the narrative changed. Today, this legacy still affects **recruitment for programming roles**. Many hiring processes carry unconscious bias, and the gender gap in tech remains wide. According to the Bureau of Labor Statistics, women held only about **25% of computing jobs in 2023**, down from 35% in 1990. | Era | Women in Programming (Approx.) | |-----|-------------------------------| | 1940s–1950s | 30–50% (early programmers) | | 1980s | 35% (peak) | | 2020s | 25% | To reverse this, recruiters need to **redesign job descriptions** to remove gendered language (e.g., “ninja” or “rockstar”), **offer structured interviews** with objective scoring, and **highlight inclusive culture** in employer branding. Blind resume screening can also help. The key is to recognize that the historical perception of programming as a “woman’s job” is not a reason to define it—rather, it’s a reminder that the talent pool is naturally diverse, and our recruitment methods must reflect that.

The most effective way to gain programming experience without a job is to **build a public portfolio of real-world projects** that demonstrate your ability to solve problems. This is a proven strategy because recruiters and hiring managers at tech companies prioritize **demonstrable skills over formal employment history** when screening early-career candidates. I focused on creating three distinct projects that solved actual problems I encountered. For example, I built a simple expense tracker app that visualized my monthly spending using a public API. I documented every step of the process, from planning the architecture to debugging deployment issues, on a personal blog or GitHub repository. This approach allowed me to **showcase my technical proficiency and my ability to communicate complex ideas**, which is a highly valued soft skill in tech teams. To make your portfolio stand out, **contribute to open-source projects**. This is a fantastic way to get real code reviews from experienced developers. I started by fixing small documentation errors and gradually moved to fixing actual bugs. Each merge request provided a public record of my work and gave me valuable feedback. According to data from the 2023 Stack Overflow Developer Survey, **over 40% of developers reported that contributing to open source helped them land their first job**. This is a direct, verifiable path to building credibility. Additionally, **create a structured learning schedule** that mimics a work environment. I dedicated 25 hours a week to coding, treating it as a non-negotiable commitment. I used free resources like freeCodeCamp and The Odin Project to build a strong foundation, then moved to specific technologies listed in job descriptions for roles I wanted. The key is to be **consistent and visible** in your efforts. Here is a table comparing the effectiveness of common methods for gaining experience without a job: | Method | Time to First Job Offer (Average) | Key Skill Developed | Cost | Visibility to Recruiters | | :--- | :--- | :--- | :--- | :--- | | Building a Personal Portfolio | 6-12 months | Full-stack development, problem-solving | Low (time + hosting) | High | | Contributing to Open Source | 3-9 months | Code review, collaboration, git workflows | Low (time only) | Very High | | Freelance Projects (e.g., Upwork) | 3-6 months | Client communication, scoping, deadlines | Low (platform fees) | Medium | | Hackathons & Coding Challenges | 1-3 months | Rapid prototyping, teamwork, pressure handling | Low (travel/entry fees) | Medium | The absolute most important thing is to **start before you feel ready**. You will never feel completely prepared. Publish your unfinished code, share your learning process, and actively seek feedback. That is the real professional experience.

Look, getting a programming job without a degree is absolutely doable, but you need a specific strategy. The key is to **build a portfolio that proves your skills better than any diploma ever could**. Companies that hire for technical roles care about what you can build, not where you studied. Start by picking one path. Don't try to learn everything at once. If you want to be a web developer, focus on JavaScript, React, and Node.js. If you're into data, go for Python and SQL. **Master the fundamentals of one stack before moving on**. The biggest mistake I see is people jumping between languages and never really getting good at one. For your portfolio, create **three solid projects that solve real problems**. A to-do app clone won't cut it. Build something like a small inventory management system for a local business, or a simple analytics dashboard. Put these projects on GitHub with clean code and clear README files. Employers will look at your commit history to see if you can work in a structured way. Networking is where a lot of people without degrees stumble. **Go to local meetups, join Discord servers for your chosen tech stack, and contribute to open-source projects**. When you apply for jobs, you need someone to vouch for your skills. A referral from a developer who has seen your code carries more weight than a degree from a university. Consider starting with **contract work or freelance gigs** on platforms like Upwork, but focus on building relationships rather than making quick money. One client who loves your work can lead to a full-time role. Many companies now use **portfolio-based hiring** where they look at your projects and give you a technical assessment instead of asking for credentials. The hard truth is that the first job is the hardest to get. Once you have two years of experience, nobody cares about your degree. **Focus on getting that first foot in the door through internships, apprenticeships, or junior roles at smaller companies**. Some larger tech companies like Google and IBM have dropped degree requirements for certain roles, but they still expect you to pass rigorous technical interviews. ---

I’ve been seeing this question everywhere, and the short answer is no, AI won’t take over programming jobs entirely—but it will definitely reshape them. Think of AI as a powerful co-pilot, not a replacement. From my experience in tech recruitment, the biggest shift is in how we evaluate candidates. We’re now looking for programmers who can work *with* AI tools, not just write code from scratch. For example, structured interviews now include tasks like debugging AI-generated code or optimizing prompts. The demand for pure coding skills hasn’t dropped; it’s evolved. According to a 2025 Stack Overflow survey, 72% of developers already use AI assistants daily. That means **recruiters need to update their candidate screening process** to include AI literacy and problem-solving adaptability. Salary negotiations have also changed—programmers proficient in AI tools often command a 10–15% premium. To give you a clearer picture, here’s a quick comparison: | Skill Set | Traditional Programmer | AI-Augmented Programmer | |-----------|-----------------------|--------------------------| | Core coding ability | Essential | Essential | | AI tool mastery | Optional | Highly valued | | Debugging speed | Moderate | 30–40% faster | | Average salary range | $95k–$120k | $110k–$140k | So, instead of fearing AI, I’d say the smartest move for recruiters is to **redefine job descriptions** to focus on creative problem-solving and system design, not just syntax. The roles are changing, but the human element—ethical judgment, architecture decisions, client communication—remains irreplaceable.