Department of Government Operations Division of Purchasing and General Services 4315 S 2700 W, FL 3, Taylorsville, UT 84129-2128 Phone: 801-957-7160 www.purchasing.utah.gov

Issuing Procurement Unit: Division of Purchasing

Conducting Procurement Unit: Division of Forestry, Fire & State Lands

NOTICE OF INTENT TO AWARD A CONTRACT WITHOUT ENGAGING IN A STANDARD PROCUREMENT PROCESS

The Division of Purchasing is publishing this notice pursuant to the Utah Procurement Code. The Conducting Procurement Unit submitted this form to the Division of Purchasing claiming that it intends to award a contract without competition if it is determined by the Division of Purchasing, in writing, that:

• there is only one source for the procurement item;

• transitional costs are a significant consideration in selecting a procurement item; or

• the award of a contract is under circumstances, described in rules adopted by the applicable rulemaking authority, that make awarding the contract through a standard procurement process impractical and not in the best interest of the procurement unit.

In the subsequent pages the Conducting Procurement Unit has identified its justification for wanting to award a contract without engaging in standard procurement process.

Determination of Other Interested Vendors

If the procurement item identified in this notice is to be awarded as a sole source (only one source for the procurement item), then this notice will help determine if there are any other interested and qualified vendors that meet the specifications of this notice. Any such vendors must submit the following information:

• The name of the contesting person; and

• A detailed explanation of the contest, including documentation showing that there are other competing sources for the procurement item.

In addition, a vendor should include:

• Documentation that your firm can provide a comparable or better procurement item that meets or exceeds the specifications;

• Documentation that your firm can also provide the same proprietary procurement item or an equivalent procurement item; and

• If transitional costs are identified as the justification for this notice, submit a cost comparison of the identified transitional costs with your firm’s anticipated transitional costs.

Regardless of any prior communications with the Division of Purchasing or the State, all vendors interested in responding to this notice must submit a response to this posting containing complete responses to all of the information requested above.

DO NOT CONTACT THE CONDUCTING PROCUREMENT UNIT. Any questions regarding this notice, including obtaining additional information, can be obtained through the Division of Purchasing during the publication period. No action is required if you agree with this notice.

If the purpose of this notice is an intent to award a sole source, after the public notice period has passed, and the Division of Purchasing determines that there are other interested and qualified vendors that meet the specifications of this notice, then the Division of Purchasing will not award a contract pursuant to this notice. An award without competition may still be made even if there are other interested vendors when the basis for the award is due to transitional costs or impracticality as stated above.

If, after the public notice period has passed, no valid contests have been received, then the Division of Purchasing may award a contract to the identified vendor without engaging in a standard procurement process.

Read the entire form very carefully before responding to this notice.

It is anticipated that this procurement will result in a:

RESULT ACTION

Agency Contract The term of this contract (or extension) will be: and renewal options: .

The agency may not make the procurement until the solicitation process is completed and a contract is written and signed by the agency, the vendor, and the Division of Purchasing.

Purchase Order The agency may not make the procurement until the solicitation process is completed, the purchase order is signed by the Division of Purchasing and delivered to the agency and the vendor.

Description of procurement item to be purchased:

Estimated value of the contract/purchase order/increase:

Freight Cost (F.O.B. Destination, Freight Prepaid): $0.00

Vendor Name:

Explain in detail the service or product to be procured (additional information included in attached Scope of Work):

CHECK THE BOX THAT IDENTIFIES WHY A CONTRACT SHOULD BE AWARDED WITHOUT ENGAGING IN A STANDARD

PROCUREMENT PROCESS:

Sole Source - There is only one source for the procurement item. Complete Section A

Transitional Costs - Transitional costs are a significant consideration in selecting a procurement item and the results of a cost-benefit analysis demonstrate that transitional costs are unreasonable or cost-prohibitive, and that the award of a contract without engaging in a standard procurement process is in the best interest of the procurement unit.

Complete Section B

Impracticality - The award of a contract is under circumstances, described in rules adopted by the applicable rulemaking authority, that make awarding the contract through a standard procurement process impractical and not in the best interest of the procurement unit.

Complete Section C

Trial use contract for a new or innovative procurement item, or for a procurement item with a novel or unproven use or application. Complete Section D

Extension of a contract without engaging in a standard procurement process. If extension will result in a request to increase the contract total, then also complete Section F below. Complete Section E

Request to increase total contract amount. Complete Section F

SECTION A: ONLY ONE SOURCE

1. What is unique about this procurement item to justify an award of contract without engaging in a standard procurement process? (Explain in detail why the service, product, etc. is only available from a single supplier.)

2. Could the procurement item be reasonably modified to allow for competition?

3. Explain the market research performed.

4. What research have you conducted to ensure the requested procurement item is not available on an existing state cooperative contract?

X

$104,703.75

5. If there is only one source for the procurement item, list the names of other similar vendors contacted, contact person, and a summary of their response.

SECTION B: TRANSITIONAL COSTS

1. Describe the existing procurement item; include the original purchase price and date of purchase for the existing procurement item.

2. Supply the following:

a. Procurement method used to purchase the existing procurement item: (e.g. IFB, RFP, Sole Source):

b. Solicitation number or RQS/RQM number for the existing procurement item:

c. Contract number for the existing procurement item:

3. Attach the cost-benefit analysis, as required by Utah Code Section 63G-6a-802, that demonstrates that transitional costs are unreasonable or cost-prohibitive.

SECTION C: STANDARD PROCUREMENT PROCESS IMPRACTICAL

1.

Review R33-108-101c and provide supporting justification why awarding the contract through a standard procurement process is impractical and not in the best interest of the procurement unit under the circumstances; including any supporting documentation.

2. Supply the following, if applicable:

a. Procurement method used to purchase existing procurement item (e.g. IFB, RFP, Sole Source):

b. Solicitation number or RQS/RQM number for the existing procurement item:

c. Contract number for existing procurement item:

SECTION D: TRIAL USE CONTRACT

1. Describe how this trial use contract for the new or novel procurement item will benefit your agency.

2. Describe how the procurement item is new or innovative, or how the procurement item has a proposed use/application that is novel or unproven.

3. Describe why a trial use contract exception is necessary for this procurement item at this time as opposed to conducting a standard procurement process to procure the procurement item.

4. What research have you conducted to ensure the requested procurement item is not available on an existing state cooperative contract?

5.

How long does the agency need to test the procurement item and what quantities of the procurement item (if applicable) will be necessary to test this procurement item? Note trial use contracts generally cannot exceed a period of 24 months.

SECTION E: EXTENSION OF CONTRACT WITHOUT ENGAGING IN A STANDARD PROCUREMENT PROCESS The procurement official may extend a contract up to 120 days. For extensions beyond 120 days from the original contract end date, the procurement official may extend the contract after consulting with legal counsel.

Original End Date: Enter date. Current End Date: Enter date.

Proposed End Date: Enter date. Contract Number: Enter text.

1.

Is this request for a contract extension the result of a protest, appeal or court action? If yes, agency does not need to complete items 2-5 below. Provide the solicitation number that resulted in a protest and date of the protest, appeal or court action.

2.

Describe why extending this contract without engaging in a standard procurement process is necessary to avoid a lapse in a critical government service, OR to mitigate a circumstance that is likely to have a negative impact on public health, safety, welfare, or property.

3.

Confirm the procurement unit is currently engaged in a standard procurement process for the procurement item that is subject to the contract extension request and that the standard procurement process is delayed due to an unintentional error.

4.

Justification for Extension: check all that apply:

☐ The standard procurement process is delayed due to an unintentional error.

☐ A change in an industry standard requires one or more significant changes to specifications for the procurement item.

☐ To prevent the loss of federal funds.

☐ To mitigate the effects of a delay of a state or federal appropriation.

☐ To enable the procurement unit to continue to receive a procurement item during a delay in the implementation of a contract awarded pursuant to a procurement that has already been conducted.

☐ To enable the procurement unit to continue to receive a procurement item during a period of time during which negotiations with a vendor under a new contract for the procurement item are being conducted.

5. For the selection(s) above, provide any additional details regarding the circumstances justifying a contract extension.

SECTION F: REQUEST TO INCREASE TOTAL CONTRACT AMOUNT

If the original solicitation type was an ACWESPP (e.g. sole source) and the proposed contract total will exceed $50,000, then public notice is required to increase the contract total. Public notice is not necessary if the procurement official waives the public notice requirement in accordance with R33-108-101e.

Contractor Name: Timmons Group Contract Number: 236317

Original Contract Total: 445,150.00 Current Contract Total: 556,703.75

Proposed Contract Total: 661,407.5 % Increase from Original: 48.58%

Solicitation Number: AM23-32 Solicitation Type: SS-MA Product or Service Description: Software Maintenance/Support

Why is the contract total being increased? Check all that apply.

☐ The term of the contract is being extended (also complete Section E above if extending).

☐ The quantity of products or services needed has increased.

☐ The price, rate, or fee for a product or service has increased.

☒ A new or upgraded product or service is needed.

Provide details for the answer that was selected in the previous question. Provide any reasons for the increase.

IT contracts are complex & evolve from their original plan to what is actually executable in the time & funds given. Due the evolution of the product during development we need to add additional funds to get the product closer to the desired goal.

The way the contract was originally written made the nuances of this unclear as the nature of cloud IT projects is more complex and perpetual than determinant. This will include development costs and hosting/maintenance fees that were not as clearly outlined as they could have been. The updated Hosting/Maintanence charges match the original contract’s outlined cost estimates.

SLAM Sovereign Land Asset Management Hosting, Maintenance, and Support Scope of Work (SOW)

MARCH 4, 2026

PREPARED BY:

Chris Gerecke 1001 Boulders Parkway, Suite 300 Richmond, Virginia 23225 804.200.6962 Chris.gerecke@timmons.com mailto:Chris.gerecke@timmons.com

SLAM Sovereign Lands Asset Management Hosting, Support and Maintenance SOW

2 | P a g e

Table of Contents

Executive Summary

Task 1. Hosting and Managed Services

Task 1.1 Hosting

Task 1.2 Managed Services

Task 2 Application Maintenance:

Task 2.1 Maintenance Work

Task 2.2 Maintenance Testing

Task 3 Application Support and Enhancements:

Task 3.1 Support planning meetings

Task 3.2 Planned application development

Task 3.3 Ad-hoc support for critical application issues

Task 3 Warranty

Hosting and Managed Services and Maintenance Fee Table

Maintenance Fee Table

Application Support and Enhancements Fee Table

FY 26 Enhancement Targets:

FY 27 Enhancement Targets:

FY 28 Enhancement Targets:

Summary Fee Table

Applicable Hourly Rates

3 | P a g e

Executive Summary Timmons Group & Utah Forestry, Fire, and State Lands (FFSL) developed the Sovereign Lands Asset Management (SLAM) application in 2023. SLAM is a system that automates the management and tracking of multiple business processes within the Sovereign Lands Program, establishing and maintaining robust internal controls, audit trails, and geospatial data access. Timmons Group will leverage our experience working with FFSL to enhance SLAM to meet FFSL’s requirements and better integrate FFSL’s internal workflows and documents to create additional internal efficiencies. FFSL and Timmons Group developed the following enhancements in Phase II:

• Ability to create reminders for the administration of lands, assets, and projects.

• Development of advanced querying abilities to assist with the management of assets and agreements.

• Development of spatial data views of assets and agreements.

• Allowing the public to have a defined view of assets and agreements.

• Multiple other enhancements as deemed priority by FFSL.

SLAM was released into production on October 28, 2025, after the completion of the implementation/development phase. The SLAM application is currently hosted by Timmons Group in Amazon Web Services (AWS) as part of the implementation project until June 2026, as part of the previous contract. At that time, the hosting will need to be renewed for SLAM to continue to be available. SLAM also needs to be maintained over time. This SOW provides an amendment to Phase II to restructure hosting, support, and maintenance costs for long-term upkeep of SLAM and support the following additional enhancements:

• Support for Additional Encumbrance Types

• Feature Service Improvements

• Table and Filter Improvements

• Bulk User Assignment Actions for Encumbrances

• Expiry Workflow and In-App Notifications

• User Management

Task 1. Hosting and Managed Services This task covers hosting and managed services for the Sovereign Lands Asset Management (SLAM) application (the ‘SOFTWARE’). The details and assumptions covered within hosting and managed services are noted below. For this agreement, Timmons Group is referred to as the ‘CONSULTANT’ and Utah FFSL Sovereign Lands is the ‘CUSTOMER’. Hosting and managed services to commence on July 1, 2026, and continue for twenty-four (24) months.

4 | P a g e

Task 1.1 Hosting

1. Infrastructure and cloud services to support specified monthly active users for the purposes of hosting the SOFTWARE in support of monthly active users.

2. Backup of CUSTOMER data daily where it is retained. Backups are stored in multiple physical locations for redundancy. Backup and recovery plan to be provided by the CONSULTANT and approved by the CUSTOMER.

3. One registered domain name

4. SSL/TLS certificate for the registered domain name

5. All applicable third-party server-side software licensing required to operate the SOFTWARE.

6. CONSULTANT shall make a reasonable effort to provide hosting services 24x7x365, not including planned downtime for infrastructure and/or server maintenance. In the event there is an interruption or issue with the hosting service, CUSTOMER shall report, and CONSULTANT shall respond to the incident and make reasonable efforts to resolve the issue and minimize the impacts to the operation of the SOFTWARE.

7. CONSULTANT shall notify the CUSTOMER in the event there is an interruption or issue with the hosting service that the CONSULTANT is aware of but not previously reported by the CUSTOMER;

CONSULTANT shall respond to the incident as if it were reported by the CUSTOMER.

Task 1.2 Managed Services

1. Set up and maintain cloud security in accordance with industry standards and best practices, utilizing the NIST Cybersecurity Framework (NIST CSF).

2. Apply software updates, patches, and minor upgrades to the underlying cloud infrastructure at least monthly.

3. Provide proactive cloud infrastructure monitoring and support.

4. Analyze and monitor infrastructure utilization.

5. Provide remediation services and intervention when an issue with the underlying cloud services is encountered.

6. Develop, maintain, and test backup procedures and a disaster recovery process for the SOFTWARE.

7. Monitor and optimize ongoing costs and services required to deliver cloud hosting and maintain desired performance of the SOFTWARE.

8. Provide a single point of contact for the CUSTOMER that knows the software and can triage issues and escalate need to the appropriate vendors when necessary.

9. CONSULTANT shall perform planned and unplanned hosting maintenance activities as needed for the purposes of applying SOFTWARE patches, updates, and system reboots. Whenever possible CONSULTANT will conduct planned hosting maintenance activates during the Nightly Maintenance Period (“NMP”) to minimize downtown to the SOFTWARE. The NMP daily time period will be between the hours of 7:00 PM and 7:00 AM, Eastern Standard Time, Sunday through Saturday, including holidays.

Task 2 Application Maintenance:

Task 2 details the recommended subtasks specific to the maintenance of the SLAM. Application maintenance is essential for ensuring the continued functionality, security, performance, and relevance of software applications in the ever-changing technological landscape. Maintenance serves as a proactive strategy for extending the life of an application by addressing technical debt, enabling continuous improvement, adapting to changing requirements, optimizing costs, preserving investments, and enhancing user experience. The work outlined in Task 2.1 and Task 2.2 are demonstrative of the

5 | P a g e work completed on a rolling basis to ensure the continued stability and optimal performance of the application. Maintenance

Task 2.1 Maintenance Work The following tasks are included in each maintenance release (scheduled on a semi-annual basis):

• Evaluate and Implement Maintenance Updates for Stability: We will assess the application's performance and functionality. Implement necessary updates to ensure sustained stability and reliability.

• Ensure Compatibility with New OS Versions, Browsers, and Software Updates: We will work to maintain compatibility with evolving technology environments by updating the application to work with new operating system versions, web browsers, and other relevant software updates, including dependencies and libraries.

• Update Technical Documentation Alongside Code Changes: We will keep technical documentation synchronized with code updates to provide developers with accurate and up-to-date information about the application's architecture, APIs, and coding standards.

• Enhance Error Logging Mechanisms: Improve error logging mechanisms to capture comprehensive data on application errors and exceptions. This enhanced logging helps in diagnosing issues more effectively and enables quicker resolution.

• Maintain a Clean, Organized, and Well-Documented Codebase: Ensure that the application's codebase is well-structured, with clear naming conventions and comments to facilitate understanding and future modifications. Alongside dependency updates we will refactor code to remove redundancies and improve maintainability as needed.

• Conduct Monthly Status and Financial Reviews: Schedule monthly meetings to review the project's progress, address any issues or concerns, and assess financial performance against budgetary goals.

• Hold Bi-weekly Internal Stand-up Meetings: Organize bi-weekly stand-up meetings to keep the development team aligned, share updates on project tasks and progress, discuss any impediments, and ensure that everyone is on the same page regarding project priorities and goals.

• Use Basecamp for Project Management: Utilize Basecamp as the central platform for project management, task tracking, collaboration, and communication. Leverage its features such as to-do lists, message boards, file sharing, and scheduling to streamline project workflows and keep all team members informed and engaged.

Task 2.2 Maintenance Testing

• Regression Testing Following Maintenance Updates: After making updates or fixes to the application, it's crucial to conduct regression testing to ensure that the changes haven't introduced new issues or affected existing functionality negatively.

• Documenting Performance Improvement Opportunities: Documenting opportunities for performance improvement helps in tracking and prioritizing enhancements that can lead to better overall user experience and efficiency.

• Updating Testing Use Cases for Client Reference: Keeping the testing use cases up to date ensures that both Utah FFSL and Timmons Group have clear documentation on how to test the application's functionalities, reducing misunderstandings and streamlining the testing process.

• Updating UAT Documentation: Updating User Acceptance Testing (UAT) documentation ensures that Utah FFSL’ and Timmons Group’s testers have the most recent information on how to test the

6 | P a g e application before its final deployment, improving the quality of feedback and reducing the likelihood of post-deployment issues.

• Verification of All Environments: Timmons Group will verify the application in all environments— development (Dev), quality assurance (QA), user acceptance testing (UAT), and production (Prod).

Task 3 Application Support and Enhancements:

Task 3 includes a budget for recommended minor application development updates, consulting, feature development (minor), bug fixes, and patches to the SLAM application on an as-needed basis. All work under this task will be estimated by Timmons Group and approved by the Utah FFSL Sovereign Lands team before work commences. This task is supported by time and materials billing and managed within a budget not-to-exceed (NTE) amount.

Task 3.1 Support planning meetings As needed cadence to scope and plan updates to the SLAM Application, each cadence will include a status update for the current and previous iteration and planning for the upcoming iteration.

Task 3.2 Planned application development Client-approved use of support and enhancement funds can include application updates, new features (minor/cosmetic), bug fixes, and patches.

Task 3.3 Ad-hoc support for critical application issues This task includes investigation, troubleshooting, correction, and resolution activities related to the SLAM. Critical needs will be responded to, and the Contractor will be actively working on critical issues within one (1) business day of being reported.

Task 3 Warranty The Service offerings are provided “as is”. The Services obligations set forth in this Agreement are in lieu of all warranties, express or implied, including, without limitation, any warranties of merchantability or fitness for a particular purpose. Services provided under this Agreement does not assure the uninterrupted operation of the SOFTWARE. Any planned application development will fall under a 15-day warranty period from the time of delivery. This Agreement does not alter, amend, extend, or replace the warranty as defined in any separate agreement between the CONSULTANT and the CUSTOMER.

7 | P a g e

Hosting and Managed Services and Maintenance Fee Table This table includes the semi-annual fee for hosting and managed services, to be billed semi-annually beginning July 1, 2026 (NOTE: Hosting for March 15, 2026 – June 30, 2026, is covered with the previous support contract). Hosting & Managed Services will be billed at the beginning of each cycle as defined in the chart below, semi-annually beginning July 1, 2026, through June 30, 2028.

Milestone Deliverable Fee Task 1. Hosting and Managed Services – (March 15, 2026 – June 30, 2028) Task 1.1 Hosting & Managed Services – FY 26 (March 15, 2026 –

June 30, 2026) $0 (2026 Fees paid before the amendment)

Sub-Total FY26 $0 Task 1.2 Hosting & Managed Services – FY 27 (July – Dec 2026) $6,000 Task 1.3 Hosting & Managed Services – FY 27 (Jan- Jun 2027) $6,000 Sub-Total FY27 $12,000 Task 1.4 Hosting & Managed Services – FY 28 (July – Dec 2027) $6,000 Task 1.5 Hosting & Managed Services – FY 28 (Jan – Jun 2028) $6,000 Sub-Total FY28 $12,000

Total Cost Burden for Hosting $24,000

Maintenance Fee Table This table includes the semi-annual fee for maintenance, to be billed semi-annually beginning July 1, 2026 (NOTE: Maintenance for March 15, 2026 – June 30, 2026, is covered with the previous support contract). Maintenance will be billed in arrears of the cycles as defined in the chart below, semi-annually beginning July 1, 2026, through June 30, 2028.

Milestone Deliverable Fee Task 2. Maintenance, Support & Enhancement – (March 15, 2026 – June 30, 2028) Task 2.1 FY26 Maintenance (March – June 30, 2028) $0* Sub-Total FY26 $0 Task 2.2 FY27 Maintenance (July 1, 2026 – December 31, 2026) $6,000 Task 2.3 FY27 Maintenance (Jan 1, 2027 – June 30, 2027) $6,000 Sub-Total FY27 $12,000 Task 2.5 FY28 Maintenance (July 1, 2027 – December 31, 2027) $6,000 Task 2.6 FY28 Maintenance (Jan 1, 2028 – June 30, 2028) $6,000 Sub-Total FY28 $12,000

Total Cost Burden for Maintenance $24,000

8 | P a g e

Application Support and Enhancements Fee Table This table includes the recommended application support and enhancement services, noted as a not-to-exceed amount, which can be increased or decreased per year. Support and enhancement services will be billed monthly, in arrears, for work completed. This table demonstrates the recommended funds for support and enhancements, beginning on March 15, 2026, through June 2028. We recommend $50,703.75 additional funding to support the remainder of FY26, based on the known enhancement request detailed below, and $24,000 for maintenance, support, and ad-hoc enhancement requests for FY27 and FY28. Support and enhancement services must be agreed upon in advance if the services are being rendered. Timmons will provide estimates for services, and only complete support and enhancement tasks upon approval by Utah FFSL.

FY 26 Enhancement Targets:

The following scope has been approved for FY26

• Support for Additional Encumbrance Types

• Feature Service Improvements o Support for Additional Attributes o Improvements to Syncing

• Table and Filter Improvements

• Bulk User Assignment Actions for Encumbrances

• Expiry Workflow and In-App Notifications

• User Management o Support for Different User Groups

FY 27 Enhancement Targets:

No Specific items have been identified. Timmons and Utah FFSL will schedule enhancement and maintenance checkpoints throughout the fiscal year to determine scope. Future amendments or change orders will be created by request from the Utah FFSL if the estimates for the enhancement request are greater than the not-to-exceed amount for the fiscal year.

FY 28 Enhancement Targets:

No Specific items have been identified. Timmons and Utah FFSL will schedule enhancement and maintenance checkpoints throughout the fiscal year to determine scope. Future amendments or change orders will be created by request from the Utah FFSL if the estimates for the enhancement request are greater than the not-to-exceed amount for the fiscal year.

Milestone Deliverable Fee Task 3. Support & Enhancement – (March 15, 2026 – June 30, 2028) Task 3.1 FY26 Enhancements $44,353.75 Task 3.2 FY26 Support, Deployment, & Testing $6,350.00

9 | P a g e

Sub-Total FY26 $50,703.75 Task 3.3 FY27 Support & Enhancements (July 1, 2026 – June 30, 2027) $3,000

Sub-Total FY27 $3,000 Task 3.4 FY28 Support & Enhancements (July 1, 2027 – June 30, 2028) $3,000

Sub-Total FY28 $3,000

Total Cost Burden for Maintenance, Support, & Enhancements $56,703.75

Summary Fee Table This table includes the recommended application support and enhancement services, noted as a not-to-exceed amount, which can be increased or decreased per year. Support and enhancement services will be billed monthly, in arrears, for work completed. This table demonstrates the recommended funds to support each fiscal year based on planned and ad hoc service requests.

Summary Fee Summary of Spend by FY – (March 15, 2026 – June 30, 2028) Sub-Total FY26 Hosting, Support, Maintenance, & Enhancements $50,703.75 Sub-Total FY27 Hosting, Support, Maintenance, & Enhancements $27,000 Sub-Total FY28 Hosting, Support, Maintenance, & Enhancements $27,000

Amendment Total $104,703.75

Applicable Hourly Rates Timmons Group has included the following rate table, effective for the term of this contract. This rate table will be used for Task 3.

Position FY26 Rate Table FY27 Rate Table FY28 Rate Table Project Principal $200.00 $205.00 $210.00 Project Manager $150.00 $155.00 $160.00 Business Analyst $150.00 $155.00 $160.00 Senior Engineer & Tech Lead $175.00 $180.00 $185.00 Quality Assurance Engineer $130.00 $135.00 $140.00 UI / UX Designer $140.00 $145.00 $145.00