VP of Technical Product Manager – $200K/year – Crossover
The SVP of Technical Product Management is responsible for building and managing a team of VPs of Technical Product Management. Their primary deliverable are highly technical product specs that make the Important Technical Decisions (ITDs) for a product.
What sets SVPs of Technical Product Management apart is their ability to:
Simplify complex architectures and decisions
Hire and manage a team
Both SVPs and VPs must learn and use a wide array of existing third-party technologies. They must know when and how to design new data structures and algorithms. They must have the experience to understand the fatal impact that poor product design decisions can have and strategies on how to avoid them. And finally, they must be able to communicate their technical decisions in a clear, written manner so that other people on the team may follow their direction.
Unfortunately, most companies do a terrible job at this. They do not do the hard work up front and they start coding too early. They don’t invest in developing expertise and innovation, they build roadmaps based on what competitors are already delivering or on the tactical needs of the sales team. Their technical product managers focus on UIs and mockups instead of the product’s core data structures and algorithms.
If this resonates with you, and you have basic management experience combined with a track record of owning fundamental architecture decisions, you should apply.
For the SVP position you must have 5+ years experience in this role at one of the following types of companies:
– A Top 100 software development company such as Microsoft, Google, Oracle, Facebook, etc.
– A leading financial institution such as Goldman Sachs, Citi, HFT Trading firm, etc.
– Be one of the top 5 technical architects at a software outsourcing organization
If you feel as I do, and you want to learn more in a year than most will learn in a decade, you should Apply.
Software products ultimately ‘win’ or ‘lose’ based on wisdom, simplicity, and technical insight.
Successful products are built when a clear understanding of the core value proposition is reflected into the core technical design. This is done by making a series of important technology decisions. These decisions determine whether the product delivers unique value to customers and can change the code/time required to implement by 10X.
Technical Product Managers must learn and know when to use a wide array of existing third-party technologies. They must know when and how to design new data structures and algorithms. They must have the experience to understand the fatal impact poor design decisions can have and know how to avoid them.
It's hard work but has enormous impact. When done correctly it creates huge customer value, a differentiated product from competitors, clarity for the engineering team, and more.
Unfortunately, most companies are terrible at this. They don’t do the hard work upfront and code too early. They don’t invest in developing expertise and innovating. Instead, they build roadmaps based on what competitors are delivering. TPMs focus on UIs and mockups instead of unique and valuable core data structures and algorithms.
Does this resonate with you? Do you have experience making the fundamental architecture decisions of software products? We encourage you to apply. You may have been a CTO or Technical Co-Founder of a company. You may have been responsible for the fundamental design decisions and technical choices for a larger scale organization.
If you see the world in the same way – and want to learn more in a year than most will in a decade – we urge you to apply.
Senior Technical Product Managers make the most impactful technical decisions for software companies.
As a Senior TPM you will be responsible for identifying the core functionality of a product and creating a very thoughtful design. This requires an understanding of the product’s core value proposition with our understanding of the way that software systems are built. You need to learn new technologies and describe when they should be used. You will be expected to create simple designs that focus on making and explaining the most Important technical decisions while leaving out low-impact details.
For example, even some of the most common technical decisions such as “which database to use” are often done without enough upfront consideration. When, why and how should we use a relational DB, versus noSQL, versus a key/value store, an in-memory DB, or another choice? When and in what way should we use micro-services? What about the many available options and configurations of Machine Learning tools? How will we deliberately design the best APIs?
Those are the more straightforward decisions. Decisions with greater impact include what the core data structures of the application will be and how to best apply existing or new CS algorithms to a given problem space.
– Identify the most important technical decisions that must be made given the strategy and goals for a product
– Build technical expertise (not industry domain expertise) in order to understand the best available options for a product design
– Select the best available existing technology and stipulate the design constraints that will accompany it
– Innovate the design of new data structures and algorithms where needed
– Communicate these decisions, and the reasons for them, in a clear written document (tech spec)
||Dubai, United Arab Emirates
التقدم للوظيفة الان
أنشئ سيرتك الذاتية الآن و تواصل على الفور مع أكبر و أفضل الشركات اون لاين. إنشائك لسيرة ذاتية على موقع المازن.كوم هي الوسيلة الأكثر فعالية للحصول على الوظيفة VP of Technical Product Manager – $200K/year – Crossover بكل سهولة الان مجانا.