Find the matching job for you with ease

The gig is a senior‑level Business Systems Analyst role focused on Microsoft 365 and SharePoint, based out of Sacramento with a hybrid schedule. It’s a C2C contract, so you’ll be billing the client directly, and they expect you to hit the ground running on a long‑term engagement. ### What You'll Actually Be Doing You’ll be the bridge between the business and the tech stack, translating functional needs into SharePoint sites, M365 groups, and automated workflows. Day‑to‑day you’ll troubleshoot desktop app issues, fine‑tune SharePoint permissions, and work with DevOps to push configuration changes. Expect a lot of cross‑team collaboration—product owners, security, and infrastructure will all be in your inbox, and you’ll need to keep the documentation clean and the release cadence smooth. ### The Core Tech Stack The non‑negotiables are deep SharePoint administration (site collections, modern pages, permission models) and a solid grasp of the broader M365 suite—Teams, OneDrive, Power Platform basics. They also want someone comfortable with DevOps tooling (think Azure Pipelines or GitHub Actions) to automate site provisioning. If you’ve built end‑to‑end solutions that span SharePoint Online, Teams, and Power Automate, you’ll be speaking the same language they need. ### Interview Expectations 1. *“Walk me through how you would design a multi‑tenant SharePoint architecture for a department that needs isolated document libraries but shared navigation.”* – They’re probing your ability to balance security boundaries with user experience and to justify using hub sites or managed metadata. 2. *“Explain a CI/CD pipeline you built for deploying SharePoint Framework (SPFx) web parts. What were the biggest pain points and how did you resolve them?”* – This shows whether you can marry DevOps practices with the M365 ecosystem, especially handling package versioning and tenant‑wide roll‑outs. ### Application Advice Tailor your resume to scream “M365, SharePoint, DevOps, cross‑team collaboration.” Put those exact terms in your summary and bullet points, e.g., “Led SharePoint Administration for 200+ users” or “Implemented Azure DevOps pipelines for SPFx deployments.” Highlight the 12+ years of experience and any C2C or contract work, and don’t forget to note the hybrid Sacramento location. A concise project line that quantifies impact (e.g., reduced document retrieval time by 30%) will help you cut through the ATS and catch the hiring manager’s eye.

The gig is a contract QA Automation role focused on building Playwright test suites for a New York‑based team. You’ll be writing end‑to‑end tests, wiring them into Azure DevOps or Jenkins pipelines, and keeping the test codebase clean enough for the devs to actually rely on it. ### What You'll Actually Be Doing You’ll spend most of your day authoring Playwright scripts that cover UI, API, and integration scenarios, then hooking those scripts into the CI pipeline so they run on every PR. Expect a lot of back‑and‑forth with developers to nail down acceptance criteria, plus hunting down flaky tests and fixing them before they break the build. You’ll also be logging bugs in JIRA or Azure DevOps and helping the team interpret test results to drive quality decisions. ### The Core Tech Stack The non‑negotiables are Playwright for both UI and API testing, plus a solid grasp of CI/CD tools like Azure DevOps, GitHub Actions, or Jenkins. You’ll also need to be comfortable with API testing utilities (Postman, REST Assured) and have a working knowledge of mainframe DB2/CICS environments, since the stack mentions IT IS_AMS_Mainframe administration. The idea is you can spin up a cross‑browser test suite, push it through the pipeline, and have it report cleanly to the team. ### Interview Expectations 1. *How would you troubleshoot a flaky Playwright test that only fails on Chrome in CI?* The interviewer wants to see your debugging workflow—checking network conditions, adding retries, using test hooks, and possibly isolating the test to identify environment‑specific issues. 2. *Describe how you’d integrate Playwright tests into an Azure DevOps pipeline and ensure test results are visible to the team.* They’re looking for concrete steps: adding a pipeline task, publishing test results as JUnit XML, gating PR merges on test pass/fail, and possibly using environment variables for secrets. ### Application Advice Tailor your resume to highlight every Playwright project you’ve shipped—mention the frameworks you built, the browsers you covered, and how you wired them into Azure DevOps or Jenkins pipelines. Sprinkle in keywords like “CI/CD integration,” “JIRA bug tracking,” “API testing with Postman/REST Assured,” and “cross‑browser automation.” If you have any exposure to DB2 or CICS, surface that too; it matches the niche mainframe admin skill set they listed. A concise bullet that reads *Designed Playwright‑based end‑to‑end test framework, integrated with Azure DevOps, reduced regression cycle by 30%* will get past most ATS filters.

This is a pure on‑site network engineer gig in Irvine, CA, focused on wiring up UPS gear, switches and surveillance cameras. It's a W‑2 contract, so you’ll be paid hourly and the work is hands‑on, not remote. ### What You'll Actually Be Doing You’ll spend most of your day pulling and terminating fiber or copper runs, installing rack‑mount UPS units, configuring enterprise switches, and hooking up IP‑based surveillance cameras. The role is entirely on‑site, so you’ll be troubleshooting hardware failures in real time, coordinating with facilities for power and rack space, and documenting as‑built diagrams for the client’s IT team. ### The Core Tech Stack The must‑know stack is pretty narrow: you need solid experience with UPS systems (understanding load calculations and battery backup), Cisco/Juniper (or comparable) switching gear, and IP camera networking (PoE, VLAN tagging, video streaming). The client also expects you to be comfortable with basic rack‑mount installation, cable management, and on‑site testing tools because there’s no room for guesswork when the hardware is physically in front of you. ### Interview Expectations 1. *“Walk me through how you would size a UPS for a core distribution switch that powers 10 downstream access switches.”* The interviewer wants to see your ability to calculate load, factor in redundancy, and discuss runtime versus budget. 2. *“A surveillance camera intermittently drops its feed after a firmware upgrade. What’s your troubleshooting flow?”* They’re probing whether you can isolate network, power, and firmware layers quickly, and whether you document each step. ### Application Advice Tailor your resume to the exact language in the posting: highlight “UPS equipment implementation”, “enterprise switch configuration”, and “surveillance camera installation”. Mention any on‑site, W‑2 contract experience and be explicit about visa status if it applies (GC or USC). Use the city name “Irvine, CA” and the work mode “Onsite” early in the summary so the ATS flags you as a local candidate. A short bullet like “Implemented UPS backup and PoE camera feeds for a 200‑port campus network (Onsite, Irvine, CA)” will get you past the first screen.

The role is a senior product ownership position focused on Salesforce Health Cloud for a healthcare payer/provider environment. You’ll own the roadmap, translate clinical requirements into user stories, and keep a tight feedback loop between clinicians and engineers. It’s a high‑visibility gig where your decisions directly affect patient data handling and compliance. ### What You'll Actually Be Doing You’ll spend most of your day grooming the backlog, writing clear acceptance criteria, and prioritizing features that improve care management workflows. Expect regular syncs with QA, developers, and clinical stakeholders to clarify HIPAA‑bound data rules, and you’ll be the go‑to person for any scope changes. Delivery is iterative—sprints end with a demo to business owners, and you’ll be responsible for ensuring each release meets both functional and regulatory expectations. ### The Core Tech Stack The non‑negotiable skill is deep, hands‑on experience with Salesforce Health Cloud—understanding its patient objects, care plans, and integration patterns. You also need a solid grasp of healthcare data standards (FHIR, HL7) and compliance (HIPAA). Agile/Scrum fluency is a must because the team runs two‑week sprints, and you’ll be the Scrum Product Owner driving story creation and sprint planning. ### Interview Expectations 1. *Design a data model for a multi‑payer scenario in Health Cloud.* The interviewer will look for how you map relationships between members, coverage tiers, and care plans while keeping PHI secure—expect discussion around sharing rules, field‑level security, and audit trails. 2. *Explain how you would prioritize a backlog that includes both regulatory fixes and new feature requests.* They want to see your reasoning framework—risk vs. value, impact on clinical outcomes, and how you communicate trade‑offs to both IT and business leaders. ### Application Advice Tailor your resume to mirror the JD language: lead with “Salesforce Health Cloud Product Owner” and list concrete achievements like “defined roadmap that reduced claim processing time by 15%.” Sprinkle keywords such as “patient/member data,” “care management,” “HIPAA compliance,” “Agile/Scrum,” and “stakeholder management.” Highlight any CVS Health or payer experience front‑and‑center, and quantify outcomes wherever possible to get past the ATS and catch the hiring manager’s eye.

This is a hands‑on QA role focused on Java/Spring Boot services, based fully onsite in Illinois. You’ll be writing and executing tests, hunting bugs, and making sure the code ships clean. ### What You'll Actually Be Doing You’ll spend most of your day writing unit and integration test cases in Java, pulling data from SQL databases, and exercising Spring Boot endpoints. Expect to own defect tracking from discovery to closure, work closely with developers to reproduce issues, and help improve the testing framework as the product evolves. The role is 100 % onsite, so you’ll be in the same room as the engineering team, doing rapid feedback loops. ### The Core Tech Stack The team lives in a Java‑centric world: Spring Boot back‑ends, relational databases accessed via SQL, and a test suite built around JUnit/TestNG (sometimes Selenium for UI). You need to be comfortable writing code‑level tests, mocking services, and understanding how Spring’s dependency injection affects test isolation. Those skills matter because the product’s reliability hinges on catching regressions before they hit production. ### Interview Expectations 1. *Design a test strategy for a Spring Boot microservice that talks to a PostgreSQL database.* The interviewer wants to see if you can separate unit, integration, and end‑to‑end layers, decide what to mock versus what to spin up in a test container, and articulate coverage goals. 2. *You have a flaky test that passes 80 % of the time. How do you diagnose and fix it?* They’re probing your debugging process: looking for race conditions, external resource dependence, or non‑deterministic data, and whether you use logs, retries, or test isolation techniques. ### Application Advice Tailor your resume to mirror the JD: lead with “2‑4 years of QA experience” and list “Java, SQL, Spring Boot” as core competencies. Mention concrete achievements like “Reduced critical bugs by 30 % through automated regression suite” and include the exact tools (JUnit, TestNG, Selenium, JIRA) to hit ATS keywords. Highlight that you thrive in an onsite environment and can collaborate face‑to‑face with developers.

Honestly, this is a straight‑up SailPoint IdentityIQ/IdentityNow gig for an experienced IAM pro. They're looking for someone who can hit the ground running on connector dev, workflow tweaks, and the whole identity lifecycle, all on‑site in Rosemead. ### What You'll Actually Be Doing You’ll spend most of your day onboarding new applications into SailPoint, writing Beanshell/Java scripts to glue data sources, and tweaking workflows that drive provisioning and de‑provisioning. Expect to troubleshoot connector failures, tune SQL queries for performance, and work with REST/SOAP APIs to keep the ecosystem in sync with Azure AD, Okta, or Ping. ### The Core Tech Stack The non‑negotiable bits are SailPoint IdentityIQ/IdentityNow, solid Java/Beanshell chops, and strong SQL. They also want you comfortable with the SailPoint connector framework and API integration (REST/SOAP) because most of the heavy lifting lives there. Bonus points if you’ve played with Okta, Ping, Azure AD, or have a SailPoint certification – that’s what will make you stand out. ### Interview Expectations 1. *Design a SailPoint connector for a legacy HR system.* They’ll probe how you’d model the schema, handle incremental pulls, and ensure idempotent provisioning – they want to see you can think about performance and error handling, not just copy‑paste code. 2. *Explain how you’d secure a workflow that updates privileged accounts.* Expect a deep dive into role‑based access, SOX/NIST considerations, and where you’d inject approval steps or MFA – the hiring manager is checking if you understand compliance as part of IAM. ### Application Advice Tailor your résumé to mirror the JD: lead with “SailPoint IdentityIQ/IdentityNow” and quantify your IAM experience (“8 years IAM, 4 years SailPoint”). Sprinkle in “Java, Beanshell, SQL, REST/SOAP, connector development, workflow automation, Okta, Azure AD, Ping, SOX/NIST/ISO compliance, SailPoint Certification”. Use those exact phrases; the ATS will be hunting for them. Also note the on‑site requirement in Rosemead to show you’re willing to relocate or already local.

This is a contract gig out of Oklahoma City focused on building full‑stack features using C# on the back end and Next.js on the front end. It’s a long‑term engagement paying $52/hr, so they need someone who can hit the ground running and own the codebase. ### What You'll Actually Be Doing You’ll be writing API endpoints in C# (likely ASP.NET Core) that power data‑intensive UI components built with Next.js. Expect to wire up authentication, handle pagination, and optimise database calls while keeping the React‑ish front‑end snappy. The team will push frequent releases, so you’ll also be troubleshooting production bugs, writing unit/integration tests, and collaborating with product owners to translate business rules into clean code. ### The Core Tech Stack The non‑negotiable skills are solid C#/.NET experience and a good grasp of modern JavaScript frameworks, specifically Next.js. They chose Next because they need server‑side rendering for SEO‑critical pages, so you’ll have to understand both static generation and API routes. Knowing SQL (or any relational DB) and RESTful design is assumed; familiarity with Azure or AWS is a plus but not a deal‑breaker. ### Interview Expectations 1. *“Explain how you would implement server‑side rendering in Next.js while still calling a C# API for data.”* – They want to see if you understand the data flow, where you’d fetch data in `getServerSideProps` vs. client‑side hooks, and how you’d handle auth tokens across the boundary. 2. *“Show me how you would design a C# service that batches database writes to reduce round‑trips.”* – This probes your ability to write efficient back‑end code, use async/await correctly, and think about performance at scale. ### Application Advice Tailor your resume to scream “C#/.NET” and “Next.js” – those exact phrases need to appear in your skill list and in the bullet points describing past projects. Highlight any work where you built APIs consumed by a React/Next front‑end, especially if you dealt with SSR or authentication. Mention the hourly rate expectation ($52/hr) and that you’re open to a long‑term C2C contract; that signals you’ve read the JD and are ready to negotiate.

Honestly, this role is a senior‑level iOS testing gig focused on XCUI automation, based in Sunnyvale and expects you to be on‑site. If you’ve spent the last decade writing Swift code and building UI tests, you’ll fit right in. ### What You'll Actually Be Doing You’ll spend most of your day authoring and maintaining XCUI test scripts against native iOS apps, integrating them into the CI pipeline, and troubleshooting flaky failures. The job also requires you to work closely with developers to understand new features, review test coverage, and push test reliability metrics forward. ### The Core Tech Stack The stack is pretty narrow: native iOS written in Swift, UI tests driven by Apple’s XCUI framework, and a CI system that runs those tests on real devices or simulators. Mastery of Swift syntax, XCTest assertions, and the quirks of Xcode’s test runner is non‑negotiable because the team lives and dies by fast, reliable UI feedback. ### Interview Expectations 1. *How would you diagnose and stabilize a flaky XCUI test that passes locally but fails on the CI server?* They’re looking for a methodical approach – isolate environment differences, add explicit waits, use launch arguments, and possibly mock external dependencies. 2. *Describe a strategy to mock network responses in an XCUI UI test without altering production code.* Expect them to mention tools like `URLProtocol` stubbing, local mock servers, or dependency injection via launch arguments, showing you can keep tests deterministic. ### Application Advice Tailor your resume to echo the exact terms the JD uses: “iOS”, “Swift”, “XCUI”, “UI Automation”, “Mobile Apps Testing”, and the “8+ years” experience badge. Highlight any on‑site or Sunnyvale‑based projects, and surface concrete metrics like “reduced flaky test rate by 30%”. A short cover note that mentions you’re comfortable working onsite in Sunnyvale will also help you get past the ATS.