A Pricing role sits at the intersection of finance, product, and go-to-market: setting list prices and discount policy, building the business case for a packaging or SKU change, running the deal desk on non-standard deals, and modeling what a price change does to revenue and margin. Titles range from Pricing Analyst and Pricing Manager up through a Director or VP of Pricing and Revenue Strategy, and the role reports into product, finance, or a dedicated revenue operations function depending on the company.
The job is equal parts analysis and negotiation. A Pricing hire spends real time in a spreadsheet or a CPQ tool building the model, and real time in a room defending a number to sales, finance, or a customer. A posting for this role is almost always screening for both halves: someone who can build and defend a quantitative case, not only run the numbers or only sit in the room.
Every major applicant tracking system we have studied (see our platform-by-platform breakdown) works from the same starting point: the posting's own listed requirements, matched or scored against the resume's own text, whether that is Greenhouse's weighted calibration, Ashby's criteria-met percentage, or a plain keyword search on a platform with no scoring tool at all. A Pricing posting typically names the same handful of things: pricing strategy, monetization, a named tool such as CPQ or Salesforce, and a quantitative skill such as financial modeling or revenue analytics. A resume that never states those terms in the language the posting uses is harder for any of these tools, or a person doing a manual keyword search, to match.
Meridino's own coverage check works the same way our matching does: deterministic, not AI. It reads a specific posting's actual requirements, compares them against what you have told us you have actually done, and shows you exactly which requirement is covered, weak, or missing, before you touch a resume. It can never invent that you have used a tool or led a project you did not tell it about.
Core : The skills that show up in nearly every posting in this family.
pricing, pricing strategy, monetization, packaging, deal desk, willingness to pay, revenue optimization, sku rationalization, discounting, cpq
Commonly expected : Frequently asked for, though not universal.
revenue analytics, unit economics, gross margin, competitive analysis, market segmentation, business case development, negotiation, sales forecasting, salesforce, renewals, upsell, cross-sell
Related and transferable : Strengthens a resume without being the headline ask.
financial modeling, forecasting, kpi, positioning, messaging, product-market fit, market analysis, dashboarding, excel, sql, data visualization, win/loss analysis, product roadmapping
Fixing what a coverage check finds is where the anti-fabrication rule is not optional. Meridino's rewrite only reorders or rewords what you already told it, and every claim traces back to a change log entry pointing at your own submitted history. It can surface the word "CPQ" on your resume only if you told us you have used a CPQ tool, never because a posting asked for it.
That is the entire trade this page is offering: an honest read of how a Pricing resume actually gets screened, the skills to make sure are stated plainly, and a coverage check that will tell you the truth about a specific posting rather than guess.
Meridino is tracking 235 live Pricing roles right now, verified from company career boards we read directly.
We do not publish those roles or any posting text on this page (see our data-usage policy for why). Sign in with Google to see them.
A live count, shown on this page and updated as our pipeline re-checks the pool. It counts only postings currently marked live by our verify sweep, from company career boards we read directly, never a stale or closed listing. Sign in to see the actual roles behind that count, not just the number.
Only from the public, first-party job-list endpoints operated by an employer's own applicant tracking system (Greenhouse, Lever, Ashby, SmartRecruiters, Workable, BambooHR, Teamtailor). We do not take postings from third-party aggregators such as Indeed or LinkedIn, and we hold no agreement, feed, or scraper for any of them. Full detail in our data-usage policy.
No. The fit score and the ATS coverage check are both deterministic code, not an AI model, run entirely on our own systems. AI is used only for optional resume structuring, bullet rewriting, and review, and only when you invoke one of those features yourself, never for scoring or matching.
Related: every role we cover, Finance jobs, Product Management jobs, and how each ATS platform screens a resume.
Finding jobs and scoring your fit are free. Bring your resume, and we tune it to the job using only what is already true about you.