An interview roadmap demonstrating how Robin Tyson can bring federal documentation rigor, modern content management, and stakeholder-focused technical writing to the FAA SETIS contract.
SETIS supports FAA modernization and mission services. For a technical writer, the contribution is disciplined documentation that technical and program teams can trust.
The FAA describes SETIS as a contract portfolio supporting systems engineering, analysis, programmatic services, National Airspace System modernization, and mission support. Documentation accuracy, traceability, clarity, and control matter in this environment.
Concrete examples from federal technical writing and communications assignments.
Developed technical SOPs and stakeholder guidance; maintained an enterprise knowledge repository; coordinated reviews and Section 508 checks. FAA value: document control, structured revisions, reliable access to current information.
Produced briefs, technical communications, training materials, and controlled deliverables in collaboration with SMEs. FAA value: accurate manuals, correspondence, briefings, and project-facing materials.
Created technical guidance and executive content; coordinated 167 Jira tasks for a Data & AI Expo. FAA value: multi-project organization, editing discipline, cross-functional follow-through.
A conversation-ready mapping of Astrion's responsibilities to directly relevant experience.
| FAA / Astrion priority | Relevant experience | How I contribute |
|---|---|---|
| Technical manuals, SOPs, reports, and instructions | DHS/ICE documentation modernization; IT Service Review SOPs; DoD technical communications | Produce standardized, accurate, easy-to-navigate documentation tailored to the intended reader. |
| Editing, style, accuracy, proofreading | Editorial standards, technical QA, accessibility checks, multi-contributor reviews | Maintain consistency, plain language, traceability, and a dependable review process. |
| SME and engineer collaboration | DHS and DoD work with IT leads, SMEs, program stakeholders, and executives | Ask targeted questions, validate details, resolve gaps, and reduce revision friction. |
| Document lists, revisions, version control | SharePoint repository serving 5,000+ users; structured templates; Jira tracking | Keep owners, status, versions, approvals, and next actions visible. |
| Adobe Communiqué / CQ5 | Hands-on Adobe Experience Manager (AEM) at Federal Reserve Board and DHS/ICE | Bring experience on the successor platform, including familiarity with enterprise CMS practices. |
| QuickSilver authoring environment | MadCap Flare listed in technical-writing résumé; Word, Acrobat, controlled authoring workflows | Transfer structured-authoring skills while learning QuickSilver-specific commands and templates. |
| Briefings, graphics, and project support | DoD leadership briefs and visuals; FRB event communications; MS PowerPoint and Word | Convert dense technical inputs into clear, audience-specific deliverables on deadline. |
You used Adobe Experience Manager at both the Federal Reserve Board and DHS/ICE. That is directly relevant to Astrion's Adobe Communiqué (CQ5) requirement because CQ5 preceded AEM. Discuss the specific page/content workflows you used; do not imply experience with a legacy CQ5 installation unless asked and confirmed.
QuickSilver is a specialized technical-publication authoring tool. Your documented MadCap Flare, Word, Acrobat, and structured-documentation background provide relevant foundations. Do not claim direct QuickSilver experience if you have not used it.
No generic 30/60/90-day promise—just a practical, adaptable approach centered on the FAA team's actual priorities.
Confirm the purpose, owner, readers, required references, applicable templates, due date, and approval path before drafting.
Gather source materials, interview technical leads, identify unresolved questions, and validate complex facts before publication.
Use approved style guidance, plain language, document registers, version tracking, review comments, and required accessibility checks.
Complete technical and editorial QA, coordinate approval, confirm the current version is findable, and track follow-up updates.
Confident answers you can adapt naturally—not scripts you need to memorize.
“Tell us how your background fits this FAA technical writing role.”
“My background is in federal technical writing and communications where accuracy, structure, and collaboration are essential. At DHS/ICE, I supported a large documentation modernization effort, authored technical SOPs, and maintained a SharePoint repository serving more than 5,000 users. At the Defense Health Agency, I worked across seven technical projects to develop clear, review-ready content for different stakeholders. I can bring that same discipline to FAA manuals, reports, correspondence, and technical briefings.”
“Have you used CQ5?”
“I've used Adobe Experience Manager, the successor to Adobe Communiqué/CQ5, at both the Federal Reserve Board and DHS/ICE. I understand enterprise content-management environments, and I can discuss the specific AEM workflows I've supported. I would confirm the FAA team's CQ5 configuration and any legacy features they rely on so I can align quickly.”
Interview cue: Be ready with one precise AEM example—such as a page edit, approval, publishing, or asset task—that you actually performed.
“What about QuickSilver?”
“My technical-authoring background includes MadCap Flare, Microsoft Word, Adobe Acrobat, and structured documentation workflows. While I haven't identified QuickSilver as a tool I've used directly, I am experienced with the core publishing disciplines—templates, navigation, revision control, technical accuracy, and production quality. I'd learn the FAA's established QuickSilver templates and processes rather than introduce unnecessary changes.”
Interview cue: State direct product experience only if true. Emphasize transferable processes, not identical interfaces.
“What sets you apart from other technical writers?”
“I combine federal documentation experience with the ability to manage the full content lifecycle—from obtaining SME input and reconciling technical details to editing, accessibility, approval, publication, and ongoing maintenance. I can work with engineers and program managers while keeping the end reader in focus. My goal is to make the documentation dependable and easier to use.”
Select two or three questions based on where the conversation goes.
Confirm the AEM tasks you personally performed at the Federal Reserve Board and DHS/ICE. Mention the successor relationship to CQ5; do not suggest identical versions.
Lead with SOPs, controlled repositories, expert interviews, executive communications, and accessibility. Mention AI work when it demonstrates process discipline, not as the centerpiece.
This role is technical documentation support for FAA SETIS. Do not claim direct aviation systems experience unless you have it. Connect your strengths to the stated responsibilities.
Source basis: Astrion Technical Writer description supplied for this interview; candidate experience shared in résumé work and confirmed AEM use; FAA public SETIS program pages. The metrics shown are résumé-derived examples, not independently audited results. This personal interview-preparation document uses a navy, blue, white, and gold FAA-inspired palette, without the official FAA seal or logo.