Senior Python and PowerShell Product Automation Systems Engineer at TYCHON | Torre

Senior Python and PowerShell Product Automation Systems Engineer

Emma highlights
This highlight was written by Emma’s AI. Ask Emma to edit it.
Full-time

Legal agreement: Employment

Compensation
USD150k - 165k/year
location_on
Remote (for United States residents)
Shared by
Julien PETIT
4 days ago

Responsibilities


Job OverviewTychon LLC is looking for an experienced Senior Python & PowerShell Product Automation Engineer to help build and evolve production software that discovers, assesses, manages, and remediates endpoints across complex enterprise environments.This is not a traditional systems administration or DevOps scripting role. You will be building software products using Python and PowerShell—designing reusable libraries, modules, command-line tools, endpoint components, integrations, and automation frameworks that must perform reliably across diverse and sometimes highly constrained environments.If you are a strong software developer who also understands how operating systems actually work—and you enjoy solving difficult compatibility, performance, and systems-level problems—this role may be a great fit.What You'll DoAs a senior member of the engineering team, you will take capabilities from requirements and design through development, testing, release, and ongoing support.Build production-quality software using Python and PowerShell.Develop endpoint discovery, assessment, software inventory, patching, application update, remediation, network discovery, and .Create reusable libraries, modules, frameworks, command-line utilities, and automation tools.Integrate product components with REST APIs, NoSQL data stores, and relational databases.Solve complex Windows and cross-platform systems-engineering problems.Develop software that operates reliably across current and legacy operating systems and constrained environments.Modernize existing code while maintaining compatibility with deployed environments.Build automated unit, integration, regression, compatibility, and performance tests.Profile and optimize software for performance at enterprise scale.Participate e reviews, CI/CD, packaging, versioning, and controlled releases.Mentor other engineers while remaining a hands-on contributor.What We're Looking ForThe ideal candidate is a developer first who treats both Python and PowerShell as serious product-development languages.You should have:5–7+ years of professional software development experience.Expert-level Python 3 development experience.Significant experience maintaining compatibility with Python 2.7 environments.Deep Windows PowerShell 5.1 development experience beyond routine administration or one-off scripting.Experience building reusable modules, libraries, frameworks, command-line tools, or product components.Strong experience integrating software with REST APIs and database platforms.Strong knowledge of Windows and Linux operating systems and how applications interact with the underlying host.Experience with automated testing, source control, CI/CD, debugging, profiling, and performance optimization.The ability to design software for compatibility, reliability, security, and long-term maintainability.The ability to expladeoffs, and architecture clearly.We are especially interested in candidates with experience in:Endpoint security or endpoint-management productsVulnerability or configuration assessmentSoftware inventory, patch management, or remediationCIM/WMI, WinRM, Windows Registry, services, scheduled tasks, event logs, and certificatesOVAL, SCAP, security benchmarks, or machine-readable assessment contentPowerShell module packaging and code signingC#/.NET integrationRegular expressions and complex data parsingAI-assisted software development with strong validation and secure-development practicesThe Engineering EnvironmentOur software operates across a wide range of enterprise endpoints, including Windows, Linux, and macOS environments.Python components may operate across all three platforms, while PowerShell development primarily targets Windows PowerShell 5.1 on Windows 10/11 and Windows Server environments.You don't need to know every operating-system release. You do need to know how to investigate unfamiliar system behavior, understand what is happening at the host level, and build software that behaves predictably across different environments.You'll Thrive in This Role If You...Enjoy solving difficult technical problems rather than simply connecting existing tools.Understand both software development and systems engineering.Care about performance, testing, compatibility, and maintainability.Are comfortable working with legacy environments when the mission requires it.Can move between high-level architecture and hands-on implementation.Question assumptions and validate behavior through testing and evidence.Enjoy building software that has to work reliably l-world enterprise environments.Most Important: This Is a Software Engineering RoleIf your PowerShell experience is primarily administering Windows environments or writing occasional administrative scripts, this is probably not the right role.If you've built reusable, tested, versioned, production-quality software with Python and PowerShell and understand the systems that software operates on, we'd like to hear from you.Benefits:401(k)401(k) matchingDental insuranceHealth insurancePaid time offVision insuranceApplication Question(s):How would you describe your Python development experience?How would you describe your PowerShell experience?Do you have professional experience developing in Windows PowerShell 5.1?Have you developed software that integrates with REST APIs and databases?Do you have hands-on software development experience working with both Windows and Linux operating systems?Briefly describe the most complex PowerShell software or automation component you have developed. What did it do, and was it deployed as reusable production code?Describe an example where you had to develop software that worked across different operating-system versions, runtime versions, or constrained customer environments. What compatibility issues did you have to solve?When developing production PowerShell, what practices do you use to make the code maintainable, testable, performant, and safe for deployment across thousands of endpoints?Experience:hands on: 5 years (Preferred)