What I'm Looking For
The Work
- Data-heavy problems — Spatial data, scale challenges, complex queries, messy real-world data
- Ambiguity welcome — Vague requirements that need shaping into working systems
- Greenfield and rescue missions — Building from scratch or fixing what's broken; both are satisfying
- End-to-end ownership — Problem to production, the whole arc. Not a slice, not a handoff
- Hands-on, the hard parts — I stay in the codebase. Architecture without keystrokes isn't for me
- Impact over tickets — Solving problems that matter, not just closing JIRAs
The Environment
- Remote-first — Async collaboration, flexible hours, results over presence
- Real autonomy — Small teams, or bigger teams with real autonomy. I do best when I can own outcomes without layers of permission
- Ownership with trust — Give me the problem, the context, and the stakes, and I'll drive it end to end
- Bias toward action — Fast-moving, minimal ceremony
- Engineering as investment — Companies where engineering drives value, not just supports it
The People
- Hands-on leadership — I like mentoring and fostering strong engineers by building alongside them, not drifting into pure management
- Leverage through example — I raise the bar, unblock people, and help a team do better work while still doing the hard technical parts myself
- Trust over titles — High-trust teams that ship; no theater, no hand-holding
Not a Fit
- Layers of approval before anything ships
- Owning a sliver instead of the whole problem
- Pure maintenance with no room to build
- "Architect-only" roles where I stop writing code
- "That's not your job" culture
Let's Talk
Sound like your team? Let's talk.
Click to reveal emailnick.a.march@gmail.com