Find your next role
Strengthen your profile
Brandt Information Services
GovTech & Civic Tech
See how your profile stacks up against this role.
We compared the job requirements to your profile to show where you're strong and where you fall short.
Principal Software Engineer, GO Payments
Must be US Citizen or Green Card holder
Full-Time Salaried Position
Remote Work Within the Continental United States
About Brandt
Brandt is the get-outdoors company. State and local agencies steward the parks, lakes, and wildlife people come for; our platforms make getting there easy, from reserving a campsite to renewing a permit, and help agencies manage those resources sustainably. A family with a trip planned doesn't get a second try at opening day, and neither do we. We're modernizing our platform, building new products, and assembling high-performing teams that have AI embedded in every workflow.
Learn more about Brandt at brandtinfo.com.
Where You Fit
Brandt’s engineering organization spans Licensing, Registrations, and Reservations, the platforms agencies rely on to run camping, hunting, fishing, and boating programs at scale, along with the services layer around them (fulfillment, CRM, contact center, and more).
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.
This is also a fully remote role, not a hybrid arrangement with an office waiting for you to return to. There’s no relocation clause in the fine print and no plan to change that as the team grows. You build your work around deep, focused engineering time instead of a commute, permanently, not as a temporary accommodation.
Responsibilities
Tech Stack & Experience
Compensation & Benefits
The selected candidate should have the skills, qualifications, and experience consistent with a Principal level within Brandt’s job architecture. The compensation range is $150,000 – $170,000, with final level and salary determined based on the candidate’s expertise, qualifications, and prior experience within the applicable pay band.
Brandt Information Services, LLC is an Equal Employment Opportunity (EEO) employer and welcomes all qualified applicants. Applicants will receive fair and impartial consideration without regard to race, sex, color, religion, national origin, age, disability, veteran status, genetic data, or other legally protected status.
Please direct all questions/inquiries to careers@brandtinfo.com
After you apply, unlock the direct contact details of the people who actually make the call. A quick follow-up makes you 5x more likely to land an interview.
Marcus Rivera
Chief Revenue Officer

GitHub

NASCO

NASCO

NinjaOne

The College Board

Brandt Information Services

Brandt Information Services

Brandt Information Services