FAQ #7: What do other engineering leaders say about ZOOM engineering?
Here are answers to the same questions, but from a group panel: Matěj - Director of Engineering, Anton - Senior Java Developer, Radek - Technical Leader, and Jindřich - Technical Leader
- We are all excited about the new product strategy with regards to persistent queues, stream processing, and NoSQL databases as well as cloud platforms and a true DevOps process. We have an opportunity to upgrade our existing architecture in a way that applies development best practices.
- We are all passionate about modern, cloud-native architectures like microservices, stream oriented design, data-driven analytics applications, and containers.
- We would recommend ZOOM to colleagues for many, many reasons: automated continuous integration, mandatory code reviews, automated E2E tests, research, periodic hackathons, innovation inside a “legacy industry,” 1600+ on-premise implementations over the world, an international company where English is required and used on a daily basis, a relatively flat company structure (get to meet and actually talk to the CEO who is up to 3 managers above you), flexible work schedule (with work from home support, agile development, JIRA, physical Kanban board, single PO, single backlog, stand-ups, customer reviews, retrospectives, grooming, planning, an in-house UX designer, and transparent product decisions and roadmap based on market research.
- It’s always nice to build something that users love while also being very proud of an effectively engineered solution. While nothing is perfect, our customers like what we build.
FAQ #8: What do executives say about ZOOM engineering?
First, engineers who are considering ZOOM should know I am a geek at heart—my undergrad degree is in biochemistry and molecular biology. I truly love and respect great engineering. Second, we are going to apply technology to our industry in a way that has never been done before and continue our strong growth track record. Three, we have built an outstanding sales org and services org during my time leading those two teams. Now, I am absolutely committed to helping our VP of Engineering take our engineering org to the next level. We want, need, and respect great engineering talent who can solve business problems and play well with others.
We pay well too. Two key tenets of our company culture are a) serving others and b) mastering our craft—improving ourselves. Of course, we also want to solve cool engineering problems, have fun, and avoid bullshit as much as possible ;-). If you are really good at what you do, please submit your CV.
Igor, VP Engineering:
I have worked at both the big engineering orgs (e.g. Avast, CA Technologies, Cisco, Valeo) and startups (e.g. Jumpshot and Navicom). I also worked at ZOOM a few years back. I came back to ZOOM nine months ago to help envision a technology strategy and architecture while turning our engineering org into a world-class department. If you want to join a company where you can have start-up opportunities, big company paychecks, and influence key decisions, then come talk to us.
Bill, VP Products:
Before joining ZOOM, I spent eight years building Interactive Intelligence from the ground up. I owned the product API layer, and we were a recognized leader in Contact Center as a Service (CCaaS). We grew like crazy, and I saw it from the ground floor to the top. We had strong collaboration with engineers there, and we are doing the same thing here. If you are a great engineer, come help us use next-gen development platforms to build truly smart contact center optimization software.
Adam, VP Marketing:
While I have spent most of my career in CRM “on the business growth side” in product marketing roles, I love software engineering. I am one who appreciates that software engineers are the ones who are leading this new era of smart apps. Pick whatever marketing buzzword you want—cloud native, microservices, Kubernetes, Kafka, natural language processing—ZOOM is building the next gen of this stuff in our industry.
Just before ZOOM, I spent five years doing technical evangelism for Cloud Foundry, Hadoop, Spring (Java), RabbitMQ, Redis, MADlib (AI/ML), Apache Geode (IMDG), Greenplum (MPP), and data science services. We want to build the same type of engineering team here—a team who leads world-class projects like these. Come join us and help build that team.
FAQ #9: What is our Functionality, Runtime Stack and Developer Tooling?
Realtime-multimedia streaming and processing from a variety of audio and video endpoints for unified communications, compression, Mobile/SIP/WebRTC based recording for variety from small to carrier grade environments, IP based Telephony networking, cloud APIs, the new voice-interface of IoT devices (e.g. Alexa, Google Home), customer and agent experience measurement, media and interaction capture APIs (i.e. website, mobile, chat, email, IoT, etc.), tagging, enrichment, correlations, matching, advanced search, business intelligence, cloud APIs, speech analytics APIs, quality measures and reviews, workforce management, forecasting, smart recommendation apps, desktop analytics, media lifecycle management, screen recording, live monitoring, robotic process automation, recruiting, time/task management, evaluations, training/coaching, customer surveys, search engine optimization, advanced reporting/analytics, advanced scheduling/calendar, and customer/agent journey.
Platform as a Service (PaaS)
A cloud technology stack including hybrid deployments, event sourcing in high availability environments, routing, authentication, app lifecycle management, server/container orchestration, data and middleware services, messaging, DevOps, automation, logging, infrastructure APIs (OS, Virtualization, Hardware), Kubernetes, Terraform, and Cloud Foundry.
Data and Middleware Services
Transactional and reference data storage (PostgreSQL), search queries (Apache Solr), analytics/reporting (HUE – Cloudera w/Apache License), real-time pub/sub streaming message queues (Apache Kafka), big data processing (Apache Spark), big data storage (Apache Hadoop), modern file storage (VMs/NAS/SAN), RabbitMQ.
Java, Spring, Scala, TypeScript, Gradle, Cloud Foundry, Cloudera HUE, Swagger APIs, JIRA, Bamboo, Stash, BitBucket, GitFlow, Docker, Linux, Cucumber, Robot.
FAQ #10: What are we turning our engineering culture into?
Go research at what Netflix did to recruit engineers when they moved from DVDs via mail to an online service.
Go look at how Spotify, Twitter, Instagram, Indeed.com, or any of the other great companies, architectures, and engineering teams that have become name brands that are known for engineering talent.
That is what we are building, and we need more people who want to be part of something like this.