Hi Quindar team,
I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still enjoy figuring out how to make complicated systems work together in a way someone can actually use. Satellite operations is a new domain for me, but the engineering problem in your posting feels familiar: understand what the operator needs, connect the software and infrastructure behind it, and make the result dependable when it matters.
I like that you are looking for a software engineer rather than requiring someone to arrive as a satellite expert. My career has moved between building applications and operating the systems they depend on. Through Technomancy IT, I take client products from discovery through implementation, deployment and support. React, TypeScript and Node.js are central to much of that work, alongside authenticated APIs, relational data and tenant-aware services. Python has also been part of my systems and project work. I would bring that breadth while learning the particular mission workflows and backend conventions your team uses.
At FRII, I ran the NOC and handled production escalations through a multiyear engineering tenure. I migrated workloads from Hyper-V and VMware ESXi into Docker and Kubernetes, used Terraform and Ansible for repeatable infrastructure work, and upgraded server and firewall systems. I worked there for years before becoming the sole systems engineer for about a year after a company purchase, with the NOC continuing first-line coverage. That responsibility taught me to look beyond whether a component was running and understand whether the whole service was doing what people needed.
The same perspective shows up in my software work. NuPrice was a long-term client engagement where I built and operated the application, billing, customer support and technical operations. It connected marketplace data and pricing rules with accounts, subscriptions and the user-facing workflow. Being responsible for both the product and the issues people brought back made me comfortable moving across the stack instead of treating the frontend, backend and operation as separate problems.
The Technomancy platform I am building takes that approach into support, CRM, scheduling, billing and infrastructure context with TypeScript, Next.js and PostgreSQL. Its delivery tooling records image and deployment identity, applies migrations and checks real HTTP responses. Separate restore-verification tooling checks a backup and restores it into a disposable database. I enjoy making that kind of operational behavior visible and repeatable, particularly when a team needs to change a system without losing track of what is running.
I am also building Kerf, formerly Weft, a TSX framework with its own compiler and the Warp UI toolkit. It is early development, but it reflects the self-directed work your posting calls out: digging into the tools, making the contracts explicit and improving the feedback people and coding agents get while building. I would bring that curiosity to Quindar without confusing an independent framework project with experience operating spacecraft.
I am based in Milliken and interested in working with your Arvada team. I would welcome a conversation about the customer-specific capabilities and core product work you need help with. When operators can focus on the mission because the software makes the complicated parts clear, that is the kind of practical magic I want to help build.
Chad