Andrew Carl

1. I led the first full-time development push in 2021–2022 and returned full-time in March 2026.
2. I took the project through a public Creative Alpha and am preparing it for Windows Early Access.

Creative Alpha | Steam product page

1. I separated the client, server, and shared simulation code into distinct Unity assemblies with clear compile-time boundaries, server authority, and persistent world state.

1. I tied those systems together so colonists can respond to their needs, their work, and changes in the world.
2. I built them around server authority and persistent world state.

1. I designed the tools so players and developers can create content inside the game.
2. I made the content reusable through blueprints and data-driven definitions.

1. I use the same tooling from local development through public releases.
2. I built repeatable release profiles and checks so each public build follows the same process.

1. I move 200–300 scoped tasks per week through the pipeline.
2. I raised weekly merged pull requests from about 40 to 60–70+ while keeping the validation and release checks in place.

1. I redesigned the V3 API for the consumer, vendor, POS, events, and admin products.
2. I cut repeated database calls and controller boilerplate.
3. I continued supporting the SaaS, POS, events, and payment systems that generated revenue.

1. I converted about 100 beta signups into 15 paid trials.
2. I grew the product to 35+ seats within five months.
3. I used Gemini and OpenAI APIs to discover 40,000 events for food trucks, caterers, and general merchants.

1. I built multiple passes for search, extraction, cleanup, duplicate removal, URL checks, and safety filters.
2. I separated onboarding from production processing so the product could respond quickly and control cost.

1. I covered POS, online ordering, invoices, ACH, cards, cash, tax, tips, and local fees.
2. I kept the revenue-generating payment systems running throughout the change.

1. I showed where the existing roadmap did not match actual customer behavior.
2. The resulting roadmap shift increased average monthly revenue per vendor from under $10 to over $25.

1. I audited the repositories and bridge rollback risks.
2. I rebuilt the core engineering team and launched the public website.
3. The engagement ended when the founders chose to refocus on existing products.

1. I hired two senior full-stack engineers with complementary skills.
2. I set responsibilities and priorities around the systems with the most risk.

1. I built the responsive design and animations.
2. I integrated the blog API, sitemap generation, and analytics.
3. I added automatic WebP conversion for site images.

1. I covered the product architecture, user experience, and monetization.
2. I mapped the staffing and delivery plan.

1. I led two investigations that traced transactions to KYC exchanges.
2. I separated suspicious activity from normal transaction patterns and traced funds across chains.

1. I worked across enterprise CMS, search, integrations, and email marketing.
2. I earned Kentico certification and fixed a slow NetForum-to-Kentico data sync.

1. I earned both credentials while delivering C#/.NET work for agency clients.
2. I applied the marketing certification while building personalized email campaigns.

1. I improved the freshness and relevance of the Azure Cognitive Search results that depended on it.
2. I made the integration easier to operate and troubleshoot.

1. I added dynamic articles, tables, subscriber content, and subscription links.
2. I tested the templates across email clients so they rendered consistently.

1. I recruited 10 engineers after reviewing 220+ candidates and conducting 60 interviews.
2. I directly managed six to seven engineers at a time across four products.
3. I stayed hands-on with the SDK, monitoring, recovery, bridge, and early lending work.

1. I built Algorand TEAL contracts and Node.js bridge services.
2. I helped roll out USDC support across eight blockchains.
3. I supervised the bridge front end and early EVM bridge work.

1. I published the SDK for internal and third-party integrations.
2. I used RPC polling and transaction APIs to monitor bridge activity.
3. I built PostgreSQL recovery so the indexed data could be rebuilt when needed.

1. I brought transactions, volume, status, and estimated completion time into one place.
2. I made both sides of cross-chain transfers traceable.
3. I connected the explorer to the same monitoring and recovery system used by operations.

1. I worked on yield optimization and safe aggregator use.
2. I designed installment-based borrowing and clear liquidation rules.
3. I developed stable-token economic models for the product.

1. I continued supporting Evapco’s engineering and sales software through May 2022 while also developing Re3 Studios products.

1. I used the results to support blockchain-security investigation reports from Aug 2021–Mar 2022.

1. I turned thermal and acoustic R&D into tools used by engineering, application engineering, sales, and marketing.
2. I removed a major bottleneck while helping protect the performance guarantees attached to equipment selections.
3. I continued contract support through May 2022.

1. I let application engineering, sales, and marketing create validated equipment selections.
2. I let those teams test design changes without sending every request through engineering.
3. I built configurable workflows around complex cooling-tower design rules.

1. We had a maximum 3% error allowance and often needed to work tighter than that.
2. I used the results to support contractual performance guarantees.
3. I turned the test data into production component and software rules.

1. I modeled sound paths, environmental effects, and configurable components.
2. I built a dynamic 3D view of cooling-tower behavior.

1. I worked on heat exchangers, nozzles, drift eliminators, and sound-reduction systems.
2. I helped design test chambers and sped up component testing through rapid prototyping.
3. I turned test-cell data into engineering models, product improvements, and production software rules.

1. I wrote a 90-page engineering design guide.
2. I co-authored two Cooling Tower Institute technical papers.

2019 CTI paper excerpt | 2015 CTI paper excerpt