Dan Mathieson
Live Demos

Strengths and Weaknesses

Strengths

It's easier for anyone to discuss their strengths, and I'm no exception. I've always been one of the hardest-working and technically proficient members of my teams. Here are three key strengths that stand out, but I'm confident I can contribute to your team, project, or company in many additional ways:

  1. Teaching - I have a knack for simplifying complex concepts, making them easy to grasp for diverse audiences. This skill has proven beneficial at FanDuel, where I regularly explained intricate aspects of the Daily Fantasy ecosystem to executives. At Google, I rapidly became a go-to resource for coworkers seeking to improve their use of internal tools. At Action, I dedicated significant time to educating others, from explaining business dynamics to executives, teaching python to my team, or informing the rest of the company about the financial impacts of their work. I have also been teaching coding to children in my free time. You can count on me to uplift the team's collective knowledge.
  2. Curiosity - I'm intrinsically driven to learn and understand. Whether I'm delving into AI/ML and blockchain engineering, listening to tech, science, and business podcasts, or learning new skills to solve problems, my curiosity is always at the forefront. When I started at FanDuel, I didn't know SQL; now I'm an expert. My curiosity, combined with my teaching ability, assures you that our collaboration will foster a continuous learning environment.
  3. High EQ - While I don't consider myself the best manager in the world, I know that people enjoy working with me and for me. I am a committed team player who cherishes a strong culture and understands the importance of emotional intelligence in the workplace. This is an area where many might claim proficiency, but I truly excel at understanding and empathizing with others.

Weaknesses

Since my departure from the Action Network in October 2022, I've had ample time to reflect on areas where I can improve. These self-identified growth areas are more instructive of what I'm looking for in a future role than simply listing my strengths. While I believe I would thrive in a role that aligns with my strengths, it's important that you understand my areas of potential improvement first:

  1. People Pleasing - While it might sound cliché, my propensity to take on more tasks than I could effectively manage was a key challenge during my tenure as a manager at Action. This tendency initially emerged from my enthusiasm to assist others and solve problems, and it was reinforced by early career successes. However, the negative consequences became apparent when my team became overloaded due to my inability to say 'no'. In a role with a more focused scope or clearer responsibilities, I am confident that I can address this issue effectively.
  2. Over-Engineering - I have a passion for delivering high-quality, polished products. However, this passion can be a hindrance when faced with tight deadlines. The analyst in me hesitates to deliver recommendations without a comprehensive data analysis, even when circumstances require swift action. This is an area I'm continuously working on improving.
  3. Prioritizing People over Ideas - It's challenging for me to separate the merit of an idea from my assessment of the person proposing it. I've learned that great ideas can come from unexpected sources, and focusing too much on perceived importance can lead to overlooked opportunities. While company culture plays a significant role in addressing this issue, it's something I need to work on personally.

Tools & Personal Productivity

Notion as an Operating System

I'm a genuine Notion power user, not in the sense of having explored every feature, but in the sense that I've rebuilt how I run my life inside of it. My personal Notion workspace spans multiple interconnected databases: a daily journal with templated prompts and mood/energy tracking, a personal CRM for staying in touch with people I care about (relationship history, next contact dates, notes from conversations), a workout tracker with historical logs and progressive overload metrics, and a daily task and priorities system that rolls up into weekly and monthly reviews.

These aren't standalone pages. They're relational databases with linked views, filtered rollups, and cross-database references (the same structural patterns I use professionally). My personal CRM has a "Companies" and "People" database linked exactly the way a sales CRM would be, with relationship stages, last contacted dates, and context notes. My workout tracker has an Exercises database linked to a Logs database so I can query personal records and volume trends over time.

The distinction I draw between personal and professional Notion use is tooling philosophy: for personal use, I lean into Notion's native automation and database features because iteration speed matters more than control. Professionally, I prefer Python when the problem requires custom logic, reliability, or integration depth that low-code can't deliver cleanly. Knowing both ends of that spectrum, and when to use each, is the actual skill.

Notion-native tools I use regularly: linked databases, rollups, filtered views, templates, relation properties, formula fields, and Notion AI for summarizing and drafting within pages.

JavaScript and Frontend Engineering

I have extensive, production-level JavaScript and frontend experience, centered on this personal website. Over two years of active development, I've built and rebuilt it through four distinct architectural eras - most recently a full agent-first rewrite using Next.js 15, React 18, TypeScript, Clerk auth, and Neon Postgres. The current site includes streaming API responses via Server-Sent Events, agentic tool loops using the Claude Agent SDK, complex async state management, CSS Modules component architecture, and a live agent that can search my experience, analyze job descriptions, and schedule meetings. I also built DocWow (a healthcare AI application with live demo on this site) in Next.js with pdfjs-dist, pixel-precise citation UX, and Lambda/S3/DynamoDB backends; and integrated QuickSight dashboards into Next.js customer portals at Thoughtful via iFrames. Frontend development is not a gap for me - it is one of the primary mediums I use to ship production AI systems.