How does swipeandhired work?

You set your target roles, salary floor and locations once. swipeandhired scores matching postings against your profile, drafts tailored application materials with AI, and either lets you swipe to apply, one tap at a time, or runs fully on autopilot. Every application is tracked in your dashboard.

Which ATS platforms does swipeandhired support?

All of them. swipeandhired applies on every applicant tracking system (ATS) employers use, including Workday, SmartRecruiters, Greenhouse, iCIMS, Lever, Ashby, Taleo, SuccessFactors, Oracle Cloud and Jobvite, and on a company's own careers page when it uses none of them. You can also bring any posting yourself by link or pasted text.

Can I cancel my subscription?

Anytime, in one click from the billing portal in Settings. Your plan stays active until the end of the current billing period. No retention calls, no dark patterns.

Is my data used for training AI models?

No. Your resume and application data are processed only to run the service for you, matching, drafting, and submitting applications. We never sell your data. If you bring your own AI provider key, requests go directly to your provider under their terms.

Operations Engineering, Senior Advisor at Peraton, Baltimore, MD

Operations Engineering, Senior Advisor at Peraton in Baltimore, MD. Contract. Est. up to $160k. Apply with swipeandhired.

Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world’s leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees do the can’t be done by solving the most daunting challenges facing our customers. Visit peraton.com to learn how we’re keeping people around the world safe and secure.

Responsibilities

The Production Operations Lead is accountable for the stability, availability, and recoverability of MARx in production. MARx is the CMS system of record for Medicare Advantage and Part D enrollment, premiums, and plan payments. It serves about 53 million beneficiaries and more than 300 Plan Sponsor Organizations, and supports about $68 billion a month in plan payments. The Lead runs day-to-day production operations across the CMS AWS environment, leads incident and problem management, owns the disaster recovery and continuity program, and makes sure the operational calendar is met on time: daily, monthly, and annual processing, payment files, file exchanges, and New Year Preparation. The Lead also drives the automation and process improvements that move capacity from operations and maintenance toward enhancements.
The Lead works closely with CMS business owners, the CMS Office of Information Technology (OIT), the MAPD Business Operations Support Contractor (MBOSC), CMS help desks and incident response teams, and the partner systems MARx depends on, including SSA, RRB, HPMS, APPS, and the Common Medicare Environment shared with MEPBS.
The position calls for hands-on operational leadership and sound judgment under pressure. Operations work competes with enhancement work for the same team capacity: ServiceNow ticket triage is continuous, security incidents take absolute priority, and New Year Preparation draws heavily on the team from July through March. The Lead must make clear prioritization decisions that protect payment accuracy, beneficiary coverage, and on-time delivery to plans.
Beyond running production, the Lead serves as a trusted operational advisor to program leadership and CMS, mentors production support staff, and drives the reliability and automation improvements that reduce operational workload over the life of the contract. The Lead will have a real opportunity to shape how MARx is operated, reduce operational workload, strengthen disaster recovery, and build a capable operations team.

Key Responsibilities

Production monitoring and availability

Lead real-time monitoring of MARx jobs, system health, cost and usage, and security events using CMS-approved tools (currently Splunk, Splunk On-Call, Datadog, Amazon CloudWatch, and Amazon QuickSight dashboards). Identify and resolve anomalies and errors before they affect plans or beneficiaries.
Manage and maintain 99.9% system availability and response time across the production environment, and report performance against that target.
Maintain scalability and code portability for operations in the cloud environment, working with the DevOps Lead and Architectural Lead.
Apply the AWS Well-Architected Framework to production operations to achieve operational excellence, security, reliability, performance efficiency, and cost optimization in the cloud hosting environment.
Plan capacity for periodic peak processing loads, such as monthly payment processing, the Annual Enrollment Period, and New Year Preparation.
Identify the causes of processing errors and correct them quickly to minimize system downtime.

Disaster recovery and continuity of operations

Own the MARx Disaster Recovery (DR) Playbook: organizational roles and contacts, management and escalation, declaration and testing guidelines, notifications, infrastructure and network configuration details, and step-by-step failover and failback procedures.
Meet the Recovery Time Objectives and Recovery Point Objectives defined in the Business Impact Assessment.
Lead MARx participation in annual Contingency Plan tabletop tests and in DR exercises CMS requests, and turn the results into corrective actions.

Incident, problem, and security event response

Lead production incident response from detection through recovery. Coordinate the scrum teams, the DevOps and Security Leads, and partner systems.
Make sure suspected or confirmed security and privacy incidents and breaches are reported to the CMS Incident Response Team, the COR, and the CO within one hour. Make sure HHS CSIRC and CMS IRT alerts and indicators of compromise get a response within 24 hours
Support the Incident and Breach Response Plan. Provide logs, images, and event data CMS requests. Produce post-incident reports covering impact, threat vector, information affected, lessons learned, and mitigation (J.9).
Lead root cause analyses for production defects and track preventive actions to closure.
Make sure users and partners get timely, accurate notice of releases, maintenance, outages, and downtime, and maintain the downtime communications playbook.
Work with the Architectural Lead and DevOps Lead to turn recurring incident causes into long-term fixes.

Operational calendar, batch processing, and file exchanges

Direct daily, monthly, quarterly, and annual MARx operations, including transmission of plan payment files to the Automated Plan Payment System (APPS) on the monthly payment cycle.
Oversee inbound and outbound data exchanges with MAOs, SSA, RRB, and internal partners. This includes the shared Split and Push file transmission service, the File Mover process (CMS EFT and S3-to-S3), and partner exchanges defined in the Plan Communications User Guide.
Lead operational readiness for New Year Preparation and the Beneficiary Rate Increase (July through March), and for the Annual Enrollment Period.
Coordinate the semiannual lower-environment data refresh, including the de-identification hand-off, and the semiannual and qualifying-beneficiary data archival processes, in line with CMS retention requirements.
Oversee the premium withhold and premium reduction request process with SSA and RRB, which runs on daily, weekly, bi-monthly, monthly, and annual schedules.
Proactively identify issues with information exchanges, and test and implement fixes thoroughly to minimize negative impact on partners.

Release and change management

Govern production deployments for the current twice-weekly release cadence: production readiness reviews, post-implementation reviews, and rollback readiness.
Make sure every production change follows the CMS Target Life Cycle and the MEPS Change Control Board process, and that production-equivalent branches keep their protection rules and CMS approval requirements.

Support desk collaboration and ticket backlog

Serve as the operations point of contact for MBOSC. Provide timely SME support on urgent tickets, lead working sessions with MBOSC and business owners, deliver time-sensitive data fixes, and keep ticket status visible across MARx, MBOSC, and CMS.
Maintain help desk scripts with the MAPD Help Desk, the CMS IT Service Desk, and other CMS help desks.
Triage the existing aging tickets during transition-in and draft the backlog reduction plan. Record improvement opportunities in production operations, ticket handling, and automation for the backlog.
Drive the aging ticket backlog toward the CMS goal of no open tickets more than one year old by the beginning of 2029.

Security, compliance, and audit operations

Make sure production vulnerabilities and findings are remediated within HHS POA&M timelines (critical 15 days, high 30 days, medium 90 days, low 360 days), and that items that can't meet those timelines are tracked in the POA&M.
Support maintenance of the MARx Authority to Operate and CMS Acceptable Risk Safeguards controls, CMS penetration testing and vulnerability scans, and mandated audits such as CFO and A-123. That includes pulling documentation, running queries, and attending auditor meetings.

Cost optimization and operational efficiency

Manage MARx resource usage responsibly to limit costs CMS incurs, using cost and usage dashboards. Cloud hosting itself is paid under a separate CMS contract.
Identify and implement automation of operational work, including responsible use of Super Intelligence (SI) (also called Artificial Intelligence) under the approved SI Compliance and Risk Management Plan, toward the CMS goal of moving the O&M-to-enhancement split from about 75/25 to 50/50 by the end of the period of performance.
Participate in CMS-led innovation efforts and recommend process improvements in operations.
Evaluate SI and machine learning uses that fit production operations, such as anomaly detection for payment and premium processing, optimization of batch processing schedules, and SI-powered chatbots for user support.

Medicare business operations and data integrity

<span style="font-family: arial, helvetica, sans-s