As of February 01, 2025, the average annual salary for an RFP Analyst, Sr. in Peoria, AZ is $93,440. Salary.com reports that pay typically ranges from $84,253 to $103,709, with most professionals earning between $75,889 and $113,059.
| Annual Salary |
Monthly Pay |
Weekly Pay |
Hourly Wage |
|
| 75th Percentile | $105,182 | $8,765 | $2,023 | $51 |
| Average | $94,767 | $7,897 | $1,822 | $46 |
| 25th Percentile | $85,450 | $7,121 | $1,643 | $41 |
An entry-level RFP Analyst, Sr. with under 1 year experience makes about $85,804. With less than 2 years of experience, a mid-level RFP Analyst, Sr. makes around $86,230. After 2-4 years, the RFP Analyst, Sr. pay rises to about $88,786. Those senior RFP Analyst, Sr. with 5-8 years of experience earn roughly $95,161, and those RFP Analyst, Sr. having 8 years or more experience are expected to earn about $97,215 on average.
| Levels | Salary |
|---|---|
| Entry Level RFP Analyst, Sr. | $85,804 |
| Intermediate Level RFP Analyst, Sr. | $86,230 |
| Senior Level RFP Analyst, Sr. | $88,786 |
| Specialist Level RFP Analyst, Sr. | $95,161 |
| Expert Level RFP Analyst, Sr. | $97,215 |
| Entry Level | 9% |
| Mid Level | 9% |
| Senior Level | 6% |
| Top Level | 0% |
| Experienced | 3% |
Not the salary data you are looking for? Choose the city salary you want to see.
Salary.com job board provides millions of RFP Analyst, Sr. information for you to search for. Click on search button below to see RFP Analyst, Sr. job openings or enter a new job title here.
Each competency has five to ten behavioral assertions that can be observed, each with a corresponding performance level (from one to five) that is required for a particular job.
Analysis: Analysis is the process of considering something carefully or using statistical methods in order to understand it or explain it.
User Stories: In software development and product management, a user story is an informal, natural language description of one or more features of a software system. User stories are often written from the perspective of an end user or user of a system. They are often recorded on index cards, on Post-it notes, or in project management software. Depending on the project, user stories may be written by various stakeholders including clients, users, managers or development team members. User stories are a type of boundary object. They facilitate sensemaking and communication; that is, they help software teams organize their understanding of the system and its context. User stories are often confused with system requirements. A requirement is a formal description of need; a user story is an informal description of a feature.
Accounting: Creating financial statements and reports based on the summary of financial and business transactions.
| Skill | Salary | Demand |
|---|---|---|
|
Business Requirements
|
$113,062 |
21%
|
|
Tableau
|
$105,587 |
13%
|
|
Scrum
|
$104,653 |
12%
|
|
Team Development
|
$103,718 |
11%
|
|
Use Cases
|
$103,718 |
11%
|
|
SQL
|
$102,784 |
10%
|
