Find the matching job for you with ease

The role is a straight‑forward Java development position based in the US. It’s a full‑time gig that expects you to ship production‑grade code for the company’s core products. If you enjoy digging into legacy code and building scalable services, this could be a solid next step. ### What You'll Actually Be Doing You’ll spend most of your day writing, debugging, and unit‑testing Java services that power the business logic. Expect regular code reviews, occasional pair‑programming, and a need to integrate with existing REST APIs and databases. The team runs sprints, so you’ll also be estimating tickets, attending stand‑ups, and helping triage production incidents when they arise. ### The Core Tech Stack The stack revolves around Java 11+ with Spring Boot for micro‑services, Maven or Gradle for builds, and a relational DB like PostgreSQL or MySQL. Knowing how to containerize with Docker and deploy to a cloud environment (AWS/GCP) is essential because the code you write ends up in CI/CD pipelines that ship to production multiple times a day. ### Interview Expectations 1. *Explain how you would design a high‑throughput order processing service in Java.* The interviewer wants to see your grasp of concurrency, thread‑pool sizing, and idempotent design—key for keeping the system reliable under load. 2. *Walk through a recent performance bottleneck you fixed.* They’re probing whether you can profile JVM metrics, use tools like JVisualVM or YourKit, and apply optimizations such as query indexing or reducing GC pressure. ### Application Advice Tailor your resume to highlight “Java”, “Spring Boot”, “REST APIs”, “Docker”, and “AWS/GCP” – those exact phrases appear in the JD and will get past the ATS. Quantify impact (e.g., “Reduced API latency by 30%”) and list any experience with CI/CD pipelines, as the team relies heavily on automated deployments. A concise cover note that mentions your comfort with full‑stack Java micro‑services will make you stand out.

The role is a senior‑level contract gig building and maintaining Seismic LiveDocs templates for a sales‑enablement team. If you enjoy turning messy business rules into clean, performant content generators, this is a solid niche to own. ### What You'll Actually Be Doing You’ll lead the end‑to‑end design of LiveDocs solutions: take pricing matrices, legal clauses, or product configs, map them to Seismic’s scripting language, and stitch the output into a seamless, on‑demand document. Expect daily debugging of data‑binding failures, performance bottlenecks, and integration quirks with Salesforce or Snowflake. You’ll also mentor junior content engineers and keep the documentation shipshape. ### The Core Tech Stack The non‑negotiable skills are deep experience with Seismic’s LiveDocs engine and solid JavaScript (or comparable scripting) chops. The company relies on you to write custom loops, conditional logic, and data transformations that scale across thousands of sales reps, so you must understand both the platform’s API surface and the underlying data models. Familiarity with CRM/CPQ integrations (especially Salesforce) is essential because the templates pull live data at runtime. ### Interview Expectations 1. *“Walk me through how you’d optimize a LiveDocs template that’s pulling 10 k rows from a Salesforce report and timing out.”* They want to see your approach to pagination, selective field retrieval, and caching inside Seismic’s data connectors. 2. *“Explain a scenario where you had to refactor nested conditional logic in a LiveDocs script to improve maintainability.”* Expect them to probe for use of functions, modular templates, and version‑control best practices. ### Application Advice Tailor your resume to surface every keyword the JD mentions: **Seismic LiveDocs**, **JavaScript**, **Salesforce integration**, **data connectors**, **template optimization**, and **performance tuning**. Highlight any contract work where you led design or mentored junior developers, and quantify impact (e.g., reduced document generation time by 40%). A concise “Senior LiveDocs Engineer” headline and a bullet list of specific LiveDocs projects will help you pass the ATS and catch the hiring manager’s eye.

The gig is a short‑term Cloud Architect contract based in Austin, Texas. You’ll be the go‑to person for designing, migrating, and optimizing cloud workloads for a client that wants solid, production‑grade solutions without a permanent hire. ### What You'll Actually Be Doing You’ll spend most of your time mapping existing on‑prem services to a cloud provider (likely AWS or Azure), sketching out network topologies, and writing infrastructure‑as‑code templates. Expect to dive into cost‑analysis, security hardening, and performance tuning while juggling stakeholder meetings that want quick wins and a clear roadmap for long‑term scalability. ### The Core Tech Stack The role revolves around deep knowledge of cloud platforms—AWS (EC2, VPC, RDS, CloudFormation) or Azure (VMs, VNets, ARM templates). You’ll also need solid experience with IaC tools (Terraform is a must), container orchestration (Kubernetes), and a good grasp of CI/CD pipelines. The client is looking for someone who can not only spin up resources but also embed governance and cost‑control policies from day one. ### Interview Expectations 1. *“Walk me through how you’d design a multi‑region, highly available architecture for a SaaS app handling 10k RPS.”* – They want to see you break down latency, data replication, failover, and cost trade‑offs, not just list services. 2. *“Explain a situation where you had to refactor a monolithic app into microservices on the cloud. What were the biggest pitfalls?”* – The hiring manager is probing your practical migration experience, especially around data consistency, network latency, and operational monitoring. ### Application Advice Tailor your resume to shout out “Cloud Architecture”, “AWS/Azure”, “Terraform”, “Kubernetes”, and “cost optimization”. Highlight any contracts where you delivered end‑to‑end cloud migrations within tight timelines—those keywords will get past the ATS. If you’ve worked on projects within the Austin metro area, surface that detail; the client explicitly wants local talent.

This contract role is a hands‑on robotics debugging gig at a company in Cupertino. You won’t be designing new arms from scratch; you’ll be the go‑to person for getting existing hardware and software to work reliably. ### What You'll Actually Be Doing You’ll spend most of your day glued to a robotic arm that’s already built, running diagnostics, swapping out power modules, and chasing down flaky ROS nodes. Expect to assemble components, run QA test rigs that move the arm from point A to point B, and write or tweak Python scripts that surface sensor data. When something crashes, you’ll trace the fault through firmware, drivers, and the control software, then hand a clean, documented fix back to the engineering team. ### The Core Tech Stack The must‑know stack is ROS on top of a Linux‑based controller, with heavy Python scripting for test automation. You also need solid hardware troubleshooting chops – power supplies, motor drivers, and sensor wiring are all fair game. The company expects you to understand the mechanical kinematics of the arm enough to spot a mis‑aligned joint without opening the CAD model. ### Interview Expectations 1. *“Walk me through how you would debug a ROS node that intermittently drops messages during a trajectory execution.”* – They’re looking for a systematic approach: checking topic bandwidth, verifying real‑time constraints, using `rqt_graph`, and maybe adding watchdog timers. 2. *“Explain how you would isolate a power‑supply fault that causes the arm to stall only under load.”* – Expect them to probe your hardware intuition: measuring voltage sag, inspecting decoupling caps, and confirming firmware limits. ### Application Advice Tailor your resume to shout out every keyword the JD uses: **debugging**, **ROS**, **Python scripting**, **hardware troubleshooting**, and **robotic arm assembly**. Highlight any contract or research projects where you took a pre‑built system and got it running end‑to‑end, especially if you documented test scripts or QA procedures. A brief bullet that says “Performed QA and debug of ROS‑based robotic arms in a production environment” will get past most ATS filters.

Senior Business Analyst role focused on metadata, data governance, and stakeholder‑driven analytics. It’s a remote‑first gig for anyone based in Texas, so you’ll be collaborating with Austin‑based teams while never leaving your home office. ### What You'll Actually Be Doing You’ll spend most of your day pulling requirements from business owners, translating them into data models, and mapping lineage across multiple data warehouses. Expect to write complex SQL queries to validate data quality, create glossaries, and surface gaps in the data catalog. You’ll also own the communication loop—running workshops, delivering status reports, and coaching less‑experienced analysts on data literacy. ### The Core Tech Stack The non‑negotiables are strong SQL chops and a deep understanding of metadata management tools like Informatica EDC/Axon. The team relies on those platforms to enforce data governance policies, so you need to know how to trace lineage, define data quality rules, and document business vocabularies. A background in BI/DW (think Snowflake, Redshift, or similar) and experience with healthcare data standards (HHS) will make your day easier because the domain is heavily regulated. ### Interview Expectations 1. *“Walk me through how you’d design a data lineage diagram for a new source system feeding an existing data warehouse.”* They’re looking for a step‑by‑step on source profiling, mapping to business entities, and how you’d capture that in EDC/Axon. 2. *“Give an example of a tricky SQL performance issue you solved in a reporting environment.”* Expect them to probe your indexing strategy, query refactoring, and how you validated results with business users. ### Application Advice Tailor your resume to mirror the exact phrasing used in the posting: “metadata analysis,” “data lineage,” “SQL,” “stakeholder management,” and “data governance.” Highlight any Informatica EDC/Axon projects and, if you’ve touched healthcare data, surface that prominently. Drop the buzzwords—use concrete metrics (e.g., reduced data‑quality incidents by 30%). A short cover note that mentions you’re Texas‑based and comfortable with remote collaboration will also help you pass the ATS.

The gig is a short‑term contract for a JavaScript engineer who can hit the ground running with modern ES6+ code, React front‑ends and Node back‑ends. It’s a Phoenix‑based role, so you’ll be in the office working with a small Agile team that ships REST‑ful services. ### What You'll Actually Be Doing You’ll spend most of your day extending existing React components, wiring them to Node.js micro‑services, and making sure the APIs stay contract‑compatible. Expect a lot of debugging in the browser console, writing unit tests with Jest, and pushing small increments through a CI pipeline that runs on every pull request. The team runs two‑week sprints, so you’ll be in daily stand‑ups, sprint planning, and retro meetings, constantly iterating on feedback. ### The Core Tech Stack The stack is pure JavaScript: ES6+ syntax everywhere, React for the UI layer, and Node.js (Express or similar) for the server side. They rely heavily on REST APIs, so you need to be comfortable designing endpoints, handling authentication, and dealing with JSON payloads. Agile isn’t just a buzzword here – they expect you to own your tickets, estimate story points, and ship code that can be rolled back if a regression shows up. ### Interview Expectations One likely question: *“Walk me through how you’d refactor a large, monolithic React component into smaller, reusable pieces without breaking existing functionality.”* They’re watching for your ability to think in terms of component composition, state lifting, and test coverage. Another tough one: *“Explain how you’d handle rate‑limiting and error handling for a Node.js service that’s called by multiple front‑end clients.”* Expect them to probe your knowledge of middleware, exponential back‑off, and proper HTTP status codes. ### Application Advice Tailor your resume to shout out the exact keywords the posting uses: JavaScript (ES6+), React.js, Node.js, REST APIs, and Agile methodology. Highlight any contract work where you delivered end‑to‑end features in a two‑week sprint cadence. If you have measurable impact (e.g., reduced API latency by 30% or cut front‑end bundle size), put those numbers front and center – the ATS will love the match and the hiring manager will see you’ve done the real‑world work they need.

This SDET role is a straight‑up contract gig in Charlotte, NC, focused on building and maintaining automation frameworks for a fast‑moving enterprise testing team. If you’ve spent years writing WinRunner, QTP or SilkTest scripts and want to own the test automation pipeline, this is the kind of hands‑on work that actually moves product quality forward. ### What You'll Actually Be Doing You’ll spend most of your day designing, coding and debugging automated test scripts, then wiring them into a reusable framework that the whole team can run nightly. Expect frequent collaboration with developers to clarify ambiguous requirements, and a lot of time triaging failed runs, digging into logs, and pushing defects upstream. Mentoring junior testers on tool quirks and best‑practice patterns is also on the docket. ### The Core Tech Stack The stack is old‑school but still in production: WinRunner, QTP (QuickTest Professional), SilkTest and TestComplete are the primary automation tools. You need to be comfortable extending those with custom VBScript or C# libraries and stitching them into a framework that can scale across multiple applications. The company relies on these tools for regression coverage, so deep knowledge of their object‑recognition models and limitations is non‑negotiable. ### Interview Expectations 1. *Explain how you would refactor a flaky QTP script that intermittently fails due to dynamic object IDs.* The interviewer wants to see your strategy for synchronization, object repository management, and whether you can introduce robust error handling without rewriting the whole test. 2. *Design a simple data‑driven framework using TestComplete that can run the same test across three environments.* They’re probing your ability to abstract test data, parameterize runs, and integrate results into a CI pipeline. ### Application Advice Tailor your resume to echo the exact tool names – WinRunner, QTP, SilkTest, TestComplete – and highlight any framework you built from scratch. Use verbs like “designed”, “maintained” and “scaled” alongside “automation framework development”. If you have a certification or a project where you reduced manual test time by a measurable percentage, surface that right up front. The ATS will be scanning for those keywords, so keep them prominent in both the skills section and your experience bullet points.

Senior Business Analyst role focused on life insurance systems. You’ll be the bridge between product owners and dev teams, making sure policy admin and underwriting workflows are captured correctly. The work is fully remote, so you need discipline and strong stakeholder chops. ### What You'll Actually Be Doing You’ll spend most of your day interviewing underwriters, agents, and ops staff to pull out the nitty‑gritty of policy lifecycle steps. Then you’ll translate those conversations into BRDs, FRDs, and user stories with clear acceptance criteria. Expect to sit in sprint planning, grooming, and UAT sessions, constantly checking that the backlog stays aligned with compliance and business goals. ### The Core Tech Stack The non‑negotiable skill set is deep life‑insurance domain knowledge—think PAS, policy admin, underwriting, and agent lifecycle systems. You must be fluent in writing BRDs, FRDs, SRS, and agile user stories, and comfortable managing traceability from requirement to release. The JD also calls out AI tools like Copilot and Claude, so being able to prototype prompts or automate doc generation will give you a leg up. ### Interview Expectations 1. *“Walk me through how you’d design a requirement traceability matrix for a new policy‑admin module.”* They want to see you can map functional specs to test cases, regulatory checkpoints, and downstream systems without losing detail. 2. *“Explain a situation where you had conflicting stakeholder demands during an agile sprint and how you resolved it.”* They’re probing your negotiation style, backlog grooming discipline, and ability to keep delivery on track. ### Application Advice Tailor your resume to surface every life‑insurance keyword the JD mentions—PAS, policy admin, underwriting, agent lifecycle, BRD/FRD, user stories, agile ceremonies, UAT, backlog management, and AI tools (Copilot, Claude). Highlight any CBAP, PMI‑PBA, or FLMI certs front‑and‑center. Quantify impact (e.g., “Reduced requirement‑to‑test cycle by 30%”) to satisfy both ATS filters and the hiring manager’s appetite for results.