- Manage an intraday U.S. equities book with $500K in buying power — synthesizing Level 2 order flow, tape, technicals, and real-time news into discretionary trades and disciplined risk management.
- Run an asymmetric, catalyst-driven book (avg winning day ≈ 2× the avg losing day), concentrating max size into a few high-conviction setups while capping risk to a single lockout per ticker.
- Built a proprietary Bloomberg-style market-news feed with Claude-assisted development, web scrapers, and LLM APIs that shaves critical seconds off intra-trade information processing.
- Built a personal operating system (Atomic Habits framework) plus trade-prep and review tooling — including a notes aggregator that cuts ~2 hrs of daily note-taking and an AI coach that flags behavioral patterns from daily report cards.
- Mentored four junior traders on setups, risk rules, habit formation, and structured review; all four went on to record multiple consecutive profitable months in their first year.
Michael Lund
Builder-operator at the intersection of markets, product & AI.
Duke computer scientist and prop trader who turns ambiguity into systems — reading a situation fast, sizing the opportunity, and shipping the tooling that makes the next decision easier. I find the leverage, build the process, and compound it.
Proof of work — built and operated.
Wage Garnishments: What the Company Must Do to Support Them Correctly
A take-home exercise from a Chief of Staff interview process at a payroll-tech company. Dropped into an unfamiliar legal-and-operational domain with about four hours, I mapped what the underlying payroll platform automates versus what the company would own end-to-end, and turned it into a decision leadership could act on — not a survey of options.
What the briefing does
- Cuts to the real problem: "The math is the easy part — the challenge is moving money to the right place on the right clock, and answering the court."
- Gives a phased recommendation: launch the common order type end-to-end now, run everything else on a written manual playbook, and let real volume decide the first thing worth building.
- Is verifiable: every material claim carries a confidence marker and resolves to a tiered source list — statutes cited to the statute, not to commentary.
- Is written for the reader: inline glossary, a capability map, a competitor teardown, per-stakeholder questions, and a first-order processing checklist.
A take-home exercise completed during an interview process — not a role I held, and not legal advice. Company names are redacted.
Crypto Sentiment + Random Forest Trading Strategy
A BTC/ETH strategy that fuses a Random Forest price model with local FinBERT news sentiment and Google Trends data to predict 15-day-average returns, then sizes positions by conviction. Backtested on QuantConnect, it placed 2nd in Duke's FinTech Trading Competition — judged on risk-adjusted return (Sharpe ratio), not raw P&L, so the finish reflects disciplined sizing rather than a lucky bet.
What I owned
- Designed and coded the piecewise "importance" function that converts a predicted move into a confidence weight — blended with a modified Kelly criterion for sizing, and part of the final winning strategy.
- Researched and implemented the Google Trends alt-data signal (pytrends) in the QuantConnect backtest.
- Structured the team into role-based workstreams and edited the final report.
The strategy (team)
- Random Forest direction/magnitude model on 15-day-average returns to cut daily noise, benchmarked against linear regression.
- Local FinBERT sentiment pipeline (in-house, no external data sharing) plus dynamic "working-memory" features.
- Drawdown / liquidation risk controls; the backtest held up through the 2021–22 crypto crash where buy-and-hold fell sharply.
Trading Operating System
Daily P&L is noisy, so I built a personal operating system to separate luck from skill and focus on the behaviors I could actually control. It started as a daily report card and grew into morning prep, end-of-day reviews, weekly pattern analysis, automated reporting, and AI workflows that summarize notes and surface recurring errors.
What it does
- Daily report card tracking thesis, execution, risk management, mistakes, and emotional state.
- Morning prep and end-of-day reviews, plus weekly pattern analysis to catch recurring behavior.
- AI note-summarization that condenses heavy daily note-taking and flags the mistakes I keep repeating.
- Automated reporting on adherence and my green-to-red day ratio, so the system grades itself.
The hard part
Making it rigorous enough to produce honest insight without being so heavy I'd stop using it. I repeatedly cut fields that didn't change decisions, added prompts around recurring mistakes, and adjusted the reports as my trading evolved. After rebuilding my process and moving to a stronger desk, I ran twice as many green days as red over a six-week stretch. The best validation: other traders started asking to see it and adapting parts for their own workflow.
Claude-Powered Market-News Feed
A market-news feed I wired together from web scrapers and language-model APIs that pull and summarize market-moving news faster than I could read through the source. Nobody assigned it — I hit a bottleneck in my own process and built the thing that removed it.
What it does
- Scrapes sources continuously and uses language-model APIs to pull and summarize catalysts as they break.
- Compresses minutes of reading into a glance, shaving critical seconds off intra-trade information processing.
- Set the template for how I work now: see a bottleneck, build the tool that kills it, keep it running.
Built at work — a cleaned-up version will be published on GitHub.
Notes Aggregator
Trading generated more daily notes than I could keep straight. I built a tool that pulls scattered daily note-taking into one structured pipeline, so review actually happens instead of piling up — it reclaimed roughly two hours a day of manual work.
What it does
- Pulls fragmented notes out of a dozen places into a single structured feed.
- Summarizes and organizes the day so end-of-day review is fast and honest.
- Freed up ~2 hours a day that used to go to manual note-wrangling.
Built at work — a cleaned-up version will be published on GitHub.
Ticket-Drop Operating System
Watching a few live ticket drops, I saw the team was running off memory — steps slipped under pressure and money got left on the table. I worked with the founder to turn the whole drop into a repeatable operating system: seven roles, each with a before / during / after checklist so nothing gets forgotten when it's live and fast.
What it defines
- Seven roles end-to-end — Ops Manager, Research Analysts, Traders/Buyers, Tech, Pricer, Inventory Manager, and Fulfillment.
- For each: a role overview, responsibilities, and repeatable before / during / after checklists.
- Clear ownership and hand-offs — who decides, who executes, who prices, who confirms — so a live drop runs like a machine instead of from memory.
Sell-Through Dashboard
I spent a week shadowing a friend's ~20-person ticket-resale business to learn how they moved inventory, then built them a Claude-powered dashboard that models sell-through targets in the weeks before an event — so the team can plan how to release inventory over days instead of dumping it and hoping. It was the first thing I built for them, and it stuck.
What it does
- Models sell-through targets ahead of an event to guide how inventory is released over time.
- Gives the team a planning tool they run on their own — it isn't a real-time system and doesn't drive live buy/sell decisions.
- Came out of a week of shadowing: get inside the system fast, find the one thing that moves it, build the tool before anyone asks.
Related: watching a few live drops, I flagged that the team worked off memory so steps slipped under pressure, and proposed systematizing each person's responsibilities per drop.
Difmo — DJ & Events Company
Once bars reopened after Covid, I started my own DJ and events service company at Duke. I became the resident DJ at Shooters, Duke's main nightclub, and played events for clubs and social organizations across campus — the first thing I built and ran as my own business.
Highlights
- Resident DJ at Shooters, Duke's main nightclub.
- One of my mixes was played at Coach K's Countdown to Craziness, Duke Basketball's sold-out season opener.
- Booked and played events for campus clubs and social organizations — sourcing, scheduling, and delivering the night end-to-end.
Where I've built and operated.
- Built a Claude-powered dashboard for a ~20-person resale business that models sell-through targets in the weeks before an event, giving the team a planning read on how to release inventory over days rather than dumping it; the team runs it themselves.
- Collaborated on-site on live buying decisions during launch week, including the Gracie Abrams and The Chicks ticket drops.
- Advise on buying across the EDM and dance-music market, applying firsthand domain expertise to flag mispriced inventory and demand trends.
- Owned all product deliverables for a cross-functional intern capstone built on Suncor's business needs — user stories, PRD, and roadmap — and ran daily standups to coordinate the engineering team.
- Managed sprint planning in Jira and Confluence and prototyped in Figma, translating requirements into a prioritized backlog.
- Partnered with engineers to ship a full-stack digital prototype, iterating through continuous stakeholder feedback.
- Crafted the pitch deck for a successful Series B round, helping secure $25MM through targeted market research and product strategy.
- Built a 50-slide Confidential Information Memorandum (CIM) giving detailed insight to prospective investors.
- Ran financial analysis to inform strategic decisions on performance and growth trajectory.
- Established a strategic partnership with trading-software company TrendSpider, driving customer acquisition and funded-account growth through an incentivized-funding program.
- Launched and managed targeted digital and social campaigns with UTM tracking, using Google Analytics to evaluate performance and refine targeting.
Skills, credentials, and foundation.
Skills & Tools
Education
Judgment, sized and executed.
Three setups where a prepared thesis met a live catalyst — mapped in advance, executed with rules-based risk.
Read Tesla's record valuation as resting on the Musk–Trump alliance. Mapped retaliation and reconciliation scenarios in advance, then took three independent max-size entries — one per escalating catalyst — as the feud erased ~$152B (~14%).
With gold gapping to all-time highs (~$5,600/oz) a third straight session, prepared a defined-risk reversal short anchored to VWAP and the prior high. Used the gold vol index rolling over to confirm exhaustion; held to the bounce as gold flushed ~$380 (~7%) in 30 minutes.
After "Liberation Day" tariffs, built a country-by-country map pairing each rate with its most exposed equities. When Trump posted Vietnam's offer to cut tariffs "to ZERO," recognized within seconds it removed RH's largest overhang while participants sat offside — and executed the prepared thesis.
Figures reflect realized P&L on the noted risk lockouts. Past performance is not indicative of future results.
A decision-maker who ships the systems behind the decisions.
I sit in a seat that pays me to be right under pressure. As a discretionary trader at Trillium, I synthesize order flow, tape, charts, and breaking news into high-conviction bets — concentrating size into a few setups while keeping risk tightly capped. It's judgment as a daily practice.
But the part I care most about is the compounding. When I hit friction, I build my way out of it: a Bloomberg-style news feed that shaves seconds off every trade, a notes aggregator that reclaimed two hours a day, an AI coach that flags my behavioral leaks. I use a computer science degree from Duke and a "vibe-coding" workflow to turn one-off problems into permanent leverage.
That combination — sharp judgment plus the instinct to systematize — is what I bring to a team. I read the situation, own the ambiguous work nobody else has picked up, and leave behind process that outlasts me. Increasingly that looks like a chief-of-staff / operator role: the person who turns a founder's intent into things that actually run.
Let's talk.
Open to chief-of-staff, operator, trading, and product roles where sharp judgment and a bias for building both matter. The fastest way to reach me is email.