In partnership with
Little Known RMD Strategy Allowed By The IRS
Not understanding RMD strategies can impact your retirement. Most retirees don't find out how costly that is until the tax bill arrives.
You're over 65 with $500K+ saved. The IRS doesn't ask if you're ready to withdraw, it tells you how much, starting now. The IRS doesn't care how your money is invested. It only cares how it's withdrawn.
That's the part many retirement plans never account for. The order you take it in, the accounts you pull from, and timing all matter.
Get that sequence wrong and you risk a higher bracket, Medicare surcharges, and lost hard earned money.
How you sequence withdrawals can affect what you pay in lifetime taxes. Results depend on your accounts, income, and tax situation.
Match with an expert advisor to find the IRS allowed RMD strategy that fits you.
If you have $500K+ invested, don't let the IRS decide for you.
Welcome to today's SCALIS CareerHack newsletter! 🚀
You have twenty years of exactly the right experience. You read the posting twice and you can do every line of it. You upload the resume, and then the form asks you three more things: what year you finished your degree, how many years of experience you have, and whether you would like to voluntarily self identify.
You answer honestly, because you are an honest person. Submit. Nothing.
Here is the part nobody says out loud. By the time anyone forms an impression of you, your age has already been transmitted as structured data. Not inferred from your writing. Not guessed from a photo. Entered by you, into a field, in a format a database can sort on.
And the legal protection you assume covers this mostly does not. The Age Discrimination in Employment Act protects applicants who are 40 or older, and it applies to private employers with 20 or more employees along with state, local, and federal government. It generally makes it unlawful to put age preferences or limitations into a job notice or advertisement. It also generally makes it unlawful to decide against you because of age. But the EEOC's own guidance is explicit that the ADEA does not prohibit an employer from asking your age or date of birth on the way in. The front door is regulated. The middle is not.
This is not a small population. AARP Research has found that 14 percent of adults 50 and older say they were not hired for a job in the past two years because of their age, and roughly half of older jobseekers report being asked for a birth date somewhere in the process. Today is about the fields, the habits, and the vocabulary that answer the question before you get to.
Read the posting for age-coded language, then use it as a filter on them
Start upstream. The EEOC's regulation on help wanted notices treats language that limits a role to new or recent college graduates as discriminatory against older workers, and AARP Foundation has litigated exactly that, suing a major aerospace and defense employer in 2024 over postings restricted to recent graduates or candidates with under two years of experience.
So when you see "recent grad," "digital native," or a hard ceiling like "3 to 5 years, no more," you are not being paranoid. You are reading language a federal agency has flagged.
The tactical use: do not spend an afternoon being angry about it. Treat it as free information about how that employer builds a candidate profile, and apply somewhere else. Your search has a fixed number of hours in it. Age-coded postings are the cheapest thing to cut.
Your graduation year is the single loudest field on the form
About 53 percent of older jobseekers report being asked for a graduation date. It is the most efficient age proxy that exists, because it is a four digit number that converts to your birth year with one subtraction.
On your resume, the degree year is almost always optional. Nobody is owed it. List the institution, the degree, and the field. Drop the year. This is not deception, it is scope: a hiring team is entitled to know you hold the credential, not when the ceremony happened.
On the application form itself, be careful. If the field is required, fill it in accurately. Never put a false year into a form you sign. Falsified application data is a legitimate firing offense later, and it converts a discrimination problem into a cause problem, which is a much worse trade. If the field is optional, leave it blank and move on.
Know what the experience dropdown is actually measuring
"Years of experience" dropdowns usually top out somewhere around "10+" or "15+." That ceiling exists because the field is a screening threshold, not a biography. Selecting the top bucket tells the system you cleared the bar. It does not award you extra points for the years above it.
Which means the standard resume convention is not a betrayal of your career. Lead with the last 10 to 15 years in full detail, then compress everything before it into a short "Earlier experience" line with employers and titles and no dates. You keep the long arc. You stop handing over a 30 year timeline nobody was going to use.
The exception is when depth is the product. Regulatory, clinical, actuarial, safety, and skilled trade roles often want total years on the record. Read the posting and decide, rather than applying one rule everywhere.
AI news from people who build AI
TLDR AI is the free daily brief curated by Anthropic and ex-Google engineers. The stories, models, and research they'd send a colleague, summarized for 1.1M+ readers.
Currency beats chronology, and vocabulary leaks harder than dates
You can strip every date off a resume and still get read as dated in six seconds, because tooling is the real tell.
Naming the current stack is what closes it. If your function has moved to newer tools in the last three years and your resume names none of them, the year on your degree is not what is costing you. Audit your last three postings of interest, list every named tool, and be honest about which ones you have actually touched. Then either use them or learn them, because inventing familiarity falls apart in the first technical conversation.
Two smaller habits that read as decades old: "References available upon request" and an email address on a legacy provider domain. Delete the first. Take five minutes on the second.
The self identification section is genuinely voluntary
Near the end of most applications there is a demographic block covering things like age range, race, gender, veteran status, and disability. It is collected for aggregate reporting, and every question in it has a "prefer not to answer" or "decline to self identify" option.
Use it if you want to. Declining is a normal, common answer and cannot lawfully be held against you. Just do not confuse this block with the application. Declining here does nothing about the graduation year field you already filled in twelve screens earlier. That is the field that mattered.
What to say when someone asks you directly
Sooner or later a recruiter asks the question in conversation, usually as "so, how many years have you been doing this?" or "when did you graduate?" The instinct is to either deflect awkwardly or over explain. Both read badly.
Answer briefly and redirect to velocity. Something like:
"Long enough to have seen a few cycles of this, which is mostly useful because I know which problems are actually new. Most recently I was doing [current thing] with [current tool], and the part I want to keep doing is [specific thing in their posting]. Where does this role sit on that?"
That does three jobs in four sentences. It does not dodge. It converts tenure from a liability into pattern recognition. And it moves the conversation to the present tense, which is where you want to be evaluated.
One honest note to close on. None of this makes bias disappear, and you should not have to manage any of it. But there is a real difference between the parts of this you control and the parts you do not, and the fields on the form are squarely in the first category. Fix those this week. Then go be the most current person in the process.
Modern Pricing Models Break Finance (And How to Fix It)
Usage-based and hybrid pricing models are reshaping B2B revenue and creating real complexity for finance teams. Tabs and PwC break down what it means for rev rec, forecasting, and ops. Watch the on-demand recording for practical frameworks you can actually use.
