Software Engineer, Platform Automation and AI Tooling

Job Description

The Software Engineer, Platform Automation and AI Tooling builds the internal tools, agents, and APIs that make Paysign's engineering organization faster. The work spans application development, cloud infrastructure, and AI-assisted automation. Paysign is hiring for diagnostic ability first: the person in this seat can enter an unfamiliar system with no documentation, work from a log file and a symptom to a root cause, and then ship the fix. Payments domain knowledge and AI agent development are both taught here. The instinct for figuring things out is not. The role reports directly to the CTO, operates from problem statements rather than a ticket queue, and uses AI-assisted development tooling daily. It suits an engineer with a few strong years behind them who wants production ownership and a working path into AI engineering. This position is based on-site in Henderson, NV and is open to local candidates only; it is not available as a remote role.

\n

\n

Key Responsibility Areas

\n

Automation & AI Tooling

\n

\n
• Extend and maintain Paysign's internal development agent, which automates branching, commit standards, merge request creation, and pipeline monitoring across roughly 400 GitLab repositories
\n
• Implement agent workflows and integrations against LLM APIs, primarily AWS Bedrock
\n
• Build evaluation and regression tests for prompts and agent behavior so changes are caught before they reach a repository
\n
• Automate manual engineering and operations work where the time saved is measurable
\n

\n

\n

API & Application Development

\n

\n
• Design, build, and document REST APIs supporting cardholder management, bank account verification, and card production workflows
\n
• Write production code in C#/.NET, Java, or TypeScript/Node.js
\n
• Produce schema changes, migrations, and backfills against high-volume tables
\n
• Implement event streaming and notification services for card transaction activity
\n

\n

\n

Systems Diagnostics & Production Support

\n

\n
• Diagnose defects in unfamiliar systems and languages, working from logs, database state, and network traces to a root cause
\n
• Troubleshoot transaction processing failures and third-party SOAP and REST integrations
\n
• Investigate infrastructure issues including ECS task execution, SFTP and SSH connectivity, and API gateway routing
\n
• Build tooling that makes recurring diagnostic work repeatable, such as log parsers and reconciliation scripts
\n
• Provide production system support and participate in on-call rotation as needed
\n

\n

\n

Data & Cloud Operations

\n

\n
• Write and tune SQL against MySQL and Aurora, including execution plan analysis and index design
\n
• Deploy and operate services on AWS using ECS, Lambda, IAM, S3, and VPC networking
\n
• Maintain GitLab CI/CD pipelines and Terraform configurations
\n
• Instrument services with Datadog monitors and dashboards and keep alerting actionable
\n

\n

\n

Collaboration & Documentation

\n

\n
• Work directly with the CTO on priorities, tradeoffs, and design decisions
\n
• Document tools, APIs, and diagnostic procedures so others can use them without the author present
\n
• Follow PCI DSS change control and secure coding practices when handling cardholder data
\n

\n

\n

Required Qualifications

\n

Diagnostics & Problem Solving (Critical)

\n

\n
• Demonstrated ability to find root cause in systems the candidate did not build and for which no documentation exists. This is the most important qualification for the role.
\n
• A structured method for narrowing a search space rather than guessing
\n
• Willingness to read someone else's code, a vendor specification, or a protocol document to reach an answer
\n
• Ability to work from a problem statement instead of a fully specified ticket
\n

\n

\n

Software Development

\n

\n
• Production experience in at least one of C#/.NET, Java, or TypeScript/Node.js, and willingness to work in the others
\n
• Working command of REST API design, authentication and authorization patterns, and versioning
\n
• Fluency with Git and branching strategies in a multi-repository environment
\n

\n

\n

Databases

\n

\n
• SQL past CRUD: execution plans, index selection, and diagnosing why a query behaves differently in production than in staging
\n
• MySQL required; PostgreSQL or MongoDB desired
\n

\n

\n

Cloud & Infrastructure

\n

\n
• Working AWS proficiency across ECS, Lambda, IAM, and S3
\n
• Linux command line fluency and comfort operating in a shell
\n
• Exposure to CI/CD pipelines and infrastructure as code; GitLab and Terraform preferred
\n

\n

\n

AI Development (Trained on the Job)

\n

\n
• Evidence of having built something with LLM APIs, whether at work, as a side project, or through self-study.
\n
• Years of professional AI experience are not required and are not screened for.
\n
• Regular use of AI-assisted development tooling, and a clear sense of where it fails
\n
• Interest in agent design and evaluation, with judgment about when deterministic code is the better answer
\n

\n

\n

Soft Skills

\n

\n
• Clear written communication, including explaining a technical finding to a non-technical reader
\n
• Self-direction across several concurrent priorities
\n
• Documentation and knowledge-sharing discipline
\n

\n

\n

Education & Experience

\n

\n
• Bachelor's degree in Computer Science, Information Systems, or a related technical field, or equivalent practical experience
\n
• 3+ years of professional software development experience
\n
• 1+ years of hands-on AWS experience supporting production workloads
\n
• No payments industry background is required. ISO 8583, jPOS, ACH and NACHA formats, and PCI DSS practices are taught on the job and should not be used as screening criteria.
\n