At Quicket, we understand that government needs great technology to best serve our communities. Quicket’s unified data management and operational intelligence software improves efficiencies by breaking down data silos, automates services for residents, and eliminates costs associated with managing infrastructure. Our software focuses around e-citation, code enforcement, hearing management, and other platforms used by municipal governments.
Primarily, we're looking for engineers with 3-5 years experience. Engineers that have proven they can help a team deliver a product and are looking to grow their careers to the next stage.
Positions:
- Backend: We use Python, but are open to strong developers in any language. This position is for building out REST APIs for mobile/.NET clients to consume, rules engines, and integrations with 3rd party systems.
- C#/.NET: WPF/UWP, The Quicket .NET team is seeking an engineer/developer with a minimum of 3 years of experience working with .NET technologies. Quicket operates under a SaaS model, and this position will focus on redesigning our desktop application to better serve as a mobile front end to our web data platform.
- Infrastructure Engineer: You will be supporting multiple product teams with automating deployment, QA, CI/CD tooling, and infrastructure for an AWS based SaaS company providing solutions for government agencies. You: Think that automating away your job means you’re doing your job. Feel strongly that if it can’t be automated, it shouldn’t be done. Cringe at the thought of a customer finding a problem before you do. Understand that “scale” refers to people as well as infrastructure. Think of success in terms of failure modes, mitigation, and resolution. Thrive on solving new problems, learning new tools and sharing them with others. Take ownership of your solutions, grow them to meet new challenges and groom them to be useful to others.
I went from fine dining cook to Marine Corps infantry to developer. Though the GI Bill takes a lot of the impressiveness out of a massive career change helped by a college degree.
When starting a new podcast I normally listen to the newest one. Then it depends on the style. News/current events podcasts, just listen to new ones. Others, browse the history and cherry pick ones that sound interesting or download them all.