FAQ

RaetOS is a career operating system. It helps you keep a structured record of your work, review opportunities, generate role-specific materials, and track applications without rebuilding from memory each time.

OS means operating system. RaetOS is meant to be the system that runs underneath your career record, job decisions, resume generation, packets, and tracking.

No. A resume builder usually starts with one document. RaetOS starts with a reusable career record, then turns that record into resumes, packets, ATS text, interview prep, and tracker history when needed.

No. RaetOS is useful while you are employed, between roles, preparing for a pivot, applying now, or rebuilding your history after time has passed.

Because career details fade. Logging accomplishments while they are fresh gives you better source material later, especially if a layoff, promotion, referral, or sudden opportunity appears.

RaetOS reduces the chaos of scattered resumes, forgotten accomplishments, job posts, weak bullets, and manual tracking. It gives you one career record that can produce many outputs.

Start with Master Resume. Upload old resumes or paste work notes, then let RaetOS extract roles, skills, projects, and evidence gaps.

No. RaetOS helps you prepare and organize. You decide what to generate, what to download, and when to apply.

RaetOS can be used by active applicants, employed professionals, career switchers, veterans, federal applicants, contractors, students entering the workforce, and people rebuilding old work history.

Yes. Employed users can log accomplishments, projects, metrics, praise, certifications, and scope changes before those details are forgotten.

Yes. Career switchers can use the Master Resume to collect transferable skills and use the Decision Engine to choose a resume type that better explains the pivot.

Yes. RaetOS supports federal-ready fields such as hours, salary, supervisor, location, clearance, and detailed work-history context when needed.

Yes. Veterans can use RaetOS to translate military experience into civilian language, preserve mission impact, and prepare different resume formats.

Yes. Projects, internships, class work, certifications, volunteer experience, and early wins can become source material.

Yes. You can paste rough notes, upload old files, or add experience manually. RaetOS is designed to help structure the raw material.

Use RaetOS in a simple loop: collect source material in Master Resume, capture interesting postings into My Queue, review serious roles in Decision Engine, generate packets only for roles worth pursuing, then track applications after you apply.

Fresh accomplishments usually include better details: numbers, context, blockers, tools, stakeholders, and impact. Those details make stronger resumes and interview answers later.

A good rhythm is monthly, after major projects, after performance reviews, after certifications, and whenever you receive measurable praise or results.

Save roles, projects, metrics, incidents resolved, systems improved, money saved, time saved, tools used, leadership moments, certifications, awards, and performance-review language.

Avoid confidential employer data, customer secrets, passwords, private source code, regulated data, or anything you are not allowed to reuse.

Send many interesting jobs to My Queue first. Later, review them in batches, generate packets only for good matches, then apply with a record of what you used.

Use it as a career log. Add wins, projects, new tools, lessons, promotions, responsibilities, and proof so you are ready before the next move appears.

Not every posting deserves your time. My Queue lets you collect first, review later, and reserve full packet generation for roles that are worth a serious application.

The Master Resume is your structured career record. It stores work history, accomplishments, skills, projects, education, certifications, metadata, and proof that can be reused in different outputs.

Because it is not one resume. It is the source record that many resumes and application materials can be generated from.

Yes. You can upload or paste existing resume content and use it as source material.

Yes. RaetOS is designed to accept rough career evidence from different sources, then help convert it into structured experience.

Yes. Manual entry is available when you want direct control or do not have files ready.

Evidence gaps are missing or weak parts of your career record, such as missing metrics, thin bullets, unclear scope, missing skills, or incomplete federal details.

RaetAI asks follow-up questions to fill gaps before weak source material becomes a weak resume, packet, or interview answer.

Yes. AI output should be treated as a draft. You should review, correct, and refine it before relying on it.

Yes. Decision Engine compares a captured job posting against your Master Resume to find relevant experience, gaps, resume strategy, and output direction.

Yes. Generated resumes pull from the structured source material in your Master Resume.

RaetOS may warn you that generated outputs could be weaker because the source record is thin or missing important sections.

My Queue is where captured job postings wait for review. It lets you collect roles first and decide later which ones deserve deeper analysis or application effort.

No. My Queue is for roles you are considering. Tracker is for applications after you decide to apply or manually track one.

A posting goes to My Queue when you send it from the extension or add/capture it through a RaetOS flow that saves it as a captured posting.

No. Capturing is curiosity. Applying is commitment.

Captured means RaetOS saved the posting details so you can review it later.

Analyzed means the posting has been reviewed by the Decision Engine or has analysis available for review.

Selected means you are moving the posting toward a serious decision, packet, or application workflow.

Not pursuing means you decided not to move forward with that posting. It can be archived instead of cluttering active review.

Yes. That is one of the main reasons My Queue exists. You can search job boards, send postings quickly, then review them in RaetOS later.

Look for role fit, job type, location, salary clues, requirements, red flags, and whether the role deserves time in Decision Engine.

Decision Engine reviews a job posting against your Master Resume so you can decide whether to generate a packet, save it for later, skip it, or apply.

It can analyze role requirements, seniority, keywords, job type, federal/private signals, relevant experience, missing proof, and the best resume strategy.

The strongest review happens after a resume or packet is generated, because the system can compare the actual output against the job and your source record.

Decision Engine is meant to think like a head hunter, seasoned recruiter, and resume strategist: fit, recruiter scan, and achievement-based positioning.

A keyword gap is something the posting asks for that your Master Resume or generated resume may not clearly show yet.

Fit should help you understand how well your existing evidence aligns with the posting. It is guidance, not a guarantee.

Yes, the goal is for the engine to recommend a format while still letting you choose the direction you want.

No. It helps you decide and prepare. You still choose when to open the job and apply.

Tracker should start when you commit to applying, such as using the apply/open-job flow or manually creating a tracker record.

The posting can remain undecided, saved for later, or returned to the relevant history/status flow depending on how you leave it.

RaetOS is designed around five resume types: chronological, functional, combination, targeted, and federal.

A chronological resume presents your work history in time order. It is often best when your recent experience directly matches the role.

A functional resume emphasizes skills and themes over job-by-job history. It can help when changing careers, returning after a gap, or reframing experience.

A combination resume blends skill themes with work history. It is useful when both your capabilities and timeline matter.

A targeted resume is built for one specific role. It emphasizes the proof, keywords, and accomplishments most relevant to that posting.

A federal resume includes more detail than a private-sector resume, such as hours, salary, supervisor, locations, and detailed duties when required.

The recommendation depends on the posting, your source evidence, your target role, and whether the role needs standard, pivot, targeted, or federal formatting.

Yes. Some roles may be worth comparing different formats before deciding what to use.

An Application Packet is the saved package for a role. It can include the compiled resume, job snapshot, analysis, cover letter, ATS text, hiring manager email, and interview prep.

Packets let you return to exactly what you generated for a specific job, instead of losing track of which resume or cover letter went with which posting.

Yes. A clear name like Google Staff Engineer v2 makes it easier to find later.

ATS text is a plain-text version of resume content that can be copied into application systems that ask you to paste resume text instead of uploading a file.

Yes, when that output is available for the packet. You should still review and edit before sending.

Yes. Interview prep should use the job posting and your resume evidence to help prepare relevant questions and talking points.

Resume Manager is where generated or uploaded resumes can be managed, reviewed, downloaded, and connected back to their purpose.

No. Generating is preparation. Applying happens when you decide to open the job and submit or manually track the application.

Tracker is where applications live after you decide to apply or manually track an application.

Tracker organizes applications by stages such as watchlist, applied, interviewing, offer, rejected, and closed.

Archive is where inactive items can live so active work stays clean. It can include not-pursuing queue items and closed or rejected applications.

Archive when a role is no longer active, you are not pursuing it, it was rejected, or it is closed and should not clutter active boards.

Yes, where restore is available. Restoring brings the item back into the relevant active workflow.

Where delete is available, you can remove items you no longer want. Deletion is different from archiving.

No. Archive is organization. It does not mean account deletion.

Move the application into an interview stage and generate or review prep from the packet or tracker context when available.

Rejected jobs can show patterns: role type, weak areas, companies contacted, and resumes used. You can keep them archived instead of active.

The extension helps detect job-posting pages and send selected postings to My Queue so you can review them later in RaetOS.

The panel should appear when you are on a job posting page, not just a general listing page.

It sends the job posting details to your RaetOS account so it appears in My Queue.

It dismisses that posting locally so the extension does not keep asking about it.

No. The extension is not intended to read Gmail, Outlook, or any mailbox content.

No. It captures postings and helps organize your workflow. You decide when to apply.

The Sent Board is local browser history showing postings sent from that browser, plus counts like week, session, and total sent.

It clears the local browser board and counts. It does not delete postings already saved in your RaetOS account.

It may detect the same job URL or a saved duplicate in your local board or RaetOS queue.

Not always. Job sites structure pages differently. The extension should improve over time as more posting patterns are supported.

No. RaetOS does not sell user data.

No. Google and Microsoft are used for sign-in identity only. RaetOS does not request Gmail or Outlook mailbox access.

AI features should receive the content needed for the selected action, such as a resume, job description, or packet context.

RaetOS does not use Google or Microsoft sign-in data to train generalized AI models. AI processing details are explained in Privacy and Security.

Account export is intended to include account-owned data such as profile details, Master Resume records, captured jobs, packets, resumes, tracker records, archive items, settings, and related career data where available.

Yes, generated resumes and packet outputs should be downloadable or exportable where those tools are available.

My Queue data is account-owned captured posting data and should be included in account export where available.

Tracker records are account-owned application records and should be included in account export where available.

Account deletion is planned as a full confirmation and backend cleanup flow in Settings. Privacy requests can also be sent to privacy support.

RaetOS uses controls such as password hashing, session handling, identity-only OAuth, Turnstile on auth flows, user-scoped data access, server-side validation, and environment secrets.

Settings is where you manage account profile, preferences, security, extension connection, data controls, and resource links.

Useful fields include current title, target roles, location, remote preference, work authorization, clearance level, LinkedIn, portfolio, GitHub, website, and phone number.

Target roles help RaetOS understand what you are moving toward, which can improve resume strategy and Decision Engine context.

Resources is the settings area for reference pages such as Privacy Policy, Terms of Service, Cookie Policy, Security, FAQ, User Guide, and Support.

Use the Resources tab in Settings or the public links for Privacy Policy, Terms of Service, Cookie Policy, and Security.

Use the Support page or email [email protected] for account, product, bug, or feature questions.

Email [email protected] for privacy, export, correction, or deletion-related questions.

Email [email protected] for vulnerability reports or security concerns.

Use Settings, the extension popup, or the extension authorization page depending on whether you are connecting, signing out, or revoking access.

Start with Support. Include what page you were on, what you expected, what happened, screenshots if useful, and any browser console errors if you can safely provide them.