about
I |> build software |> develop teams |> educate.
skillz
- javascript
- react
- ruby
- ruby on rails
- elixir
- phoenix
- node
- graphql
- nextjs
- now
- docker
experience
echobind
engineering team lead
skills utilized
- react
- node
- ruby on rails
- business development
- team development
- mentorship
- graphql
- now
story
After 2.5 years of working with the team at Echobind, I was promoted in january 2019 as engineering team lead. My promotion was based on exemplary experience around taking ownership on projects, establishing a good rapport with existing clients and ensuring we focused on building the right features for a product. These implicit responsibilities combined with my passion for mentorship and collaboration made it a great fit to redefine my role to better provide Echobind with the appropriate services needed.
role and responsibilities
- Hands-on technical leader to 5 software engineers
- Mentor reports in all aspects of software engineering
- Collaborate w/ product management and managing partners to define customer needs, and to identify, define and scope solutions
- Lead engineering team in delivering customer value incrementally
achievements
- Established consistent weekly 1 hour 1:1 with all direct reports
- Created the technical internship program, with 2 engineers hired as associate engineers full-time
- Brought in 3 new clients (1 Enterprise level client and 2 startups)
- Helped improve client relationships on 2 established clients, delivering projects under budjet and on time
senior software engineer
skills utilized
- emberjs
- ruby on rails
- elixir
- team development
- mentorship
- business development
story
After being in the product world for some time, I wanted to explore the consulting industry with folks I knew in the greater boston area. It was a natural fit to join Echobind since I was working in the same technologies. the role would give me the exposure I wanted in healthcare and fintech - so I decided to join the team as their first hire.
role and responsibilities
- Work closely with managing partners to define requirements and scope projects
- Ensure quality code and standards were followed on each project
- Develop and architect various frontend solutions using emberjs and react
- Maintain existing projects in rails and elixir
achievements
- Improve the rendering time of various applications by 5 - 10x
- Created two-way messaging system for healthcare client
- Upgraded ember for 2 of our exisiting clients
- Attended and represented Echobind at two industry conferences
customer.io
senior front-end engineer
skills utilized
- emberjs
- ruby on rails
- golang
- microservices
- team development
story
After having worked at 3 fairly large companies (5k+ people), I wanted a change of pace - one where my work would have an immediate impact while having a long-term outlook on improvement. Customer.io was growing and needed a frontend engineer and after my project was shutdown at McGraw-hill - the timing couldnt have been more perfect. They were using ember, rails and golang - all technologies that I eithr already knew or wanted to work with more. So I made the switch and loved every moment of it.
why did I leave?
I felt I had outgrown the position. I wanted to officially move towards a lead/coach position, something the company couldn't offer at the time. I had wrapped up my projects and given the team enough resources to succeed and so it was a good time to look for a new opportunity.
role and responsibilities
- Worked closely with Colin and product to scope incoming projects
- Collaborated with backend team develop internal API endpoints
- Lead the development of the frontend architecture
achievements
- Worked with our designer to establish a resuable component library
- Improved first initial page load by removing unused CSS across the app
- Created a consistent data fetching pattern to ensure we always had live data
- Incrased code coverage from 30% to 82%
- Hired two senior software engineers
mcgraw-hill education
software engineer
skills utilized
- emberjs
- ruby on rails
- team development
- event sponsorship
- mentorship
- training
story
I had started in the agency world and was tired of it - I wanted to work on a product. During my search I stumbled upon a recruiter who was hiring for a new office being built in Boston for an ed-tech company - McGraw-Hill Education. This struck me immeidately since I always wanted to be a part of improving education for everyone. The hiring manager and I immediately connected. After a successful initial pairing session I received and offer and joined the new office to help build out the new engineering team!
why did I leave?
My project was shut down after 2 years. The company shifted to data analytics using technologies I was just not interested in. I did stay to try it out - but ultimately it left me bored and i wasn't producing the quality of software I wanted to build. So I made the decision to leave due to the shift in company priorities.
role and responsibilities
- Develop and build the engineering team in the boston office
- Continue the research and development of educational collaborative software
- Collaborate with vendors to develop needed libraries
- Participate and represent McGraw-hill education at leading tech conferences
- Provide consultation on acquired strategical partnerships
achievements
- Hired a team of 13 software engineers
- Sponsored McGraw-hill education as diamond sponsors (funded 10k to event)
- Acquired vendor for the research and development of an analytics platform
Want to see more xp? Check out my linkedin
education
rochester institute of technology
personal accomplishments
- Multiple publications on personal and echobind blog
- Author of HTML5 iPhone Web Application Development
- Various meetup talks in Boston (EmberJS, Boston JavaScript, etc...)
- Grand LIA for American Express Small Business Saturday application