About ApplyStorm

A job board you set to Full Auto on Ashby, Workday or iCIMS now works as on Greenhouse and Lever: Storm prepares the application, your Chrome fills it, and Storm presses Submit for you.

• ·It needs the “Submit applications for me” permission and “Fill on any site” turned on in the ApplyStorm extension (0.12.3 or later).
• ·If you set one of these boards to Full Auto before today, it meant Storm hands the application back for you to finish. Storm keeps doing that until you confirm with “Let Storm press Submit” in Settings.
• ·An application comes back to you, with the reason on its page, when the site asks you to sign in first, when “Fill on any site” is off or the extension needs an update, when the form sits inside another site’s frame or Storm finds no form, when the posting is not on that board’s own site, or when no Chrome with the extension picked it up within a day.
• ·If several applications in a row come back on one board, Storm pauses Full Auto there and stops preparing new ones for it. Settings shows a Resume button.
• ·The pause switch and turning the permission off stop it, as on every board.

Before asking you a required question, Storm now checks your profile, résumé, saved answers, salary target and the job’s posted pay, and answers from them when they settle it.

• ·A question your profile already answers, however the employer words it, is filled: for example “No” to an F-1 visa question when your profile says you are a citizen or permanent resident.
• ·With “Let Storm fill in the gaps” on (Settings, Storm’s permissions), Storm may also infer an answer, such as a desired salary from your salary target or the job’s range, or your highest education from your résumé. Inferred answers show in amber on the application page and in the extension, so you can check them before Submit.
• ·Work authorization and visa answers come only from what you told Storm. Self-identification, criminal history, references, consents and requests to contact your employer are left for you.

The Chrome extension can now fill an application on any employer’s careers site, not only Greenhouse and Lever, and when a CAPTCHA appears it hands the page to you and carries on as soon as you have done it.

• ·Turn on “Fill on any site” in the extension, or say yes when Chrome asks the first time you start one. Storm fills the form from your profile and answers, and you click Submit, unless you set Other employer sites to Full Auto in Storm’s permissions: then Storm clicks Submit on the applications you start there.
• ·On a job description page, Storm presses the Apply button that opens the form, then fills it.
• ·Storm does not solve CAPTCHAs. When one blocks the page, Storm brings the tab forward and shows a desktop notification. Once you have done the check, Storm carries on by itself, with no Resume to press.
• ·A tick-box check beside Submit does not stop Storm filling the form any more; you tick it when you submit.
• ·This needs extension 0.12.0.

Settings reads as sentences you can change, each job and application shows one next step, and every page says plainly when it has nothing to show or could not load.

• ·Settings has five sections: You, Job search, Storm’s permissions, Notifications and Account. Each choice is a sentence with Change beside it, and the less common ones sit under More.
• ·In Storm’s permissions you can tick kinds of question Storm leaves for you to answer.
• ·The number of things that need you is the same in the top bar and on Storm’s page.
• ·Jobs are cards with the company’s initials, your match score as a ring and one button. Jobs you have already applied to say so, and every filter sits under Refine.
• ·An application shows where it is in four steps. If something went wrong, it says what happened once, in plain words, with the next thing to do.
• ·An answer Storm reused says where it came from, such as your answer at another company, and you can tell Storm not to reuse it.
• ·Applications, Interviews, Rehearsal, Target companies, Offers and setup now look and work like the rest of the app. Rehearsal names the job you are practising for, and removing an offer asks first.
• ·When a list is empty, a page is loading or something could not be read, the page says which, with Storm’s orb, instead of showing an empty list.

Your best matches now list first the jobs that link to the employer’s application, and a job that only links to a job board’s listing says so.

• ·A job whose listing does not link on to the employer’s application shows “No employer link yet”. You can still open it on the job board it came from.
• ·Storm does not prepare a résumé and cover letter on its own for a job with no application link. You can still prepare them yourself from the job page.

The top bar has six places to go, Storm’s page starts with the next thing that needs you, and Messages puts employers first, sorted by what each conversation needs from you.

• ·The bar is Storm, Jobs, Applications, Messages, Interviews and Career. Offers is a tab under Applications, Rehearsal a tab under Interviews, and the detailed numbers a tab under Career. Your Answer Library and company exclusions are in the account menu. Old links still open the same page.
• ·On a phone, the same six places are along the bottom of the screen.
• ·Storm’s page opens with one sentence about what Storm is doing, the next thing that needs you, and a chart of your search over the last 30 days.
• ·Messages groups mail by employer and application in three lists: to reply, waiting, and done, with Interviews and Unread to narrow them. Notices from Storm, such as new roles and company news, have their own list, and a security code from an employer shows with a Copy button.
• ·Opening a message no longer scrolls you away from it.

If Storm has not started an application within 10 minutes of your click, it stops waiting, tells you nothing was sent, and offers Try again.

• ·On a site Storm cannot fill for you, such as a company’s own careers page, your tailored résumé, cover letter and the link to the posting are ready as soon as you press Prepare to apply and confirm. Apply on the employer’s site, then mark the application as submitted.
• ·The application page and its timeline show the same 10-minute limit.

On your dashboard pages, press ⌘J (Ctrl+J on Windows) or the Storm button in the top bar, and ask about your search: what is new at your target companies, where an application stands, or what you answered before.

• ·Storm answers from your own data and shows what it looked at. When it finds nothing, it says so.
• ·Ask from a job page and “this job” means the one you are looking at.
• ·When you ask for a change, such as adding a company to your target companies, Storm shows the exact change first and makes it only when you confirm. Removing a company can be undone.
• ·Company news, the results check and skill gaps are part of Pro. On Free, Storm shows what Pro adds when you ask for one of them.
• ·You can ask Storm up to 30 questions a day.

Before Storm asks you an employer’s question, it now tries every way of answering it from what it already knows, and asks only what it cannot answer or what is yours to say.

• ·A follow-up such as “If yes, please explain” is not asked when your answer to the question before it was No.
• ·Add any links you want employers to see in Settings › Profile › Other links: X, GitHub, Kaggle, a portfolio, a scheduling page. Storm uses them whenever a form asks for a profile, handle or website, and suggests the links it finds in your résumé.
• ·Optional questions Storm has no answer for are left blank instead of being sent to you.
• ·Open questions such as “Why do you want to work here?” are drafted from your own résumé and saved answers, written for that job, and listed on the application with where each came from. When you submit an application yourself, you can edit them on the form first.
• ·Pay, start date, eligibility, self-identification and consent questions are still yours to answer. When Storm does ask, the question shows what it tried first.
• ·Questions already waiting in Needs your answer were checked again; the ones Storm can now settle are gone from the list.

The Storm orb, a globe of small cells where each cell is a job, now shows what Storm is doing: on Storm Home and at the top of the Chrome extension’s side panel.

• ·The orb takes a pose for each state, with its label under it: Ready, Applying while Storm fills a form in your Chrome, Needs you when something waits on you, Sent when an employer confirms, Paused when Storm cannot run (switched off, or the extension is not connected).
• ·With reduced motion turned on in your system settings, the orb holds a still pose.
• ·The extension’s toolbar icon is the orb too. This needs extension 0.11.0.

Pages begin to show in about a fifth of a second instead of half a second or more, and the rest fills in as it is ready.

• ·The top bar and the page outline appear first; the numbers in the bar (messages, answers, what needs you) fill in a moment later.
• ·The Jobs list shows your matches before the counts above it finish, and “all time” loads about twice as fast as before.
• ·Nothing about what you see changed, only how soon you see it.

An application Storm has filled and checked no longer holds up the next one: start another job from the Chrome extension, and go back to submit the first when you are ready.

• ·The side panel lists the applications waiting for you, such as “Waiting for your review: Affirm”, each with a link back to its tab.
• ·On the next job’s page, Start is where you expect it. Storm opens that application in a tab of its own, so each application is filled in its own tab.
• ·If an application waiting in another tab needs an answer from you, the side panel says so and lists it first.
• ·This needs extension 0.10.2.

Storm watches the news for your target companies and for companies in your search, and tells you when one of them starts hiring.

• ·Suggested companies appear on Storm Home, at the top of the Email tab in Messages, and as “Suggested by Storm” on Target companies. Each card shows the headline, where it came from, why it matters to your search, and how many open roles match you.
• ·Add to targets puts the company on your Target companies list. Not interested hides the card, and you can say why in one tap: not this company, not this kind of news, or already applied.
• ·For a company you already watch, a card tells you about good news with a link to its matching roles, and tells you plainly when there are job cuts.
• ·In Settings → Discovery you choose Suggest companies, Add strong matches for me (up to 3 a week), or Off.
• ·Company news is part of Pro. On Free, a card explains it and links to Upgrade to Pro.

Set the job you want next, see where your search stalls, and start the fix with one button.

• ·Your goal: the job you want next, with the pay you need and a date. If you name a company, it joins your Target companies.
• ·One diagnosis, based on what Storm can see in your last 90 days, with one button that starts the fix: tailor a résumé, rehearse an interview, update the roles Storm searches for, or build a negotiation plan. Free shows one diagnosis; Pro shows each one as your search changes.
• ·Readiness for your target role (Pro): what postings for that role ask for, and which of those your résumé already shows.
• ·A plan, or quests if you are early in your career (Pro): skills to show or build, questions to answer and strong matches to review. Mark an item done or set it aside.
• ·Ask Storm about your results (Pro): short answers that use only your own numbers, each with the facts behind it.
• ·Why applications closed: record the reason an employer gave, or your reason for declining an offer, and see the pattern over time. Storm does not guess a reason you did not give.

A new Career page shows your career so far and your job-search results in one picture.

• ·Your career timeline, drawn from your résumé.
• ·Your results from jobs found to offers accepted, with rejected and expired beside them, for the last 30 days, 90 days, 12 months or all time.
• ·Comparisons with published hiring figures, each with its source, once you have applied to 10 jobs in a period.

Name the companies you’d like to work at, and Storm watches their job boards and tells you when a role that matches you opens.

• ·Add a company from the new Target companies page under Jobs, from the star next to a company in your jobs list or applications, or during sign-up.
• ·Storm finds the company’s job board — Greenhouse, Lever, Ashby or Workday — and shows what it found and when it last checked. When it isn’t sure, it asks you for the careers page link.
• ·New roles at a target company that match you are ranked higher, marked “Target”, and sent to you once each in Messages and by email.
• ·On Greenhouse and Lever, Storm can apply, and since 19 October on Ashby, Workday and iCIMS too. On other sites, Storm finds the roles and can tailor your résumé, and you apply on the company’s site.
• ·Companies aren’t told you’re watching them.

An answer you give Storm in the Chrome extension is saved for your next applications, so Storm can use it there instead of asking you again.

• ·Answers you give in the side panel are saved to your Answer Library automatically; there is no box to tick. Each one has a “change” link to edit or delete it there.
• ·Answers about one employer, such as “Have you worked at this company before?”, are kept for that employer only. Answers that depend on the job, such as why you want to join or when you can start, are offered as a starting point you edit, not filled for you.
• ·Storm finds your earlier answer when another employer words the question differently, and picks the employer’s own wording for it, for example “I have not previously been employed at …” for a No.
• ·Questions about your state or province are answered from the location in your profile, and sponsorship questions from your work authorization.
• ·The side panel shows where each answer came from: your profile, your résumé, your Answer Library, or the date you answered it before.
• ·Choosing an answer in a dropdown now takes one click of Answer.
• ·Legal confirmations and consents are still answered for one application at a time, and self-identification answers stay in your profile.

We updated both documents, and you will be asked to read them and agree once, the next time you open ApplyStorm.

• ·The Terms now say paid plans are billed monthly or quarterly, depending on the billing option you choose.
• ·The Terms make an exception for a permission you choose that tells you, before you agree, about a platform’s own terms. “Work on LinkedIn for you” is one.
• ·The Privacy Policy now describes application tracking as it works: when an ApplyStorm address is on your applications, replies sent to it arrive in your ApplyStorm inbox, and ApplyStorm reads them to match confirmations, read one-time verification codes and update your applications. In Settings → Integrations → Application tracking you can choose to use your own email address on new applications instead; replies to applications already sent with your ApplyStorm address still arrive in your ApplyStorm inbox. It no longer mentions a Gmail connection, and ApplyStorm does not read your personal inbox.
• ·Elsewhere, both documents use plainer wording; the facts are unchanged.

The wording on this page and in the Chrome extension now says plainly who presses Submit: you do, unless you set a job board to Full Auto and turn on “Submit applications for me”.

• ·By default you review the form Storm filled and click the employer’s Submit yourself.
• ·On a job board you set to Full Auto, with the “Submit applications for me” permission on, the extension clicks Submit inside your own Chrome. A form that needs your own legal acknowledgement is handed back to you, so the final Submit is yours.
• ·The extension’s opening tips say the same thing. The updated wording arrives with the next extension release.

Applications opens faster, and expired applications are tucked away until you ask for them.

• ·The Applications list loads noticeably faster, especially if you have a long history.
• ·Expired applications are hidden by default. The top of the list shows how many are active and how many have expired, for example “66 active · 2,890 expired”.
• ·“Show expired” brings them back into the list, and “Hide expired” puts them away again. Paging through the list keeps your choice.
• ·Going back from an expired application returns you to the list with expired applications shown, so the one you were looking at is still there.

Storm can now work on LinkedIn jobs for you once you allow it. It is off until you turn it on, and it treats LinkedIn like any other job site.

• ·Settings → Automation → Storm permissions has a new permission, “Work on LinkedIn for you”. It is off until you allow it, and you can turn it off at any time.
• ·With it on, Storm handles a LinkedIn job the way it handles any other job site that is not on its supported list: it fills what it can and stops for you before Submit. If LinkedIn puts a sign-in in the way, Storm stops and tells you, as it does on any site that needs one.
• ·Without it, Storm does not open LinkedIn jobs. A LinkedIn job that was already queued stops with a note that says where to turn the permission on, and you can retry it once you have.
• ·LinkedIn’s terms don’t allow automated tools, and LinkedIn may restrict accounts that use them. The permission says so before you agree, because allowing it means accepting that risk.
• ·The permission lasts three years. Thirty days before it ends, Storm leaves a reminder in your ApplyStorm Messages, and emails you unless you have turned those emails off, so you can renew it.
• ·Settings keeps a record of when you allowed or turned it off, and the wording you agreed to.

If something on the employer’s page changes an answer Storm already filled and checked — browser autofill, the page itself, or you — Storm now says so, puts it back only when that overrides nobody’s choice, and otherwise asks you.

• ·While Storm waits for you to answer something on the form, it re-checks the form when the page changes. An answer that no longer reads back is not shown as answered, and “ready to continue” only appears when it is true.
• ·Text left in a dropdown’s search box is no longer mistaken for a choice. If a dropdown Storm filled only has stray text over it, Storm clears the text when you resume — it does not pick over whatever is chosen underneath — and checks the answer again.
• ·If a different answer is chosen, or an important answer such as work authorization is cleared, Storm does not overwrite it. It shows you the field; if you meant it, press Resume and Storm keeps it.
• ·When you resume, Storm fixes what it can before stopping again, and the stop names what actually needs you. If nothing on the page changed since the last time, Storm says so instead of repeating itself.
• ·In Review before submit, you click the employer’s Submit. Storm clicks it only on job boards you set to Full Auto, with “Submit applications for me” turned on.
• ·This needs extension 0.8.1.

When Storm stops for you, you can now answer right in the Storm panel, choosing from the employer’s own options. Storm fills the field, checks it took, and remembers your answer for the rest of that application.

• ·Each question Storm needs you for has “Answer here”. You see the employer’s real choices — radio buttons, a list, text, or chips for “select all that apply” — and Storm fills exactly the one you pick, then checks the page kept it.
• ·When your saved answer fits more than one of the employer’s choices (“LinkedIn” when they offer “LinkedIn (Company Page)” and “LinkedIn (Job Posting)”), Storm asks which one instead of saying nothing matches. This now also happens when Storm only finds out while filling.
• ·Your answer counts for the rest of the application, including after Resume — Storm will not ask again. If the employer changes the question in the meantime, Storm says so and asks again.
• ·Answers are for this application only. For a few general questions (such as work authorization) you can also choose “Save this answer for future applications”. Questions specific to one employer, like which cities you are available in, are not saved that way.
• ·Legal questions are not treated as ordinary answers. A routine notice covered by your Storm permission shows “Covered by your Storm permission”. An employer-specific consent shows the employer’s wording and an “Authorize for this application” button. Anything only you may complete, such as a background-check authorization, says so and stays on the employer’s page.
• ·In Review before submit, you click the employer’s Submit. Storm clicks it only on job boards you set to Full Auto, with “Submit applications for me” turned on.
• ·This needs extension 0.8.0.

Having an answer saved is no longer the same as Storm being allowed to use it. Ticking a legal box, sharing your self-identification answers and clicking Submit for you each now need a permission you gave, which you can see, renew or turn off in Settings.

• ·Settings → Automation has a new Storm permissions section: acknowledge routine privacy notices, confirm your applications are accurate, share your self-identification answers, and submit applications for you. Each shows when you turned it on and when it expires, and each can be turned off at any time.
• ·Saved answers to legal questions (“I agree”, “I certify”) are no longer ticked on your behalf just because they are saved. Storm ticks a routine notice or the accuracy statement only under the matching permission, only right before Submit, and records each one on the application under “What Storm did in your name”.
• ·Consents that are specific to one employer, such as processing your demographic data, need your OK for that application. You can give it with one click from the application page. Background checks, arbitration agreements, e-signatures and anything similar are yours to complete on the employer’s page.
• ·Full Auto now needs the permission to submit for you. Choosing Full Auto asks for it first; if it expires or you turn it off, Full Auto pauses and Storm Home says so. Nothing switches to Full Auto silently.
• ·If you have not given permission to share self-identification answers, Storm leaves those questions for you. It still picks “decline to answer” when that is what you saved. Your saved answers are not deleted.
• ·When you create an account, and once for existing accounts, you are asked to agree to the updated Terms of Service and Privacy Policy. The box is not ticked for you.
• ·This needs extension 0.7.0.

If Storm is waiting on you and you finish the form and click the employer’s Submit yourself, ApplyStorm now sees the employer’s confirmation and records the application as submitted — no Resume needed.

• ·While Storm is waiting on you in Chrome — for a question it could not answer, or for your review — it watches for the employer’s confirmation page. In that state the click is yours: Storm only notices that you made it.
• ·“Submitted” still appears only when the employer’s own confirmation is there. If the site refused your click (a field left empty), Storm says so and keeps waiting.
• ·A thank-you page is not mistaken for a closed job posting, even if you press Resume on it.
• ·If ApplyStorm still could not see it, the application page now offers “mark as submitted” while Storm is waiting on you in Chrome — recorded as your confirmation, and the waiting run closes.
• ·An application you send to Chrome now appears in the open Storm panel straight away, even beside a finished one. You no longer need to close and reopen the panel.
• ·This needs extension 0.6.1.

Clicking the ApplyStorm icon in Chrome now opens Storm in a side panel that stays open while you browse — and when Storm needs an answer only you can give, it says which question, why, and takes you to it on the employer’s form.

• ·The small pop-up is gone. The ApplyStorm icon opens the Storm panel, which shows the company and role it is working on, what it has done, and what happens next.
• ·When Storm stops for you, the panel lists each question as its own card — “Will you require sponsorship?”, “You haven’t answered this before” — with a Show field button that scrolls the employer’s form to it.
• ·A small ApplyStorm card also appears on the employer’s page itself, so you notice even with the panel closed. It highlights the questions, counts them down as you answer, and does not touch the form or its Submit button.
• ·When everything is answered, Resume becomes the obvious next step. Storm picks up the same application where it left off and keeps what you entered.
• ·In Review before submit, the panel ends at “Ready for your review”, and the click on the employer’s Submit is yours. Full Auto, where Storm submits for you, is clearly labelled, and says “Full Auto paused” when it needs you.
• ·“Submitted” appears only after ApplyStorm has the employer’s confirmation. The icon in your toolbar also shows how many answers are waiting.
• ·This needs extension 0.6.0 (Chrome 116 or later).

The Chrome extension now lists every application waiting for you to start, by company and job title, with its own Start button — and Start opens that application or tells you it cannot, rather than a different one.

• ·One Start per application. The popup and side panel show each application you sent to Chrome, oldest first, as company and job title. Clicking Start on one opens that one.
• ·Previously there was a single “Run next” button that opened whichever application had waited longest, which was not necessarily the one you meant.
• ·If an application can no longer be started — another device picked it up, it was cancelled, or it moved on — the extension says so and starts nothing else.
• ·Full Auto is unchanged: applications you set to Full Auto are still picked up by the extension on their own.
• ·This needs extension 0.5.7. An older extension will ask you to update when you press Start.

When your Chrome extension opens an application and the job is no longer accepting applications, stopping the run now moves that application to Expired instead of sending it back to your queue — and when you press Submit, Storm notes which filled fields you changed first, without keeping what you typed.

• ·A closed posting is treated as closed. If the extension lands on a job that has stopped accepting applications and you press Stop, the application moves to Expired — the same place applications go when a job disappears from its board — instead of returning to Ready to apply to be tried again. If the board lists the job again, it comes back on its own; Restore on the application page also brings it back.
• ·Storm now learns from your corrections. When you edit a field the extension filled and then press Submit, Storm records that the field was changed and what kind of change it was — retyped, reformatted, a different option, a different file. It is the raw material for fills that need fewer corrections; nothing about your answers or your account changes yet. Storm records only that you changed it, not the value you typed.
• ·This needs extension 0.5.0. Storm Home’s header tells you when your Chrome is on an older build.

When you set a job board to Full Auto, applications that pass your gates are filled and submitted by the ApplyStorm extension inside your own Chrome, with no click from you — and you are told when one is waiting on a Chrome that is closed.

• ·Full Auto is now a real setting, not a label. For a job board you put in Full Auto mode, an application that meets your score threshold, passes the résumé quality check and fits under your daily limit is handed to your Chrome extension, which fills the form, uploads your documents, checks the fields and clicks Submit. Chrome has to be open with the extension on; it does not run without it.
• ·Everything you stage yourself is unchanged. Send to Chrome extension, a Storm approval and Retry still fill the form and stop — Submit is your click. The extension only submits on its own for applications the Full Auto setting produced.
• ·A form the extension cannot complete — a question it will not answer for you, a challenge, a sign-in — is parked for you exactly as before. Full Auto does not invent an answer.
• ·The pause switch still stops it: pausing after an application is handed off turns that run back into one you submit yourself.
• ·If an application has waited fifteen minutes for a Chrome that has not picked it up, you get an email saying so, and Storm Home shows it — before, it waited a day and quietly failed.
• ·This needs extension 0.4.0. Storm Home’s header tells you when your Chrome is on an older build.

The emails ApplyStorm sends to confirm your address, reset your password or sign you in now put a 6-digit code first. Type it on the page you left open — or on any device — and you are in. The link still works, but it now opens a page with one more button rather than signing you in on sight, so the security scanners many company mailboxes run cannot use it up before you do.

• ·The confirmation, password-reset and sign-in emails begin with the code. It works for one hour and is single-use, and ApplyStorm does not ask you for it.
• ·Emailed links open a confirm page instead of signing you in directly. Nothing happens until you press the button on that page, which is what keeps a mail scanner from consuming the link.
• ·If a link really has expired, the sign-in page now says so instead of "Sign-in link is missing or invalid".
• ·The 6-digit code and the link are the same email — request either once and use whichever is easier.

A prepared application whose listing has disappeared, or that waited more than two weeks without you looking at it, now moves to Expired instead of sitting in your queue indefinitely. ApplyStorm also prepares at most 25 applications ahead of your review, and the KPI funnel now measures reviewed, submitted and responses against what was prepared — with expired shown beside it, not as progress.

• ·Expired is a new, reversible state: nothing is sent, the tailored documents are kept, and the application page says why — the employer stopped listing the job, or it was not reviewed in 14 days. Restore to queue puts it back; if a listing reappears on the employer’s site it is restored for you.
• ·Automatic tailoring now stops at 25 applications waiting for your review and resumes as you act on them or they expire. Pressing Generate on a job yourself is not limited by this.
• ·The KPI page’s funnel is now Discovered → Prepared (with how many passed or failed the quality check) → Reviewed → Submitted → Responses, each as a share of the stage before it, for the last 30 days. Expired applications are listed beside the funnel and are left out of the percentages.
• ·Storm Home lists expired applications under Recent outcomes, not under things that need you.
• ·The LLM-cost and embedding-usage cards left the KPI page; they were operator numbers, not yours.

Pro now costs $39 a month, or $105 every three months, and includes 75 applications, 40 submissions and up to 100 tailored résumés a month. Anyone already subscribed keeps the price they signed up at for as long as they stay subscribed, and any change to their limits comes with 30 days’ written notice and a prorated refund if they cancel before it takes effect.

• ·Two ways to pay: monthly, or quarterly at $105 (about $35 a month). Quarterly plans refund in full within 7 days of the charge and are otherwise non-refundable, with access kept to the end of the quarter. There is no annual plan on purpose — a search rarely lasts a year.
• ·Pro’s limits went up: 75 applications and 40 submissions a month, from 50 and 25. Tailored résumés are “up to 100 a month”, which is more than a 75-application month needs; existing subscribers keep unlimited tailoring until the written notice period has run.
• ·Existing subscribers are grandfathered. Nothing about their subscription changes; the earlier price stays on their account and is simply no longer sold to new customers.
• ·Each configured price is checked against Stripe before a checkout is created, so a wrong price is not sold by mistake — checkout refuses and names the setting instead.
• ·The budget banner no longer mentions a “Premium” plan; there was no such plan to buy.

The application page now shows the résumé’s quality-check result beside Send to Chrome and Submit. A résumé that failed a check is not sent on one click: you see which checks failed, can edit the résumé, and confirm in so many words if you want to send it as it is.

• ·Above the Send and Submit buttons the résumé’s result is stated plainly: passed; could not be fully checked (a check did not run, so the résumé is unjudged rather than bad); not checked yet; or failed, with each failed check named — a claim the résumé makes that your own material does not support, say — and what it found.
• ·Sending a failed résumé takes a second, deliberate click. The first shows exactly what failed and what confirming means for the path you chose — handing it to your Chrome to fill the form, or submitting it with the résumé as written — and offers Edit résumé instead. Nothing goes out until you confirm you have reviewed it.
• ·A résumé that could not be fully checked, or has not been checked yet, still sends on one click, with the notice in view — you are the reviewer.
• ·On the Jobs and applications lists, the reason Auto-apply is unavailable now says which of those three it is, instead of “hasn’t passed the quality check” for all of them.
• ·Storm is unchanged: it does not hand a résumé to your Chrome unless the check passed, whatever you confirm here.

Everything waiting on you now lives on the Storm page. Jobs shows a short summary of it and gets on with the job list, and the number in the top bar takes you straight to the queue.

• ·The Jobs page no longer lists every approval and question above the job list. A compact card says how many things need you and what kinds — "19 approvals", say — shows the two most pressing, and links to Storm for the rest. It is the same size whether one thing is waiting or a hundred.
• ·The "need you" number in the top bar is the way into that queue from anywhere in the product: it opens Storm at Needs your attention.
• ·On Storm, the queue is grouped — Approvals, Ready for your review in Chrome, Failed runs, Employer questions, Refused résumés — with a count on each. Large groups show five and fold the rest behind "Show all"; every approval stays on the page with its Approve and Decline buttons.
• ·A question from your specialist, or an interview email you have not answered, now appears on Storm too, so the number in the bar and the page it opens agree on what is waiting.
• ·These screens now refer to Storm by name.

Storm is now the first entry in the top bar: whether it is on, what it is working on, what it needs from you, what happened, and what actually got submitted — read from the same records the rest of the product uses, on one page.

• ·The header answers three things at a glance: is Storm on, paused or not yet enabled for you; does it ask before acting, and who clicks Submit; and is your Chrome extension connected, offline, unpaired or in need of an update.
• ·Needs your attention lists only what is waiting on you — an approval, a form filled and parked in Chrome for your review, a failed run you can retry, an employer question, or a résumé the quality check refused — each with the company and job, why Storm stopped, and one link to act. Approvals can be answered right there.
• ·In progress and Recent activity say what Storm and your browser are doing and did, in plain words: prepared, handed to Chrome, filling, waiting for you, quality check passed or refused and why, skipped and the rule, temporarily deferred.
• ·Recent outcomes labels each application with how far it got. “Submitted” is shown only for applications an employer actually received; a filled form, a parked form and an approved handoff are not called submitted.
• ·The page refreshes itself while anything is moving, and says so when part of your data could not be read rather than showing an empty list.

If your submission path is the Chrome extension, a tailored résumé and cover letter are now generated automatically only for postings the extension can fill; other strong matches are still found, scored and ranked, and are tailored the moment you ask.

• ·Matches from aggregators, or on sites the extension cannot drive, no longer consume your generation allowance on their own. Open one and press Generate now — the documents are produced the same way, through the same quality checks, and the application appears ready for a manual submission.
• ·The job page says when a match was not tailored automatically and why, so a strong match without documents is not a mystery.
• ·The same posting reissued under a new listing is not tailored twice. Two openings that merely share a title and employer — a different city, a different description — are still treated as two.
• ·If your path is self-service or a specialist, nothing changes: strong matches are tailored automatically, as before.

When Storm prepares an application and stops because your settings say ask first, the question now appears in Settings → Autonomy with Approve and Decline beside it.

• ·Each waiting action says what Storm wants to do and to which job, when it asked, and when the question lapses if nobody answers.
• ·It also says what it will not do. Approving hands the application to your Chrome extension, which fills the form, uploads your documents and checks the result — then stops. You click Submit; approving does not send the application to the employer.
• ·Approving releases the work Storm had already paused; it does not start something new. Declining is final for that application — Storm will not ask about it again.
• ·Only you can answer: the decision is recorded against your sign-in, and it applies to that one action rather than changing what Storm may do next.
• ·Questions that lapsed before you saw them say so instead of offering a button. Storm asks again the next time it reaches that step.

Three new pages you can read without an account: how it works, what it costs, and the questions people ask — with the same answers the help guide gives.

• ·How it works walks through the pipeline in order: finding roles, writing the materials, filing the application under your control, following employer replies, and preparing for the call.
• ·Pricing now has its own page — the Terms of Service had pointed to one for months. It states the free tier and the Pro plan side by side, with the monthly limits of each and how refunds and cancellation work.
• ·The FAQ publishes the customer half of the help guide, so what happens with CAPTCHAs, LinkedIn, the kill switch, recordings and your data can be read before you decide.
• ·Links to all three sit in the footer of every page.

Settings → Autonomy shows each thing Storm can do, whether it is Off, asks you first, or runs automatically, and why — and lets you make a time-boxed change.

• ·Every capability shows its level and where that level comes from: the product default, a choice you made, or a limit Storm tightened on itself.
• ·A temporary change lasts from one hour to seven days. Tightening takes effect immediately. Loosening is recorded as a request and changes nothing until you approve it in a second step that names the consequence — so a looser setting does not take effect without a deliberate yes from you.
• ·You can end a temporary change early, or withdraw a request you have not approved, at any time.
• ·If a setting cannot be read, the page says Unknown rather than guessing. It does not show a more permissive level than it can prove.
• ·Not yet: changing a permanent level from this page. It is shown honestly as not offered rather than as a button that does nothing.

Paste or upload an offer and the terms are read out — base, bonus, equity over four years — with anything read wrong yours to fix in two clicks.

• ·Find it under Interviews → Offers. Paste the offer email or upload the letter (PDF or Word); the terms appear as editable numbers with the original text kept alongside.
• ·Terms are not guessed: a term the letter does not state shows as a dash, not an invented “typical” value. A bonus stated as a percent is computed from the stated base — by arithmetic, not by the model.
• ·Each offer shows its 4-year value and what arrives each year — a vesting cliff delays money, it does not reduce it, and the math treats it that way.
• ·With two or more offers in the same currency, a side-by-side ranks them by net present value. It is labeled as arithmetic, not advice: the right offer weighs things no letter states.
• ·A parsed offer can become a negotiation playbook: what to ask for first and the exact words to say it, a sendable email, the 60-second phone version, and replies to the pushback you will actually hear. No number appears in a script unless it came from the letter or from you.
• ·Then practise it out loud: one click seeds the recruiter’s pushback lines into Rehearsal, where your answers are scored on holding your anchor, arguing value rather than need, and not inventing a figure.

When an employer replies, ApplyStorm reads the outcome — and what it cannot decide alone, it asks you in one click.

• ·An interview invitation or an offer from a verified sender moves the application forward automatically, so your pipeline reflects reality without you doing anything.
• ·A rejection is not applied automatically. It appears on the application as a one-click question — “this email looks like a rejection, is that right?” — with the exact phrases that made us think so. Rejections are final, so a human decides.
• ·You can now record what happened off-platform: a screening call, an interview, an offer, an acceptance or a rejection — straight from the application page. Phone calls and hallway offers count too.
• ·The KPI page now shows the whole journey: how many applications reached screening, interviews, offers — and the median days spent in each stage. Percentages appear only once there is enough data for them to mean anything.
• ·Every resume is tagged with how it was generated, so once enough applications resolve, the page can tell you which resume approach actually gets conversations. Until then it honestly says “collecting”.

The number beside Messages now tells you what kind of message arrived, not just how many — and there is a searchable guide to everything the product does.

• ·Amber means an employer, cyan means your specialist, violet means a notice from us. Several kinds waiting shows small dots so you can tell which, without opening anything.
• ·Nothing is shown when nothing is unread — the badge appearing means something genuinely arrived.
• ·Help now has a searchable guide to the product’s features. Search the words you would actually use: “stuck”, “captcha”, “delete my account”.
• ·Replying to an employer from Messages works again — replies had been failing to send, and now keep the conversation threaded properly on their side.

Employers close postings without warning. When that happens you now see it said plainly, instead of a failure that looked like something had gone wrong on our side.

• ·A job that has been removed is recognised in about a second and labelled as closed, rather than timing out.
• ·A run of closed postings no longer pauses automatic applying — it used to look like a fault and stop the jobs queued behind them.
• ·You are not notified for these. A posting being taken down is not something you need to do anything about.

When the other person asks you something, the shape of an answer appears on screen — which of your experiences to reach for, and the two or three beats to hit.

• ·Turn it on with its own tick when you start a recording. It is off unless you choose it, and only for that one interview.
• ·It reads only the other person’s side of the call, only while you are recording, and none of it is kept.
• ·It writes the framing itself, drawing on your résumé and saved answers — but it will not put a number or a company in front of you that is not already yours.
• ·If nothing of yours fits the question it still helps, with a structure to fill rather than nothing at all.
• ·Withdraw permission at any point and it stops sending immediately.
• ·The panel shows how long each answer took to arrive, so you can judge for yourself whether it is fast enough to be worth a glance.

After an interview is transcribed, you now get a written review of it: what you were asked, what you said, what either side promised, and what to do next.

• ·Every question you were asked is listed with the time it came up, so you can jump straight to that moment in the recording.
• ·Your answers are scored against the same criteria the Rehearsal Studio uses, so practice and the real thing are directly comparable.
• ·Anything you did not really answer is called out — and those questions are added to your future practice sets, so you get another go at them.
• ·Commitments are recorded: what they said they would send you, and what you said you would do.
• ·A follow-up note is written for you, referencing something you actually discussed. It is text for you to use; ApplyStorm does not send it.
• ·You can record how each interview turned out, which is what lets your dashboard show which kinds of interview actually convert.
• ·Phone interviews are supported properly: choose "a phone call" and you will not be asked to share a screen there is no point sharing.
• ·You can upload an interview you recorded somewhere else — a voice memo, a Zoom export — and it goes through exactly the same steps.
• ·We do not predict whether you will be hired, rate you as a candidate, or assess your personality. The review records what was said; it does not judge who said it.

You can now delete your account yourself, from Settings. It removes your files first and then every record we hold about you — and you have a week to change your mind.

• ·Settings → Account has a Delete your account section. You confirm by typing your own email address rather than clicking a dialog, because the mistake worth preventing is being on the wrong account, not clicking too fast.
• ·Deletion runs 7 days after you confirm, and you can cancel at any point during those 7 days. Until then nothing is removed.
• ·When it runs it removes your uploaded résumés, generated documents, employer messages and attachments, interview and practice recordings, and transcripts — the stored files first, then every record.
• ·Billing records are kept for 7 years because tax law requires it. That was already in the Privacy Policy; it is now also stated on the deletion screen itself, where it is actually read.
• ·Only the account owner can start or cancel a deletion.

Roles now come from employers well beyond the tech company boards — universities, banks, healthcare systems, government contractors — and each one is tailored from the full job posting.

• ·A broad job-market source that had been quietly returning nothing is now live. In its first hours it brought in over a thousand roles, from employers the company-by-company boards do not cover.
• ·Résumés and cover letters are written from the complete job posting. Previously, roles from that source arrived as a short preview — a few hundred words — and everything was tailored from that. The full text is now pulled in first, averaging roughly five times more to work from.
• ·Where only a short posting is available, the résumé review page says so plainly, so you know why a résumé reads more generally than usual instead of guessing.
• ·A source that fails once mid-run no longer throws away everything it had already found.

Record an interview and get a transcript — with permission handled properly, because the other person on the call did not sign up for anything.

• ·Recording is per interview, not a setting you leave on. Permission expires after four hours and you can withdraw it mid-call.
• ·Before your first recording you are told the part that catches people out: in much of the world, recording a conversation is only lawful if everyone on it has agreed. You confirm you will tell them.
• ·A recording indicator stays visible the whole time, including in the browser tab title when you are looking at the call instead of us.
• ·Audio is transcribed on ApplyStorm’s own servers by default and deleted after 30 days. The transcript is kept for a year. You can delete either yourself at any time.
• ·Audio by default, with screen video as a separate opt-in that is off unless you tick it. You pick which tab carries the call and tick “Also share tab audio”; while you record, the panel shows which sources are actually live so you can tell if only your own half of the conversation is being captured.
• ·Audio recordings have no player and no download link — they exist to become a transcript, then they go. Where you recorded the screen, the video is playable on the transcript page, because a screen recording cannot be read as text.

Talk to the specialist working your applications, and read employer mail as conversations instead of a wall of messages.

• ·Messages is now two places: a private conversation with your specialist, and your employer mail. They are kept apart on purpose — a note to your specialist should not be one keystroke away from a reply to a hiring manager.
• ·When your specialist needs something before they can submit an application, the question now appears where the notification sends you, and you can answer it there. Answering it releases the application.
• ·Your specialist can see when you have replied, so a question you have answered stops holding things up.
• ·Your email is grouped into conversations, so a reply sits with the message it answers rather than somewhere else in the list. It covers everything that arrives at your application address — employers, recruiters, agencies and job boards — not employers alone.
• ·If more than one specialist works your account, every message says who wrote it, in one shared conversation rather than several you would have to keep track of.
• ·Unread mail is marked as unread, with a filter for it and a count on the tab. Opening a conversation marks only that one read.

Practise interview questions written from the job you actually applied to, answer them out loud, and get scored on what an interviewer would be listening for.

• ·Questions are generated from the job description, the résumé that was actually submitted for it, and your own match-score rationale — not from a generic question bank.
• ·Each question traces to a specific line in the posting or your résumé. Anything the system cannot trace is discarded rather than shown.
• ·Answer out loud. Recordings are transcribed on ApplyStorm’s own servers by default; audio is not sent to a third party unless you are explicitly moved to one.
• ·Each answer is scored against a rubric built for that question type — behavioural, technical, system design, case, and role-specific each get different criteria.
• ·Feedback cites its evidence. Each "what was missing" point quotes the phrase from your own answer that prompted it, so you can check it rather than take our word.
• ·Answers you are happy with can be saved to your Answer Bank and reused when filling out real applications.
• ·Practice mode allows unlimited retries per question; full mock gives you one attempt each, the way a real interview does.

Mail from employers now arrives in the product, is matched to the application it belongs to, and can be replied to without leaving the dashboard.

• ·Each account gets its own address for applications, so replies come back somewhere the product can see them.
• ·Incoming mail is classified — confirmations, rejections, interview invitations — and linked to the right application.
• ·Reply to an employer directly from Messages, with proper threading so it lands in the same conversation on their side.
• ·Attachments employers send are stored and downloadable, and are not opened or rendered in the browser.
• ·Correspondence is kept for 365 days and then deleted automatically.

A managed service line where a trained rep works your application backlog on your behalf — with your explicit consent, and a full audit trail.

• ·Nothing happens until you opt in. Consent is required before a rep can see your material, and revoking it closes their access immediately.
• ·Actions a rep takes on your account are recorded and visible to you.
• ·Reps do not see your EEO information; it stays encrypted and out of their view.

Free and Pro tiers, with usage caps enforced in the pipeline itself.

• ·Monthly caps on applications, submissions and résumé tailoring, applied where the work happens rather than only in the interface.
• ·Trial codes for early access.