Job Description & Details
This is a serious enterprise production support role focused heavily on managing massive batch execution pipelines using SMA OpCon. If you enjoy untangling complex job dependencies, digging into Linux shell scripts, and keeping critical financial or data pipelines moving, this gig will keep you on your toes—especially since it includes rotational and night shifts.
What You'll Actually Be Doing
You'll be the person holding the pager and managing over 200 production batch jobs. Your day-to-day involves configuring complex job dependencies, installing and patching the OpCon platform, troubleshooting abrupt exit codes, and performing root cause analysis when a critical workflow crashes at 3 AM. You'll also work closely with development and infrastructure teams, write custom Unix/Linux shell scripts, and query PostgreSQL databases via AWS RDS to validate data integrity during failure recoveries.
The Core Tech Stack
OpCon Workload Automation is the absolute centerpiece here—you need deep, hands-on experience designing schedules and managing migrations between environments. Alongside that, you'll rely heavily on Unix/Linux with strong Bash or KSH scripting, robust SQL for data troubleshooting, and AWS PostgreSQL RDS. Knowing your way around Azure DevOps for incident management and Splunk for setting up monitoring dashboards will make your life significantly easier when dealing with high-volume SFTP and batch file transfers.
Interview Expectations
Expect the hiring team to present a scenario where a massive cascading job failure occurs mid-cycle due to a downstream dependency lock and ask you to walk them through your exact triage steps. They want to see how you methodically check exit codes, coordinate across teams, and execute a safe recovery without corrupting the downstream data. They will also likely quiz you on your Unix shell scripting capabilities and how you'd write a script to automate log parsing or pre-flight checks for a batch cycle.
Application Advice
Make sure your resume doesn't just list OpCon as a bullet point, but explicitly highlights the scale of the batch environments you've managed—mention the number of jobs, complex dependencies, and specific AWS or PostgreSQL integrations you've handled. Weave in keywords like root cause analysis, Azure DevOps, Splunk monitoring, and Unix/Linux shell scripting naturally into your experience descriptions to easily sail past the ATS keyword filters.