Find the matching job for you with ease

Senior Test Lead for a Houston‑based insurance team. The role is purely local—no remote or relocation options—so you’ll be in the office every day, steering QA for annuities products. ### What You'll Actually Be Doing You’ll own the end‑to‑end testing strategy for fixed, variable and indexed annuities. That means writing test plans, coordinating manual and automated suites, and making sure releases meet strict regulatory timelines. You’ll also act as the bridge between product owners, developers, and external auditors, translating business rules into test cases and reporting defects with enough detail to keep compliance happy. ### The Core Tech Stack The non‑negotiable knowledge is the annuities domain—understanding how life insurance policies translate into cash‑flow calculations, surrender charges, and tax treatment. On the tooling side, you’ll need solid experience with test management platforms (e.g., qTest, Zephyr) and a strong grasp of automated frameworks like Selenium or RestAssured because the team is pushing for more CI/CD coverage. Stakeholder management is another must; you’ll be presenting test metrics to senior leadership and negotiating scope with developers. ### Interview Expectations 1. *“Walk me through how you’d design a test strategy for a new indexed annuity product that must comply with NAIC regulations.”* They want to see you break the problem into risk‑based test design, coverage of edge‑case scenarios (e.g., market downturns), and how you’d embed regulatory checkpoints into automated pipelines. 2. *“Explain a time you had to convince a skeptical developer to adopt a QA process you introduced.”* The hiring manager is probing your stakeholder‑management chops—look for a concrete example, metrics of improvement, and how you framed the change in business value terms. ### Application Advice Tailor your resume to hammer the exact keywords the JD repeats: **Annuities Domain**, **Life Insurance**, **Fixed/Variable/Indexed Annuities**, **Test Leadership**, **QA Strategy**, and **Stakeholder Management**. Put those phrases in your professional summary and bullet points describing past projects. If you have experience with specific test tools (qTest, Selenium, RestAssured), list them prominently; the ATS will likely be scanning for both domain and tooling terms. Also, note that the role is local‑only—make sure your address or “Houston, TX” appears somewhere on the resume to clear the location filter.

The role is a senior‑level SAP FICO consulting gig that also expects you to sprinkle AI know‑how into finance processes. It’s a contract position, so you’ll be paid hourly and expected to hit the ground running on large‑scale finance implementations. ### What You'll Actually Be Doing You’ll spend most of your time designing, configuring, and testing core FI modules (GL, AP, AR) for new roll‑outs. The client wants you to lead 2‑3 full‑cycle implementations, so you’ll own requirement workshops, map business processes, and translate them into SAP configuration. A smaller but critical piece is the RAR (Revenue Accounting & Reporting) component – you’ll need to set up tax‑aware revenue recognition and ensure it meshes with the core FI data. Expect heavy collaboration with business analysts and the AI team to prototype predictive cash‑flow models that sit on top of the FI data. ### The Core Tech Stack The non‑negotiables are deep SAP FI expertise (5‑10 years) and hands‑on experience with SAP FICO functional design. You must also have a solid grasp of RAR (1‑2 years) because the client is moving toward ASC 606 compliance. On the AI side they aren’t asking for a PhD – just enough experience to talk about how you’d feed FI data into a machine‑learning pipeline for forecasting. Knowing OData services, SAP BW/4HANA, or SAP Analytics Cloud will give you a leg up when the AI folks start pulling data. ### Interview Expectations 1. *“Walk me through a complete FI module implementation you led – from blueprint to go‑live. What were the biggest configuration pitfalls and how did you resolve them?”* They’re looking for concrete numbers, change‑request handling, and how you mitigated data‑migration issues. 2. *“Explain how you would integrate SAP RAR with FI to support ASC 606 revenue recognition, and how you might expose that data to an AI model for cash‑flow prediction.”* They want to see you connect finance compliance with data‑science pipelines, not just recite module names. ### Application Advice Tailor your resume to scream “SAP FI, SAP FICO, RAR, 12 + years” right at the top – those exact keywords will get you past the ATS. Highlight any end‑to‑end implementation you owned, especially if you mention the number of full roll‑outs (2‑3). Add a bullet that shows you collaborated with data‑science or AI teams, even if it was just “provided FI data feeds for predictive models”. Keep the format clean, use the same terminology the JD uses (FI, FICO, RAR, configuration), and drop the email address in the cover note so the recruiter can match you quickly.

They're looking for a hands‑on blockchain engineer who knows Ripple's XRPL and can ship stablecoin features for a fintech client in Phoenix. The role is hybrid, so you'll be in the office three days a week and remote the rest. ### What You'll Actually Be Doing You'll build and maintain backend microservices that talk to the XRPL ledger, wrap RippleNet APIs, and expose REST/GraphQL endpoints for internal products. Expect to design token‑issuance pipelines, handle mint‑and‑redeem flows, and integrate KYC/AML checks. Debugging transaction signing, wallet key management, and scaling the ledger traffic are daily pain points. ### The Core Tech Stack The stack revolves around Ripple XRPL (ledger, RippleNet, SDKs) plus a server language you’re comfortable with—Java, Python, or Go. Those services run in containers behind a cloud provider (AWS/Azure/GCP) and follow a micro‑services architecture with Kafka or similar messaging. Cryptography primitives for wallet generation and transaction signing are non‑negotiable, and you’ll need solid security chops to keep the ledger tamper‑proof. ### Interview Expectations 1. *How does XRPL achieve consensus without mining, and what would you do if the network split into two partitions?* They want to see you understand the UNL‑based consensus, its fault tolerance, and how you’d handle fork resolution or fallback logic. 2. *Design a secure end‑to‑end stablecoin minting flow that satisfies KYC/AML, includes wallet key storage, and can scale to thousands of transactions per second.* Look for a clear separation of duties, encrypted key vaults, audit trails, and async processing to keep latency low. ### Application Advice Tailor your resume to mirror the JD: sprinkle **Blockchain Development**, **Ripple XRPL**, **Stablecoin**, **Token Issuance**, **Microservices**, **AWS/Azure/GCP**, **KYC/AML**, **Cryptography**, and **Wallet** throughout your experience bullets. Highlight any open‑source blockchain contributions and explicitly state your US work authorization (Citizen, Green Card, etc.). Mention the hybrid model and your willingness to be onsite three days a week to satisfy the location filter.

The role is a hands‑on Project Manager for a NetSuite re‑implementation that lives entirely in a remote setting, syncing EST/CST teams across the US and offshore dev groups. It’s a nine‑month stretch that will test your ability to keep a complex ERP rollout on track while juggling multiple stakeholders. ### What You'll Actually Be Doing You’ll own the end‑to‑end schedule: drafting the master plan, flagging risks, and driving daily stand‑ups with finance, business owners, the implementation partner, and offshore developers. Expect to spend a lot of time in status calls, updating Jira or Smartsheet, and translating technical blockers into clear action items for non‑technical leaders. When something stalls—say a custom script fails in the sandbox—you’ll be the one escalating, re‑prioritizing, and making sure governance checkpoints stay intact. ### The Core Tech Stack The tech side isn’t about coding; it’s about NetSuite’s configuration modules, SuiteTalk integrations, and the custom scripts that offshore teams will push. You need to speak the language of ERP workflows, understand how a GL roll‑forward works, and be comfortable reading SuiteScript error logs enough to ask the right questions. The company needs you to bridge that gap—turning a business requirement like “automated revenue recognition” into a concrete NetSuite configuration and a set of test cases. ### Interview Expectations 1. *“Walk me through how you’d handle a critical integration failure two days before go‑live.”* The interviewer wants to see your crisis‑management playbook: rapid root‑cause triage, stakeholder communication cadence, and a rollback or hot‑fix plan that minimizes downtime. 2. *“Explain a time you coordinated between on‑shore business owners and an offshore dev team with different time zones.”* They’re probing your ability to align EST/CST schedules with offshore hours, set clear hand‑off points, and keep documentation airtight so nothing gets lost in translation. ### Application Advice Tailor your resume to shout out “NetSuite implementation,” “ERP project management,” and “offshore team coordination.” Mirror the JD language: include “project plan,” “milestones,” “risk management,” and “stakeholder communication.” If you have experience with SuiteTalk or SuiteScript, list those explicitly. A concise bullet like “Managed 12‑month NetSuite re‑implementation across finance, sales, and offshore dev teams, delivering on‑time within budget” will hit the ATS hard.

This is a senior PLM program manager role focused on driving large‑scale transformation initiatives for a PLM Teamcenter environment. It’s a hands‑on PMO position that sits on‑site in San Jose, coordinating across engineering, IT and vendors. ### What You'll Actually Be Doing You’ll own the end‑to‑end PMO rhythm: building and constantly updating project plans, RAID logs, and KPI dashboards. Expect to run steering committee decks, keep the schedule tight, and chase dependencies across business users, engineering squads, IT ops, and external vendors. The day will be a mix of status reporting, risk mitigation workshops, and making sure every rollout – whether a migration, upgrade, or new implementation – follows the governance checklist. ### The Core Tech Stack The non‑negotiable skill is deep experience with Teamcenter (or a comparable PLM suite). You need to speak the language of Item & BOM management, change control, PDM, and CAD integrations because the team will be wiring those processes into the new system. Beyond the PLM tool, you’ll be expected to use classic PM tooling – think MS Project, JIRA/Confluence, or similar – to drive schedules, risk registers, and KPI tracking. ### Interview Expectations 1. *“Walk me through how you’d set up a RAID log for a multi‑phase PLM migration and how you’d keep stakeholders informed of high‑impact risks.”* – They want to see you can translate abstract risk concepts into concrete artifacts and communication cadences. 2. *“Explain the difference between Item Management and BOM Management in Teamcenter, and how a change in one propagates through the other during a product launch.”* – This tests whether you truly understand the PLM domain, not just project mechanics. ### Application Advice Tailor your resume to echo the exact terminology from the JD: “PLM‑Teamcenter,” “large‑scale transformation,” “RAID logs,” “KPI/governance metrics,” and “cross‑functional stakeholder management.” Highlight any end‑to‑end PLM rollout you led, quantify scope (e.g., “managed migration of 5,000+ CAD files”), and list certifications like MP if you have them. A concise bullet that reads “Drove PMO for enterprise PLM implementation, delivering on‑time, on‑budget, with 95% risk mitigation success” will get past most ATS filters.

This is a senior ETL gig centered on building and maintaining Informatica pipelines for a client based in Phoenix. They need a consultant who can walk into the office tomorrow and start delivering real data‑integration value. ### What You'll Actually Be Doing You’ll spend most of your day in PowerCenter Designer and Workflow Manager, crafting mappings that pull data from source systems, apply business rules, and load into a data warehouse. Expect to troubleshoot broken workflows, tune performance for large volume loads, and collaborate with data architects to ensure the warehouse schema aligns with the ETL design. The role is hands‑on from day one – you’ll be debugging session logs, fixing deadlocks, and documenting the end‑to‑end flow for the team. ### The Core Tech Stack The non‑negotiable skill set is deep expertise in Informatica PowerCenter (mappings, transformations, workflows) plus solid SQL/PLSQL for source/target manipulation. They also expect you to know the underlying relational platform (Oracle, SQL Server, or similar) and data‑warehousing concepts like slowly changing dimensions, fact/lookup design, and push‑down optimization. If you’ve automated deployments with Informatica’s command‑line tools or used version control for mappings, you’ll be ahead of the curve. ### Interview Expectations 1. *“Walk me through how you’d implement a Type 2 slowly changing dimension in Informatica and why you’d pick that approach over Type 1.”* – They’re probing your grasp of CDC patterns and your ability to justify design trade‑offs. 2. *“A mapping that processes 50 million rows is failing with ‘Out of memory’ errors. How do you diagnose and resolve it?”* – They want to see your systematic troubleshooting: checking session cache settings, partitioning strategy, push‑down vs. in‑database processing, and hardware constraints. ### Application Advice Tailor your resume to scream “10+ years of hands‑on Informatica” right at the top. Sprinkle keywords like *Informatica PowerCenter, ETL development, performance tuning, SQL/PLSQL, data‑warehouse, SCD, workflow monitoring, on‑site consultant, Phoenix* throughout the experience section. Highlight any past contracts where you hit production deadlines and mention that you’re local and can meet face‑to‑face interview requirements. A concise cover note that references the exact job title and location will help you get past the ATS and land the interview.

The gig is a contract Node.js backend role based in Dallas with four days a week on‑site. It’s a straightforward backend‑focused position—no client‑facing calls, just code that powers services. ### What You'll Actually Be Doing You’ll be writing and maintaining RESTful services in Node.js, mostly using Express or a similar framework. Expect to own the full API lifecycle: design endpoints, handle data validation, integrate with databases (likely PostgreSQL or MongoDB), and write unit/integration tests. The team runs a tight CI/CD pipeline, so you’ll be pushing small, frequent releases and troubleshooting production incidents when they arise. ### The Core Tech Stack The must‑have is solid Node.js/JavaScript chops; the stack revolves around Express (or Fastify), a relational or document DB, and a cloud provider like AWS for hosting. They’ll also expect you to be comfortable with Docker containers because the services are packaged that way for deployment. If you’ve touched TypeScript, that’s a big plus—it makes the codebase easier to maintain at scale. ### Interview Expectations 1. *“Walk me through how you’d design a rate‑limited API endpoint in Node.js.”* They’re looking for your ability to use middleware, Redis or in‑memory stores, and proper error handling to prevent abuse. 2. *“Explain the difference between process.nextTick and setImmediate, and when you’d choose one over the other.”* This tests depth of event‑loop knowledge—candidates who can articulate the timing nuances and performance impact will stand out. ### Application Advice Tailor your resume to shout out the exact buzzwords they care about: **Node.js**, **Express**, **REST APIs**, **Docker**, **AWS**, **PostgreSQL/MongoDB**, and **TypeScript** if you have it. Highlight any contract work where you shipped production‑grade services on a CI/CD pipeline, and be sure to note “on‑site” availability for Dallas. A brief line about “4‑day on‑site schedule” can help the ATS match the location requirement.

The role is a senior AI/ML Engineer gig in Indianapolis, geared toward someone with a decade of hands‑on experience. It’s a contract position, so you’ll be expected to hit the ground running and deliver production‑ready models without a lot of onboarding fluff. ### What You'll Actually Be Doing You’ll spend most of your day designing, training, and deploying machine‑learning pipelines that solve concrete business problems. Expect to clean noisy data, experiment with feature engineering, and iterate on model architectures while keeping latency and scalability in mind. The contract nature means you’ll also need to document your work clearly and hand it off to the client’s team at the end of the engagement. ### The Core Tech Stack The stack is all about Python‑centric ML: you’ll be deep in NumPy, pandas, and scikit‑learn for classic models, and TensorFlow or PyTorch for deep learning work. The client also runs models in a cloud environment (likely AWS or Azure), so containerizing with Docker and orchestrating with Kubernetes is a must. They care about reproducibility, so version control with Git and experiment tracking (MLflow, Weights & Biases) are non‑negotiable. ### Interview Expectations 1. *“Walk me through how you’d handle concept drift in a production model that’s seeing a gradual shift in input data distribution.”* They want to see you talk about monitoring pipelines, statistical tests, and a plan for periodic retraining or online learning. 2. *“Explain the trade‑offs between using a large transformer model versus a distilled version for real‑time inference.”* Expect them to probe your understanding of latency, GPU memory constraints, and how distillation can keep accuracy while cutting cost. ### Application Advice Tailor your resume to highlight the exact buzzwords the JD drops: “AI/ML Engineer,” “10+ years,” “Python,” “TensorFlow/PyTorch,” “Docker,” “Kubernetes,” and “AWS/Azure.” Put those terms in your experience bullet points and in a skills summary so the ATS flags you. Also, mention any contract work you’ve done where you delivered end‑to‑end pipelines, because that signals you can thrive in a short‑term, results‑focused setting.