User Guide

A practical operating manual for using RaetOS from first setup to captured postings, Decision Engine, generated packets, applications, Archive, Settings, and support.

Recommended Operating Loop

  1. 1.Build your Master Resume.
  2. 2.Capture interesting jobs into My Queue.
  3. 3.Review serious roles in Decision Engine.
  4. 4.Generate packets only for roles worth pursuing.
  5. 5.Apply on the job site when ready.
  6. 6.Track real applications after you apply.

1. Understand the RaetOS Workflow

RaetOS works best when each page has a clear job.

  1. 1Use Master Resume as your source record.
  2. 2Use My Queue for roles you are curious about but have not committed to.
  3. 3Use Decision Engine when a role deserves serious review.
  4. 4Use Application Packets and Resume Manager for generated outputs.
  5. 5Use Tracker after you apply or decide to manually track an application.
  6. 6Use Archive to keep inactive jobs out of the active workflow.

Simple rule: My Queue is curiosity. Decision Engine is commitment. Tracker is after applying.

2. Your First Session

Get enough source material into RaetOS so the rest of the system has something real to work with.

  1. 1Open Master Resume.
  2. 2Upload an existing resume, paste rough work notes, or add experience manually.
  3. 3Add more than one source if you have it, such as old resumes, Jira notes, ServiceNow summaries, performance reviews, or project notes.
  4. 4Review what RaetOS extracts before treating it as source truth.
  5. 5Fill obvious gaps such as job titles, companies, dates, skills, projects, certifications, and measurable outcomes.
  6. 6Save the structured record before moving into job analysis.

You do not need a perfect resume to start. RaetOS is meant to help turn rough source material into a usable career record.

3. Build and Maintain Master Resume

Master Resume is the well you keep filling so future resumes are easier to generate.

  1. 1Add each role with title, company, dates, location, and work type where relevant.
  2. 2Add accomplishments as evidence, not just duties.
  3. 3Tag skills, tools, systems, leadership examples, metrics, and project outcomes.
  4. 4Add projects that show proof outside normal job bullets.
  5. 5For federal roles, include hours, salary, supervisor, location, and clearance details when needed.
  6. 6Use RaetAI follow-up questions to close thin sections.
  7. 7Return after major projects, promotions, incidents resolved, certifications, and performance reviews.

Strong generated resumes come from strong source data. If the Master Resume is thin, outputs will be thin too.

4. Use RaetOS While Employed

RaetOS is not only for emergency job searches.

  1. 1Log wins while the details are fresh.
  2. 2Save metrics such as time saved, money saved, tickets closed, users supported, systems migrated, downtime reduced, or revenue protected.
  3. 3Capture praise, promotion language, performance-review highlights, and leadership moments.
  4. 4Add new tools, certifications, responsibilities, and projects as they happen.
  5. 5Review your Master Resume monthly or after each major work milestone.

The goal is readiness. If a layoff, promotion, referral, or better role appears, you are not starting from memory.

5. Capture Jobs With the Extension

Use the extension to collect postings quickly while browsing job boards.

  1. 1Sign in to the RaetOS extension.
  2. 2Browse job boards normally.
  3. 3When the floating panel appears on a job posting page, choose Send to My Queue if the role is worth reviewing later.
  4. 4Choose Not interested if you do not want that posting to keep appearing.
  5. 5Use the popup sent board to see weekly, session, and total local sends.
  6. 6Clear the local sent board when you want a fresh local browser view.

Clearing the extension sent board does not delete jobs already saved to My Queue in your RaetOS account.

6. Review My Queue

Batch-review captured jobs before spending time generating resumes.

  1. 1Open My Queue.
  2. 2Filter by status if you want to focus on captured, analyzed, selected, applied, or not pursuing items.
  3. 3Open a captured posting and review the basic job details.
  4. 4Send promising roles to analysis.
  5. 5Use the analysis summary to decide whether to review in Decision Engine, save for later, or mark not pursuing.
  6. 6Keep My Queue for exploration, not final application history.

This is where you avoid wasting time. Not every job that looks interesting deserves a custom resume.

7. Work in Decision Engine

Use Decision Engine when a role is serious enough to compare against your career record.

  1. 1Open a role from My Queue or paste a job description directly.
  2. 2Review what the role asks for: skills, seniority, job type, federal/private signals, and keywords.
  3. 3Review how your Master Resume supports or misses those requirements.
  4. 4Check the recommended resume type.
  5. 5Override the resume type if you know a different format better fits your strategy.
  6. 6Generate a resume or packet only when the role is worth pursuing.
  7. 7If you are not ready, save for later or return without applying.

Decision Engine helps you make a better decision. It does not apply for you.

8. Choose a Resume Type

Use the format that matches the role and your career story.

  1. 1Use chronological when your recent work history clearly matches the role.
  2. 2Use functional when you need to highlight transferable skills or explain a pivot.
  3. 3Use combination when both skills and timeline matter.
  4. 4Use targeted when the resume is built for one specific job posting.
  5. 5Use federal when the posting requires government-style detail.
  6. 6Review the generated resume before downloading or using it.

The recommendation is guidance. You remain the final reviewer.

9. Generate and Use Application Packets

Keep every generated output connected to the job it was made for.

  1. 1Generate the resume from Decision Engine.
  2. 2Name the packet clearly, such as Company Role v1.
  3. 3Review the resume and make sure it matches the posting.
  4. 4Download the resume when ready.
  5. 5Use Copy ATS Text when an application asks for pasted resume text.
  6. 6Generate a cover letter, hiring manager email, or interview prep when useful.
  7. 7Use the packet later to remember exactly what you prepared for that role.

A packet is preparation. It becomes application history only when you apply or track it.

10. Apply and Track

Move from preparation into application history when you actually apply.

  1. 1When ready, open the job link from the packet or Decision Engine flow.
  2. 2Submit the application on the employer or job-board site.
  3. 3Create or confirm the Tracker record when you commit to applying.
  4. 4Move the application through stages such as applied, interviewing, offer, rejected, or closed.
  5. 5Add notes, dates, contacts, follow-up reminders, and interview details where available.
  6. 6Generate interview prep when the application moves into an interview stage.

Tracker should reflect real application activity, not every job you casually captured.

11. Use Archive

Keep inactive items without cluttering your active boards.

  1. 1Move jobs you are not pursuing out of active queue review.
  2. 2Move rejected or closed applications out of active Tracker columns when you no longer need them visible.
  3. 3Use Archive to review not-pursuing queue items and closed application history.
  4. 4Restore an archived item if it becomes active again.
  5. 5Delete only when you are sure you no longer need the record.

Archive is organization. It is not the same thing as account deletion.

12. Configure Settings

Settings gives RaetOS context and keeps account controls in one place.

  1. 1Add profile context such as current title, target roles, location, remote preference, work authorization, clearance, phone, LinkedIn, portfolio, GitHub, and website.
  2. 2Set preferences such as theme, default resume format, My Queue filter, and Tracker view.
  3. 3Review security settings, active sessions, sign-in methods, and extension access.
  4. 4Use data controls for export, retention, and account deletion flows where available.
  5. 5Use Resources to open Privacy, Terms, Cookies, Security, FAQ, User Guide, and Support.

Profile and preference context can help Decision Engine understand what you are aiming for.

13. Export, Privacy, and Data Care

Know what you can take with you and how to handle sensitive information.

  1. 1Use export tools where available to collect account-owned data.
  2. 2Expect exports to cover profile data, Master Resume records, captured jobs, packets, resumes, tracker records, archive items, settings, and related career data where available.
  3. 3Avoid storing employer secrets, credentials, customer data, private source code, or regulated data you are not allowed to reuse.
  4. 4Use Privacy, Security, Cookie Policy, and Terms of Service for source-of-truth policy details.
  5. 5Contact [email protected] for privacy, export, correction, or deletion questions.

Career evidence is valuable. Treat it like sensitive personal information.

14. Get Help

Use support when something breaks or when you need product guidance.

  1. 1Open Support from Resources or the app sidebar.
  2. 2Describe what page you were on, what you expected, what happened, and what you already tried.
  3. 3Include screenshots when helpful.
  4. 4For product or account help, email [email protected].
  5. 5For privacy questions, email [email protected].
  6. 6For security concerns, email [email protected].

Clear reports make issues easier to reproduce and fix.

Need a Faster Answer?

Use FAQ for short searchable answers, or Support for help with a specific issue.

FAQSupport[email protected]