Hire iOS and Swift developers in Salt Lake City
What the published figures say about hiring this skill into the Salt Lake City-Murray, UT market, what a seat here actually costs, and how to run the search so it closes.
The local market for this occupation
iOS and Swift developers are counted by the Bureau of Labor Statistics under Software Developers. In the Salt Lake City-Murray, UT area the Bureau puts employment in that occupation at 19,040, with a median annual wage of $129,600. The national median for the same occupation is $135,980, so Salt Lake City sits about 5% below the country as a whole.
Ranked against every US metropolitan area where this occupation is separately published, Salt Lake City is 87 of 377 by median wage. Of the 28 markets covered on this site it is 25. Those two numbers together are a better guide to what an offer needs to look like than any single national figure, because they say where the market sits rather than what it averages.
The middle half of the local market runs from $102,560 to $160,740. That band, not the midpoint, is the number to carry into a budget conversation about a iOS developer here. Where in the band a particular hire lands depends far more on what the person can be left to own than on how many years the CV shows, which is why the level definitions matter more than the title.
One qualification applies to all of this and it is worth stating plainly. The Bureau classifies by occupation, not by technology. Nobody publishes an official wage figure for iOS and Swift specifically, and any site that quotes one has either modelled it or made it up. The occupation figures are the honest available baseline: they describe the market a iOS developer is hired into, and the technology adjusts where inside that band a given person sits.
What each level looks like against local pay
Percentiles describe a market; they do not describe a person. The useful step is to read the published Software Developers band for Salt Lake City against what someone at each level can actually be left to own. The mapping below is a working guide rather than a rule, and the overlap between adjacent levels is genuine: a strong mid-level engineer can be worth more than a weak senior one and frequently is.
| Level | Indicative local band | What they can be left to own |
|---|---|---|
| Junior | $79,610 to $102,560 | Builds screens within an existing application. Needs review on memory, threading and state ownership. |
| Mid-level | $102,560 to $129,600 | Owns a feature including its networking, persistence and tests. Can profile with Instruments and find a retain cycle. |
| Senior | $129,600 to $160,740 | Owns application architecture, the concurrency approach, the interface framework strategy, and the release pipeline including store submission. |
| Staff | $160,740 to $177,090 | Owns the platform upgrade path, the privacy and data-use posture, the boundary with any shared cross-platform code, and the response to annual platform changes. |
Bands are percentiles of the published local occupation wage, not FuturByte rates, and not a guarantee that any individual sits where the band suggests.
Two things go wrong when this mapping is used carelessly. The first is budgeting a senior seat at the local median and then interviewing people who can genuinely own an area of the system; in Salt Lake City that band starts around $129,600 and an offer below it will not close against a counter. The second is the reverse: paying at the top of the band for someone who still needs their work scoped by somebody else. The level definitions are there so the conversation is about what the person will own rather than about how many years the CV shows.
It is also worth being explicit that years and level are only loosely related in iOS and Swift work. Somebody who has spent six years maintaining one application carries less transferable judgement than somebody who has spent three across three very different ones. When a CV and a band disagree, the interview should settle it, not the CV.
The titles you are bidding against locally
A iOS developer in Salt Lake City is not only being recruited by other teams hiring the same title. The same person is a credible candidate for several adjacent occupations, and what those pay locally is part of what any offer has to clear. These are the published local figures for the titles that compete for this pool.
| Occupation | Employed | 25th percentile | Median | 75th percentile | 90th percentile |
|---|---|---|---|---|---|
| Software Developers | 19,040 | $102,560 | $129,600 | $160,740 | $177,090 |
| Web Developers | not published | $67,160 | $88,770 | $124,130 | $139,200 |
| Software QA Analysts and Testers | 1,610 | $61,530 | $82,940 | $106,170 | $133,740 |
| Data Scientists | 2,970 | $81,260 | $114,990 | $146,160 | $159,820 |
| Information Security Analysts | 1,190 | $78,180 | $102,830 | $131,510 | $170,320 |
Where a row is missing, the Bureau does not publish a separate estimate for this metro, usually because the local sample is too small to release.
The spread across these titles in Salt Lake City runs from $129,600 for software developers down to $82,940 for software qa analysts and testers. That gap is the practical reason technical people move sideways between titles rather than up within one: in this market the fastest available pay rise for a competent engineer is often a change of job title rather than a change of employer. If you are hiring at the lower end of that range, expect to lose some candidates to the upper end of it, and expect that to happen after they have accepted.
This also affects how a role should be written. A specification that describes the work in terms of one narrow title competes only for people who already hold it. One that describes the system and the ownership on offer reaches people currently sitting under a different title who would be entirely capable of the work, and that is usually where the available capacity in a tight market actually is.
Which direction this market is moving
A single year tells you the price. Three tell you whether it is going up. These are the published figures for software developers in the Salt Lake City-Murray, UT area across the last three releases.
| Reference period | Employed | Median wage |
|---|---|---|
| May 2023 | 14,450 | $115,750 |
| May 2024 | 16,740 | $128,350 |
| May 2025 | 19,040 | $129,600 |
Source: BLS Occupational Employment and Wage Statistics, metropolitan area files. The Bureau does not design these releases to be read as a time series; treat the movement as a direction rather than as a growth rate.
Across those two years the local median moved up 12%. Employment moved up 32% over the same period. For someone planning a iOS developer hire in Salt Lake City, the practical reading is that a salary band set from figures more than a year old is now likely to be under the market.
Markets a candidate here would also consider
Candidates do not compare your offer against a national average. They compare it against what they could get nearby, and for a iOS developer in Salt Lake City that means a handful of specific metros. These are the closest comparisons on the published figures.
| Metro area | Employed | Median wage | vs Salt Lake City | Location quotient |
|---|---|---|---|---|
| Salt Lake City-Murray, UT | 19,040 | $129,600 | — | 2.12 |
| Denver-Aurora-Centennial, CO | 27,010 | $137,610 | +6% | 1.55 |
| Phoenix-Mesa-Chandler, AZ | 29,380 | $131,750 | +2% | 1.14 |
| Seattle-Tacoma-Bellevue, WA | 92,770 | $167,280 | +29% | 4.10 |
Percentages compare each metro against Salt Lake City rather than against the national median.
Seattle-Tacoma-Bellevue pays meaningfully more for this occupation than Salt Lake City does. For remote-capable work that is a real competitor for the same people, and it is worth knowing before you set a band rather than after a candidate declines.
The same table read the other way is a sourcing map. If the local pool is thin and a neighbouring metro pays less for the same occupation, that metro is where a remote or relocating candidate is most likely to come from, and the conversation is easier because the move is upward for them.
Where iOS and Swift work actually sits in this economy
The Salt Lake City economy is anchored by SaaS and devtools, financial services, outdoor commerce and healthcare data. iOS and Swift is not used identically across those, and the version of the skill that is abundant locally is shaped by whichever of them employs the most engineers. That is the part a national salary table cannot tell you and it is usually what decides whether a shortlist converts.
SaaS and devtools
Where iOS and Swift appears in SaaS and devtools, it most often looks like the hardware companion applications pattern: Applications pairing with physical devices over Bluetooth, where the platform's connectivity behaviour is the main challenge. Developers coming out of this part of the Salt Lake City market therefore tend to arrive strong on the constraints that sector imposes and lighter on the ones it never had to deal with. If your product shares those constraints, that is experience you would otherwise spend a year building. If it does not, the gap is real, and it is a fair thing to ask about directly rather than to discover in month two.
Financial services
Where iOS and Swift appears in financial services, it most often looks like the consumer applications pattern: Products where iOS users are the primary or most valuable audience and platform polish is a differentiator. Developers coming out of this part of the Salt Lake City market therefore tend to arrive strong on the constraints that sector imposes and lighter on the ones it never had to deal with. If your product shares those constraints, that is experience you would otherwise spend a year building. If it does not, the gap is real, and it is a fair thing to ask about directly rather than to discover in month two.
Outdoor commerce
Where iOS and Swift appears in outdoor commerce, it most often looks like the media and entertainment pattern: Streaming and content applications, where playback, background audio and offline behaviour are the hard parts. Developers coming out of this part of the Salt Lake City market therefore tend to arrive strong on the constraints that sector imposes and lighter on the ones it never had to deal with. If your product shares those constraints, that is experience you would otherwise spend a year building. If it does not, the gap is real, and it is a fair thing to ask about directly rather than to discover in month two.
Healthcare data
Where iOS and Swift appears in healthcare data, it most often looks like the enterprise and field applications pattern: Internal applications distributed through managed deployment rather than the public store. Developers coming out of this part of the Salt Lake City market therefore tend to arrive strong on the constraints that sector imposes and lighter on the ones it never had to deal with. If your product shares those constraints, that is experience you would otherwise spend a year building. If it does not, the gap is real, and it is a fair thing to ask about directly rather than to discover in month two.
The practical use of this is in reading CVs rather than in sourcing. Two candidates in Salt Lake City with the same number of years of iOS and Swift can have been solving quite different problems, and the interview should be aimed at the difference rather than at the technology they have in common.
What a local iOS developer seat costs to keep open
Salary is the quoted number and it is not the budget. Below is the employer-side payroll cost of one person in this occupation in Salt Lake City, using published local wages and the statutory 2026 employer rates.
| Wage point | Annual wage | Employer OASDI and Medicare | Wage plus these taxes |
|---|---|---|---|
| 25th percentile | $102,560 | $7,846 | $110,406 |
| Median | $129,600 | $9,914 | $139,514 |
| 75th percentile | $160,740 | $12,297 | $173,037 |
Employer OASDI at 6.2% to a wage base of $184,500, Medicare at 1.45% uncapped. Source: Social Security Administration, Contribution and Benefit Base, retrieved 2026-09-25. Unemployment insurance, benefits, equipment and recruitment cost are additional.
Then there is the cost nobody puts in the model. Every month the role is open, the work it was meant to do is not happening. That cost is the same whichever way you eventually fill the seat, and in a specialist search it routinely exceeds the difference between the options being compared. It is the single most common reason a cost comparison that looked careful turns out to have been wrong.
What to test when the pool is this one
The full interview guide for this technology is on the iOS and Swift developers page. What changes in Salt Lake City is emphasis rather than substance: given what the local market has been building, these are the areas where candidates here differ most from each other, and therefore where an interview earns its keep.
Retain cycles and memory
The classic iOS defect, invisible until it is a problem.
- Strong answer: Explains strong and weak capture, uses the memory graph debugger, and can describe a leak they found.
- Warning sign: Captures self strongly in long-lived closures without thinking about it.
Swift Concurrency and actors
The clearest test of whether their knowledge is current.
- Strong answer: Uses structured concurrency, understands actor isolation and main-actor annotation, and can explain what the compiler now catches.
- Warning sign: Works entirely in dispatch queues and completion handlers, which places their experience several years back.
SwiftUI state ownership
Where declarative interface bugs and performance problems originate.
- Strong answer: Explains which property wrapper owns state versus observes it, and can diagnose an unnecessary re-render.
- Warning sign: Uses state wrappers interchangeably and cannot explain the difference.
Two patterns worth asking about directly, because they show up in inherited codebases far more often than candidates volunteer them:
Massive view controllers
- What you see: A single controller of thousands of lines holding networking, business logic and presentation.
- What it costs: Nothing is testable in isolation and every change risks unrelated behaviour.
- The fix: Extract networking and logic into separate types with clear inputs and outputs. The controller should coordinate.
Blocking the main thread
- What you see: Network calls, disk access or heavy decoding performed synchronously on the main actor.
- What it costs: A frozen interface, and in the worst case a watchdog termination that appears as a crash.
- The fix: Move work off the main actor and update the interface on it. Structured concurrency makes this explicit rather than conventional.
The options, and what actually decides between them
Once the local figures are on the table, most teams are choosing between three ways of getting iOS and Swift capacity into Salt Lake City. They are not ranked. Which one is right depends on how long the work lasts, how much of it there is, and how much of the surrounding context the person needs to hold.
Hiring locally onto your own payroll
The right answer when the work is permanent, when the person needs to accumulate context that has no value anywhere else, or when presence in Salt Lake City is a genuine requirement rather than a preference. The costs are the ones in the table above plus benefits and recruitment, and the risk is time: in a market this concentrated the search itself is usually quick and the closing is where offers are lost.
Adding a vetted developer to your existing team
Staff augmentation suits work that is real but not permanent, and teams that already have the review capacity and the architectural direction in place. The person joins your standups, your repository and your process. What you are buying is capacity and specific iOS and Swift experience, not decision-making, and the constraint is almost always how much code your existing team can review rather than how many developers you add.
A dedicated team that owns an area
The right shape when there is a whole area of work to own rather than a queue of tickets, and when you would otherwise be hiring three or four people at once into a market where that takes a year. It asks more of you at the start, because an area cannot be owned without a clear definition of what it includes and who decides, and it asks less of you afterwards.
The comparison people get wrong is between a local salary and an hourly rate. Those are not the same quantity. A fair comparison puts the fully loaded employer cost of a local seat, including the months it stands empty and the recruitment spend that filled it, against the total cost of the alternative including the coordination overhead it adds. Run honestly, that comparison sometimes favours hiring locally, and when it does we will say so.
A realistic plan for this search
Compress the process before you start
With iOS and Swift work this concentrated in Salt Lake City, the candidates worth hiring are in several conversations at once. Fix the panel, the decision-maker and the offer range before the first call. Processes that add a stage midway lose the people they were trying to be careful about.
Plan for the counter-offer
Expect the current employer to respond, and decide in advance whether you will match, improve or walk. Improvising that decision under a deadline is how teams end up overpaying for a hire who leaves in a year anyway.
Give the hire something to land on
A running environment on day one, a named reviewer and access to the real system rather than a mock. The difference between a first merged change in week one and in week four is almost entirely on your side of the table, not the candidate's.
Write the brief around the system, not the stack
State what the system does, what it runs on, what is already decided and what the new person would own. A list of technologies with no context filters for keyword matches, and keyword matches are exactly who gets rejected in the technical round.
What changes when the developer is not in the building
Most of what makes a distributed iOS developer productive is decided in their first two weeks, and almost all of it is on the client side. These are the things that reliably separate a first merged change in week one from a first merged change in week four.
A first task that is small and real
Something that ships in the first few days. It proves the environment, the review path and the deployment path all work, and it surfaces the broken one while it is still cheap to fix.
Decisions written down where they can be found
In a team split across time zones, a decision made in a conversation in Salt Lake City does not exist for anyone who was not in it. This is the discipline that distributed teams either build early or pay for repeatedly.
An agreed overlap window
A few hours, published, treated as real, and used for review and decisions rather than status. Teams that skip this do not save meeting time; they spend it several times over in waiting.
A running environment on day one
Not documentation describing how to build one. An environment that starts, with seed data, on the machine the developer actually has. Every day spent on environment setup is a day billed at full rate for no output, and it is the single most common avoidable cost in an engagement.
None of this is specific to working with us. It is what any developer joining any team needs, and it is worth stating plainly because the failures above get attributed to the developer far more often than to the setup that produced them.
The same role in other US markets
Ranked by how many people are employed in this occupation locally, which is the figure that most affects how long a search takes.
- iOS and Swift developers in New York $166,830
- iOS and Swift developers in Seattle $167,280
- iOS and Swift developers in San Jose $213,110
- iOS and Swift developers in Washington, D.C. $154,930
- iOS and Swift developers in San Francisco $186,640
- iOS and Swift developers in Dallas-Fort Worth $133,290
- iOS and Swift developers in Los Angeles $160,920
- iOS and Swift developers in Boston $166,090
- iOS and Swift developers in Chicago $134,380
- iOS and Swift developers in Atlanta $132,960
- iOS and Swift developers in Austin $134,120
- iOS and Swift developers in Phoenix $131,750
- iOS and Swift developers in Philadelphia $133,040
- iOS and Swift developers in Minneapolis-St. Paul $130,920
- iOS and Swift developers in Denver $137,610
Other technologies in Salt Lake City
Skills that appear alongside iOS and Swift on most job specifications.
- TypeScript developers in Salt Lake City
- React Native developers in Salt Lake City
- Flutter developers in Salt Lake City
- Android and Kotlin developers in Salt Lake City
- AWS developers in Salt Lake City
For the technology itself, including the full interview guide, migration paths and what each level can own, see hiring iOS and Swift developers. For the wider Salt Lake City technical market across every occupation, see hiring developers in Salt Lake City.
Frequently asked questions
What does a iOS developer cost in Salt Lake City?
There is no official wage figure for iOS and Swift specifically, because the Bureau of Labor Statistics classifies by occupation rather than by technology. The honest baseline is Software Developers in the Salt Lake City-Murray, UT area, where the median annual wage is $129,600 and the middle half of the market runs from $102,560 to $160,740. Those are employer wages, before payroll taxes, benefits and recruitment cost.
How many iOS developers are there in Salt Lake City?
Nobody counts developers by technology, so any specific number you see quoted is an estimate. What is published is the occupation: 19,040 people in software developers in the Salt Lake City-Murray, UT area. iOS and Swift is one technology inside that population, and the share using it is a matter of inference rather than record.
Is it faster to hire a iOS developer locally in Salt Lake City or remotely?
With the occupation this concentrated in Salt Lake City, local sourcing is usually quick and closing is the slow part, because good candidates have options and current employers counter. Remote widens the pool but does not remove the closing problem.
Do we need someone in the Salt Lake City time zone?
Usually less than teams assume. What genuinely needs the local clock is live incident response, work with people who are only available in local hours, and anything tied to a physical site. Everything else needs a committed overlap window of a few hours rather than a matching working day. Salt Lake City runs on Mountain time.
Which local industries will a iOS developer here have come from?
The anchors of this economy are SaaS and devtools, financial services, outdoor commerce and healthcare data. Most experienced candidates in this market will have spent time in at least one of them, and that background shapes both what they are good at and what they have never had to handle. It is worth asking about explicitly rather than inferring from the CV.
Can you supply a iOS developer who overlaps with Salt Lake City hours?
Yes. Overlap is the thing we schedule around rather than a side effect of where someone happens to live, and it is agreed before an engagement starts rather than negotiated afterwards. Tell us which hours genuinely need to be covered and why, and we will tell you whether we can meet it.
How do you assess a iOS developer before we see them?
Working code and a conversation about decisions, not a quiz. We look at what someone has built, ask what they would now do differently and why, and probe the areas where this technology most reliably separates people. You see our reasoning alongside the shortlist, including the reservations.
What if the shortlist is wrong?
Tell us why and we will recalibrate. A rejected shortlist normally means the brief and the need had drifted apart, and that is worth finding out in week one rather than month three. We would rather say we are not the right fit for a role than keep sending candidates against a brief that is not working.