I’m Jason McCullough, a product engineer with a strong frontend background, based in Glastonbury, Connecticut.
I started my career in agency development, building websites for different clients, industries, and technical environments. That work gave me a strong foundation in frontend development, responsive design, CMS platforms, estimation, and working closely with designers and backend developers. It also taught me how to get up to speed quickly, work within constraints, and turn a design into something that works reliably.
Moving to a product team changed how I approached the work. Instead of building a site, launching it, and moving to the next client, I was working on products that continued to develop over time. I could see how decisions affected customers, business operations, and the underlying system long after a feature was released. I became more involved in working through requirements, identifying gaps, creating wireframes and prototypes, and helping decide how a feature should work before building it.
Over time, those product responsibilities became a larger part of my role. My work now often begins with an idea or a problem rather than a completed design. I help determine what needs to be built, map out customer and operational workflows, work through UX and technical tradeoffs, and turn the result into a functioning product. Frontend development remains one of my strongest skills, but it is now part of a broader process that includes product planning, architecture, prioritization, and implementation.
I’m especially useful when something is still being figured out. I’m comfortable taking incomplete requirements, asking the questions that expose what is missing, and creating something concrete enough for a team to evaluate. I also look beyond the customer-facing interface. The product has to make sense for the people using it, the people operating it, and the developers who will need to maintain it.
I work well with founders, product managers, designers, engineers, and business stakeholders. I ask questions, challenge assumptions when something does not add up, and help move the work from a broad idea toward clear decisions and a practical implementation.
I’m looking for a role where I can contribute throughout that process: helping shape the product, working closely with design and engineering, and remaining directly involved in building it. I want to join a team that values engineers who can participate in the entire process rather than joining only after every important decision has already been made.
Outside of work, I spend a lot of time hiking around Connecticut with my dog, Max. I enjoy exploring new trails, foraging for ingredients to cook with, and embarrassing my daughter on a regular basis.