As of March 01, 2025, the average annual salary for a Data Architect II in San Francisco, CA is $144,684. Salary.com reports that pay typically ranges from $125,593 to $166,415, with most professionals earning between $108,211 and $186,200.
| Annual Salary |
Monthly Pay |
Weekly Pay |
Hourly Wage |
|
| 75th Percentile | $133,132 | $11,094 | $2,560 | $64 |
| Average | $115,748 | $9,646 | $2,226 | $56 |
| 25th Percentile | $100,474 | $8,373 | $1,932 | $48 |
An entry-level Data Architect II with under 1 year experience makes about $137,362. With less than 2 years of experience, a mid-level Data Architect II makes around $137,955. After 2-4 years, the Data Architect II pay rises to about $145,538. Those senior Data Architect II with 5-8 years of experience earn roughly $154,780, and those Data Architect II having 8 years or more experience are expected to earn about $155,440 on average.
| Levels | Salary |
|---|---|
| Entry Level Data Architect II | $137,362 |
| Intermediate Level Data Architect II | $137,955 |
| Senior Level Data Architect II | $145,538 |
| Specialist Level Data Architect II | $154,780 |
| Expert Level Data Architect II | $155,440 |
| Entry Level | 19% |
| Mid Level | 19% |
| Senior Level | 26% |
| Top Level | 34% |
| Experienced | 34% |
Not the salary data you are looking for? Choose the city salary you want to see.
Salary.com job board provides millions of Data Architect II information for you to search for. Click on search button below to see Data Architect II 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.
Troubleshooting: Troubleshooting is a form of problem solving, often applied to repair failed products or processes on a machine or a system. It is a logical, systematic search for the source of a problem in order to solve it, and make the product or process operational again. Troubleshooting is needed to identify the symptoms. Determining the most likely cause is a process of elimination—eliminating potential causes of a problem. Finally, troubleshooting requires confirmation that the solution restores the product or process to its working state. In general, troubleshooting is the identification or diagnosis of "trouble" in the management flow of a system caused by a failure of some kind. The problem is initially described as symptoms of malfunction, and troubleshooting is the process of determining and remedying the causes of these symptoms. A system can be described in terms of its expected, desired or intended behavior (usually, for artificial systems, its purpose). Events or inputs to the system are expected to generate specific results or outputs. (For example, selecting the "print" option from various computer applications is intended to result in a hardcopy emerging from some specific device). Any unexpected or undesirable behavior is a symptom. Troubleshooting is the process of isolating the specific cause or causes of the symptom. Frequently the symptom is a failure of the product or process to produce any results. (Nothing was printed, for example). Corrective action can then be taken to prevent further failures of a similar kind.
Data Modeling: Data modeling in software engineering is the process of creating a data model for an information system by applying certain formal techniques.
Agile: Agile is a development process where feedback is continuously gathered from users to create the best user experience.
| Skill | Salary | Demand |
|---|---|---|
|
Consulting
|
$153,365 |
6%
|
|
Big Data
|
$151,919 |
5%
|
|
Data Architecture
|
$151,919 |
5%
|
|
AWS
|
$150,472 |
4%
|
|
Data Lakes
|
$150,472 |
4%
|
|
Data Integration
|
$150,472 |
4%
|
