• 🎯 I'm currently looking for a permanent, fully remote, W-2 role — CTO, VP Engineering, Chief Architect, Principal, or Director. Details here.
• 🔭 I’m FULLY REMOTE from Seattle, WA (PST). 🚀
• 🌱 I’m a daily learner, who tries to learn something new every day. Also Trying to get more sleep. 😴
• 👯 I’m looking to collaborate on ways to make the world better, while also looking for ways to share in the success I create for others.
• 🤔 I’m looking for help with learning to be a better human, engineer, and friend. I want more friends.
• 💬 Ask me about distributed systems, browser internals, production AI, agentic systems, or the weird things I've learned after 25+ years of building software.
• 📫 How to reach me: LinkedIn if it's about work, twitter for everything else.
• 😄 Pronouns: he/him
• ⚡ Fun fact: Most programming languages use the same patterns to define their internals.

• I'm a long-term software craftsman with broad, T-shaped experience who is still passionate about expanding my skills, helping my team succeed, and communicating complex technical ideas clearly.

• Prior Fortune 50 Tech Executive.
• Distributed Systems
• Artificial Intelligence (Generative A.I. Large Language Models aka LLM, LLM Orchestration, LLM Agents)
• Web Browser Development (C++/Chromium/Blink/Ninja)
• REST/GraphQL and Web API Architecture
• Language Agnostic Full Stack, Any Platform, Principal Software Developer.
  • C, C++, Python, Rust, C#/DotNet, Assembly, Java, GoLang, Elixir/Erlang, SQL, JavaScript and more are all interesting to me.
  • I started with hardware pin-outs and worked my way up the stack to write web microservices that scale to web scale.
  • JavaScript on NodeJS is generally not my first choice, but it has its uses when you need to re-live the glory days of 1990's PHP.
  • I have prior PHP (LAMP/LAPP) experience.
• Open-minded, but prefers PostgreSQL or MySQL when the requirements say we need an ACID Compliant DB as these are battle tested and I trust them.
• Agile, Test Driven Development (TDD), Behavior-Driven Development (BDD), Domain Driven Design (DDD), all tools in a toolbox, and like most craftsmen I know of a lot of tools. The secret is to not use a screwdriver to hammer a nail, but if you hammer the screwdriver you can carve wood. I maintain both my tools and my skills with them.
• Very Interested in Accessibility/a11y and wants to find a more formal way to support that. Extremely limited by lack of access to the tools due to their cost.
  • We live in a broken world when it costs nearly $16,000 to buy an 80 character braille screen reader.
  • How would you use your company's main product while wearing a full blindfold?
  • How would you use your company's main product while wearing full ear plugs?
  • It is my firm belief that accessibility is part of good engineering. Building systems that work for more people improves the product, exposes assumptions, and makes teams think more carefully about how humans actually interact with technology.
• Business Optimization and Business Process Optimization.
  • My engineering background includes executive leadership, technical strategy, architecture, and understanding how technology decisions affect cost, risk, productivity, and business growth.
• I'm good at changing my mind based on the available data.

• What I bring: prior Fortune 50 tech executive experience, distributed systems at web scale, browser internals in C++ on Chromium/Blink, and LLM orchestration and agents. I started at hardware pin-outs and worked my way up to microservices that scale.
• I'm 100% remote due to family obligations and only consider roles that do not require travel or commuting to an office.
  • I have others to think about. I also found a peace and personal productivity level that I never want to lose. I'm a better member of my team as 100% WFH.
  • A car is an expense and use of time I only needed for work. My current goal is to live a "car free" life.
  • The hours I save by not commuting give me more time, energy, and mental resources for both my life and writing better code.
• I'm committed to remaining fully remote.
• Running a fully remote team well is a real leadership skill, and it's one of the things I evaluate a role on.
• I value leadership teams that set realistic expectations, communicate clearly, and create an environment where engineers can do their best work.

• The words "plumless" and "buckeroo" both have the same crc32 hash of 0x4ddb0c25 and will thus create a hash collision.
• Please do not contact me about your electronic currency, web3, or blockchain startup. I actively avoid any request that I apply to such roles.
  • Hash collisions are a fundamental cryptographic property that is often misunderstood when evaluating blockchain systems.
  • I have strong concerns about systems that use technical complexity to obscure risks from users who cannot reasonably evaluate those risks themselves.
  • I don't consider Web3 a sound technical foundation for the kinds of systems I want to build.
  • I don't consider NFTs a sound technical model for durable ownership when the underlying asset or metadata is hosted off-chain. Ownership of a token does not guarantee continued availability of the referenced asset, and if that external resource disappears, control of the token cannot restore it. This dependency has already caused real-world failures: https://www.theverge.com/2021/3/25/22349242/nft-metadata-explained-art-crypto-urls-links-ipfs

Thanks for your interest. I'm currently looking for a permanent, fully remote, US W-2 role where my Principal-level engineering and technical leadership experience is a strong fit.

• I'm based in Washington State and work remotely on Pacific Time.
• My preference is permanent employment rather than agency contract work, sub-vendor arrangements, or multi-tier engagements.
• For direct consulting engagements, I consider architecture reviews, technical due diligence, interim CTO/VP Engineering work, and hands-on technical strategy during critical builds.
• For agency engagements, I understand the economics of technical staffing and expect transparency around the end client, engagement structure, bill rate, agency margin, and compensation.
• Please include the compensation range and working-hours expectations when contacting me.

I have additional information for recruiters, including how I evaluate opportunities and the information I need before proceeding: https://www.DuaneFKing.com/recruiters