Find the matching job for you with ease

This contract is a senior‑level lead role on an on‑site Informatica MDM/IDMC platform. You’ll own the end‑to‑end design, implementation, and ongoing tuning of a SaaS‑based MDM solution that feeds critical business data. ### What You'll Actually Be Doing You’ll spend most of your day in the Informatica IDMC console, wiring up Cloud Application Integration (CAI) and Cloud Data Integration (CDI) flows, then polishing data quality rules and governance policies. Expect to dive into data modeling—building entity hierarchies, defining match/merge logic, and tweaking performance knobs for scalability. You’ll also mentor junior engineers, review code, and act as the technical gatekeeper for any changes that could affect the MDM hub’s reliability. ### The Core Tech Stack The non‑negotiables are Java (or any compiled OO language) with solid Spring experience, because the integration layer is built on Spring‑boot services that talk to IDMC. On the Informatica side you need deep hands‑on with CAI, CDI, Data Quality, Data Governance, and the MDM SaaS APIs. The stack is essentially a Java‑Spring back‑end glued to Informatica’s cloud services, so you must be comfortable moving between code and the low‑code Informatica UI. ### Interview Expectations 1. *“Walk me through how you’d design a match/merge strategy for a hierarchical customer entity in Informatica MDM SaaS.”* They’re probing whether you understand entity‑level deduplication, survivorship rules, and the performance impact of large‑scale merges. 2. *“Explain a situation where a Spring‑based integration service caused a bottleneck in a CAI workflow. How did you diagnose and fix it?”* They want to see your debugging depth—JVM profiling, thread‑pool tuning, and how you tie those fixes back into the Informatica pipeline. ### Application Advice Tailor your resume to hit the exact buzzwords: *Informatica IDMC, CAI, CDI, Data Quality, Data Governance, MDM SaaS, entity modeling, match/merge, Java, Spring, technical lead.* Put the years of experience right next to each skill (e.g., “5+ years Informatica IDMC administration”). Highlight any end‑to‑end MDM projects you led and quantify impact (e.g., “Reduced duplicate records by 30% after redesigning match rules”). This will get past the ATS and signal you’ve done the exact work they need.

The role is a senior‑level, remote contract gig focused on government‑grade security frameworks. You’ll be the go‑to person for mapping risk, proving compliance, and passing audits for federal, state, or local clients—basically the bridge between tech controls and regulatory bodies. ### What You'll Actually Be Doing You’ll spend most of your day dissecting NIST 800‑53 and CSF controls, building risk assessments (800‑30) and system authorization packages (800‑37). Expect to draft and review System Security Plans, conduct gap analyses, and lead auditors through evidence collection. The job isn’t about writing code; it’s about translating dense compliance language into actionable remediation tickets and convincing stakeholders that the controls actually work. ### The Core Tech Stack The stack is all about standards, not languages. You must be fluent in NIST 800‑53, NIST CSF, FIPS 199/200, and the SAM/SIMM audit packages. Certifications aren’t optional fluff—they prove you can navigate the CISSP domains, CRISC risk‑management lifecycle, and the CISA/CDPSE/GSNA audit mind‑set. The company needs you to own the end‑to‑end compliance lifecycle, from risk identification to continuous monitoring. ### Interview Expectations 1. *“Walk me through how you’d conduct a NIST 800‑30 risk assessment for a new cloud service.”* They’re looking for a step‑by‑step methodology, evidence‑collection tactics, and how you tie findings back to 800‑53 controls. 2. *“A federal auditor is demanding evidence you’ve implemented FIPS 199 classification. How do you prove it?”* Expect you to discuss documentation artifacts, system security plans, and the audit trail you’d provide. ### Application Advice Tailor your résumé to mirror the exact language in the posting: drop “CISSP (5+ years)”, “CRISC (5+ years)”, “NIST 800‑53/CSF”, “FIPS 199/200”, “risk management using NIST 800‑30 & 800‑37”, and “government security audit”. Highlight any past FedRAMP, DoD, or state‑level audit work, and make sure the certifications appear in the top‑right of your resume so the ATS flags them immediately.

The team is looking for a seasoned blockchain engineer who can actually ship production‑grade smart contracts and keep the whole stack resilient. If you thrive on designing secure, scalable distributed systems and aren’t afraid to roll up your sleeves on both the protocol and cloud side, this role is worth a look. ### What You'll Actually Be Doing You’ll spend most of your day architecting permissioned DLT solutions, writing Solidity (or other contract languages) and wiring them to off‑chain services via oracles. Expect to build integration libraries that talk to internal APIs, push code through CI/CD pipelines on Azure or AWS, and mentor junior engineers on best‑practice patterns. The job also demands you keep an eye on data‑protection compliance for digital payments, so security reviews become a routine part of your sprint. ### The Core Tech Stack The must‑know pieces are Solidity for smart contracts, Java Spring Boot for the surrounding services, and a solid grasp of cryptography primitives that keep the ledger tamper‑proof. You’ll also need to be comfortable with Node.js or Python when stitching together oracle feeds, and have hands‑on experience deploying containers or VMs on Azure/AWS. The stack is deliberately polyglot because the platform needs to handle high‑throughput transactions while staying fault‑tolerant. ### Interview Expectations 1. *Design a scalable permissioned blockchain network*: they’ll want you to outline node topology, consensus choice, and how you’d handle shard‑level fault tolerance. They’re looking for depth in both theory and practical trade‑offs, not just buzzwords. 2. *Optimize a Solidity contract for gas*: expect a code snippet and be ready to explain how you’d refactor it to reduce gas costs while preserving security guarantees. The interviewer wants proof you can write efficient, audit‑ready contracts. ### Application Advice Tailor your resume to hit keywords like “Solidity”, “Java Springboot”, “Azure/AWS”, “oracle development”, and “cryptography”. Highlight any end‑to‑end blockchain projects where you led the full SDLC, especially if you mention CI/CD pipelines or fault‑tolerant architecture. A concise bullet that says “Designed and deployed permissioned DLT solution on Azure with 99.99% uptime” will get past most ATS filters.

Honestly, this is a hands‑on role in a data center in Boardman, Oregon. You’ll be the go‑to person for fixing servers, desktops and board‑level hardware, and you’ll need enough networking know‑how to keep the racks talking. It’s a solid entry‑to‑mid‑level gig for anyone who likes to roll up their sleeves. ### What You'll Actually Be Doing You’ll spend most of the day running diagnostics on rack‑mounted servers, swapping out failed blades or drive bays, and re‑imaging desktops that come in for repair. Expect to maintain an inventory of spare parts, document every incident in the ticketing system, and coordinate with the networking crew when a connectivity issue looks like a hardware fault. The job isn’t just “replace a bad fan” – you’ll also be called on to troubleshoot power distribution problems and keep the cooling infrastructure humming. ### The Core Tech Stack The shop floor is filled with Dell PowerEdge and HPE ProLiant servers, a mix of Windows and Linux OSes for health checks, and Cisco or Juniper switches for the basic networking layer. You’ll need to be comfortable with BIOS/UEFI settings, RAID controller configs, and using tools like iLO/iDRAC for out‑of‑band management. A solid grasp of TCP/IP, VLAN tagging, and simple cable‑tracing is essential because the data center’s uptime hinges on those low‑level connections. ### Interview Expectations One likely question: “A server powers on but never reaches POST – walk me through your diagnostic flow.” They’re hunting for a methodical approach – power‑supply verification, POST beep code interpretation, and fallback to minimal hardware boot. Another: “Two racks can’t communicate over a VLAN; how do you isolate the problem?” Expect them to probe your understanding of switch port configs, VLAN tagging, and how to use a packet sniffer or loopback test to pinpoint the fault. ### Application Advice Tailor your resume to echo the exact phrasing from the posting: highlight “hardware troubleshooting (servers/desktops/computer boards)”, “basic networking knowledge”, and “self‑starter mindset”. Sprinkle in “data center operations”, “server maintenance”, and “relocation willing” to get past the ATS. If you’ve logged hours on iLO/iDRAC, RAID rebuilds, or cable‑management projects, put those details front‑and‑center – they’ll signal you’ve already lived the day‑to‑day grind this role demands.

This contract gig is for a Salesforce SDET on an insurance client’s platform. You’ll be writing automated tests for Salesforce customizations while also handling manual test cycles when needed. ### What You'll Actually Be Doing You’ll spend most of your day designing test cases around Salesforce objects, flows and Apex code, then translating those into Java‑Selenium scripts that run in Copado pipelines. Expect to juggle both UI‑level Selenium suites and API‑level tests, track defects in RQM, and keep the GitHub repo tidy. The team moves fast in Agile sprints, so you’ll be triaging flaky tests, updating test data, and occasionally stepping in to verify a new integration manually. ### The Core Tech Stack The non‑negotiable skills are Java + Selenium for automation and a solid grasp of Salesforce testing concepts (validation rules, triggers, Lightning components). Copado is the CI/CD tool they rely on, so you need to know how to plug your Selenium suites into its pipelines. RQM for test management and GitHub for source control round out the daily toolkit. A background in Salesforce development (Apex/Lightning) isn’t mandatory but helps you write more meaningful test scenarios. ### Interview Expectations 1. *How would you design a Selenium framework to test a multi‑step Lightning flow that involves both UI clicks and server‑side Apex triggers?* – They want to see you break down the problem, decide where to use UI vs. API calls, and how you’d keep the framework modular for Copado integration. 2. *Explain a situation where a test that passed locally started failing in the CI pipeline. What steps would you take to diagnose and fix it?* – This probes your debugging process, familiarity with flaky Selenium tests, and how you handle environment‑specific issues in a regulated insurance context. ### Application Advice Tailor your resume to highlight “Salesforce Testing”, “Java Selenium Automation”, “Copado CI/CD”, and “RQM/GitHub” exactly as they appear in the JD. If you have any Apex or Lightning experience, surface it under a “Salesforce Development Background” bullet. Mention Agile sprint work and defect management to satisfy the ATS, and don’t forget to list your contract eligibility (GC & USC) right up front.

This contract gig is looking for a senior Dynamics 365 developer to keep a multi‑industry enterprise app humming. It’s fully remote but they explicitly want a U.S.‑based candidate, probably to match PST support windows. ### What You'll Actually Be Doing You’ll spend most of your time extending and customizing Dynamics 365 CE modules (Sales, Customer Service, Field Service) and stitching them together with Power Apps, Power Automate flows, and Power BI dashboards. Expect to write plugins, custom workflow activities, and JavaScript/TypeScript form scripts, then expose or consume REST APIs via Azure Functions, Logic Apps, or Service Bus. The team uses Azure DevOps for source control and CI/CD, so you’ll be building pipelines that package both Dynamics solutions and Power Platform assets for automated deployments. ### The Core Tech Stack The non‑negotiables are deep knowledge of Dynamics 365 CE (entity model, security, business rules) and the Power Platform stack—Dataverse, Power Apps, Power Automate, Power BI. On the code side you need solid C#/.NET experience, plus front‑end chops in JavaScript/TypeScript for form customizations. Azure integration is a daily reality: Functions, Logic Apps, Service Bus, and a fully fledged Azure DevOps CI/CD pipeline. If you can move between low‑code and full‑code without breaking a sweat, you’ll fit right in. ### Interview Expectations 1. *“Design a plugin that enforces a complex cross‑entity validation rule without degrading performance.”* They’ll look for you to talk about registering the plugin on the appropriate message pipeline, using pre‑operation stages, minimizing data calls, and possibly leveraging the ExecutionContext and Entity images. 2. *“Walk me through setting up an Azure DevOps pipeline that builds, validates, and deploys a Dynamics solution together with Power Platform components.”* Expect them to probe your understanding of solution layering, the Power Platform Build Tools, and how you’d handle environment variables, secrets, and automated testing. ### Application Advice Tailor your resume to mirror the JD verbatim: drop in “Microsoft Dynamics 365 (CE, Sales, Customer Service, Field Service)”, “Power Platform – Power Apps, Power Automate, Power BI”, “Dataverse”, “C#/.NET”, “JavaScript, TypeScript”, “Azure Functions, Logic Apps, Service Bus”, and “Azure DevOps / CI‑CD Pipelines”. Highlight the 8+ years of Dynamics work and 5+ years on Power Platform right up front, and list any of the preferred certifications (Power Platform Developer Associate, Azure Developer Associate, etc.). A short bullet that says “Built end‑to‑end CI/CD pipelines for Dynamics + Power Platform using Azure DevOps” will get past most ATS filters.

This is a senior‑level Salesforce developer role in Hartford, CT, looking for someone with a decade of hands‑on experience. The team needs a local who can walk in for an onsite interview and start contributing to existing implementations right away. ### What You'll Actually Be Doing You’ll be maintaining and extending a suite of custom Salesforce apps that support core business processes. Expect to dig into legacy Apex code, refactor bulky triggers, and build new Lightning components to replace outdated Visualforce pages. The job also involves integrating Salesforce with external ERP and marketing platforms via REST/SOAP APIs, and troubleshooting data‑quality issues that surface in the daily pipeline. ### The Core Tech Stack The non‑negotiables are Apex, Lightning Web Components, and a solid grasp of the Salesforce data model (objects, relationships, SOQL/SOSL). You’ll also need to be comfortable with declarative tools like Process Builder and Flow because the org relies on a hybrid of code and clicks. Integration experience (REST, SOAP, named credentials) is critical since the team is stitching Salesforce into several on‑prem systems. ### Interview Expectations 1. *“Explain how you would redesign a trigger‑heavy org to reduce CPU time limits.”* The interviewer wants to see you understand bulkification, async patterns (Future, Queueable, Batch) and how to move logic into declarative tools where possible. 2. *“Walk us through a recent integration you built: authentication method, error handling, and how you ensured data consistency.”* They’re probing for practical API experience, handling of callouts, and strategies like platform events or out‑of‑the‑box Salesforce Connect. ### Application Advice Tailor your resume to scream “Salesforce veteran.” Highlight 10+ years of Apex development, Lightning Web Components, and any large‑scale integration projects you’ve led. Sprinkle exact keywords from the JD—*Salesforce, Apex, Lightning, Visualforce, SOQL, REST/SOAP integration, trigger‑heavy, H1B, local*—in both the skills and experience sections so the ATS flags you as a perfect match. If you have any certifications (e.g., Platform Developer II), put them front‑and‑center.

The contract Data Architect role is based in Alpharetta, GA and sits at the intersection of business analytics and cloud data engineering. You’ll own the end‑to‑end data blueprint, from high‑level models down to the ETL/ELT pipelines that feed the warehouse. It’s a hands‑on gig that matters because the company’s reporting and decision‑making depend on the architecture you design. ### What You'll Actually Be Doing You’ll start by translating business KPIs into a logical data model, then materialize that model into physical tables optimized for Snowflake, Redshift, or Synapse. Day‑to‑day you’ll be sketching schema diagrams, writing dbt models or Informatica mappings, and wiring Airflow DAGs that move data from on‑prem sources to the cloud. Expect to troubleshoot pipeline bottlenecks, enforce governance policies, and fine‑tune storage costs while keeping security controls tight. ### The Core Tech Stack The non‑negotiables are a solid grasp of cloud data warehouses—Snowflake, AWS Redshift, or Azure Synapse—and the ability to design scalable ETL/ELT flows with dbt, Informatica, or Airflow. You must also be fluent in relational modeling (conceptual, logical, physical) because the team relies on you to keep the schema performant and future‑proof. Data governance, access control, and security aren’t afterthoughts; they’re baked into every pipeline you ship. ### Interview Expectations 1. *Design a Snowflake data model for a multi‑tenant SaaS product.* The interviewer will look for how you partition data, handle semi‑structured JSON, and minimize cross‑cluster traffic while preserving tenant isolation. 2. *Explain how you would orchestrate an incremental load from an on‑prem Oracle DB to Azure Synapse using Airflow.* They want to see your approach to change‑data‑capture, idempotent DAG design, and error‑handling strategies. ### Application Advice Tailor your resume to shout out the exact tools the JD lists: “Data architecture”, “ETL/ELT pipelines”, “Snowflake”, “AWS Redshift”, “Azure Synapse”, “dbt”, “Informatica”, “Airflow”, “data governance”, and “data modeling”. Highlight any end‑to‑end projects where you built a cloud warehouse from scratch and enforced security policies. Quantify impact—e.g., reduced pipeline latency by 30% or cut storage costs by 20%—to make the ATS and hiring manager see you as the right fit.