As of May 01, 2025, the average annual salary for a Bid/Quote Administrator in Eugene, OR is $69,000. Salary.com reports that pay typically ranges from $62,700 to $73,800, with most professionals earning between $56,964 and $78,170.
| Annual Salary |
Monthly Pay |
Weekly Pay |
Hourly Wage |
|
| 75th Percentile | $73,800 | $6,150 | $1,419 | $35 |
| Average | $69,000 | $5,750 | $1,327 | $33 |
| 25th Percentile | $62,700 | $5,225 | $1,206 | $30 |
An entry-level Bid/Quote Administrator with under 1 year experience makes about $67,129. With less than 2 years of experience, a mid-level Bid/Quote Administrator makes around $68,534. After 2-4 years, the Bid/Quote Administrator pay rises to about $70,458. Those senior Bid/Quote Administrator with 5-8 years of experience earn roughly $71,769, and those Bid/Quote Administrator having 8 years or more experience are expected to earn about $71,988 on average.
| Levels | Salary |
|---|---|
| Entry Level Bid/Quote Administrator | $67,129 |
| Intermediate Level Bid/Quote Administrator | $68,534 |
| Senior Level Bid/Quote Administrator | $70,458 |
| Specialist Level Bid/Quote Administrator | $71,769 |
| Expert Level Bid/Quote Administrator | $71,988 |
| 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 Bid/Quote Administrator information for you to search for. Click on search button below to see Bid/Quote Administrator 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
|
$77,280 |
12%
|
|
Use Cases
|
$74,520 |
8%
|
|
Data Analysis
|
$73,830 |
7%
|
|
Visio
|
$73,140 |
6%
|
|
Tableau
|
$73,140 |
6%
|
|
Business Analysis
|
$72,450 |
5%
|
