Find the matching job for you with ease

The role is an Embedded Software Engineer building Linux‑based middleware for networking gear aimed at North American customers. You'll be writing C/C++ code, integrating open‑source router stacks, and troubleshooting issues both on‑site and remotely. ### What You'll Actually Be Doing You’ll work hand‑in‑hand with marketing and customers to nail down feature requirements, then translate those into concrete technical solutions. Day‑to‑day you’ll be coding network applications and services, extending embedded middleware on Linux, and validating both software and system behavior. A big chunk is stitching together open‑source components (think OpenWRT, RDK, Opensync, Prpl) with the gateway middleware, plus you’ll field support tickets—sometimes hopping on a customer site, other times digging remotely to squash bugs. ### The Core Tech Stack The non‑negotiables are solid C/C++ skills for bare‑metal and Linux user‑space work, plus a deep grasp of TCP/IPv4 & IPv6 and Wi‑Fi protocols. You’ll be developing on embedded Linux, ideally comfortable with kernel‑space tweaks, and you’ll be pulling in router‑specific stacks like OpenWRT, RDK, Opensync, and Prpl. Version control with GIT and task tracking in Jira are part of the daily grind, and you’ll need to read and extend fairly complex software architectures. ### Interview Expectations 1. *How would you track down a memory leak in a user‑space daemon running on OpenWRT?* – They want to see your systematic approach: using tools like valgrind, heaptrack, or custom instrumentation, understanding the build environment, and how you’d isolate the leak without crashing the router. 2. *Describe the steps to add IPv6 support to an existing TCP stack in an embedded Linux device.* – Expect them to probe your knowledge of the Linux networking stack, kernel configuration, sysctl tuning, and how you’d test interoperability while keeping the footprint low for an embedded platform. ### Application Advice Tailor your resume to echo the exact buzzwords from the posting: Embedded C, C++, Linux (user‑space and kernel‑space), TCP/IPv4/IPv6, Wi‑Fi, OpenWRT, RDK, Opensync, Prpl, middleware development, system validation, on‑site/remote support, GIT, Jira. Highlight any past work that involved integrating open‑source router components or debugging network protocols, and make sure those terms appear in both your experience bullet points and the skills summary so the ATS flags you as a perfect match.

Azure Data Engineer role focused on AI‑enabled data pipelines for a healthcare client. You’ll be the go‑to person for moving massive clinical and pharmacy datasets through Azure and Databricks, and you’ll get to sprinkle LLM‑type AI features on top. It’s a senior hands‑on gig that expects you to hit the ground running with minimal onboarding. ### What You'll Actually Be Doing You’ll design and maintain ingestion pipelines that pull data from disparate health‑system sources (EHRs, pharmacy claims, 340B data) into Azure Data Lake and then transform it in Databricks for downstream analytics. Expect to work directly with VP‑level stakeholders to translate business questions into data models, and you’ll be responsible for performance‑tuning Spark jobs, handling schema evolution, and ensuring compliance with healthcare data regulations. Occasionally you’ll prototype simple LLM integrations—think summarizing clinical notes or generating dosage recommendations—without needing deep research‑level AI expertise. ### The Core Tech Stack The non‑negotiables are Azure (Data Factory, Synapse, ADLS) and Databricks (Spark, Delta Lake). You must be comfortable writing scalable PySpark/Scala jobs, orchestrating pipelines with Azure Data Factory, and modeling large, PHI‑laden datasets. Healthcare domain knowledge (especially 340B pharmacy workflows) is a huge plus because the data shapes are quirky and compliance‑heavy. A dabble in LLM APIs (Azure OpenAI, Hugging Face) is useful but not a make‑or‑break skill. ### Interview Expectations 1. *“Walk me through how you would design a scalable ingestion pipeline for 100TB of pharmacy claim data that must be GDPR/HIPAA compliant.”* They’re probing your ability to pick the right Azure services, partition strategy, encryption at rest/in‑flight, and how you’d validate data quality. 2. *“Explain the trade‑offs between using Delta Lake’s Z‑order vs. traditional partitioning for query performance on a mixed‑type clinical dataset.”* They want to see if you understand Delta optimizations and can justify choices based on query patterns and storage cost. ### Application Advice Tailor your resume to scream “Azure Data Engineer + Healthcare” – put Azure Data Factory, Databricks, Spark, and Delta Lake right up top. Highlight any 340B or pharmacy‑related projects; even a short stint with claims data will get you noticed. Sprinkle in “LLM integration”, “AI‑enabled pipelines”, and “VP stakeholder communication” to match the soft‑skill cues. Keep the experience bullet concise: *12+ years building end‑to‑end data solutions in Azure for regulated health domains* – that exact phrase will help you pass the ATS.

The role is a senior‑level AI leadership position where you’ll own end‑to‑end GenAI product pipelines for big‑ticket verticals like telecom, health and manufacturing. It’s not a vague research gig – they expect you to ship production‑grade models that actually move the needle for enterprise customers. ### What You'll Actually Be Doing You’ll spend most of your day translating business problems into LLM‑driven solutions, designing RAG architectures, and then shepherding those models through the whole dev‑ops lifecycle – from prompt engineering to CI/CD, monitoring, and cost‑control on Azure OpenAI or Anthropic. Expect frequent triage on model drift, latency spikes, and budget overruns, plus occasional deep‑dives with domain SMEs to fine‑tune data pipelines. ### The Core Tech Stack The must‑know stack is LLMs (Llama, Mistral, Gemma, Phi, Qwen) plus the RAG pattern, all wrapped in Azure OpenAI or Anthropic services. You need solid experience with prompt engineering, vector stores, and retrieval‑augmented generation, plus a production mindset around Docker/Kubernetes, Terraform, and cost‑optimization dashboards. If you’ve built an end‑to‑end GenAI service that scales to thousands of requests per day, you’re already speaking their language. ### Interview Expectations 1. *Design a cost‑effective RAG pipeline for a telecom churn‑prediction use case.* The interviewer will watch for how you pick vector DBs, chunking strategies, and how you instrument Azure cost‑monitoring. They want proof you can balance latency, relevance, and a $‑budget. 2. *Explain how you would mitigate hallucinations in a medical‑record summarization model deployed on Azure OpenAI.* Look for a discussion around prompt guardrails, post‑processing filters, and human‑in‑the‑loop validation. They’re testing depth of safety awareness, not just model performance. ### Application Advice Tailor your resume to scream “GenAI production expert.” Lead with verbs like *designed*, *deployed*, *optimized* and sprinkle the exact tech keywords: LLM, RAG, Azure OpenAI, Anthropic, Llama, Mistral, Gemma, Phi, Qwen, NLP, cost‑optimization, enterprise AI strategy. Highlight any telecom/healthcare/manufacturing projects and quantify impact (e.g., reduced inference cost by 30%). A concise one‑page summary that mirrors the bullet list in the JD will get past most ATS filters.

Security & Compliance Engineer (SOC 2/HIPAA) – a hands‑on role where you’ll own the security control build‑out for a fast‑growing cloud SaaS. It’s not a paper‑pusher gig; you’ll actually design, code and validate controls that keep healthcare and government data safe. ### What You'll Actually Be Doing You’ll start by mapping the existing platform to SOC 2 Trust Service Criteria and HIPAA Security Rule, then write the policies, standards and evidence collection scripts needed for auditors. Day‑to‑day you’ll be wiring up RBAC, MFA, encryption at rest/in‑flight, and audit‑logging pipelines in AWS or Azure, while embedding those controls into CI/CD pipelines. Expect frequent risk‑assessment workshops, rapid remediation of findings, and on‑call incident‑response drills that simulate PHI breaches. ### The Core Tech Stack The non‑negotiables are deep AWS/Azure security knowledge (IAM, KMS, CloudTrail, GuardDuty) plus a solid grasp of NIST CSF and how it maps to SOC 2 and HIPAA. You’ll need to be comfortable scripting in Bash/Python to automate evidence collection, and you should have built Secure SDLC/DevSecOps gates (e.g., Terraform Sentinel, Snyk, or Checkov). Those skills let the team prove compliance continuously rather than once a year. ### Interview Expectations 1. *“Walk me through how you would design a SOC 2‑ready logging architecture on AWS, and how you’d prove its completeness to an auditor.”* – They’re looking for a clear data‑flow diagram, use of CloudWatch Logs, S3 bucket immutability, and a retention policy that satisfies the five Trust Service Criteria. 2. *“A vulnerability scan flags a misconfigured S3 bucket exposing PHI. Explain the remediation steps and how you’d document the fix for HIPAA compliance.”* – Expect them to hear about immediate bucket policy changes, bucket encryption enablement, logging activation, a root‑cause analysis, and updating the risk register and SOPs. ### Application Advice Tailor your résumé to echo the exact phrasing from the JD: “SOC 2 implementation,” “HIPAA security controls,” “RBAC,” “MFA,” “audit logging,” “NIST Cybersecurity Framework,” and “DevSecOps.” Highlight any AWS Security Specialty or Azure Security Engineer certs you hold, and surface concrete metrics (e.g., reduced audit remediation time by 30%). A short cover note that mentions “remote‑first, US‑based compliance work for healthcare SaaS” will help you pass the ATS and catch the recruiter’s eye.

This is a senior‑level manager role focused on keeping the CAPPS platform secure and running smoothly for Texas state agencies. You’ll be the bridge between the Comptroller’s office, external vendors, and the development teams, making sure the PeopleSoft ecosystem stays compliant and reliable. ### What You'll Actually Be Doing You’ll own the end‑to‑end technical operations of CAPPS Central – that means monitoring production health, triaging security incidents, and enforcing segregation‑of‑duties controls across multiple agencies. Day‑to‑day you’ll coordinate with managed service providers, push out PeopleSoft patches, and translate executive‑level requirements into concrete project plans. Expect a lot of cross‑functional meetings, vendor scorecards, and occasional fire‑fighting when a data‑quality issue surfaces in a live payroll run. ### The Core Tech Stack The stack is all about PeopleSoft FSCM/HCM 9.2, PeopleTools, and PeopleCode, backed by an Oracle database you’ll query with SQL for data‑integrity checks. You’ll need to be fluent in SDLC best practices, ITIL service‑management processes, and the security controls that keep a state‑wide financial system compliant. The job leans heavily on your ability to design integration pipelines and audit trails that satisfy both auditors and the business. ### Interview Expectations 1. *“Walk me through how you would design a segregation‑of‑duties matrix for PeopleSoft Financials and ensure it stays enforceable after a major system upgrade.”* They’re looking for concrete steps: role‑based access design, automated SoD testing, remediation workflow, and how you’d document changes for auditors. 2. *“Describe a multi‑vendor PeopleSoft rollout you managed under tight regulatory deadlines. What risk‑mitigation tactics did you employ?”* Expect them to probe your vendor‑management playbook, change‑control procedures, and how you balanced compliance with delivery speed. ### Application Advice Tailor your resume to surface the exact buzzwords the posting repeats: CAPPS, PeopleSoft FSCM/HCM 9.2, PeopleTools, PeopleCode, Oracle/SQL, ITIL, SDLC, segregation of duties, vendor oversight, and contract compliance. Highlight any Texas public‑sector projects and quantify the size of the teams or budgets you’ve managed. A concise bullet like “Led CAPPS security ops for 5 state agencies, enforcing SoD controls across a $200M PeopleSoft environment” will get past most ATS filters.

This contract gig is looking for a senior Azure DevOps engineer to own CI/CD pipelines and IaC for enterprise workloads. You’ll be the go‑to person for everything from Terraform to AKS, and the team expects you to keep the cloud delivery reliable and secure. ### What You'll Actually Be Doing You’ll spend most of your time wiring Azure DevOps pipelines end‑to‑end: pulling code from Git, building Docker images, pushing them to a registry, and deploying to AKS or VMs. You’ll also write Terraform or ARM/Bicep modules to spin up the underlying infrastructure, keep the state tidy, and make sure releases are repeatable. Monitoring and troubleshooting live pipelines, tweaking branching strategies, and collaborating with dev, QA, security, and ops to squash blockers are daily chores. ### The Core Tech Stack The non‑negotiables are deep experience with Azure DevOps Services and the broader Azure ecosystem—think VMs, Storage, Networking, Monitor, and especially AKS. You must be fluent in IaC (Terraform, ARM Templates or Bicep) and comfortable scripting in PowerShell, Bash, or Python to glue everything together. Containerization with Docker and orchestration with Kubernetes are also core, plus solid Git branching and release‑management knowledge to keep enterprise‑scale codebases tidy. ### Interview Expectations 1. *Design a blue‑green deployment for an AKS service using Azure DevOps pipelines.* Expect the interviewer to probe how you handle traffic shifting, health checks, and rollback without downtime—show you can orchestrate multiple stages and validate each step. 2. *Explain Terraform state management in a multi‑team environment.* They’ll look for strategies like remote backends, state locking, workspace segregation, and drift detection, demonstrating you can keep infrastructure consistent across dozens of engineers. ### Application Advice Tailor your resume to hit the exact buzzwords the JD throws at you: Azure DevOps, CI/CD pipeline design, Terraform/ARM/Bicep, Azure VMs, Azure Storage, Azure Networking, Azure Monitor, AKS, Docker, Kubernetes, PowerShell, Bash, Python, Git branching strategies, release management, enterprise‑scale, reliability, scalability, security, compliance. Highlight any end‑to‑end pipeline you built, especially if you automated infra provisioning and managed state. A concise bullet that says “Implemented blue‑green deployments on AKS via Azure DevOps, reducing release downtime by 90%” will jump out to both ATS and the hiring manager.

Honestly, this is a hands‑on QA lead role for a consumer‑facing connectivity platform, based out of Chicago with a hybrid schedule. They need someone who can own automation from UI Selenium scripts to API testing while mentoring a small team. ### What You'll Actually Be Doing You’ll be the point person for all automation work: writing and maintaining Selenium WebDriver suites, crafting API tests with RestAssured or Postman, and wiring everything into the CI/CD pipeline. Expect to spin up Wi‑Fi test beds and network emulators, track defect flow, and produce metrics for stakeholders. A big chunk of your day will be reviewing junior testers’ code and guiding them toward best‑practice automation patterns. ### The Core Tech Stack The non‑negotiables are Selenium for UI, RestAssured/Postman for API, and a solid scripting language—Python or Java. They’re also looking for someone comfortable with CI tools (think Jenkins or Azure Pipelines) because the tests have to run on every push. If you’ve built a reusable framework before, you’ll hit the sweet spot; otherwise, be ready to design one from scratch. ### Interview Expectations 1. *“Walk me through how you’d design a scalable Selenium framework for a multi‑browser web app that also needs to test mobile‑responsive layouts.”* They’re probing your ability to abstract page objects, handle parallel execution, and keep the codebase maintainable. 2. *“Explain a tricky API testing bug you uncovered with RestAssured and how you isolated it in a CI environment.”* The hiring manager wants proof you can dig into request/response details, mock dependencies, and surface flaky tests before they break the pipeline. ### Application Advice Tailor your resume to shout out the exact keywords they used: **Selenium**, **RestAssured**, **API testing**, **CI/CD integration**, **test automation framework**, **Wi‑Fi test beds**, and **mentoring**. Highlight any hybrid or on‑site experience in Chicago, and make sure your most recent QA lead project sits at the top of the work‑experience section with metrics (e.g., % reduction in regression time). A concise bullet like “Led a team of 4 testers to deliver 200+ automated UI tests, cutting manual regression by 70%” will get past most ATS filters.

This is a contract gig centered on OpenText Media Management (OTMM) version 25+ for on‑prem deployments. You’ll be the go‑to person for workflow customizations and third‑party integrations, reporting directly to IT leadership. ### What You'll Actually Be Doing You’ll spend most of your time tweaking OTMM workflows – adding custom actions, scripting Java/JavaScript extensions, and updating MS SQL queries that power metadata searches. Deployments are on‑prem, so you’ll handle the full install/upgrade cycle, troubleshoot environment‑specific issues, and work with integration services to hook OTMM into other enterprise apps. A big chunk of the role is communication: you’ll translate technical constraints to non‑technical stakeholders and keep the IT leadership looped in on progress. ### The Core Tech Stack The stack is pretty narrow but deep: OTMM 25 or newer (on‑prem), heavy Java and JavaScript for custom workflow code, and MS SQL for the backend metadata store. The company expects you to know the OTMM integration services inside‑out because they rely on them to push assets to downstream systems. Since it’s an on‑prem setup, solid knowledge of Windows/Linux server administration and networking basics is also a plus. ### Interview Expectations 1. *Design a custom OTMM workflow that triggers a REST API after an asset is ingested.* The interviewer will look for how you break down the workflow into stages, which OTMM services you’d extend, and how you’d secure the API call. They want to see you can map business rules to OTMM’s workflow engine without breaking the core system. 2. *Troubleshoot a slow OTMM SQL query that joins multiple metadata tables.* Expect to discuss index strategies, execution plans, and how OTMM caches metadata. They’re probing whether you understand the performance implications of OTMM’s schema and can tune it in a production environment. ### Application Advice Tailor your resume to mirror the JD’s buzzwords: “OTMM version 25”, “workflow customization”, “Java”, “JavaScript”, “MS SQL”, “on‑prem deployment”, and “integration services”. Highlight any projects where you integrated OpenText with third‑party apps or optimized OTMM performance. Since it’s a remote contract, flag your remote work experience and your ability to interact with IT leadership. A concise summary at the top that reads “5+ years OTMM, Java/JS, MS SQL – on‑prem specialist” will help you sail past the ATS.