> Markdown version of [/jobs/ext/3457799-principal-software-engineer-go-payments](https://www.wearedevelopers.com/jobs/ext/3457799-principal-software-engineer-go-payments). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Principal Software Engineer, GO Payments - **Company:** Brandt - **Location:** Tallahassee, FL, United States (Remote available) - **Experience:** Expert - **Salary:** $150,000.0 - $170,000.0 - **Contract:** Temporary contract - **Skills:** .NET Framework, Artificial Intelligence, Amazon Web Services, Microsoft Azure, Cloud Computing, Code Review, Continuous Integration, Relational Databases, DevOps, Entity Framework, Github, PostgreSQL, Microsoft SQL Server, PCI Data Security Standards, Software Engineering, ReactJS, Blazor, Containerization, AngularJS, Kubernetes, Front End Software Development, Software Coding, Restful APIs, Docker, Microservices - **Published:** September 7, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=6e5796e0b5fd551a ## About the Role * Strong foundation in C# and .NET * Front-end experience with Angular, React, or Blazor * RESTful APIs, microservices, and cloud platforms (Azure, AWS) * Relational databases (SQL Server, PostgreSQL) and ORMs (e.g., Entity Framework) * DevOps practices and tools (GitHub Actions, Azure DevOps) * 10+ years of hands-on software engineering experience, including experience setting technical direction across multiple teams * Nice to have: containerization (Docker, Kubernetes), contributions to open-source projects or technical blogs * Extensive experience in the fintech space is required for this opening, specifically hands-on work building or maintaining payment and transaction-processing software * Familiarity with payment gateways/processors, PCI DSS, and transaction reconciliation is a strong plus ## Description This specific opening sits on the Payments team, which owns the payment and transaction-processing systems that power every license, registration, and reservation purchase across our platforms - the infrastructure that turns a campsite booking, a fishing license, or a boat registration into funded conservation work. As Principal Software Engineer, you set the architecture and technical standards for this domain, partnering directly with the Chief Engineer on how those standards extend to the other teams building on top of it. This role is reserved for advanced, high-caliber engineers - the kind who don't need close oversight to do their best work, and who know it without needing to say it. Engineers on our IC track are expected to bring strength that travels: while this role is anchored on Payments today, you're built for range, not a lane, and you may be asked to contribute across Licensing, Registrations, Reservations, or emerging initiatives as business needs shift, picking up new domains quickly rather than needing years to ramp on one narrow system. And you care about the mission. The systems you build here don't just move money - they get people outdoors and fund the conservation work that keeps those spaces open. That's not incidental to the payments work; it's the point. The Role This is our principal individual contributor role, for engineers who want to stay close to the code while working at the highest technical level we have. You're not here to manage a team or own anyone's headcount; we have dedicated Engineering Managers and Tech Leads for that. You're here to write and design the hardest, highest-leverage systems yourself, and to set the architecture and technical standards the rest of engineering builds on. That means systems thinking is part of the job, not a nice-to-have: you step back from the immediate task and ask what the broader pattern is, especially since your work spans multiple product domains. You don't need a fully-specified spec to start making real progress on the right problem; ambiguity is where this role begins, not where it stalls. You'll take ambiguous, cross-cutting problems and turn them into shipped, production-grade systems, with the judgment to know when to move fast, when to slow down, and when a pattern you're building should become a capability the rest of the org can use. That same judgment extends to the tools you use: you lean on AI to move faster, and you know exactly where to trust its output and where to verify it yourself. None of this runs through formal authority. You'll set technical direction and raise the bar for engineers you don't manage, including Tech Leads and other senior engineers, by writing standards clear and well-reasoned enough that people adopt them because they're right, not because you outrank anyone., * Lead the design, development, and delivery of complex technical solutions that meet functional, performance, and security requirements * Translate ambiguous business and product requirements into a clear technical plan and execute against it * Write high-quality, maintainable, testable code, and take ownership of the most complex or critical components on your team * Conduct code reviews and design reviews as a peer contributor, raising the bar through your own standard of work rather than through formal management * Collaborate across product, architecture, QA, and DevOps to ensure end-to-end delivery quality * Advocate for engineering best practices, coding standards, and strong CI/CD discipline * Identify and resolve technical risks and dependencies early in the development lifecycle * Evaluate and adopt emerging technologies and tools, including AI-assisted development, to drive modernization and efficiency * Move across product domains (Licensing, Registrations, Reservations, and beyond) as business priorities shift * Mentor senior and staff-level engineers directly, without a formal reporting line, raising the technical bar through review and example * Design, build, and maintain secure, PCI-compliant payment and transaction-processing systems that power license, registration, and reservation purchases across our agency partners * Integrate with third-party payment gateways and processors, ensuring transaction integrity, accurate reconciliation, and resilience at scale * Partner with compliance and product stakeholders to navigate payment-industry regulations and security standards (e.g., PCI DSS) as the platform evolves