As of March 01, 2025, the average annual salary for a Business Analyst - RFP in Lansing, MI is $67,070. Salary.com reports that pay typically ranges from $60,900 to $71,740, with most professionals earning between $55,283 and $75,992.
| Annual Salary |
Monthly Pay |
Weekly Pay |
Hourly Wage |
|
| 75th Percentile | $71,740 | $5,978 | $1,380 | $34 |
| Average | $67,070 | $5,589 | $1,290 | $32 |
| 25th Percentile | $60,900 | $5,075 | $1,171 | $29 |
An entry-level Business Analyst - RFP with under 1 year experience makes about $65,229. With less than 2 years of experience, a mid-level Business Analyst - RFP makes around $66,612. After 2-4 years, the Business Analyst - RFP pay rises to about $68,465. Those senior Business Analyst - RFP with 5-8 years of experience earn roughly $69,719, and those Business Analyst - RFP having 8 years or more experience are expected to earn about $69,928 on average.
| Levels | Salary |
|---|---|
| Entry Level Business Analyst - RFP | $65,229 |
| Intermediate Level Business Analyst - RFP | $66,612 |
| Senior Level Business Analyst - RFP | $68,465 |
| Specialist Level Business Analyst - RFP | $69,719 |
| Expert Level Business Analyst - RFP | $69,928 |
| 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
|
$75,118 |
12%
|
|
Use Cases
|
$72,436 |
8%
|
|
Data Analysis
|
$71,765 |
7%
|
|
Visio
|
$71,094 |
6%
|
|
Tableau
|
$71,094 |
6%
|
|
Business Analysis
|
$70,424 |
5%
|
