Find the matching job for you with ease

This contract is a senior Mainframe development role focused on AI/GenAI extensions. You’ll spend six months on‑site in Berkeley Heights, working on COBOL, JCL, VSAM, DB2 and CICS to keep critical batch and online systems running. ### What You'll Actually Be Doing You’ll take requirements, do impact analysis, then code, unit‑test and document batch programs and online transactions. Expect to troubleshoot production incidents, support integration and UAT, and participate in code and design reviews. The team looks to you to set standards and drive the technical direction. ### The Core Tech Stack The non‑negotiable skills are Enterprise COBOL, JCL, VSAM, DB2 and CICS. The client is modernizing legacy batch flows, so you need to know how to write efficient COBOL with proper file handling, manage CICS transaction boundaries, and tune DB2 queries. Anything less and you’ll be stuck in maintenance mode. ### Interview Expectations One likely question: “Describe how you would redesign a high‑volume CICS transaction to be idempotent while preserving performance.” They want to see your grasp of transaction semantics and scaling. Another: “Walk me through debugging a failing VSAM read in a COBOL program; which logs, dump utilities, and test harnesses would you use?” They’re probing depth of hands‑on troubleshooting. ### Application Advice Tailor your resume to mirror the JD: lead with “Mainframe Enterprise COBOL”, “JCL”, “VSAM”, “DB2”, “CICS”, and “Batch Processing”. Highlight any AI/GenAI integration work on mainframe if you have it. Quantify impact – e.g., “Reduced batch runtime by 20% using optimized JCL and DB2 indexing.” Use those exact terms to get past the ATS.

This is a senior‑level automation testing gig right in McLean, VA, demanding 8‑10 years of hands‑on work with Selenium, Cypress or Appium and a solid grasp of CI/CD tooling. It’s an onsite, full‑time role that will sit inside an enterprise‑scale Agile team, so you’ll be expected to ship reliable, maintainable test suites that can be run daily. ### What You'll Actually Be Doing You’ll spend most of your day building and extending a hybrid Selenium/Cypress/Appium framework, writing API tests in Postman or Rest‑Assured, and wiring everything into Jenkins pipelines that run inside Docker containers. Expect frequent triage of flaky tests, debugging of cross‑browser or mobile failures, and collaborating with developers to validate backend data via SQL queries. The role also expects you to mentor junior testers on best‑practice test design and keep the CI/CD flow humming. ### The Core Tech Stack The non‑negotiables are solid OOP fundamentals in Java, Python, C# or JavaScript and deep experience with Selenium WebDriver (or Cypress/Appium for the web‑mobile mix). You’ll need to be comfortable scripting CI pipelines in Jenkins, containerizing test runs with Docker, and version‑controlling everything in Git. The team relies on Cucumber for BDD, so you must know how to structure feature files and step definitions that stay readable as the suite scales. ### Interview Expectations 1. *Design a scalable test automation framework* – they’ll ask you to sketch how you’d support web, API and mobile tests in a single repo, handle environment config, and keep flaky tests under control. They’re looking for clear separation of concerns, reusable page objects, and a strategy for parallel execution in Docker. 2. *Integrate Selenium tests into Jenkins with Docker* – expect a deep dive on how you’d spin up a Docker image, run tests headlessly, capture logs, and fail the build on intermittent issues. The hiring manager wants to see you can troubleshoot container networking, manage test data, and implement retry logic without masking real bugs. ### Application Advice Tailor your résumé to mirror the JD’s buzzwords: Automation Testing, Selenium WebDriver, Cypress, Appium, Postman, Rest‑Assured, CI/CD, Jenkins, Docker, Git, Cucumber, Test Automation Framework Design, Agile/Scrum, SQL, OOP, and any of the listed languages (Java, Python, C#, JavaScript). Highlight concrete projects where you built end‑to‑end pipelines, reduced flaky test rates, and mentored teams. A concise bullet that reads “Designed a hybrid Selenium‑Cypress framework integrated with Jenkins/Docker, cutting regression run time by 30%” will speak directly to what they care about.

The role is a senior‑level AS400 developer gig at a wholesale‑retail outfit. You’ll be deep‑in the iSeries stack, writing and maintaining RPGLE code that actually moves merchandise. It’s not a hobby project – the team expects you to keep the production environment humming while adding new features. ### What You'll Actually Be Doing You’ll spend most of your day in Rational Developer or SEU, extending existing RPGLE modules and writing new ones that talk to SQL tables. Expect to translate functional specs into code, run unit tests, and push changes through a controlled release pipeline. When a batch job blows up at midnight, you’ll be the one digging into MQ triggers or CL programs to get the system back online. Collaboration is constant: you’ll sit with product owners to clarify requirements, review peers’ code, and document everything for the QA crew. ### The Core Tech Stack The non‑negotiables are RPG ILE, SQLRPGLE, and embedded SQL – the company’s whole retail back‑office runs on those. You must be comfortable with physical and logical files, service programs, and binding directories because the deployment model is tightly coupled to ILE concepts. Advanced SQL is also a must: stored procedures, cursor handling, and query tuning are daily chores. They throw in MQ and XML integration for messaging, so a working knowledge of those APIs will save you a lot of firefighting. ### Interview Expectations 1. *“Explain how you would refactor a monolithic RPG program that suffers from performance bottlenecks due to excessive embedded SQL calls.”* – They’re looking for your ability to separate data access layers, use prepared statements, and possibly move heavy logic into stored procedures or service programs. 2. *“Walk me through the steps you’d take to troubleshoot a failing MQ trigger that’s preventing a nightly batch from completing.”* – Expect you to discuss checking message queues, examining trigger definitions, reviewing error logs, and using diagnostic tools like WRKACTJOB. ### Application Advice Tailor your resume to hit the exact keywords they listed: **RPG, RPG ILE, SQLRPGLE, CLP/CLLE, embedded SQL, stored procedures, MQ, XML integration, iSeries Navigator**. Highlight any retail‑domain projects and quantify impact (e.g., reduced batch runtime by 20%). Put the 8+ years of AS400 experience front‑and‑center, and don’t forget to list the “nice‑to‑have” tools like X‑Analysis or ROBOT if you’ve touched them. A concise bullet that reads “Hybrid on‑site 3 days/week – Issaquah, WA” will also reassure the recruiter you’ve noted the work mode.

This is a senior‑level contract role focused on designing and running large hybrid AWS environments for a Fortune‑scale enterprise. You’ll be the go‑to person for everything from VPC networking to Infoblox DNS/IPAM, and the client expects you to be hands‑on while also steering architectural decisions. ### What You'll Actually Be Doing You’ll spend most of your day stitching together AWS accounts and on‑prem datacenters, writing Terraform and CloudFormation modules that spin up EC2, EKS, and RDS clusters. Expect frequent firefighting of DNS/DHCP issues in Infoblox, plus building CI/CD pipelines in Jenkins that push code to Lambda or ECS. The role also demands you draft disaster‑recovery runbooks, run failover drills, and keep the monitoring stack (CloudWatch, Prometheus, Grafana, Nagios) humming. ### The Core Tech Stack The non‑negotiables are deep AWS architecture experience (VPC, IAM, multi‑account strategy) and a solid grasp of Infoblox DNS/DHCP/IPAM. You must be fluent in Terraform and CloudFormation because the client lives by IaC. Kubernetes/EKS and Docker are required for container workloads, and you’ll need to automate everything with Ansible, Python, or PowerShell. On the on‑prem side, VMware vSphere/vSAN and classic Windows/Linux server admin are still in play. ### Interview Expectations 1. *“Walk me through how you would design a multi‑account AWS landing zone that integrates with an existing Infoblox DNS infrastructure.”* – They’re looking for your ability to map AWS Route 53 to Infoblox, handle cross‑account trust, and automate the whole thing with Terraform. 2. *“Explain a recent disaster‑recovery scenario you owned. What metrics did you monitor, and how did you validate failover?”* – Expect them to probe your hands‑on testing process, use of CloudWatch alarms, and how you document the runbook. ### Application Advice Tailor your résumé to echo the exact terms the JD repeats: “Hybrid Infrastructure,” “Terraform,” “CloudFormation,” “Infoblox,” “AWS Solutions Architect,” and “VMware VCP.” Highlight any projects where you built end‑to‑end DNS/IPAM solutions or ran multi‑region failover drills. If you have certifications (AWS SA, VCP, CCNA), put them front‑and‑center. A concise bullet that says “Designed and automated hybrid AWS‑on‑prem network using Terraform, Infoblox, and VMware” will get past most ATS filters.

This role is a senior QA position that expects you to own both manual and automated testing for Java, Python, and .NET applications. It’s targeted at candidates who can work on‑site three days a week in one of three US cities and have an H‑1B or EAD visa. The focus is on delivering reliable releases for a product line that still relies heavily on legacy code. ### What You'll Actually Be Doing You’ll spend most of your day writing and maintaining test suites for web and desktop apps, toggling between Selenium‑based UI scripts and API‑level checks written in Java or Python. Expect to partner with developers to debug flaky tests, review pull requests for testability, and keep the test environment in sync with frequent releases. Because the team is hybrid, you’ll also need to coordinate test runs and defect triage during the on‑site days, acting as the go‑to QA voice in sprint planning. ### The Core Tech Stack The non‑negotiable skills are solid Java and Python coding ability plus experience testing .NET services—think NUnit, MSTest, or xUnit alongside REST‑assured or Postman for API validation. They need you to automate across UI and service layers, so familiarity with Selenium/WebDriver, CI pipelines (Jenkins or Azure DevOps), and test‑data management is a must. The stack reflects a mixed‑technology product, so they want someone who can bridge the gap between legacy .NET components and newer micro‑services written in Java/Python. ### Interview Expectations 1. *“Explain how you would design a cross‑language test framework that can run the same test logic against a Java backend and a .NET backend.”* They’re looking for your ability to abstract test steps, use language‑agnostic tools (like Cucumber or Robot Framework), and manage shared test data. 2. *“A flaky Selenium test is failing intermittently on the CI server but passes locally. Walk us through your debugging process.”* They want to see systematic troubleshooting: environment parity, explicit waits, screenshot analysis, and possibly refactoring the locator strategy. ### Application Advice Tailor your résumé to scream “10+ years QA, Java, Python, .NET, Selenium, CI/CD”. Put the exact city you’re applying for (Tulsa, OK; Marietta, GA; or Reston, VA) right under the location line, and highlight your H‑1B/EAD status early so the recruiter doesn’t have to hunt for it. Use keywords like *Hybrid*, *manual testing*, *automation*, *test framework*, *API testing*, and *test data management* throughout the experience bullets to get past the ATS.

The team needs a Saviynt Architect who can take ownership of the entire IGA platform—design, build, and keep it running for a six‑month sprint. It’s a hands‑on role, not just a diagram‑drawer, and you’ll be the go‑to person for any L3/L4 escalations. ### What You'll Actually Be Doing You’ll lead the Saviynt architecture from concept to production, translating business access policies into concrete RBAC and SoD models. Day‑to‑day you’ll troubleshoot provisioning failures, debug custom connectors (often written in BeanShell or JavaScript), and keep the certification campaigns on schedule. Expect a lot of cross‑team coordination: you’ll be fielding tickets, doing root‑cause analysis, and reviewing code to make sure security compliance never slips. ### The Core Tech Stack The non‑negotiable skill set is deep Saviynt IGA expertise—knowing the platform’s data model, lifecycle hooks, and how to extend it with custom REST APIs. You also need solid IAM fundamentals (JML processes, access governance) and be comfortable scripting in BeanShell/JavaScript for connector development. The company relies on you to stitch together enterprise integrations, so experience with Java‑based connectors and API orchestration is a must. ### Interview Expectations 1. *“Walk me through how you’d design a custom connector for a legacy HR system that only exposes SOAP endpoints.”* They’re looking for your ability to map SOAP operations to Saviynt provisioning flows, handle error handling, and secure credential storage. 2. *“Explain a time you resolved a provisioning dead‑lock during a certification campaign. What logs did you examine and how did you fix it?”* The hiring manager wants proof you can dig into Saviynt audit logs, identify race conditions, and apply a quick patch while preserving audit integrity. ### Application Advice Tailor your resume to mirror the exact terminology used in the posting: **Saviynt IGA Architecture**, **RBAC/SoD Controls**, **Custom Connectors**, **BeanShell**, **JavaScript**, **Provisioning**, **Certification**, **L3/L4 Support**, and **Incident Management**. Highlight any end‑to‑end Saviynt implementations you’ve led, especially where you built or debugged connectors. A short bullet that quantifies impact—e.g., “Reduced provisioning failure rate by 30% across 50+ applications”—will help you cut through the ATS and catch the recruiter’s eye.

This is a junior‑level contract gig building Angular front‑ends for enterprise apps. It's a W2/C2C role based out of Fremont, CA, so you'll likely be working onsite with the rest of the engineering team. ### What You'll Actually Be Doing You’ll spend most of your day turning UI/UX mockups into reusable Angular components, wiring them up to REST endpoints, and making sure the app stays responsive across browsers. Expect to write a lot of TypeScript services, manage state with RxJS, and participate in daily stand‑ups and sprint planning. Because it’s an enterprise codebase, you’ll also be debugging integration quirks and polishing edge‑case UI bugs that pop up during QA. ### The Core Tech Stack The stack is pure front‑end: Angular (latest stable), TypeScript, vanilla JavaScript, HTML5/CSS3, and a suite of RESTful APIs you’ll consume. They run on an Agile/Scrum cadence, so you’ll need to be comfortable with sprint cycles, story points, and quick iterative deliveries. Mastery of Angular’s component lifecycle and change‑detection strategies is non‑negotiable – the team relies on you to keep bundle sizes low and performance snappy. ### Interview Expectations 1. *Explain Angular’s change‑detection mechanisms and when you’d switch a component to OnPush.* The interviewer wants to see if you understand how Angular decides to re‑render and whether you can proactively optimise rendering for large data sets. 2. *Describe a systematic approach to finding and fixing memory leaks in a large Angular SPA.* They’re probing your debugging chops – expect to talk about unsubscribing from observables, using the Chrome profiler, and avoiding retained references in services. ### Application Advice Tailor your resume to echo the exact terms from the posting: “Angular (Expert)”, “TypeScript”, “JavaScript”, “HTML & CSS”, “Front‑End/UI Development”, “REST API Integration”, and “Agile/Scrum”. Highlight any enterprise‑scale Angular projects you’ve shipped, and quantify impact (e.g., reduced page load by X%). If you’ve worked on W2 or C2C contracts before, note that too – it signals you’re ready for the hiring model. Keep the formatting clean so the ATS can pick up those keywords quickly.

The role is a senior‑level Java backend gig focused on building and maintaining high‑throughput microservices. You’ll be on an engineering team that cares about clean architecture, performance, and reliability – not just shipping code. ### What You'll Actually Be Doing You’ll spend most of your day designing Spring Boot services, wiring them into a Kafka‑driven event pipeline, and making sure they play nicely with Oracle and Cassandra backends. Expect frequent design reviews where you argue over trade‑offs like synchronous vs async APIs, and you’ll be on‑call for performance tuning using ELK and Prometheus dashboards. Collaboration isn’t optional; you’ll pair with front‑end, QA, and ops folks to ship features end‑to‑end. ### The Core Tech Stack The non‑negotiable skills are Java 8+ (especially concurrency primitives), Spring Boot with Spring Data JPA/Hibernate, and a solid grasp of microservices patterns (service discovery, circuit breaking, eventual consistency). The team leans heavily on Apache Kafka for messaging and ELK for observability, so you need to be comfortable instrumenting logs and metrics. Knowing Oracle and Cassandra schema design is a must because you’ll be juggling relational and wide‑column stores in the same transaction flow. ### Interview Expectations 1. *Design a resilient order‑processing pipeline using Spring Boot and Kafka.* The interviewer will look for how you handle message ordering, duplicate suppression, and back‑pressure – expect follow‑up on idempotency and transactional guarantees. 2. *Explain the differences between JPA’s first‑level cache and Redis caching, and when you’d combine them.* They want to see if you understand cache‑aside patterns, cache invalidation, and the performance impact on read‑heavy services. ### Application Advice Tailor your resume to echo the exact terminology from the JD: “Spring Boot microservices”, “Kafka”, “ELK Stack”, “Oracle & Cassandra”, “JUnit/Mockito testing”, and “Git/SonarQube CI”. Highlight any Azure or Kubernetes exposure, even if it’s on‑prem, because “Cloud experience (Azure) – Nice to Have” shows you’re a plus. Quantify impact (e.g., reduced API latency by 30% through async processing) to satisfy the hiring manager’s focus on performance and reliability.