As of April 01, 2025, the average annual salary for a Business Analyst - RFP in Everett, WA is $84,260. Salary.com reports that pay typically ranges from $75,600 to $94,060, with most professionals earning between $67,716 and $102,982.
| Annual Salary |
Monthly Pay |
Weekly Pay |
Hourly Wage |
|
| 75th Percentile | $94,060 | $7,838 | $1,809 | $45 |
| Average | $84,260 | $7,022 | $1,620 | $41 |
| 25th Percentile | $75,600 | $6,300 | $1,454 | $36 |
An entry-level Business Analyst - RFP with under 1 year experience makes about $79,996. With less than 2 years of experience, a mid-level Business Analyst - RFP makes around $81,873. After 2-4 years, the Business Analyst - RFP pay rises to about $85,307. Those senior Business Analyst - RFP with 5-8 years of experience earn roughly $87,834, and those Business Analyst - RFP having 8 years or more experience are expected to earn about $88,256 on average.
| Levels | Salary |
|---|---|
| Entry Level Business Analyst - RFP | $79,996 |
| Intermediate Level Business Analyst - RFP | $81,873 |
| Senior Level Business Analyst - RFP | $85,307 |
| Specialist Level Business Analyst - RFP | $87,834 |
| Expert Level Business Analyst - RFP | $88,256 |
| Entry Level | 5% |
| Mid Level | 3% |
| Senior Level | 1% |
| Top Level | 4% |
| Experienced | 5% |
Not the salary data you are looking for? Choose the city salary you want to see.
Salary.com job board provides millions of Business Analyst - RFP information for you to search for. Click on search button below to see Business Analyst - RFP 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 |
|---|---|---|
|
Scrum
|
$94,371 |
12%
|
|
Use Cases
|
$91,001 |
8%
|
|
Data Analysis
|
$90,158 |
7%
|
|
Visio
|
$89,316 |
6%
|
|
Tableau
|
$89,316 |
6%
|
|
Business Analysis
|
$88,473 |
5%
|
