Career command
Nick Vidal
USAF, retired 2026 · Solutions consulting / solutions engineering · Remote from New Mexico
Specialist: AlisonEdits stay in this browser · showing original snapshot

Résumé review with Alison

Open
7
still recommended
Discuss next
0
queued for the call with Alison
Unconfirmed
10
possibly addressed, not confirmed
Addressed
1
2 more need no change
My evidence notes
0
saved in this browser
Round 1 of 2 · First résumé

Alison reviewed my first version and said it was good to go, with suggestions to make my target direction clearer and to give more evidence of scale, reliability, and business value for my recent AI work.

14 items1 open10 unconfirmed1 addressed2 no change
What Alison said is working
  • Contact information, layout, and format look really good.
  • Stronger than most military transition résumés in civilian translation and measurable outcomes.
  • Shows a combination of technical implementation, program delivery, and training, in readable language, with accomplishments that show what changed because of my involvement.
Round 2 of 2 · Updated résuméLatest

I sent an updated version partway through her review. She said I brought forward the right work and projects for Solutions Engineer and Implementation roles, and that some of her earlier recommendations were already addressed. She added new notes on the summary, the Selected Work section, and showing adoption rather than just delivery.

Came second. Where Alison's later notes say the updated résumé handled earlier advice, that advice is marked addressed or unconfirmed, not open.

6 items6 open
What Alison said is working
  • Brought forward the right work and projects for Solutions Engineer and Implementation roles.
  • The Selected Solutions and Implementation Work section connects my accomplishments to my target roles.
  • Liked the more human voice of the summary (better suited to LinkedIn or a cover letter).
Career directions Alison suggestedgaps are evidence gaps, not qualification gaps
Direction
Shown on my résumé
Not yet documented
AI Solutions / Integration Engineer
Shown on my résuméAI workflows, MCP services, API integrations, identity controls, infrastructure, and automation. Projects add relevant implementation examples.
Not yet documentedProduction usage, integration volume, testing methods, reliability, latency, and operating costs. These are evidence gaps, not established qualification gaps.
Technical Program Manager — AI / Platform / IT
Shown on my résuméCross-team coordination, modernization, accelerated delivery, operational improvements, and work spanning requirements through support.
Not yet documentedProgram budgets, roadmap ownership, formal dependency management, release planning, and executive reporting examples.
AI Enablement / Technical Enablement
Shown on my résuméImplementation combined with workshops, procedures, administrator training, and user support.
Not yet documentedAI-specific workshops, adoption measures, user onboarding, or sustained changes in how employees used AI. Broader training experience is transferable.
Senior / Principal AI Engineer
Shown on my résuméHeld a Principal AI Engineer title and describes substantial ownership of AI services and supporting platforms.
Not yet documentedArchitecture scale, engineering standards established, technical mentorship, evaluation methods, or organization-wide technical influence. Readiness depends heavily on the employer's expectations.
Review items · 20 of 20
Status
Round
Move Projects up for AI Solutions rolesProjectsRound 1 · First résuméOpen
Alison's guidance

Consider moving Projects immediately after HRMLESS for AI Solutions positions, to increase visibility.

Why this status: Repeated in the updated-résumé notes: adding the Zero Hour Cyber position "reinforces my recommendation to move the projects higher for AI Implementation positions."

Not edited yet
Professional summary: drop the first personSummaryRound 2 · Updated résuméOpen
Alison's guidance

The casual, human voice communicates personality and what drives me, but it works best for the LinkedIn About section or a cover letter.

For the résumé, remove the first person and make it more concise. Approachability can stay without the first-person narrative.

Alison's suggested wording, draft until I confirm the factsAlison's suggested summary

Solutions and implementation professional with 20 years in Air Force IT and cybersecurity and recent experience building AI integrations at an HR technology startup. Works with stakeholders to understand what they need, identify what is getting in the way, and turn business problems into practical technical solutions. Brings hands-on experience building prototypes, connecting systems, coordinating rollouts, and training users, with the ability to explain technical concepts in plain language.

Why this status: New recommendation on the updated résumé.

Not edited yet
For Solutions Engineer / Solutions Consultant rolesTargetingRound 2 · Updated résuméOpen
Alison's guidance

Bring forward: needs discovery, prototypes, integrations, technical problem solving, and explaining systems to stakeholders.

Strengthen: who took part in discovery, how I demonstrated solutions, what feedback shaped the design, and how success was evaluated.

Alison's questions · answer only with facts I can back up
  • Who participated in discovery?
  • How did I demonstrate solutions?
  • How did stakeholder feedback change a prototype?
  • How was success evaluated?

Why this status: New recommendation on the updated résumé.

Not edited yet
For Implementation Consultant rolesTargetingRound 2 · Updated résuméOpen
Alison's guidance

Bring forward: rollouts, configuration, cross-team coordination, migrations, training, and operational handoff.

Strengthen: implementation milestones, testing, go-live support, issue resolution, and how I established that users were ready.

Alison's questions · answer only with facts I can back up
  • What were the implementation milestones, and how was testing done?
  • What go-live support and issue resolution did I provide?
  • How did I know users were ready, and that they kept using the tool?

Why this status: New recommendation on the updated résumé.

Not edited yet
Selected Work: keep it, with clearer labels and where the work happenedSelected workRound 2 · Updated résuméOpen
Alison's guidance

Alison likes this section: it connects my work to my target roles. Keep it and keep the examples relevant to each job description.

Present it with a little more formality: clearer labels and where the work occurred.

Her example of the 832-hour tracker below repeats a figure she questions under "Show adoption, not just delivery."

Alison's suggested wording, draft until I confirm the factsNeeds Discovery and Solution Development | HRMLESS

Translated business problems and desired outcomes from the CTO into working AI solutions, developing prototypes and refining them through stakeholder feedback. Built a shared AI gateway that provided one interface to 65 tools across eight providers.

Alison's suggested wording, draft until I confirm the factsImplementation Leadership | U.S. Air Force

Led a stalled $250K operations center modernization, directing 10 people through a 120-hour installation that replaced 4 projectors with 26 displays. Resolved a three-year delay and reduced emergency team setup time from 30 minutes to 5.

Alison's suggested wording, draft until I confirm the factsWorkflow Tracking and User Adoption | U.S. Air Force

Built an IT request tracker that became the team's daily tool for tracking incoming requests, ownership, and status, saving 832 hours of wait time annually.

Alison's suggested wording, draft until I confirm the factsCross-Functional Delivery and Evidence Automation | HRMLESS

Led SOC 2 Type II readiness and audit activities across 33 controls, coordinating engineering, product, and leadership through completion of a clean report. Automated evidence collection using Python scripts and source-system APIs to replace manual gathering.

Alison's suggested wording, draft until I confirm the factsMigration Training and User Readiness | U.S. Air Force

Trained 191 site and process owners during a SharePoint migration completed ahead of deadline.

Why this status: New recommendation on the updated résumé.

Not edited yet
Show adoption, not just deliveryAdoptionRound 2 · Updated résuméOpen
Alison's guidance

I already show strong implementation outcomes: faster setup, shorter processing times, completed deployments, and training delivered. The next step is to explain how I knew the solution worked for its users.

Evidence doesn't have to be data-driven. It can be anecdotal, based on routine use of the product or how often people used the tool.

Delivery is getting a tool to the customer. Implementation is making sure the people who are supposed to benefit can use it successfully and keep using it because it does what it's supposed to do.

Alison's questions · answer only with facts I can back up
  • IT request tracker: how did I calculate the 832 hours saved?
  • Does "wait time" mean elapsed request time or employee labor hours? Those describe different benefits.
  • Did team members test it with actual requests?
  • Did I adjust the workflow based on feedback?
  • Did the team stop using email or a spreadsheet to track requests?
Alison's templateAlison's template, if those activities happened

Built an IT request tracker, tested request submission and status tracking with X team members, and refined the workflow based on feedback; adopted for daily use across Y staff, providing visibility into request ownership and progress.

Alison's templateAlison's template, if I have usage data

Built and rolled out an IT request tracker used by X staff to manage Y requests monthly, replacing [previous tracking method] and reducing [verified measure] by X%.

Why this status: New recommendation on the updated résumé.

Not edited yet
Zero Hour Cyber: add a start monthHeader and datesZero Hour CyberRound 2 · Updated résuméOpen
Alison's guidance

Keep date ranges consistent by adding a starting month, for example "Sep 2026 – present" if that's accurate.

Adding this position reinforces the recommendation to move Projects higher for AI Implementation roles.

Alison's questions · answer only with facts I can back up
  • What month did Zero Hour Cyber start? (Alison's "Sep 2026" is a guess for me to confirm.)

Why this status: New recommendation on the updated résumé.

Not edited yet
Elevate my recent AI work with evidenceBulletsRound 1 · First résuméPossibly addressed; not confirmed
Alison's guidance

Give more evidence of scale, reliability, and business value for the recent AI work.

My AI bullets explain what I built very well; they could say more about how it was used and what changed.

Why this status: Alison said some first-round recommendations were already addressed in the updated version but didn't say which.

Not edited yet
Consider adding GitHub to the headerHeader and datesRound 1 · First résuméPossibly addressed; not confirmed
Alison's guidance

Add my GitHub profile to the header if it gives a clear path to my strongest work.

Keep individual project links in the Projects section.

Why this status: Not mentioned in the updated-résumé notes.

Not edited yet
HRMLESS: show the scope of the AI workflows and MCP servicesBulletsPrincipal AI Engineer | HRMLESSRound 1 · First résuméPossibly addressed; not confirmed
Alison's guidance

Add a measured result if available, such as processing time, successful task completion, or manual steps removed.

Alison's templateAlison's template (blanks are hers to fill only with real numbers)

Designed and implemented [X] AI workflows and MCP services with FastAPI and FastMCP to connect AI agents to [X] internal systems, using role-based authorization, scoped tokens, and audit logging to control access.

Why this status: Alison said some first-round recommendations were already addressed but didn't say which.

Not edited yet
HRMLESS: quantify the audit evidence automationBulletsPrincipal AI Engineer | HRMLESSRound 1 · First résuméPossibly addressed; not confirmed
Alison's guidance

The current bullet already has the action, method, and a useful result.

The revision adds the breadth of the work and quantifies the time recovered, so a reader understands the significance without interpreting the tools.

On my résuméCurrent

Automated audit evidence collection with Python scripts that pulled data from source systems through their APIs, replacing manual collection before each review.

Alison's templateAlison's template

Automated audit evidence collection from [X] source systems using Python and REST APIs, replacing manual collection for [X] recurring evidence requests and reducing preparation time from [X] to [Y] hours per review.

Why this status: Alison said some first-round recommendations were already addressed but didn't say which.

Not edited yet
Principal AI Engineer: this role deserves the most attentionRole by rolePrincipal AI Engineer | HRMLESSRound 1 · First résuméPossibly addressed; not confirmed
Alison's guidance

It establishes my recent AI credentials.

Lead with the AI workflows and integrations most relevant to the application.

Add users, systems connected, workflow volume, or business processes supported.

Explain testing, troubleshooting, and reliability where I have evidence.

Keep the SOC 2 and AI governance results, while distinguishing my leadership from the independent assessor's conclusions.

Why this status: Alison said some first-round recommendations were already addressed but didn't say which.

Not edited yet
Senior Manager, Cyber Operations: reorder and drop an acronymRole by roleSenior Manager, Cyber OperationsRound 1 · First résuméPossibly addressed; not confirmed
Alison's guidance

The modernization, interim director assignment, and early device delivery are strong. For most civilian technical roles, put them ahead of the career-field working group bullet.

Spell out or simplify CFETP.

Alison's suggested wording, draft until I confirm the factsAlison's suggested wording

Contributed to the career field's training framework.

Why this status: Alison said some first-round recommendations were already addressed but didn't say which.

Not edited yet
IT Operations Manager: clarify the users and sessions numbersRole by roleIT Operations Manager, Client SystemsRound 1 · First résuméPossibly addressed; not confirmed
Alison's guidance

One of my strongest sections: team leadership, technical work, automation, lifecycle management, and training.

Alison's questions · answer only with facts I can back up
  • I mention 46,000 users and 439,000 concurrent sessions. Were those sessions generated by the same 46,000 users, or does the session count refer to a larger network?
  • What part did my team and I directly support?

Why this status: Alison said some first-round recommendations were already addressed but didn't say which.

Not edited yet
Program Manager: explain "keeping 480 documents accurate"Role by roleProgram Manager, Squadron ProgramsRound 1 · First résuméPossibly addressed; not confirmed
Alison's guidance

Bullets look great. Keep the evaluation-process and digital-routing results, especially for program management applications; they show measurable process ownership even in an administrative setting.

Alison's questions · answer only with facts I can back up
  • What does "keeping 480 documents accurate" mean?
  • What was my level of ownership: did I personally review and update the documents, coordinate updates with the document owners, or oversee the process?
Alison's suggested wording, draft until I confirm the factsAlison's suggested wording

Maintained 480 documents, reviewing and updating content to support accuracy and currency.

Why this status: Alison said some first-round recommendations were already addressed but didn't say which.

Not edited yet
ZeroHour Times: say what I built and how it performsProjectsRound 1 · First résuméPossibly addressed; not confirmed
Alison's guidance

Could strengthen the project by adding the points below.

Alison's questions · answer only with facts I can back up
  • What was my specific design and implementation contribution?
  • Is the tool a prototype, a personal tool, or used by others?
  • How do I test matching quality and unsupported claims?
  • What are the typical posting volume, run time, and actual operating cost?
  • How are failures, duplicate postings, and unsuccessful imports handled?

Why this status: Alison said some first-round recommendations were already addressed but didn't say which.

Not edited yet
Veteran Transition Roadmap: explain how it's produced and checkedProjectsRound 1 · First résuméPossibly addressed; not confirmed
Alison's guidance

The current description establishes the inputs and output but leaves my implementation and evaluation work unclear.

If I have usage or feedback data, add it. If not, accurately calling it a working project or prototype still adds value.

Alison's questions · answer only with facts I can back up
  • How is the roadmap produced, and how is it checked?

Why this status: Alison said some first-round recommendations were already addressed but didn't say which.

Not edited yet
Make my target direction clearerTargetingRound 1 · First résuméAddressed in updated résumé (per Alison)
Alison's guidance

My headline emphasized AI enablement and technical program management, while my most recent title and first several bullets emphasized hands-on engineering.

Both directions are supported but call for different emphasis. A TPM recruiter needs to see how I managed requirements, decisions, dependencies, stakeholders, and delivery. An AI solutions recruiter needs more detail about what I implemented, how it was tested, and how it performed.

Be open to changing the focus depending on the position.

Why this status: In her updated-résumé notes Alison wrote that, given the more defined career direction, I brought forward the right work and projects for Solutions Engineer and Implementation roles.

Not edited yet
Senior Enlisted Advisor: good as isRole by roleCyber Communications Senior Enlisted AdvisorRound 1 · First résuméNo change needed
Alison's guidance

The civilian translation of the role is good, and so are the bullets.

Why this status: Praise only; no change suggested.

Not edited yet
Earlier roles: look fineRole by roleEarlier rolesRound 1 · First résuméNo change needed
Alison's guidance

No changes suggested.

Why this status: Praise only; no change suggested.

Not edited yet
Tailoring guidance from Alison · referencenot tasks
Bullet formula: Action + Purpose + Impact
Alison's guidance
  • Action: what I did.
  • Purpose: what need or problem I addressed.
  • Impact: what changed, with scope and metrics where available.
  • Not every bullet needs a percentage, but outcomes matter. Observable outcomes, such as replacing manual updates with a source-system integration, count. Make the result clear and defensible.
Tailoring to a job announcement
Alison's guidance
  • Review the announcement for required qualifications, recurring responsibilities, technical skills, and business priorities.
  • For each qualification I have, ask: where does my résumé show this, and what example supports it?
  • Use the employer's terminology when it accurately describes my experience. If relevant experience is missing or hard to find, revise the wording, reorder bullets, or add a specific example.
Change the lens, not the experience
Alison's guidance
  • The same work can be shown from a different angle. For a management role, emphasize directing people, assigning work, setting priorities, and monitoring performance. For a learning and development role, emphasize identifying training needs, developing instruction, coaching, and evaluating learning.
  • Management lens example: Coordinated onboarding assignments and monitored new employees' progress to support staffing readiness.
  • Learning and development lens example: Delivered onboarding instruction and coached new employees on procedures to support their development.
  • Use only responsibilities and results I can substantiate.
  • A summary full of the right keywords won't help if the bullets tell the story of a different role. Bullets need to show the work behind the target.
Use technology with human judgment
Alison's guidance
  • Treat suggestions from automated comparison tools or AI as a starting point. They can miss transferable experience, misread terminology, or recommend qualifications I don't have.
  • A match score doesn't establish whether I meet the requirements or predict an interview. Keywords help me get found; accomplishments, scope, and impact help me get interviewed.
  • The goal isn't a perfect match score. It's finding the announcement's language and qualifications that honestly apply to me, and making that evidence easy for both the applicant tracking system and the hiring manager to find.
  • Never add a skill just because a tool recommends it. If a tool sees "Python" and decides I have reptile-handling experience, that's where human judgment needs to come back in.
  • Any AI-assisted summary, skills list, or bullet is a draft. Verify every claim, figure, and description before using it.
Track what's working
Alison's guidance
  • Track which résumé version I submitted for each position and the response I got from different types of roles.
  • Over time that shows where my experience is gaining traction and helps us adjust the strategy.