El diagnóstico de brecha de habilidades: descubre qué necesitas aprender realmente antes del próximo puesto
Por qué importa este prompt
Professionals routinely spend months on generic upskilling — a Python course here, a stats refresher there — without checking whether any of it maps to what a specific target role actually requires. A LinkedIn Learning survey found the average employee spends 24 minutes a week on self-directed learning, but without a gap analysis tied to a real target, much of that time goes toward skills that don't move the needle on the next promotion or job application, and critical gaps go unaddressed until they surface in an interview.
Para qué lo usamos
A data analyst with 4 years of SQL experience is applying for a senior analyst role that requires Python ETL pipelines and A/B testing design — two skills the job posting lists as core requirements but that aren't in their current toolkit. They have 5 hours a week and 90 days before they plan to apply.
Prompt
Role: You are a skills-development coach who has reviewed thousands of job postings and helped professionals close specific, measurable skill gaps rather than chase vague self-improvement. Context: I currently work as [YOUR CURRENT ROLE] with [X YEARS] of experience. My current skill set includes: [LIST YOUR KEY SKILLS, TOOLS, AND EXPERIENCE]. I am targeting this specific role or opportunity: [PASTE JOB POSTING, PROMOTION CRITERIA, OR TARGET ROLE DESCRIPTION]. I have [AVAILABLE TIME PER WEEK, e.g., 5 hours] to invest in closing gaps over the next [TIMEFRAME, e.g., 90 days]. Task: Compare my current skill set against the target role's actual requirements. Produce a gap analysis that separates what I already have from what I'm missing, then build a time-boxed learning plan to close the highest-priority gaps within my stated timeframe and weekly time budget. Constraints: - Do not list generic advice like "improve communication skills" — every gap must be specific and tied to something in the target role description. - Rank gaps by how much they would actually block me from getting or succeeding in the role, not by how interesting they are to learn. - Respect my stated weekly time budget. If the gaps can't realistically close in the timeframe given that budget, say so explicitly and tell me which gaps to defer. - Distinguish between gaps I can close through self-study versus gaps that require hands-on practice, a mentor, or real project experience — self-study alone won't fix all of them. - Do not recommend paid courses or certifications by brand name unless I specifically ask; prioritize free or already-accessible resources first. Output format: 1. **Strengths That Transfer** — skills I already have that map directly to the target role, with the specific requirement each one satisfies. 2. **Critical Gaps** (ranked) — for each: what's missing, why it matters for this specific role, and whether it's closable via self-study or requires practice/mentorship. 3. **Nice-to-Haves** — lower-priority gaps worth noting but not blocking. 4. **[TIMEFRAME] Learning Plan** — week-by-week or milestone-by-milestone breakdown that fits my stated weekly time budget, with a concrete, checkable deliverable at each milestone (not just "study X"). 5. **Reality Check** — one paragraph on whether this timeline is realistic given the gaps found, and what to deprioritize if time runs short.
Resultado
**Strengths That Transfer** - 4 years of SQL and dashboarding (Looker) directly satisfies the posting's "proficiency in BI tooling" requirement — no gap here. - Experience presenting metrics to non-technical stakeholders maps to "communicate insights to leadership," listed as a core responsibility.
**Critical Gaps (ranked)** 1. **Python for data pipelines (blocking).** The posting requires "building and maintaining ETL pipelines in Python," and your experience is SQL-only. This is self-study closable — Python's pandas/SQL overlap is substantial, so this isn't starting from zero, but it needs deliberate practice, not just reading. 2. **A/B testing statistical design (blocking).** The role owns experimentation strategy; you've only consumed test results, not designed them. This requires some self-study (power analysis, sample size calculation) but the sequencing and pitfalls are best learned by running a real test — pure reading won't be convincing in an interview. 3. **Stakeholder-level experiment readouts (moderate).** You present dashboards well, but translating a null or ambiguous A/B result into a confident recommendation is a distinct skill. Closable through deliberate practice: write 3 mock experiment readouts this month using public datasets.
**Nice-to-Haves** - Familiarity with Airflow (mentioned once in the posting, not emphasized) — defer unless time allows after the above three.
**90-Day Learning Plan** - Weeks 1–3 (5 hrs/week): Python fundamentals focused on pandas, not general syntax tutorials. Deliverable: rebuild one of your existing SQL reports as a Python script. - Weeks 4–6: A/B testing design — power analysis, minimum detectable effect, common pitfalls. Deliverable: design (not run) a full test plan for a hypothetical feature change at your current company. - Weeks 7–9: Run an actual small experiment if your current role permits, or use a public dataset to simulate one end-to-end. Deliverable: one complete experiment readout, written as if presenting to leadership. - Weeks 10–12: Buffer and portfolio polish. Combine the Python script and experiment readout into two concrete work samples you can reference in interviews.
**Reality Check** Given a 5-hour weekly budget, this plan is realistic but tight — the A/B testing gap is the riskiest because it depends on having something real to test, which you don't fully control. If you can't access a live experiment by week 7, substitute a simulated analysis using a public A/B testing dataset (several exist on Kaggle) rather than letting the plan stall. Defer Airflow entirely; it's mentioned once and isn't worth the time against two blocking gaps.
La mayoría de los planes de desarrollo de habilidades fracasan por una razón muy simple: no están ligados a nada concreto. La gente toma un curso de Python, un taller de liderazgo, un repaso de estadística —habilidades razonables en abstracto, pero sin ninguna garantía de que se correspondan con lo que realmente exige un puesto objetivo real. Este prompt corrige eso al forzar una comparación directa entre lo que tienes y lo que pide realmente una oferta concreta o unos criterios de promoción específicos.
Por qué existe cada sección del prompt
El Rol presenta a la IA como un coach que ha visto miles de ofertas de empleo; esto importa porque aleja al modelo de los consejos tipo póster motivacional y lo orienta hacia la comparación con requisitos, una tarea más mecánica y mucho más útil.
La sección de Contexto obliga a incluir tres datos específicos: tus habilidades actuales, el texto real del puesto objetivo (no una descripción vaga de él) y tu presupuesto de tiempo real. Pegar el texto literal de la oferta de empleo, en lugar de resumirlo tú mismo, es importante: resumir introduce tus propios puntos ciegos sobre lo que realmente se requiere.
Las Restricciones son las que hacen el trabajo más importante en este prompt. Prohibir consejos genéricos («mejora tu comunicación») obliga a que cada brecha se remita a un texto concreto del puesto objetivo. Clasificar según la gravedad del bloqueo, y no según el interés personal, mantiene el plan honesto: la brecha que más te apetece aprender no es necesariamente la que se interpone entre tú y ese puesto. Y forzar la distinción entre brechas que se cierran con autoestudio y brechas que requieren práctica real evita el error habitual de pensar que leer sobre el diseño de A/B testing es lo mismo que haber diseñado uno.
Qué hace que el formato de salida funcione
La estructura de cinco secciones —fortalezas, brechas críticas, aspectos deseables, cronograma y verificación de realidad— refleja la forma en que un buen gerente o mentor realmente estructuraría una retroalimentación: empezar por lo que funciona, clasificar lo que falta según su importancia y cerrar con una evaluación honesta de si el plan es viable. La sección de Verificación de realidad es la que la mayoría de los prompts omite, y es precisamente la que evita que esto se convierta en un resultado motivacional genérico: un modelo que siempre dice «sí, puedes lograrlo en 90 días» no sirve de mucho. Uno que dice «esta brecha en concreto es la arriesgada, y aquí tienes tu plan de respaldo» sí sirve.
Cómo reutilizar bien este prompt
Vuelve a ejecutar este prompt cada vez que evalúes un puesto nuevo, no solo una vez al año. El campo del puesto objetivo está pensado para cambiar constantemente: pega una oferta de empleo distinta, una rúbrica de promoción o incluso las expectativas declaradas en una evaluación de desempeño, y obtén cada vez un análisis de brechas nuevo y específico, en lugar de un plan genérico de aprendizaje y desarrollo que no se corresponde con ninguna oportunidad concreta.