Hi True Anomaly team,
I call myself a technomancer because technology has fascinated me since I was a kid, and I still love turning a complicated system into something another person can use. Your Digital Engineering role caught my attention because the people using the software are close to the work it supports. An engineer changing a design, a buyer following a handoff and a technician building from a record all need the software to tell a coherent story.
Reading about Jackal's modular hardware and GravityWorks made that connection feel concrete. The internal tools behind a spacecraft have to stay useful as the product changes and production moves forward. I would enjoy learning those workflows with your team and building software that people can rely on throughout that process.
At Office Evolution, I built centralized applications connecting CRM, provisioning, onboarding and service operations across locations. The useful part was understanding where one department's work became another's responsibility, then making that handoff explicit in the software. That experience has stayed with me as I have taken on broader product ownership.
My own Technomancy IT platform brings support, customer records, scheduling, billing and infrastructure context into a connected operating layer. I build it with TypeScript, Next.js and PostgreSQL, keeping client access boundaries intact through tenant-aware services. I also own its delivery and support. The deployment tooling records image identity and deployment status, applies database migrations and checks service health; separate restore-verification tooling checks backups in a disposable database. I care about being able to understand and recover the system after the feature has shipped.
For ProofMark, I completed a client engineering contribution to a document-signing workflow spanning identity, PDF fields, routing, audit history and verification. My work connected the interface, APIs and data while keeping sensitive state and fallback paths explicit. That is a useful foundation for thinking about records whose history matters, while your parts, revisions and manufacturing processes would be a domain I would learn directly from the people using them.
I bring an operator's perspective as well. At Front Range Internet Inc., I ran the NOC, handled escalations and migrated workloads from Hyper-V and VMware ESXi into Docker and Kubernetes. I also ran the company's SOC 1 and SOC 2 audit work. Those responsibilities taught me to follow a problem across application and infrastructure boundaries and make the operating procedures understandable to other people.
Frontend architecture is work I enjoy in its own right. Alongside my longstanding React experience, I am building Kerf, an independent TypeScript/TSX framework with its own compiler, reusable UI toolkit and agent-oriented diagnostics. It is in early development. I use AI heavily in my engineering work, and this project gives me a concrete place to think about the patterns and feedback that help people and coding agents build interfaces consistently.
I am based in Milliken, Colorado. I would welcome the chance to talk about the first workflows your Digital Engineering team wants to bring in-house, how you plan to keep their records trustworthy during the transition, and where my product and operations experience could help. Thank you for considering my application.
Chad