Justin Washington
Product Manager
Justin Washington is the professional I have chosen to interview regarding architecture. He is a product manager at Apple, a multinational technology company. His role contributes to the technology, media, and entertainment industries, with one of his meaningful contributions relating to video entertainment to engage specific audiences.
Professional Interview
Question 1: What made you want to follow your current career path?
Question 2: What's something you wish you knew before you started?
Question 3: What challenges have you had to overcome?
Response
Q1: "Interestingly, I didn’t start out thinking I would become a product manager. I’ve always been someone who loved building things and being creative. ... I studied engineering in school, which taught me how systems are built and how to solve problems. Over time, I realized product management sits right at the intersection of technology, creativity, and people. As a product manager, you’re helping shape ideas into real products that millions of people can use. I loved the idea that I could combine technical thinking, design, storytelling, and collaboration to help create experiences for customers. That combination is what ultimately pulled me into the field."
Q2: "One thing I wish I knew earlier is that product management is less about having all the answers and more about asking the right questions. When people first hear “product manager,” they sometimes think you’re the person with the big ideas or the one who tells everyone what to build. In reality, a big part of the job is listening carefully to customers, engineers, designers, and partners, and helping the team figure out the best path forward together."
Q3: "One challenge early in my career was learning to believe that I belonged in rooms with very smart and accomplished people. When you work in tech, you’re surrounded by extremely talented engineers, designers, and leaders. Early on, it’s easy to feel like you need to prove yourself constantly. Over time, I learned that everyone brings something unique to the table. My strengths (being creative, understanding people, and thinking about the bigger picture of how products fit into people’s lives) were just as valuable as anyone else’s technical expertise. Another challenge is that product work often involves ambiguity. Sometimes there isn’t a clear answer, and you have to help your team move forward anyway. Learning to navigate uncertainty is a big part of the job."
Connection
Q1: Architects also need a strong interest in how things are built and how systems function. Architects use creativity to design spaces, but they also rely on technical knowledge such as engineering principles, materials, and construction methods. Washington's comment about combining creativity with technical thinking is especially relevant because architecture requires both artistic vision and logical planning. Architects design attractive spaces while making sure they meet building codes, fit the environment, and serve the people using them. Like product managers, architects must transform ideas into real projects through teamwork and careful planning.
Q2: Architects do not simply create designs based only on personal ideas. They must first ask important questions such as: What does the client need? What is the budget? How will the building be used? What environmental concerns need to be considered? Listening is one of the most valuable skills in architecture. If an architect ignores input from others, the final project may not meet the client’s needs or may have construction issues.
Q3: Architecture is a demanding and competitive profession. Students and professionals often work alongside highly skilled designers, engineers, and construction experts. It is common to feel pressure to prove yourself, especially early in a career. His point about recognizing personal strengths is important for architecture because different architects contribute different talents. Some excel in creative design concepts, some in technical drawings, some in sustainability, and others in communication with clients. The uncertainty he described also exists in architecture. Many projects face changing budgets, zoning restrictions, weather issues, material shortages, or client revisions. Architects must stay flexible, solve unexpected problems, and make decisions even when every answer is not clear.