Jay Allen Interview
1. What originally drew you to web development, and how has your focus changed over time?
Jay developed an interest in technology and computers at a young age and was naturally drawn to programming. While he explored traditional programming early on, it was the visual and interactive nature of web development that made the work more engaging and ultimately kept his interest. After earning a bachelor’s degree in business, he decided he did not want to pursue a generic business career. He returned to NWTC to take web and technical courses while working part-time in academic support roles. Over time, his focus shifted from learning how to code to understanding how technology serves users, departments, and organizational goals.
2. What types of projects or clients do you usually work with, and which technologies do you rely on most?
Jay primarily works on internal projects serving different departments within the college. His work is largely centered around .NET and C# applications, with occasional front-end responsibilities involving HTML, CSS, and JavaScript. In addition to collaborating with coworkers and internal stakeholders, he also works with outside vendors when projects require external support. His role often involves balancing technical requirements with business and departmental needs.
3. What tools, software, or CMS platforms do you use most often in your daily workflow?
Jay works primarily in a .NET development environment, using Visual Studio for C# development. He relies on Git and GitHub for version control and collaboration across teams. Within the institution, content management is handled through Microsoft-based systems, such as SharePoint, which align with the college’s broader Microsoft and SQL Server infrastructure. His work is primarily performed on Windows-based systems, and he occasionally uses command-line scripting as part of his workflow.
4. Can you walk me through your typical development process—from client request to final deployment?
Jay approaches development from a high-level lifecycle and analyst perspective. He begins by understanding how a department or business unit operates and how they want the software to function. From there, he discusses alternative solutions, design considerations, and tradeoffs with stakeholders. Communication occurs daily or weekly depending on project size. Development includes testing, iteration, and change management, with frequent check-ins to ensure everyone remains aligned throughout the process.
Direct Quote:
- “Make sure you’re doing projects for people, not to them.”
5. How does your company or team collaborate on projects between developers, designers, and clients?
Collaboration occurs through email, regular check-in meetings, and shared tools. For larger projects, Jay’s team uses Figma for design collaboration and GitHub for issue tracking and project coordination. Collaboration often extends beyond developers to include designers, business stakeholders, and outside vendors, ensuring that technical and non-technical perspectives are considered.
6. What’s the biggest challenge you face as a web developer, and how do you handle it?
Jay identified communication and project management as the biggest challenges in web development. As projects grow in scope and teams expand, the difficulty shifts from technology itself to ensuring everyone is aligned on expectations, design, and outcomes. He emphasized the importance of minimizing surprises and moving forward together as a group, noting that strong soft skills play a major role in successful development.
7. How do you stay current with evolving technologies in web development?
Jay stays current by engaging with blog posts, podcasts, paid training platforms, and conference opportunities. He mentioned structured learning resources such as Front End Masters and noted that networking played a larger role earlier in his career. He views staying current as an ongoing responsibility that requires consistent effort.
8. What skill, language, or concept do you wish you had learned sooner in your career?
Jay expressed that learning source control earlier would have been highly beneficial. He also emphasized the importance of critical thinking and communication, noting that technical skills alone are not enough to succeed in collaborative development environments.
9. What skills or traits do you think separate a good developer from a great one?
According to Jay, great developers are able to evaluate problems from multiple perspectives, including code quality, user experience, and business value. They understand tradeoffs, avoid overengineering, and focus on delivering meaningful solutions. Strong problem-solving skills and the ability to recognize when a solution is being overthought are key traits.
10. What advice would you give to a current web development student preparing to enter the industry?
Jay encourages students to show excitement, curiosity, and a willingness to learn. He emphasized that it is okay to ask “dumb” questions and invest extra effort early in their careers. He also stressed the importance of remaining flexible, avoiding rigid thinking, and developing interpersonal skills alongside technical abilities.
Closing Insight
Jay expressed long-term satisfaction with his career, noting that despite the challenges of constant learning and change, he still enjoys both the work and the people he works with.
Direct Quote:
- “I feel really lucky to have found both the type of work I do and the people I get to do it with.”