5 exercises — the vocabulary that bridges engineering and product: churn, feature flags, OKRs, A/B testing, and growth metrics. Essential for developers working in product-driven teams.
A product manager announces in a team meeting: "Our monthly churn rate increased to 8% last quarter — we need to investigate why customers are leaving." Which definition of churn rate is correct?
Churn rate (also called customer attrition rate) is the percentage of customers who cancel or stop using a SaaS product in a given time period. Formula: Churn Rate = (Customers lost during period / Customers at start of period) × 100. High churn is the enemy of SaaS growth — even modest churn compounds aggressively: 8% monthly churn = ~64% customer base lost annually. The SaaS metrics family: Churn rate — customers leaving. Retention rate — inverse of churn; 100% − churn rate. "We improved retention from 91% to 94% by improving onboarding." MRR (Monthly Recurring Revenue) — total predictable monthly revenue from subscriptions. ARR (Annual Recurring Revenue) — MRR × 12. LTV / CLV (Lifetime Value) — average revenue from one customer over their entire relationship. CAC (Customer Acquisition Cost) — cost to acquire one new customer. The key ratio: LTV/CAC > 3 is generally considered healthy. In conversation: "We can tolerate higher CAC if our LTV projection is strong and churn stays below 3%."
2 / 14
A developer asks a product manager: "Should we roll out the dark mode feature to all users at once, or can we use a feature flag to release it gradually?" What is a feature flag (also called a feature toggle)?
A feature flag (feature toggle, feature switch) is a technique for turning features on or off in production using a configuration change — without redeploying code. Feature flags enable: Gradual rollout — enable for 1% → 10% → 50% → 100% of users, monitoring each step. Canary releases — test on a small set before full rollout. A/B testing — show version A to group 1, version B to group 2. Kill switch — instantly disable a broken feature without reverting code. Beta access — enable only for internal users or paying beta testers. Feature flag tools: LaunchDarkly, Flagsmith, Unleash, GrowthBook, or a simple database config table. Related vocabulary: Rollout — progressively deploying a feature to more users. Rollback — reverting to the previous version. Dark launch — code is deployed but the feature is hidden from users (flag is off). In conversation: "We shipped the new checkout flow behind a flag two weeks ago — it's currently enabled for 20% of users and conversion is up 3%."
3 / 14
The CEO reads from a board report: "Our North Star metric this quarter is to increase Weekly Active Users by 25%. To achieve this, each team has defined their OKRs accordingly." What does OKR stand for, and what is it?
OKR = Objectives and Key Results, a goal-setting framework popularised by Intel and Google. Structure: Objective — what you want to achieve (qualitative, inspirational, time-bound). Example: "Make our onboarding experience best-in-class." Key Results (KRs) — how you measure progress toward the objective (quantitative, specific, verifiable). Example: KR1: Reduce time-to-first-value from 14 days to 5 days. KR2: Increase 30-day activation rate from 45% to 65%. KR3: Reduce onboarding-related support tickets by 40%. OKR vs. KPI: OKRs — set for a quarter/year, aspirational (60–70% achievement is good), focus on outcomes and change. KPIs (Key Performance Indicators) — ongoing metrics that track the health of the business (revenue, uptime, NPS) — not necessarily tied to a specific goal. OKR vocabulary: "Set OKRs", "OKR cycle", "check-in on OKRs", "confidence score" (how likely you are to hit the KR), "stretch goal" (ambitious target intentionally set above what's easy). In practice: "Our team's OKR this quarter is to increase API reliability — KR1 is reducing error rate below 0.1%."
4 / 14
A growth team is running an experiment described as: "We split users randomly into two groups: Group A sees the original sign-up page, Group B sees the new version with a video walkthrough. We measure 14-day retention for both." What is this experiment called?
An A/B test (split test) is a controlled experiment that compares two versions (A = control, B = variant) by randomly splitting users into groups and measuring a target metric. Key concepts: Control group (A) — sees the original/current version. Variant group (B) — sees the new version being tested. Target metric — the outcome you're measuring (retention, conversion, click-through rate). Statistical significance — the test result is reliable and not due to random chance (typically p < 0.05). Sample size — must be large enough to detect the expected effect. Multivariate test (option B) — tests multiple variables simultaneously (e.g., different headlines and different CTAs at the same time); requires much larger samples. Canary deployment (option D) — an infrastructure technique for gradual rollout, not designed to compare metrics between groups. A/B testing in SaaS: "We ran an A/B test on the onboarding email — version B (personalised subject line) improved open rate by 18% with 95% confidence at n=50,000." Tools: Optimizely, VWO, Google Optimize, Statsig, GrowthBook.
5 / 14
A SaaS startup's pricing page shows three tiers: Free (limited features), Pro ($29/month), Enterprise (custom pricing). What pricing model does the Free tier represent?
Freemium (free + premium) is a SaaS business model where a permanently free tier provides enough value to attract users, while advanced features are gated behind paid plans. The goal: acquire users at zero cost, then convert a percentage to paying customers. Classic examples: Slack (free for small teams, paid for large orgs), Dropbox (free storage + paid for more), GitHub (free for public repos, paid for private/enterprise), Figma (free for small teams, paid for larger teams). Key freemium metrics: Free-to-paid conversion rate — industry average is 2–5%. PQL (Product Qualified Lead) — a free user whose behaviour signals they're ready to pay (hit usage limits, used a premium feature, invited teammates). Freemium vs. free trial: Freemium — forever free with feature limits, no time limit. Free trial — full product access but time-limited (14 days, 30 days). Option A describes a free trial. In product conversation: "Our freemium conversion rate is 4% — above the industry average — but we want to improve it by surfacing premium features earlier in the user journey."
6 / 14
Sarah (Lead Engineer) comments on a pull request: 'This function is returning null when it should be returning an empty string. Is this intentional?' What does 'null' typically represent in programming contexts?
Null in programming signifies the absence of a meaningful value—it's not zero or an empty string; it indicates that a variable has not been assigned a value yet, or that a resource is unavailable. Misunderstanding this can lead to unexpected behavior and errors during runtime. It's crucial to differentiate null from other representations of missing data like an empty string.
7 / 14
Ben (Product Manager) sends a Slack message: 'Hey team, we're implementing A/B testing on the onboarding flow. We'll be monitoring key metrics like conversion rate and time to value.' What is A/B testing?
A/B testing (also known as split testing) is a method of comparing two versions of something—in this case, the onboarding flow—to see which one performs better. It involves randomly assigning users to either version and then analyzing the resulting data to determine which version leads to higher conversion rates or faster time-to-value.
8 / 14
David (Product Manager) writes in a Slack channel: 'We're seeing a high bounce rate on the landing page – around 65%. It suggests users aren't finding what they expect when they first arrive.' What does 'bounce rate' primarily measure in this context?
'Bounce rate' in web analytics refers to the proportion of single-page sessions. A high bounce rate (like 65%) indicates that many users land on the page and immediately leave without interacting or exploring further – likely because the content wasn't relevant or the user experience was poor. It's distinct from overall traffic volume.
9 / 14
Maria (Lead Engineer) is reviewing a pull request and comments: 'The API endpoint returns `404 Not Found` when attempting to access the user profile data. This seems incorrect given the established routing.' What does a '404 Not Found' HTTP status code signify?
A '404 Not Found' status code indicates that the web server successfully received the request but couldn't locate the requested resource at the specified URI. This often happens when a URL is mistyped, a page has been moved or deleted, or there's a problem with the application routing.
10 / 14
John (Product Manager) sends a Slack message: 'We're planning to migrate our database to PostgreSQL. We'll need to thoroughly test the new schema and ensure minimal downtime during the switch.' What does 'minimal downtime' typically refer to in this context?
'Minimal downtime' in this scenario means the migration should cause as little disruption to users and services as possible. It implies a carefully orchestrated process with a defined window of interruption and a rapid return to normal operation – crucial for SaaS applications. The key is a planned outage, not continuous availability.
11 / 14
Emily (Lead Engineer) is reviewing a pull request and comments: 'The API endpoint returns `500 Internal Server Error` when processing high volumes of requests. We need to investigate potential bottlenecks in the backend code.' What does a '500 Internal Server Error' generally signify?
A '500 Internal Server Error' is a standard HTTP status code indicating that the server encountered an unexpected condition while fulfilling the request. It signifies a problem on the *server* side – often due to code errors or resource limitations - rather than a client-side issue.
12 / 14
David (Product Manager) writes in a Slack channel: 'We're experimenting with dynamic pricing for our Pro tier. We'll be monitoring metrics like conversion rate and customer lifetime value to assess the impact.' What is 'customer lifetime value' (CLTV)?
Customer Lifetime Value (CLTV) is a critical metric in SaaS that represents the predicted revenue a single customer will generate throughout their entire relationship with your company. It's calculated based on factors like subscription duration and average revenue per user – far more than just the initial purchase price.
13 / 14
Maria (Lead Engineer) is reviewing a pull request: 'The application logs show numerous 'WARN' messages related to deprecated API calls. We need to update the codebase to utilize the newer versions.' What do 'WARN' messages typically indicate in log files?
'WARN' messages in log files are used to signal potential problems. They don't represent critical errors that immediately halt operations, but rather indicate situations where something *might* be going wrong – perhaps an outdated function or configuration setting – and should be investigated further.
14 / 14
Ben (Product Manager) sends a Slack message: 'We're implementing feature flags to control the rollout of the new UI. We'll be using percentage splits to gradually expose the changes to users.' What is a 'percentage split' in the context of A/B testing?
A 'percentage split' in A/B testing defines how many users are assigned to each variation (control and variant). For example, a 50/50 split means half the users will see the original UI and half will see the new version – ensuring equal representation for comparison.
What does the "SaaS & Product Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to saas & product vocabulary through 14 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 14 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.