As of April 01, 2025, the average annual salary for a Business Analyst - RFP in Tulsa, OK is $65,140. Salary.com reports that pay typically ranges from $59,150 to $69,680, with most professionals earning between $53,696 and $73,813.
| Annual Salary |
Monthly Pay |
Weekly Pay |
Hourly Wage |
|
| 75th Percentile | $69,680 | $5,807 | $1,340 | $34 |
| Average | $65,140 | $5,428 | $1,253 | $31 |
| 25th Percentile | $59,150 | $4,929 | $1,138 | $28 |
An entry-level Business Analyst - RFP with under 1 year experience makes about $63,356. With less than 2 years of experience, a mid-level Business Analyst - RFP makes around $64,699. After 2-4 years, the Business Analyst - RFP pay rises to about $66,499. Those senior Business Analyst - RFP with 5-8 years of experience earn roughly $67,717, and those Business Analyst - RFP having 8 years or more experience are expected to earn about $67,920 on average.
| Levels | Salary |
|---|---|
| Entry Level Business Analyst - RFP | $63,356 |
| Intermediate Level Business Analyst - RFP | $64,699 |
| Senior Level Business Analyst - RFP | $66,499 |
| Specialist Level Business Analyst - RFP | $67,717 |
| Expert Level Business Analyst - RFP | $67,920 |
| Entry Level | 3% |
| Mid Level | 1% |
| Senior Level | 2% |
| Top Level | 4% |
| Experienced | 4% |
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
|
$72,957 |
12%
|
|
Use Cases
|
$70,351 |
8%
|
|
Data Analysis
|
$69,700 |
7%
|
|
Visio
|
$69,048 |
6%
|
|
Tableau
|
$69,048 |
6%
|
|
Business Analysis
|
$68,397 |
5%
|
