Software Engineering Manager · Rochester, NY
I build high-performing teams, deliver reliable software, and explore what AI-powered development makes possible next.
Solution Lead and Software Engineering Leader with 13+ years of experience spanning engineering, architecture, and leadership. Currently at Mindex, leading teams to deliver reliable software and payroll compliance for a long-standing Paychex product in a regulated environment. Known for improving delivery predictability, reducing dependencies, and aligning engineering execution with business priorities.
Certified ScrumMaster (CSM) and advocate for Agile practices — with a deep interest in how AI is reshaping the way teams plan, estimate, share knowledge, and continuously improve. I believe AI presents an opportunity to rethink how teams deliver value while preserving the principles that make Agile effective. That intersection of emerging technology and disciplined delivery is where I focus my energy.
I believe predictability is a leadership responsibility, not a project management artifact. I build the conditions for reliable delivery: clear processes, visible dependencies, and a team that understands not just what they're building, but why it matters. When friction shows up, I treat it as a signal to improve the system — not push harder.
The best investment I make is in the engineers around me. I spend real time on career development, not just annual reviews — understanding where each person wants to go and removing the obstacles between here and there. I've built mentoring programs from scratch and coached engineers into senior roles. Growing people isn't adjacent to the work. It is the work.
I'm actively building AI-enhanced workflows into how I lead and how my teams operate — from planning and knowledge sharing to code quality and delivery effectiveness. I'm not waiting for AI to transform engineering. I'm in the middle of that transformation right now, experimenting with what works and bringing those practices to the teams I lead.
ROC IT Solutions was acquired by TraceLink LLC in August 2018.
“Eric was placed into a difficult situation from the start, navigating a team environment that hadn’t yet found its footing. Rather than retreating, he leaned in. His communication was consistently clear, he demonstrated the technical depth the role demanded, and he brought a collaborative spirit to every decision-making conversation. What impressed me most was his genuine ‘we’re in this together’ mentality — he never treated the challenges as someone else’s problem. That combination of steady leadership and forward thinking is rare, especially under pressure.”
“Eric is an extremely dedicated employee. He was dedicated to helping the team deliver quality work in a timely manner but also in making sure his team had everything they needed, in and out of the office. He cares about the product he is working on but also cares about all those reporting to him. When we were in the trenches trying to meet a deadline, he was always right there with us. He was the best manager I’ve worked with.”
“Eric brings an infectious enthusiasm to every project he undertakes. He consistently handles challenging situations with a positive attitude and professional demeanor. While his resilience is a core strength, what truly stands out is his authenticity and trustworthiness. His genuine approach to collaboration and ability to build strong relationships across teams has made a lasting impact on our organization.”
I taught 2D Animation and Algorithmic Problem Solving in RIT’s Interactive Games and Media department. Standing in front of a room and making complex ideas land clearly is something I carry into every technical conversation. I believe deeply in passing knowledge forward — it’s one of the reasons mentorship has always been central to how I lead.
My graduate work at RIT focused on graphics programming and game engine development — systems-level work that demands performance, precision, and architectural thinking. That foundation shapes how I evaluate technical tradeoffs today, and it’s a reminder that I came up through the code before I came up through the org chart.
Outside of my day-to-day leadership work, I’m actively experimenting with AI-powered development workflows — exploring how agents, tooling, and prompt engineering can change what’s possible for engineering teams. This isn’t a side interest. It’s where I think the next decade of software engineering is headed, and I want to be ahead of it.
These are personal projects — built outside my day job using my own AI Engineering Platform. Each one is a real problem I wanted to solve, built from idea to shipped using agentic AI workflows.
Every AI coding session starts cold. You re-explain the project, reconstruct what was in progress, and lose the idea you had on your phone. I built this to solve that — not as a productivity app, but as a system.
Every workstream is a GitHub Issue. Lifecycle state lives in labels — not in memory, not in a session. Any client that can run gh issue list has full project context.
review backlog. bootstrap WS-001. promote idea. The same command on the same state always produces the same output. Determinism builds trust.
An idea costs nothing to capture and carries no WIP obligation. A workstream is a commitment. Conflating the two means either losing ideas or creating chaos.
This website was built using the platform — every section, bug fix, and feature tracked from idea to shipped. 15+ workstreams and counting.
$ review backlog SHIPPED 15 workstreams ACTIVE WS-016 Personal Work section IDEAS 0 pending $ bootstrap WS-016 portfolio → Requirements done → Architecture done → Backlog done → Implement running → Validate — → Ship —
Most velocity trackers give you data without context. I built this to answer the questions that actually matter in sprint planning: how much can this team deliver this sprint given who’s out, who’s on support rotation, and how each person is allocated?
Every sprint tracks PTO, support days, and allocation per member. The tool computes what the team would have delivered at full capacity — separating a slow sprint from an interrupted one.
Monte Carlo simulations compute P50/P85/P95 delivery windows for release milestones. Not a best-guess date — a probability distribution backed by the team’s own sprint history.
Agent Buddy runs inside the Electron desktop app on a bundled Ollama instance. No API key, no cloud dependency. Injected with sprint history and metrics for context-aware planning conversations.
Click to expand
Click to expand
Click to expand
Click to expand
Open to new opportunities and conversations. Send a message using the form.
Your message has been sent. I'll be in touch soon.