As of April 01, 2025, the average annual salary for a Model Builder in Idaho Falls, ID is $65,290. Salary.com reports that pay typically ranges from $58,090 to $75,590, with most professionals earning between $51,535 and $84,968.
| Annual Salary |
Monthly Pay |
Weekly Pay |
Hourly Wage |
|
| 75th Percentile | $75,590 | $6,299 | $1,454 | $36 |
| Average | $65,290 | $5,441 | $1,256 | $31 |
| 25th Percentile | $58,090 | $4,841 | $1,117 | $28 |
An entry-level Model Builder with under 1 year experience makes about $62,912. With less than 2 years of experience, a mid-level Model Builder makes around $63,129. After 2-4 years, the Model Builder pay rises to about $65,295. Those senior Model Builder with 5-8 years of experience earn roughly $69,153, and those Model Builder having 8 years or more experience are expected to earn about $70,696 on average.
| Levels | Salary |
|---|---|
| Entry Level Model Builder | $62,912 |
| Intermediate Level Model Builder | $63,129 |
| Senior Level Model Builder | $65,295 |
| Specialist Level Model Builder | $69,153 |
| Expert Level Model Builder | $70,696 |
| Entry Level | 4% |
| Mid Level | 3% |
| Senior Level | 0% |
| Top Level | 6% |
| Experienced | 8% |
Not the salary data you are looking for? Choose the city salary you want to see.
Salary.com job board provides millions of Model Builder information for you to search for. Click on search button below to see Model Builder 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.
Problem Solving: Analyzing and identifying the root cause of problems and applying critical thinking skills to solve problems.
Agile Methodology: The Agile methodology is a way to manage a project by breaking it up into several phases. The goal of Agile is to produce shorter development cycles and more frequent product releases than traditional waterfall project management.
Functional Requirements: In software engineering and systems engineering, a functional requirement defines a function of a system or its component, where a function is described as a specification of behavior between outputs and inputs. Functional requirements may involve calculations, technical details, data manipulation and processing, and other specific functionality that define what a system is supposed to accomplish. Behavioral requirements describe all the cases where the system uses the functional requirements, these are captured in use cases. Functional requirements are supported by non-functional requirements (also known as "quality requirements"), which impose constraints on the design or implementation (such as performance requirements, security, or reliability). Generally, functional requirements are expressed in the form "system must do <requirement>," while non-functional requirements take the form "system shall be <requirement>." The plan for implementing functional requirements is detailed in the system design, whereas non-functional requirements are detailed in the system architecture.
| Skill | Salary | Demand |
|---|---|---|
|
Financial Modeling
|
$77,042 |
18%
|
|
Employee Health and Safety
|
$75,736 |
16%
|
|
Taking Action
|
$75,736 |
16%
|
|
Microsoft Excel
|
$74,431 |
14%
|
|
Analysis
|
$72,472 |
11%
|
|
Insight
|
$71,166 |
9%
|
