Education, Government & Nonprofit

How to get hired as a policy analyst in 2026-27

The short answer

To get hired as a policy analyst in 2026-27 you need three things an employer can verify: a sole-authored writing sample of two to five pages that reads like a decision memo rather than a seminar paper, quantitative work you can defend in Excel plus one of R, Stata or Python against named public data such as American Community Survey microdata or a Bureau of Labor Statistics series, and a target list that treats federal agencies, think tanks and research firms, advocacy organizations, legislative offices and government contractors as separate hiring processes on separate clocks. There is no license and no exam for policy analysts, so the de facto credential is a master's (an MPP, an MPA, or a disciplinary master's in economics, statistics or public health), but federal jobs are gated by the OPM occupational series rather than by the degree: GS-0343 Management and Program Analyst carries no education requirement, while GS-0110 Economist requires specific coursework that is either on your transcript or is not. Federal hiring runs through USAJOBS and commonly takes months rather than weeks, with a self-rated occupational questionnaire deciding whether a policy person ever opens your resume, while think tanks and research firms move in three to eight weeks and usually add a timed data or writing exercise, and advocacy groups and congressional offices can hire in two weeks on a referral. The writing sample is the piece entirely within your control: recommendation in the first paragraph, real options with costs, and every number traceable to a source you can name out loud.

License or credentialNone. Policy analyst is an unlicensed, unregulated title: no board, no exam, no continuing education requirement, and nobody can stop you calling yourself one. The de facto credential is a master's degree, with the Master of Public Policy as the canonical version, alongside the MPA and disciplinary master's degrees in economics, statistics, public health, social work and city planning. NASPAA accredits MPP and MPA programs; that accreditation matters to some public employers and to almost no private ones.
What the de facto credential actually requiresA two-year master's, usually four semesters, built around microeconomics, statistics and econometrics, public budgeting, program evaluation and a capstone client project for a real agency or nonprofit. Most programs expect calculus or a statistics course before entry and many run a quantitative boot camp before the first term. The summer internship between the two years does more hiring work than the diploma does.
How long it takesTwo years for the master's. Without one, expect to enter at a support title (research assistant, research analyst I, legislative correspondent, program assistant, fiscal analyst I, management analyst I) and reach a full analyst title in roughly two to four years, which is a normal and respectable route at state and local level, on Capitol Hill and at contractors. Federal onboarding adds its own clock on top: commonly two to nine months from the day an announcement closes to your start date, and longer when the job needs a security clearance.
The federal rule that really gates youThe OPM occupational series, not the prestige of your school. GS-0343 Management and Program Analyst carries no positive education requirement and is the widest federal door for a policy person. GS-0110 Economist has a mandatory coursework requirement (currently stated by OPM as 21 semester hours of economics plus 3 semester hours of statistics, accounting or calculus, so read the current standard). GS-1530 Statistician and GS-1515 Operations Research Analyst have their own coursework rules. GS-0101 Social Science and GS-0301 Miscellaneous Administration and Program sit in between. Read the Qualifications section of an announcement before you read anything else, because that is the part that disqualifies people.
Who screens you, by employer typeFederal: a human resources specialist who is not a policy person scores your self-assessment questionnaire and checks your resume for the announcement's exact specialized experience wording, and only a certificate of eligibles reaches the hiring manager. Think tanks and research firms: a recruiter, then researchers who read your writing sample line by line and ask where each number came from. Advocacy and legislative offices: the hiring manager directly, frequently from a referral, sometimes start to finish in under two weeks.
The artifact that decides itA sole-authored writing sample of two to five pages, recent, and cleared for release. The genre that works is a decision memo or issue brief: recommendation in the opening paragraph, two or three real options with costs and distributional effects, the strongest objection stated fairly, every figure sourced. Sending a thesis chapter, a literature review, or a co-authored report with no note on which parts you wrote is a common way a strong candidate loses to a weaker one.
The quantitative floorExcel at the level of a working cost model, a pivot table over a hundred thousand rows, and a projection whose assumptions sit in labeled cells, plus one of R, Stata or Python used on a real dataset you can discuss unprompted: ACS or CPS microdata from IPUMS, a BLS series, a state administrative extract. Research firm and think tank roles test above that floor: weighted survey estimates with correct standard errors, a script that runs from raw data to table, and the ability to say what a difference-in-differences estimate does and does not license you to claim.
Pay, and where to look it upDo not quote a salary aggregator for this title. Policy analyst work is split across several BLS OES codes, so start with 19-3094 (political scientists), 13-1111 (management analysts), 13-2031 (budget analysts), 19-3011 (economists) and 19-3099 (social scientists, all other) for medians and percentiles by metro area. Then use the sources that publish real numbers rather than estimates: OPM General Schedule tables with the correct locality adjustment, the House Statement of Disbursements and Senate public reports for congressional staff pay, state classified salary schedules, IRS Form 990 filings for nonprofit and think tank ladders, and posted ranges in pay-transparency jurisdictions such as Colorado, California, Washington, New York, Illinois, Maryland and the District of Columbia (the list of those jurisdictions keeps growing, so check the current rule where you are applying).

Several different jobs share the title, and the employer decides which one you applied for

The phrase policy analyst covers at least five jobs that have almost nothing in common day to day. They pay differently, they are hired differently, they reward different skills, and the resume that wins one is often ignored by another. Before you write a word of application material, work out which one you are aiming at, because that single decision determines whether your time is better spent learning Stata or learning a legislature's committee calendar.

In a government agency, a policy analyst is usually implementing. You are the person who turns an enacted statute into something an agency can actually do: writing the guidance document, drafting the rule and its preamble, assembling the regulatory impact analysis, answering the congressional inquiry, running the clearance process that sends a document through six offices and a general counsel. The work is heavily textual, deadline-bound, and constrained by process you did not design. Federal titles for this work are often not policy analyst at all: Management and Program Analyst, Program Analyst, Social Science Analyst, Policy Advisor, Economist.

In a think tank or a research firm, a policy analyst is producing evidence. At the Urban Institute, Brookings, RAND, Mathematica, Abt, Westat, RTI, NORC, MITRE, the Pew Charitable Trusts or a university policy center, the entry role is usually titled research assistant or research analyst, and it is quantitative in a way the title policy analyst does not signal. You will spend real weeks cleaning data, writing code, checking somebody else's regression output, and building the exhibits for a report with your name third on it. The senior title, policy analyst or senior researcher, often requires a PhD, and at RAND in particular the title Policy Analyst sits in a research career ladder rather than an administrative one.

In an advocacy organization, a policy analyst is arguing. You write the comment letter on a proposed rule, the fact sheet a legislator reads in the elevator, the testimony, the state-by-state table that makes a national argument local. The organization has a position and you are expected to advance it honestly, which is a different discipline from being neutral: your numbers must survive hostile checking precisely because somebody hostile will check them.

In a legislative office, at either the federal or state level, the job is speed and triage. Congressional staff titles run staff assistant, legislative correspondent, legislative assistant, legislative director, and a legislative assistant covering health or tax is doing policy analysis under a clock measured in hours. State legislative service agencies are the quieter and often better version of this: the California Legislative Analyst's Office, the Texas Legislative Budget Board, the Colorado Legislative Council, Florida's Office of Economic and Demographic Research and the fiscal and research offices in most other statehouses hire nonpartisan analysts to write fiscal notes and bill analyses, and they hire on written exercises rather than on connections. Executive budget offices (a governor's budget division, Washington's Office of Financial Management, a city budget office) are the executive branch equivalent and hire the same way.

In a consulting firm or a federal contractor, a policy analyst is billable. Deloitte Government and Public Services, Booz Allen, Guidehouse, ICF, Accenture Federal and dozens of smaller firms staff the analysis that agencies are not resourced to do themselves. The hiring is faster than the government's, the pay is usually higher, the work can be excellent or can be slide production, and the question to ask in the interview is which contract you would sit on and how many option years remain on it.

Two practical consequences follow. First, apply to at least two of these categories at once, because their clocks differ by an order of magnitude and a search built only on federal applications can leave you unemployed for a quarter waiting on a certificate. Second, name the category in your own materials. An opening line that says you want to do regulatory analysis at a health agency beats one that says you are passionate about public policy, because the first is a claim a hiring manager can evaluate.

Credentials: no license, a de facto master's, and the federal rules that are the real gate

Policy analysis is not a licensed profession anywhere in the United States. There is no board, no registration, no protected title, and no exam you must pass before someone may pay you to analyze policy. That is worth saying plainly because advice written about other professions leaks into this one, and candidates waste money on certificates no hiring manager has heard of.

What exists instead is a strong hiring convention. For an analyst title at a federal agency above the entry grades, at a national think tank, at a research firm, or at a well-funded advocacy organization, a master's degree is the normal expectation. The Master of Public Policy is the canonical one and is usually the most quantitative of the public sector master's degrees. The MPA sits closer to management and is the better fit for local government, nonprofit leadership and program administration. A disciplinary master's is often a stronger signal than either for a specialized job: economics for anything with a price or a tax in it, statistics or data science for evaluation work, public health for health policy, social work for human services, planning for land use and transportation.

A master's is not required, and treating it as required is itself a mistake. Three routes in without one are well worn. The congressional ladder: a staff assistant or legislative correspondent position, two or three years, then a legislative assistant portfolio, then a move downtown to an association or a firm that wants a person who knows a committee. The state route: a fiscal analyst or program evaluator position in a legislative service agency or an executive budget office, which hires on a written test and promotes on competence. The data route: a data or research analyst job anywhere that has administrative data, then a lateral move into the policy shop that consumes your tables.

There is also a set of federal on-ramps that exist specifically for people without federal experience, and they are easy to miss because they are announced differently. Pathways internships hire current students; the Recent Graduates Program hires people within a limited window after completing a degree (OPM has long set that window at two years, extended for veterans, so confirm the current eligibility text before you rely on it). Both can convert to a permanent position. Agency use of them varies by year and by budget, so check whether the agency you want is actually running them rather than assuming.

If you do pursue the master's, two details matter more than rank. First, does the program put you in front of a real client? A capstone or practicum that produces a deliverable for an actual agency gives you the sole-authored or clearly attributed writing sample this field hires on, and a transcript does not. Second, is the quantitative sequence real? Compare syllabi, not brochures: a program whose required statistics course ends before regression leaves you unable to pass a research firm's data exercise.

Funding deserves a blunt paragraph. Policy analysis pays less than law, consulting or finance for a comparable amount of schooling, and a debt-financed MPP at full price is a genuinely risky trade. Chase funded offers. Ask every program for the share of students receiving aid and the median award, ask about assistantships that come with tuition remission, and compare a funded offer at a good state school against an unfunded offer at a famous one with clear eyes. Public Service Loan Forgiveness has been the standard answer to this problem for public sector workers; its rules and its administration have been contested and amended repeatedly, so verify the current terms with your servicer and the Department of Education rather than with a blog post or with this page.

Certificates are mostly noise, with a few exceptions that are specific rather than general. For analysts who will touch confidential federal statistical data, the training and the data use agreements that come with restricted data access are real and worth naming on a resume. For anyone doing budget work, the Government Finance Officers Association and the National Association of State Budget Officers publish the vocabulary your interviewers use, and their conferences are where state budget people actually meet. In evaluation, visible participation in the American Evaluation Association does more than any paid certificate. A generic online certificate in data analytics will not move a policy hiring decision, although the skills it teaches will, if you can show the output.

One more credential-shaped item: a security clearance. Some agency and contractor policy jobs require one, and an active clearance is a genuine hiring advantage because it removes months from the employer's timeline. You cannot sponsor yourself. If a posting requires an active clearance and you have none, it is usually not worth your application unless the announcement says the employer will sponsor.

Different hiring machines, different clocks, and the one that will waste your year

These employers do not run the same process. Running one search against all of them as though they did is the most common structural error in a policy job hunt. Here is what each one actually does.

Federal agency hiring through USAJOBS is a rating process disguised as an application. An announcement goes up with a closing date and sometimes a cap on applications. You answer an occupational questionnaire in which you rate yourself on each competency, usually with the top option phrased as having performed the task as a regular part of a job and having trained others in it. A human resources specialist then verifies that your resume supports the ratings you claimed and that you meet the specialized experience statement for the grade, which is normally one year of relevant experience at the next lower grade level. If the questionnaire ratings and the resume do not match, you are rated ineligible and no policy person ever sees you. If you clear, you land on a certificate of eligibles and the hiring manager selects from it. Then come interviews, a tentative offer, a suitability and background investigation, and a start date. Two to nine months end to end is normal, with veterans' preference, direct hire authorities and funding lapses all capable of changing the arithmetic. Apply, then keep applying to other things.

The nonpartisan legislative support agencies run their own assessments and are worth separating out. GAO hires analysts into a pay band structure and uses a structured process that typically includes a writing assessment and a competency-based panel; the work is engagement-based, team-based, and famously good training. The Congressional Budget Office and the Congressional Research Service hire on demonstrated analytical writing and demonstrated nonpartisanship, and both will read what you have published. If you intend to work in any of these, be careful what you put your name on publicly: a sharp partisan opinion piece is an asset in advocacy and a liability at CBO, CRS, GAO and most state legislative service agencies, where your entire value is that both parties trust you.

Think tanks and research firms move faster and they test. A recruiter screen, then a take-home or timed exercise, then a panel, then a director conversation. The exercise is the heart of it and comes in two flavors: a data task (here is a messy extract, produce these three estimates and tell us what you would caveat) or a writing task (here is a study and a press release about it, write a two-page memo for a nontechnical principal). Three to eight weeks is typical. Firms with federal contracts (Mathematica, Abt, Westat, RTI, NORC, ICF) also hire in waves tied to contract awards, so a rejection in March and an offer in September from the same firm is unremarkable and worth re-applying for.

Advocacy organizations and philanthropies hire the way a small team hires: a hiring manager who will be your boss, a work sample, two conversations, references, offer. Two to six weeks. The screen that eliminates most candidates is not skill but fit with the organization's theory of change. Read their last three publications before the first call and be able to say what they are trying to accomplish and where you would contribute. Many of these organizations have moved to structured, scored interviews and to publishing salary ranges, partly because of pay-transparency laws and partly because small teams have learned that unstructured interviews hire people who sound like the interviewer.

Legislative offices hire on referral and availability. For Congress, the practical channels are the House and Senate vacancy and placement services, the Tom Manatos and Brad Traverse job lists, committee and leadership networks, and alumni of your school's Washington program. Applications are frequently a resume, a cover letter, two writing samples and references in a single PDF, emailed to an address that gets hundreds of them. Turnaround can be a week. Pay at the bottom of the ladder used to be indefensible and has improved in the House through a staff salary floor and larger office allowances, but the top of the ladder is still well below private sector equivalents and the hours during session are long. State legislative offices run on the legislative calendar: hiring happens between sessions, and the fiscal office of a statehouse is one of the best training grounds in the field.

There is also a side door most candidates never try. Policy organizations consume more research help than they can budget for and routinely hire people who have already done visible work in their space: a public comment you filed on a docket under your own name, a state-by-state dataset you assembled and published, a short analysis you posted that a program officer quoted. This is not advice to work for free. It is advice to produce one public artifact in the specific policy area you want to be hired into, because it converts a cold application into a warm one. Filing a comment on a proposed rule at regulations.gov costs nothing, is permanently public, and is a legitimate line on a resume.

If you are not applying in the United States, the structure differs enough to matter. The United Kingdom hires policy people through the Civil Service recruitment system against the Success Profiles framework, with the Fast Stream as the graduate entry route and separate professions for the Government Economic Service and Government Social Research, both of which run technical assessments including a numerical test and a presentation. Canada hires into pools through GC Jobs with standardized tests and official language requirements, and its Policy Analyst Recruitment Program has historically been the main graduate on-ramp. The European institutions hire through EPSO competitions that take the better part of a year. Australia runs an annual Australian Public Service graduate program intake. In all four, the written assessment is a bigger share of the decision than in the United States, and the deadlines are annual rather than rolling, so a missed window costs twelve months.

The writing sample: what to send, how to build it, and what gets you cut

This is the part of the application that decides policy analyst hiring, and it is the part candidates get wrong most often. Nearly every serious employer in this field asks for a writing sample, and most of them are using it to answer one narrow question: can this person take something complicated and give a busy decision maker what they need in two pages without being either vague or wrong.

Send a decision memo or an issue brief. Two to five pages, single-authored, written in the last two years, and about a policy question rather than about a literature. If you only have academic work, write something new; it takes a weekend and it is the single best weekend you can spend on this search. Do not send a thesis chapter, a literature review, a research proposal, a journalism clip, or a twenty-page seminar paper with the recommendation on page fourteen. A reviewer reads the first paragraph and the headings, and if your conclusion is not in the first paragraph they conclude you do not know the genre.

The skeleton below is the standard shape of a policy memo and no reviewer will think less of you for following it exactly. What they will notice is whether the options are real. The most common weakness in a sample is three options where one is obviously correct, one is a straw man and one is do nothing. Real options have different losers. If nobody is worse off under your recommendation, you have not found a policy question, you have found a press release.

Every number in the sample must be traceable. Put the source in the sentence or in a footnote with enough detail to re-find it: the dataset and vintage, the table number, the series ID, the year. A Bureau of Labor Statistics series ID rather than according to the BLS. ACS 2023 five-year estimates, table B17001, rather than Census data. You will be asked about one of these numbers in the interview, and the answer that gets you hired is the one that includes where it came from, what the denominator is, and what you would not use it for.

Clearance and confidentiality are non-negotiable and candidates do get eliminated here. If a sample came from a government job, a client engagement or an internship, ask permission, remove anything pre-decisional, embargoed, client-identifying or personally identifying, and say on the first page what you redacted and why. Never send a document marked as a draft deliberative product, never send unpublished client data, and never send anything derived from confidential federal statistical data or from protected health or education records. An employer who sees you hand over somebody else's confidential material learns something true about you.

Label your contribution when work is co-authored. One line at the top: you wrote sections two and four, built the cost model, and did not write the legal analysis. Reviewers assume the worst about unlabeled co-authored work, and they are often right to.

Match the sample to the employer. A nonpartisan office wants a sample that presents a disputed question fairly and does not reveal which side you are on. An advocacy organization wants to see you make an argument with evidence and handle the counterargument honestly. An agency wants to see you write within a process: a rule preamble paragraph, a guidance document, a response to a comment, a clean one-page summary for a principal. A research firm wants to see you describe a method and its limits. Keeping three samples in a folder and choosing per application takes an hour of setup and visibly outperforms one general-purpose sample.

If nobody has yet paid you to write policy, the portfolio items below are all available to anyone with a library card and a laptop. Pick the policy area you want to be hired into and produce two of them.

The quantitative bar: what you must actually be able to do, with the data named

Candidates either overestimate or underestimate this, rarely get it right, and the honest answer depends on the employer. For most government and advocacy analyst jobs, the quantitative bar is lower than applicants fear and the Excel bar is higher than they expect. For research firms, think tanks and evaluation offices, the bar is a genuine applied statistics bar and it is tested.

Start with Excel, because most policy numbers in the world live in a spreadsheet and most analysts who get stuck are stuck there. The working standard is: build a cost model where every assumption is in a labeled input cell and nothing is hard-coded inside a formula; pivot a hundred thousand rows without the file dying; write INDEX and MATCH or XLOOKUP rather than nested IFs; build a three-scenario projection and a one-way sensitivity table; chart something so the point is legible without a caption. If you can also read somebody else's inherited model and find the error, you will be the most useful person in several offices.

Then one language, used properly on one real dataset. R, Stata or Python, and which one depends on where you are going: Stata remains the common language in economics-adjacent policy shops and at several research firms, R dominates in evaluation and public health, Python wins where the work touches engineering, text or scale. SAS persists in some federal statistical agencies and in older state systems. Pick one, use it on something real, and be able to talk about your own code without notes. Knowing three languages badly is worth less than knowing one well, and interviewers can tell the difference in two questions.

SQL deserves its own sentence. The moment your work touches administrative data (Medicaid claims, unemployment insurance wage records, student records, licensing systems, 311 calls), someone is going to hand you database access rather than a CSV, and the analysts who can write a join and a group-by get the interesting assignments. It takes a weekend to learn enough and it compounds for a career.

The methods you need are mostly reading methods, not producing methods. Unless you are in an evaluation shop, you will spend far more time judging whether a study supports a claim than running a model. The literacy that matters: what randomization buys you and what it does not; why a difference-in-differences design needs a credible comparison group and what a pre-trend plot is for; what a regression discontinuity and an instrumental variable estimate are identifying and for whom; the difference between statistical significance and policy relevance; why a precisely estimated tiny effect is often a finding of no importance; what a confidence interval covers; and the practical difference between an intent-to-treat and a treatment-on-the-treated estimate when a program has low take-up. Being able to say that a study is well identified but the effect is too small to justify the appropriation is a sentence that marks you as a policy analyst rather than a student.

Weighted survey data is where honest candidates get caught. If you are using ACS, CPS, NHANES, NHIS, SIPP, NSDUH or any complex survey, you must use the person or household weights, and you must use the replicate weights or the design variables to get standard errors that are not nonsense. Reporting an unweighted mean from a complex survey in an interview exercise is a correctable mistake; not knowing the question exists is not. Know how to say what your margin of error is and why a five-year ACS estimate for a small county is not a one-year estimate.

Cost estimation is the most transferable quantitative skill in policy work and the least taught. It is the one thing every employer in this list eventually needs: how many people are eligible, what share will take it up, what it costs per person, over what period, against what baseline, with what second-order effects, and what happens if take-up is double your assumption. Build one of these for a real proposal, document the assumptions, and you will have the artifact that makes a budget office interview easy.

Finally, reproducibility is now a hiring criterion rather than a virtue. A script that runs from raw downloaded data to final table with no manual steps, a README that says where the data came from and when it was downloaded, and a folder structure somebody else can follow. Research firms ask for this explicitly. Government offices increasingly ask for it after being burned by an analysis whose author left and whose numbers nobody can rebuild.

The resume, and why the federal resume is a different document entirely

A policy resume has one job: to let a reader see, in about fifteen seconds, what you have produced and what decision it informed. Everything on the page that does not do that is taking up space that could have held a deliverable.

So write bullets around artifacts and consequences. Not supported policy research on housing affordability, but wrote the two-page issue brief and ten-state cost table used by the housing coalition in testimony to the Senate committee, and the estimate held up under opposing testimony. Not assisted with data analysis, but cleaned and merged five years of state unemployment insurance wage records in Stata to produce the earnings outcomes in the agency's annual workforce report, and documented the method so the next analyst could rerun it. Name the document, the audience, the data, the tool and the outcome. Policy work generates artifacts constantly and candidates leave almost all of them off the page.

What reliably gets ignored: passionate about public policy, strong written and verbal communication skills, a list of coursework, a GPA more than two years after graduation, generic software lists including Microsoft Office, student organization leadership once you have a real job, and the word stakeholder used four times. What gets read: the publications or products list, the named datasets, the tools with the thing you did in them, the legislative or regulatory process you have actually been inside, language skills if the job touches a community that needs them, and any evidence your work was used by somebody with authority.

Put a short publications and products section on the resume even if nothing is peer reviewed. Include the public comment you filed, the fiscal note, the issue brief, the dashboard, the testimony you drafted, with dates and links. This section is why a candidate with thinner titles beats one with better titles.

The federal resume is a separate document and treating it as the same one is an expensive mistake. For USAJOBS: four to six pages is normal and often necessary, every position needs month and year start and end dates, hours per week, your salary or grade, and your supervisor's name and whether they may be contacted. Your bullets should mirror the language of the specialized experience statement in the announcement, because a human resources specialist with no policy background is looking for exactly that language and cannot infer that your phrasing means the same thing. If the announcement says experience analyzing program data to make recommendations to senior leadership, then those words, honestly applied to something you actually did, need to appear in your resume. This is not keyword stuffing; it is answering the question that was asked in the vocabulary it was asked in.

The occupational questionnaire needs the same care and gets less of it. Rate yourself accurately and do not be falsely modest: if you have performed a task as a routine part of a job and have shown someone else how to do it, that is the top rating, and claiming less than the truth is how qualified people fail to be referred. But every rating has to be supported somewhere in the resume, because that is precisely what the HR specialist checks, and an unsupported top rating can get your whole application tossed. Read the questionnaire before you write the resume.

Two small mechanical points that cost people interviews. First, submit every document the announcement demands, including transcripts where there is a positive education requirement and the SF-50 if you are a current federal employee claiming status; a missing transcript is an automatic ineligibility for an Economist or Statistician series job. Second, note the closing time, not just the closing date, and the fact that some announcements close early once they hit an application cap. Apply in the first week.

The interview: a case, a timed exercise, and a quiet test of whether you can be trusted

Policy interviews test four things, and only one of them is knowledge. They test whether you can structure an unfamiliar problem out loud, whether your numbers are yours, whether you can be brief, and whether you can be trusted with something contested. Prepare for all four separately.

The structure test usually arrives as a case. The governor wants to cut the childcare subsidy waitlist in half within two years, what do you need to know and what are the levers. Or: a legislator has asked whether our state should adopt the thing the state next door just adopted, you have three days, what do you do. They are not scoring the answer, they are scoring whether you ask what decision is being made and by when, whether you separate the question into eligibility, take-up, cost, capacity, legal authority and implementation, whether you say what data you would pull and from where, and whether you name what you would not be able to answer in the time available. Say your structure out loud before you start solving. End with what you would hand over and when.

The numbers test is an interrogation of your own writing sample, and candidates who did not build the thing they sent get caught here within two minutes. Expect: where did that figure come from, what is the denominator, what year is that, is that nominal or real and which deflator, why does your number differ from the one in the agency's report, what is the margin of error, who is excluded from that universe. Go into every interview having re-read your own sample and having re-derived your own key numbers the night before. If you do not know, say you do not know and say how you would find out, and then actually describe the lookup. That answer scores better than a confident wrong one, every time.

The brevity test is continuous and most candidates fail it without noticing. The practical drill: be able to answer every question at three lengths. Thirty seconds for a principal in a hallway, three minutes for a briefing, fifteen minutes with the method. Start with the thirty-second version and stop. In an interview for a legislative office, the question how would you explain this to a member with four minutes between votes is a literal description of the job.

The trust test is the one nobody prepares for. In nonpartisan offices it sounds like: tell us about a time your analysis did not support the answer your principal wanted. Tell us how you would handle being asked to leave a finding out. What would you do if your estimate was being cited for something it does not support. The answers that work are concrete, show that you escalated through legitimate channels, and do not cast you as either a pushover or a martyr. In advocacy organizations the same test runs in reverse: can you be committed to a position and still tell your own side that a number is weak. In both settings the hiring manager is deciding whether you are going to embarrass them.

Timed exercises are common enough that you should have practiced one. The patterns: a two-hour take-home writing a memo from two attached documents; an on-site writing exercise with a prompt, a packet and ninety minutes; a data exercise with a messy file and three required estimates; an editing exercise where you improve somebody else's bad paragraph; a presentation on a topic sent in advance, usually ten minutes with a hard stop, followed by questions designed to see whether you defend or revise. The two habits that matter in all of them: answer the question asked rather than the question you prefer, and leave a visible note of your assumptions and caveats. A clean, short answer with honest limits beats a longer one that overclaims.

Your own questions at the end are part of the assessment, so make them operational. What does the first ninety days look like. Who are the two or three people whose decisions my work would feed. What does a good product from this seat look like, and can you show me one. How long is the funding or the contract. How is the team's work used when the political direction changes. Those questions mark a candidate who intends to do the job rather than have the title.

A note on reference checks, which matter more in this field than in most. Policy is a small world and your reference may be called informally by someone who already knows them. Keep the relationships: the supervisor from your internship three years ago is likely to be asked about you by someone you will never know was asking.

Pay, and what the 2026-27 market actually looks like

Pay first, with sources rather than invented bands. Policy analyst work does not map to one Bureau of Labor Statistics occupation, which is why aggregator numbers for this title are unreliable. Look at OES code 19-3094 for political scientists, 13-1111 for management analysts, 13-2031 for budget analysts, 19-3011 for economists and 19-3099 for social scientists not otherwise classified, read the metro-level percentiles rather than the national median, and remember that the Washington metropolitan area distorts every national figure in this field. For federal jobs the number is knowable exactly: find the grade and step in the announcement, then apply the General Schedule table for the correct locality from OPM. For congressional staff, the House Statement of Disbursements and Senate public reports list actual individual salaries, which is the most transparent pay data in the field and almost nobody uses it. For state jobs, most states publish classified salary schedules and many publish individual employee compensation. For think tanks and larger nonprofits, the IRS Form 990 lists the highest-paid employees and tells you the shape of the ladder you are joining.

Then the market, honestly. The federal policy job market contracted sharply in 2025 through a combination of deferred resignation offers, reductions in force, agency reorganizations and the elimination or curtailment of some agencies and programs, and it did so after a long period in which federal hiring had been the reliable backstop for this profession. Two consequences followed into 2026 and 2027. Experienced former federal analysts are competing for think tank, state, local, contractor and nonprofit jobs that used to be filled by people at your level, which raises the bar on every posting. And the federal track itself has become less predictable in ways you should price in rather than ignore: hiring freezes and funding lapses can suspend a process you are already inside. Verify the current state of hiring at any agency you are targeting rather than trusting any written source including this one, and if the federal track is your preference, run it in parallel with something else rather than waiting on it.

There is also a structural change worth understanding before an interview rather than during one. Rules reviving a schedule of excepted service positions for roles of a confidential, policy-determining, policy-making or policy-advocating character have been promulgated and litigated, and the practical question for a candidate is whether a specific position you are offered carries the competitive service protections you assume it does. Ask what service and what schedule the position sits in, ask about the probationary period, and read the announcement's Conditions of Employment. That question is entirely fair to ask and a good hiring manager will answer it straight.

Where the demand is growing is as important as where it shrank. State and local government has absorbed both policy responsibility and policy hiring: when federal capacity contracts, state agencies, statehouses, big-city governments and the intergovernmental organizations around them (the National Conference of State Legislatures, the National Governors Association, the Council of State Governments, the National Association of State Budget Officers) carry more of the analytic load. Philanthropy and advocacy have moved money toward state capacity for the same reason. For a candidate willing to leave Washington, a statehouse fiscal office or a state agency policy shop is now one of the better places in this profession to get three years of real experience quickly.

The substantive areas showing up most often in 2026 and 2027 postings: artificial intelligence governance and digital regulation across state attorneys general offices, state legislatures, agencies and the advocacy and industry organizations around them; energy, permitting and electricity demand, where the data center build-out has turned a technical question into a political one; health policy, driven by Medicaid financing, pharmaceutical pricing and coverage changes; housing and land use, which has become a state-level legislative fight in a long list of states; immigration and benefit eligibility administration; defense, industrial policy and export controls; and the permanent, unglamorous, reliably hiring world of budget and program evaluation, which exists in every government in every year regardless of politics.

Three tactical conclusions. First, specialize enough to be the obvious candidate for something: a policy area plus a method plus a jurisdiction beats general competence, and the combination of health policy, Medicaid claims data and a specific state is a hireable identity in a way that interested in social policy is not. Second, geography still matters in this field more than in software: Washington, state capitals (Sacramento, Austin, Albany, Tallahassee, Springfield, Lansing, Olympia, Denver) and a handful of large cities hold most of the jobs, and remote policy work exists but is a minority of postings and usually goes to people with a track record. Third, expect your first job to be narrower than your ambition. The analyst who spends two years becoming the person who understands one funding formula completely is far more employable afterwards than the one who spent two years adjacent to everything.

A closing word on the thing that actually compounds in this career. It is not the degree and it is not the software. It is being the analyst whose numbers hold up. A reputation for being accurate, brief and honest about uncertainty follows you across a small professional world, and it is the reason a program officer emails you about a job that never gets posted. Build it from the first memo.

Working with AI in this role

What a policy analyst has to know about AI in 2026-27

The honest version first, because the hype around this is badly calibrated. AI has not changed what a policy analyst is for. A fiscal note still has to be defensible to a legislature's opposing party. A rule still has to survive judicial review on the record the agency built. A finding still has to be traceable to a source. A hearing still happens on a date set by a committee chair, and the appropriations calendar does not care what tools you use. Nobody has been replaced at the core of this job, and the judgment about what is politically feasible, and about whether an agency's data system can even produce the field a proposal assumes, still rests on a person.

What has changed is the middle of the workflow, and it has changed a lot. Three categories of task that used to eat weeks now take hours, and the change is large enough that employers ask about it directly in interviews. The first is reading at volume: summarizing a nine-hundred-page proposed rule, pulling the comparable provision out of forty state statutes, extracting the relevant paragraph from two hundred comments, finding which of fifty studies actually used a randomized design. The second is structured extraction, which is the genuinely new quantitative skill in this field: turning unstructured text (bills, contracts, dockets, inspection reports, meeting minutes) into a dataset you can count, with a documented validation step. The third is drafting support: a first pass at a summary, an outline, a plain-language translation, a set of counterarguments to pressure-test your own memo.

The discipline that separates a credible analyst from a dangerous one is citation integrity. Models fabricate citations, statute numbers, case names, dollar figures and study findings, fluently and in the correct format. A hallucinated citation in a fiscal note, a comment letter, a brief or testimony is not an embarrassing typo: it is the kind of error that gets an organization's whole analysis discounted and the analyst quietly moved off the work. The rule, and it is worth saying in exactly these words in an interview, is that nothing reaches a document under your name unless you have opened the source yourself. Model output is a lead, not a cite.

Confidentiality rules are the second hard boundary and they are specific rather than vague. Pre-decisional and deliberative material, embargoed data, procurement-sensitive information, restricted-use federal statistical data covered by CIPSEA, tax data under Internal Revenue Code section 6103, protected health information, student records under FERPA, and anything personally identifying must not go into a tool that has not been approved for it. Agencies, legislative offices and research firms have internal policies naming which tools are permitted for which data classes, and those policies are not optional. Ask on day one what is approved, and never answer that question by experimenting.

The third thing is that AI is now a large part of the policy subject matter, which is where the actual job growth is. State legislatures have produced a volume of AI bills that nobody can track by hand, state attorneys general are applying existing consumer protection and anti-discrimination law to algorithmic systems, procurement offices are writing AI clauses into contracts, agencies are publishing inventories and use-case rules for their own systems, and the EU AI Act creates obligations that reach American companies through the market rather than through American law. A policy analyst who can read a model card, a system card, an evaluation report or an audit and translate it accurately for a legislator is scarce and in demand. If you are entering this field now and have no settled specialty, this is the most defensible place to put the next six months of your learning. One caution that matters more here than anywhere else in this article: compliance dates in this area have been amended and deferred more than once, so never state a deadline in a memo or an interview without checking the current text. Being confidently wrong about a date in a hearing room is worse than saying you will confirm it.

Citation integrity as an explicit, stated practice

A policy analyst's entire value is that their numbers and cites hold up under hostile checking, and generative tools produce fluent, correctly formatted, entirely fictional citations, statute numbers and findings. One fabricated source in a fiscal note or comment letter discredits the whole document and the organization behind it, which is why hiring managers in this field now probe for the habit.

Show it: Say the rule out loud in the interview: model output is a lead, never a cite, and nothing goes under my name until I have opened the source. Then show the mechanics in your writing sample, with footnotes carrying dataset vintage, table number, series ID and retrieval date, so a reviewer can re-find every figure in under a minute.

Structured extraction from documents, with a validated sample

The task that used to be impossible on an analyst's budget is now routine: coding four hundred state bills into comparable fields, classifying a docket of public comments, pulling provisions out of two hundred contracts, extracting findings from a stack of studies. This is the new quantitative skill in policy work, and it is only credible with a validation step, because an unvalidated automated coding is just an assertion.

Show it: Build one dataset this way and publish it: the codebook, the extraction logic or prompt, a hand-coded random sample with the agreement rate reported, and the disagreements discussed. Then say in the interview exactly how you measured accuracy. That paragraph is the difference between a tool user and an analyst.

Reading an AI system the way you read any other regulated thing

AI governance is among the fastest growing policy hiring areas, and the roles need people who can read the artifacts the technology produces about itself: a model card, a system card, an evaluation or red-team report, a bias audit, an impact assessment. Most policy candidates cannot, and most engineers cannot write for a legislator, so the overlap is thin and well paid.

Show it: Write a two-page analysis of one published system card or evaluation report for a nontechnical principal: what the system does, what the evaluation measured, what it did not measure, and which of the proposed obligations in a named bill would actually bind it. Use it as your AI-adjacent writing sample.

Knowing the frameworks by name, without asserting their dates

Interviews in this area test vocabulary fluency. The NIST AI Risk Management Framework and its generative AI profile, ISO/IEC 42001, the EU AI Act's risk tiers and its obligations on high-risk systems, federal agency inventory and use-case requirements, state algorithmic discrimination and disclosure laws, and local rules such as New York City's automated employment decision tool audit requirement are the furniture of the conversation. The dates attached to them move, and reciting a stale compliance date in a hearing is the error that costs you credibility.

Show it: Be able to describe what each instrument obliges and who it binds, in one sentence each, with the date handled as a thing to confirm rather than a thing to assert. In writing, phrase obligations substantively (governs training and validation data for high-risk systems) and footnote the current official text rather than a news article about it.

Detecting and describing automated comment campaigns

Public comment dockets now routinely receive mass-generated submissions, which matters to a policy analyst in both directions: an agency analyst has to triage a docket and respond to substantive comments without being swamped, and an advocacy analyst has to run a legitimate campaign that does not get discounted as synthetic. Being able to cluster, deduplicate and characterize a docket is concretely useful and rare among applicants.

Show it: Pull a large docket from regulations.gov, cluster the comments, report how many distinct substantive arguments it actually contains, and write the one-page triage note an agency would need. Publish it. It is also an excellent interview story.

Using the tools for code and data work, and saying where the line is

A policy analyst who can get unstuck in R, Stata, Python or SQL with model assistance works several times faster than one who waits for help, and this is now assumed rather than impressive. What is still rare is the judgment about where assistance stops: a generated regression specification you cannot justify, a cleaning step you did not read, or a weighting decision you did not make yourself will fail in the exact moment the number is challenged.

Show it: Keep your analysis scripts readable and commented, and be ready to explain any line of your own code in the interview. If asked how you use AI in your work, give a specific, bounded answer: a real task you accelerate, a real task you do by hand, and the reason for the boundary.

Knowing your employer's data rules before you touch a tool

Policy analysts handle exactly the categories of information that must not be pasted into an unapproved tool: pre-decisional and deliberative drafts, embargoed statistics, procurement-sensitive material, restricted-use statistical data under CIPSEA, tax data under section 6103, health and education records, and personally identifying information. A single disclosure incident is a firing offense in a government office and a contract-breaking event at a firm.

Show it: Ask in the interview which tools are approved for which data classes, which signals that you already know the question exists. If you have handled restricted data before, name the agreement and the training rather than the dataset.

Being honest in writing about what AI has and has not changed in your own field

Hiring managers in policy are tired of memos that assert transformation and deliver nothing. The analyst who can write a sober paragraph distinguishing where a technology has genuinely changed a process from where it has only changed the marketing is demonstrating the core skill of the job, which is calibrated judgment under uncertainty.

Show it: In your writing sample and in the interview, draw the line explicitly: here is the task that got ten times faster, here is the task that did not change at all, and here is the obligation that still rests on a person. Specificity reads as competence; enthusiasm reads as inexperience.

What a screen is looking for

These are the terms that a resume screen, human or automated, is matching against for this role. Use the ones that are true of you, in the words the posting uses.

Mistakes that cost people this job

Sending a graduate seminar paper or a thesis chapter as the writing sample, because it is the longest and most impressive thing you have written.

Send a two to five page decision memo or issue brief with the recommendation in the first paragraph. If you do not have one, write one this weekend about a live question in the policy area you are targeting. Reviewers are checking whether you know the genre, and a long academic document answers that question badly.

Submitting a tight one-page resume to USAJOBS, because every career website says a resume should be one page.

Write a four to six page federal resume with month and year dates, hours per week, grade or salary and supervisor contact for each position, and mirror the announcement's specialized experience language honestly. A one-page federal resume routinely fails because the human resources specialist cannot find evidence for the experience you claimed, and nobody with policy judgment ever sees the rest of your case.

Rating yourself modestly on the occupational questionnaire because claiming the top option feels like boasting.

Rate accurately. If you have performed the task routinely in a job and have shown somebody else how to do it, that is the top rating and it is the truth. Then make sure your resume visibly supports every rating you claimed, because the mismatch between a top rating and a thin resume is what actually gets applications thrown out.

Running a search that is only federal applications, then waiting.

Run the federal track and at least one other track at the same time. Federal processes take two to nine months and can be suspended by a hiring freeze or a funding lapse after you are already inside them, while advocacy organizations, state offices, research firms and contractors can close in two to six weeks. Patience is required for the first and fatal for the second.

Writing the resume around responsibilities (supported research on housing affordability) rather than around what you produced.

Name the artifact, the data, the tool, the audience and the consequence: wrote the ten-state cost table and two-page brief used in Senate testimony, built from ACS five-year microdata in R. Policy work generates artifacts constantly, and candidates leave nearly all of them off the page, which is why their resumes read as interchangeable.

Claiming a quantitative skill you cannot demonstrate under questioning, usually phrased as proficient in Stata, R and Python.

Claim one language and know it. Be able to describe a real dataset you cleaned, the decisions you made about missing values and weights, and what you would do differently. Interviewers find the bluff with two follow-up questions, and the recovery from that moment is worse than never having claimed it.

Sending a sample containing material you were not cleared to release: a client deliverable, a pre-decisional draft, unpublished data, or anything with identifying details in it.

Ask permission, redact, and state on the first page what you removed and why. Or write a fresh sample from public sources. An employer who watches you hand over somebody else's confidential material has learned something about you that no interview answer can undo.

Carrying a loud partisan public footprint while applying to nonpartisan offices such as GAO, CBO, CRS or a state legislative fiscal office.

Decide which track you want, because these two reputations are in tension. If nonpartisan analysis is the goal, keep your published work analytical, present disputed questions fairly, and be ready to answer the neutrality question with a concrete example. If advocacy is the goal, lean in, and accept that it narrows the nonpartisan doors.

Pasting a figure, citation or statute number from a model into a memo without opening the source.

Treat model output as a lead and never as a cite. Open every source, record the dataset vintage, table number or series ID with the retrieval date, and footnote the primary document rather than a summary of it. A fabricated citation in a fiscal note or testimony does more career damage to a policy analyst than a missed deadline ever will.

Quoting a compliance deadline from memory in a memo or an interview, especially on anything AI-related.

Write the obligation without the date, or name the date and say it needs confirming against the current official text. Deadlines in this area have been deferred and amended more than once, and being confidently wrong about one in a hearing room costs you the credibility the rest of your analysis depends on.

Applying as a generalist who is interested in public policy, across every area at once.

Pick a hireable identity: one policy area, one method, one jurisdiction. Health policy plus Medicaid claims data plus one state. Housing plus permit and ACS data plus one metro. AI governance plus state legislation tracking. You can broaden later from a specific first job, and you cannot get a first job as everybody's second choice.

Treating the end-of-interview questions as a formality and asking about culture.

Ask operational questions: what the first ninety days contain, which two or three people consume your output, what a good product from this seat looks like and whether you can see one, how long the funding or contract runs, and what happens to the team's work when political direction changes. These questions are themselves evidence that you intend to do the work.

Assuming the interview is about knowledge and preparing by reading more about the policy area.

Prepare the four things actually being tested: structuring an unfamiliar problem out loud, defending the numbers in your own writing sample, answering at thirty seconds and three minutes before fifteen, and handling the question about a time your analysis did not support what your principal wanted. Spend the night before re-deriving your own sample's key figures rather than reading one more report.

Questions people ask

Do I need a master's degree to become a policy analyst?

A policy analyst does not legally need any degree, and there is no license or exam for the title, but a master's is the normal expectation for analyst-level roles at federal agencies above the entry grades, at national think tanks and research firms, and at well-funded advocacy organizations. The MPP is the canonical degree, the MPA leans toward management, and a disciplinary master's in economics, statistics, public health, social work or planning is often a stronger signal for a specialized desk. The well-worn routes in without one are a congressional office, a state legislative fiscal or evaluation office, a local budget office, a federal Pathways or Recent Graduates appointment, or a data analyst job adjacent to the policy shop, and each typically reaches an analyst title in roughly two to four years.

What writing sample should a policy analyst send with an application?

A policy analyst should send a sole-authored decision memo or issue brief of two to five pages, written in the last two years, with the recommendation in the opening paragraph, two or three genuine options with costs and distributional effects, the strongest objection stated fairly, and every figure footnoted to a named source with its vintage. Do not send a thesis chapter, a literature review, a journalism clip or a twenty-page seminar paper. If co-authored work is the only thing available, add one line at the top stating exactly which sections and which analysis were yours, and if a sample came from a government or client job, get permission, redact anything pre-decisional or identifying, and say on the first page what you removed.

How quantitative does a policy analyst actually have to be?

For most government and advocacy roles, a policy analyst needs Excel at the level of a labeled, auditable cost model with scenarios and a sensitivity table, plus one of R, Stata or Python used end to end on a real dataset they can discuss unprompted, plus the literacy to judge whether somebody else's study supports the claim being made from it. For research firms, think tanks and evaluation offices the bar is higher and it is tested in a timed exercise: weighted estimates from complex survey data with correct standard errors, a script that runs from raw data to final table, and a clear account of what a difference-in-differences or regression discontinuity estimate does and does not license you to claim. Cost estimation is the most transferable quantitative skill in the job and the least taught.

Which software should a policy analyst learn first, R, Stata or Python?

A policy analyst should learn one of them properly rather than three badly, and the right choice depends on the destination: Stata remains the common language in economics-adjacent policy shops and at several federal research contractors, R dominates in program evaluation and public health, and Python wins where the work touches text, scale or engineering. SAS still persists at some federal statistical agencies and in older state systems. Add SQL regardless of which you pick, because the moment the work touches administrative data such as Medicaid claims or unemployment insurance wage records, somebody will hand you database access rather than a spreadsheet.

How long does federal policy analyst hiring take?

A federal policy analyst position commonly takes two to nine months from the day the USAJOBS announcement closes to a start date, and longer if a security clearance is required. The sequence is an occupational questionnaire you rate yourself on, a human resources specialist verifying that your resume supports those ratings and the specialized experience statement, a certificate of eligibles reaching the hiring manager, a panel interview, a tentative offer, and then a suitability and background investigation. Hiring freezes and appropriations lapses can suspend a process you are already inside, which is why a policy analyst should always run a non-federal track in parallel rather than waiting.

What is the difference between GS-0343 and GS-0110 for a policy analyst job?

For a policy analyst applying to the federal government, GS-0343 Management and Program Analyst carries no positive education requirement and is the widest door, qualifying on specialized experience alone, while GS-0110 Economist has a mandatory coursework requirement in economics plus statistics, accounting or calculus, which means a transcript either qualifies you or does not. GS-1530 Statistician and GS-1515 Operations Research Analyst have their own coursework rules, and GS-0101 Social Science and GS-0301 Miscellaneous Administration and Program sit in between. The practical instruction for any policy analyst applying through USAJOBS is to read the Qualifications section of the announcement before the duties, because that is the section that disqualifies people, and to submit transcripts whenever a positive education requirement exists.

What does a policy analyst interview actually test?

A policy analyst interview tests four separate things: whether you can structure an unfamiliar problem out loud, usually through a case such as costing a proposal with incomplete data; whether the numbers in your own writing sample are genuinely yours, probed with questions about denominators, vintages, deflators and margins of error; whether you can be brief, which is why you should have a thirty-second, a three-minute and a fifteen-minute version of every answer and offer the shortest first; and whether you can be trusted with something contested, which arrives as a question about a time your analysis did not support what your principal wanted. The highest-yield hour of preparation for a policy analyst is re-deriving your own writing sample's key figures the night before.

Is a policy analyst job being replaced by AI?

No. The core of a policy analyst's job has not changed: a fiscal note still has to survive the opposing party, a rule still has to stand on the record the agency built, a hearing still happens on a chair's calendar, and the judgment about what is politically feasible and whether an agency's data system can even produce the field a proposal assumes still rests on a person. What has changed is the middle of the workflow, where reading at volume, structured extraction from documents into datasets, and first-draft support now take hours instead of weeks. The hard boundaries for a policy analyst are citation integrity, because a fabricated cite in a memo discredits the whole organization, and data rules, because pre-decisional, embargoed, restricted-use statistical, tax, health and student data must not go into an unapproved tool.

Where should a policy analyst look up salary rather than trusting an aggregator?

A policy analyst should start with the Bureau of Labor Statistics OES data across the several codes this work is split between, 19-3094 political scientists, 13-1111 management analysts, 13-2031 budget analysts, 19-3011 economists and 19-3099 social scientists not otherwise classified, reading metro percentiles rather than the national median because the Washington area distorts every national figure in this field. For a federal job the number is exact once you know the grade, step and locality from the OPM General Schedule tables. For congressional staff, the House Statement of Disbursements and Senate public reports list individual salaries. For think tanks and nonprofits, the IRS Form 990 shows the top of the ladder, and in pay-transparency states the posted ranges themselves are the best available data.

Can a policy analyst get hired without any paid policy experience?

Yes, and a policy analyst does it by producing public artifacts in one specific policy area rather than by applying more widely. File a public comment on a proposed rule under your own name at regulations.gov. Write the fiscal note for a bill in your own state legislature that does not have one, with the assumptions in a table. Build and publish a fifty-state comparison table from statutes and agency rules with a methods note and a date. Translate one recent peer-reviewed study into two pages for a nontechnical reader, including what it does not show. Two of those, in the area you want to be hired into, convert cold applications into warm ones and give you the sample and the interview stories you otherwise lack.

Put this on a resume in about a minute

Paste your history once and point it at the Policy Analyst posting you are looking at. No account, no card.

Build my resume free More roles