Find the matching job for you with ease

Full Stack Developer (React + .Net) role based in Lisle, IL. They need a veteran who can take old ASP.NET Web Forms and rebuild them on .NET Core with a React front‑end, while keeping the whole CI/CD pipeline humming. If you enjoy juggling API design, Kubernetes deployments, and deep SQL work, this is a straight‑up engineering challenge. ### What You'll Actually Be Doing You’ll spend most of your day modernizing legacy ASP.NET Web Forms apps, rewriting them as .NET Core Web APIs and pairing them with a React SPA. Expect to write a lot of unit tests, set up CI/CD pipelines that push Docker images to Kubernetes, and troubleshoot performance or security issues in production. You’ll also be the go‑to person for complex SQL queries, SOAP/REST integration, and ensuring the GitFlow branching strategy stays clean across multiple feature teams. ### The Core Tech Stack The non‑negotiables are .NET Core (C#) and React – you must be comfortable building RESTful APIs in C# and consuming them with a modern React codebase (hooks, functional components). They also demand solid SQL skills for stored procedures, a working knowledge of Azure services, and hands‑on experience with Docker/Kubernetes for deployments. CI/CD isn’t optional; you’ll be wiring up pipelines in Azure DevOps or similar, so familiarity with GitFlow, TFS/Git, and automated testing is a must. ### Interview Expectations 1. *Design a migration plan*: “How would you move a large ASP.NET Web Forms app to .NET Core with a React front‑end while minimizing downtime?” They’re looking for a phased approach – extract business logic into services, create API contracts, set up feature toggles, and use blue‑green deployments on Kubernetes. 2. *Performance debugging*: “Explain how you would identify and fix a slow‑running stored procedure that’s causing API latency.” Expect them to probe your ability to use execution plans, index tuning, and possibly caching strategies, as well as how you’d monitor the issue end‑to‑end with Application Insights. ### Application Advice Tailor your resume to shout out the exact stack: .NET Core, C#, React (hooks), Azure DevOps, Docker/Kubernetes, and complex SQL. Mirror phrasing from the JD like “CI/CD pipeline”, “GitFlow”, “SOLID design principles”, and “modernizing legacy ASP.NET Web Forms”. Highlight any projects where you turned a Web Forms app into a SPA, and quantify impact (e.g., reduced page load by 40%). A concise bullet that says “Built end‑to‑end CI/CD pipelines deploying .NET Core microservices to Azure Kubernetes Service” will get past most ATS filters.

The gig is a contract‑only SAP Security role based out of Culver City, focused on keeping S/4HANA, BW/4HANA and GRC environments locked down. You’ll be the go‑to person for role design, SoD checks, and day‑to‑day access tickets – a real‑world security ops shop. ### What You'll Actually Be Doing You’ll spend most of your day in the SAP Security cockpit: creating and tweaking roles, moving them through transports, and handling user provisioning requests. When a user hits an authorization error, you’ll dig into the profile, cross‑check SoD rules, and fire off a fix. The role also involves running regular access reviews, responding to incident tickets, and collaborating with functional and technical teams to align security with business changes. Expect a mix of hands‑on troubleshooting and strategic compliance work. ### The Core Tech Stack The must‑know stack is SAP S/4HANA security, BW/4HANA authorizations, and the full GRC suite (ARA, BRM, ARM, EAM). You’ll also need to be comfortable with Fiori security objects—catalogs, groups, and pages—because a lot of the UI access lives there. The role leans heavily on ITIL/ITSM processes for ticket handling, so familiarity with change management and incident workflows is non‑negotiable. ### Interview Expectations 1. *Design a role for a sales analyst who needs S/4HANA sales data and Fiori analytics while staying SoD‑clean.* The interviewer wants to see how you break down business requirements, map them to authorization objects, and run a quick SoD check. 2. *Walk through troubleshooting a user receiving an "Authorization Failure" in GRC ARA.* They’re looking for a systematic approach: check the user’s role, the relevant risk analysis, the underlying profile, and how you’d document and close the ticket. ### Application Advice Tailor your résumé to scream SAP Security Administration, S/4HANA, BW/4HANA, and GRC (mention ARA, BRM, ARM, EAM explicitly). Highlight any Fiori security work, role‑creation and transport experience, and concrete SoD analysis projects. Sprinkle in “ITIL”, “ITSM”, “access reviews”, and “compliance” to beat the ATS. A short bullet on “long‑term contract” or “consulting” experience will also line up with the hiring manager’s expectations.

They need a Salesforce Business Analyst who can hit the ground running on an Agentforce implementation. It's a contract gig, onsite in Juno Beach, paid $50‑$55/hr, and the client wants you in the interview room the same day. ### What You'll Actually Be Doing You'll spend most of your day talking to business users and product owners, pulling apart vague requests into concrete Salesforce requirements. Expect to run Agentforce workshops, draft user stories, map out process flows, and produce functional specs that the dev team can hand‑code. You'll also be the bridge between stakeholders and the technical crew, ensuring the solution aligns with both sales and service cloud capabilities. ### The Core Tech Stack The role revolves around deep knowledge of Salesforce Business Analysis, especially the Agentforce add‑on and AI‑driven extensions. You must be comfortable with Sales Cloud and Service Cloud data models, know how to configure objects, fields, and automation tools, and be able to translate business rules into flows, validation rules, or Apex when needed. The client is looking for someone who can quickly assess gaps and design solutions that scale. ### Interview Expectations 1. *Design a multi‑tenant Agentforce data model*: They'll ask you to sketch out objects, relationships, and sharing rules, watching how you balance flexibility with security. They're probing your ability to think beyond point‑and‑click and into architecture. 2. *Translate a complex business rule into a declarative solution*: Expect a scenario where you must decide between a flow, a validation rule, or custom Apex. They're looking for justification of your choice and how you'd unit‑test it. ### Application Advice Tailor your resume to echo the exact phrasing from the JD: “Salesforce Business Analyst”, “Agentforce”, “Sales Cloud”, “Service Cloud”, “Requirements Gathering”, “User Stories”, “Acceptance Criteria”, and “Stakeholder Management”. Highlight any C2C or contract work and quantify your impact (e.g., “led 5 Agentforce workshops delivering X% efficiency gains”). A concise, results‑focused bullet list will get past the ATS and catch the hiring manager's eye.

The role is a straight‑up Project Manager gig focused on moving massive on‑prem file servers into SharePoint Online/O365 for a tightly regulated financial services firm. If you’ve ever wrestled with data‑center exits, Azure lift‑and‑shifts, or the quirks of BlackRock Aladdin, this is a real‑world chance to own the end‑to‑end delivery. ### What You'll Actually Be Doing You’ll be the single point of accountability for planning, scheduling, and executing large‑scale server and file‑server migrations. That means building a migration blueprint, aligning security and compliance checkpoints for a highly regulated environment, and keeping the business side happy via daily stand‑ups, status decks, and escalation paths. You’ll also be the bridge between technical teams (Azure, networking, storage) and business owners, making sure every stakeholder knows what’s happening and why. ### The Core Tech Stack The non‑negotiables are deep experience with on‑prem to SharePoint Online/O365 migrations and a solid grasp of Azure‑related projects. You’ll need to speak the language of asset‑management and financial‑services compliance, and be comfortable pulling data from Jira and Confluence to drive transparent reporting. If you’ve ever touched BlackRock Aladdin, that’s a huge plus because the client expects you to understand its data‑flow constraints. ### Interview Expectations 1. *“Walk me through how you’d design a migration from an on‑prem file server farm to SharePoint Online while staying compliant with FINRA/SEC regulations.”* – They’re looking for a step‑by‑step risk‑assessment, data‑classification, and validation plan, not just a high‑level checklist. 2. *“How would you use Jira and Confluence to manage stakeholder communication on a high‑risk data‑center exit?”* – Expect them to probe your ability to set up custom workflows, traceability matrices, and real‑time dashboards that keep auditors and business owners on the same page. ### Application Advice Tailor your resume to hit the exact buzzwords the JD throws at you: **large‑scale server/file‑server migrations, SharePoint Online, O365, Azure, regulated environment, asset management, financial services, Jira, Confluence, BlackRock Aladdin**. Lead with a bullet that quantifies a similar migration you drove (e.g., “Led 200TB on‑prem to SharePoint Online migration for a $2B asset‑management firm, achieving 0 % compliance breaches”). Sprinkle those terms throughout your experience section so the ATS flags you as a perfect match.

The gig is a senior‑level, contract role driving end‑to‑end SAP S/4HANA Finance rollouts. You’ll be the go‑to person for FI design, configuration, and stakeholder alignment, and the success of the transformation hinges on your depth of finance knowledge. ### What You'll Actually Be Doing You’ll own the full FI blueprint—from General Ledger and Asset Accounting to Payables/Receivables and period‑close automation. Day‑to‑day you’ll translate finance requirements into S/4HANA config, troubleshoot tricky data migrations, and mentor offshore/onshore junior consultants. Expect heavy client interaction: status calls, risk mitigation workshops, and delivering crisp documentation that keeps the project on schedule. ### The Core Tech Stack The non‑negotiables are SAP S/4HANA Finance (FI) modules, especially GL, AP, AR, and AA, plus a solid grasp of the new S/4HANA data model and embedded analytics. You’ll need to be fluent in SAP Activate methodology, know how to use SAP Fiori for finance users, and be comfortable with integration points to ECC or other ERP systems. The client wants someone who can also dive into ABAP‑based enhancements if a standard solution falls short. ### Interview Expectations 1. *“Walk me through how you’d design a multi‑currency, multi‑entity closing process in S/4HANA FI.”* – They’re probing your end‑to‑end finance knowledge, data‑model awareness, and ability to balance global reporting with local compliance. 2. *“A client reports a discrepancy between the GL balance and the balance sheet after a migration. How do you troubleshoot?”* – Expect you to discuss reconciliation tools, delta‑load validation, and the importance of proper mapping of master data. ### Application Advice Tailor your resume to echo the exact phrasing in the JD: “SAP S/4HANA Financial Accounting,” “GL, AP, AR, AA,” “financial closing,” and “offshore/onshore team leadership.” Highlight any SAP Certified Application Associate – SAP S/4HANA for Financial Accounting and list each implementation project with duration and your role (e.g., Lead Configurator, Solution Architect). Sprinkle in “SAP Activate,” “Fiori,” and “stakeholder management” to get past the ATS and signal you’ve spoken the same language as the hiring team.

This contract role is for a Business/Functional Analyst focused on the Vision Next core‑banking platform, based in Berkeley Heights, NJ. You'll be the go‑to SME for card and payment workflows, translating business needs into functional specs that engineering can actually build. ### What You'll Actually Be Doing You’ll run requirement‑elicitation workshops, map current state processes to Vision Next capabilities, and produce detailed functional specifications. The day will involve maintaining JIRA backlogs, drafting user stories with clear acceptance criteria, and coordinating with product owners, architects, and engineers to keep sprints on track. You’ll also own functional testing and regression cycles, surface automation opportunities, and churn out senior‑level KPI reports for stakeholders. ### The Core Tech Stack The heart of the job is Vision Next – a core banking/cards/payments suite that handles everything from card authorization to billing and fee calculations. You need to speak the language of the card lifecycle (auth, validation, personalization, admin) and understand banking processes like invoicing and fee structures. On the tooling side, you’ll be expected to navigate JIRA/Confluence for Agile delivery, query MS SQL for data analysis, and grasp REST/OpenAPI concepts for integration work. Heavy Excel reporting and PowerPoint decks round out the everyday toolkit. ### Interview Expectations 1. *“Walk me through how you’d model the card authorization flow in Vision Next and which edge‑cases you’d validate.”* – They want to see you can break down the end‑to‑end flow, spot fraud checks, decline handling, and how you’d document those scenarios. 2. *“Design a functional test plan for a new billing module, including regression coverage.”* – The hiring manager is probing your ability to translate specs into test cases, prioritize critical paths, and ensure existing VN modules aren’t broken by the change. ### Application Advice Tailor your resume to highlight Vision Next or any similar core‑banking platform experience, and sprinkle in keywords like *card lifecycle, payments, regulatory compliance, functional analysis, Agile, JIRA, Confluence, MS SQL, REST/OpenAPI, user stories, acceptance criteria, test strategy, automation, stakeholder workshops*. Show concrete examples of backlog grooming, sprint planning, and KPI reporting to get past the ATS and catch the recruiter’s eye.

This role is a senior‑level analyst gig focused on the Facets healthcare platform. You’ll be the bridge between clinical operations and IT, making sure the system actually supports the day‑to‑day work of a busy health‑care provider. ### What You'll Actually Be Doing You’ll spend a good chunk of time digging into existing Facets configurations, mapping out gaps, and writing detailed requirements for enhancements. Expect to run workshops with clinicians, translate their language into technical specs, and then validate that the delivered changes meet compliance rules (HIPAA, HEDIS). Day‑to‑day you’ll be juggling data‑model tweaks, reporting requests, and occasional troubleshooting of claim‑processing errors. ### The Core Tech Stack The non‑negotiable skill is deep experience with the Facets suite—especially the claims and enrollment modules. You’ll also need solid SQL/PL‑SQL chops because most customizations live in the database layer. A working knowledge of HL7, FHIR, or other health‑exchange standards is a plus, as is familiarity with ETL tools that move data into/from Facets. The company needs this because they’re trying to reduce claim re‑work and improve reporting latency, so any inefficiency in the stack directly hits the bottom line. ### Interview Expectations 1. *“Walk me through how you’d design a new eligibility check workflow in Facets without breaking existing claim processing.”* The hiring manager wants to see you can think in terms of the Facets data model, understand transaction boundaries, and anticipate downstream impacts. 2. *“Explain a performance issue you encountered with a large Facets SQL report and how you resolved it.”* They’re looking for concrete evidence you can tune complex queries, use indexing wisely, and balance load‑time versus data‑freshness. ### Application Advice Tailor your resume to echo the exact phrasing from the posting: “Healthcare System Analyst,” “Business System Analyst,” and “Facets.” Highlight any end‑to‑end implementations you led, especially those that involved requirements gathering, workflow redesign, and compliance testing. Sprinkle in keywords like “HIPAA,” “claims processing,” “SQL/PL‑SQL,” “HL7/FHIR,” and “process improvement.” A concise bullet that says “10+ years delivering Facets enhancements for multi‑site health systems” will get past most ATS filters and signal you’re the senior candidate they need.

This is a six‑month contract Business Analyst role that lives at the intersection of mainframe CICS and front‑end UI work for a client in McLean, VA. It’s not a vague “process‑doc” gig – you’ll be expected to understand the business, sketch UI screens, and translate those into concrete data models. ### What You'll Actually Be Doing You’ll spend most of your day meeting with subject‑matter experts to capture functional requirements, then turn those notes into UI wireframes and SQL‑backed data specifications. Expect to write a lot of Excel‑based documentation, build simple relational tables, and validate that the CICS transactions you touch actually surface the right data in the UI. Because the job is onsite, you’ll also be the go‑to person for quick clarifications when the team hits a roadblock. ### The Core Tech Stack The must‑know pieces are CICS (you need to speak the language of transaction codes, COMMAREA handling, and basic debugging), relational databases with solid SQL chops, and UI design fundamentals—think mock‑ups, user flows, and the ability to prototype quickly. Excel isn’t optional; it’s the primary tool for requirement traceability and stakeholder presentations. The company wants someone who can bridge the old‑school mainframe world with modern UI expectations. ### Interview Expectations 1. *“Walk me through how you would diagnose an intermittent CICS transaction failure.”* – They’re looking for a systematic approach: checking logs, examining COMMAREA, reviewing resource limits, and using tools like CEMT or CICS Explorer. 2. *“How would you convert a business process diagram into a relational schema and then into a UI prototype?”* – The answer should show you can identify entities, define primary/foreign keys, map them to UI forms, and justify design decisions with usability in mind. ### Application Advice Tailor your resume to hit the exact buzzwords the JD throws at you: **Business Analyst**, **CICS**, **UI design**, **SQL**, **relational database**, **Excel**, **requirements documentation**, and **mainframe**. Highlight any project where you linked a UI mock‑up to a back‑end CICS or SQL solution, and quantify the impact (e.g., “Reduced requirement clarification time by 30%”). A concise “Technical Skills” block that lists CICS, SQL, Excel, and UI tools will help you get past the ATS.