ExaThought Data Engineer Interview Guide

Getting ready for a Data Engineer interview at ExaThought? The ExaThought Data Engineer interview process typically spans several question topics and evaluates skills in areas like data pipeline design, SQL and Python development, system architecture, data quality, and stakeholder communication. At ExaThought, interview preparation is especially important because the company emphasizes scalable data solutions, robust cloud-based analytics, and seamless collaboration with both technical and non-technical teams. Data Engineers here are expected to not only build and optimize complex data systems but also ensure that data is accessible, reliable, and actionable for diverse business needs.

In preparing for the interview, you should:

• Understand the core skills necessary for Data Engineer positions at ExaThought.
• Gain insights into ExaThought’s Data Engineer interview structure and process.
• Practice real ExaThought Data Engineer interview questions to sharpen your performance.

At Interview Query, we regularly analyze interview experience data shared by candidates. This guide uses that data to provide an overview of the ExaThought Data Engineer interview process, along with sample questions and preparation tips tailored to help you succeed.

ExaThought is a rapidly expanding technology company specializing in data-driven solutions, cloud computing, and AI-powered analytics. Serving global enterprises, ExaThought enables smarter decision-making, improved operational efficiency, and accelerated innovation through advanced data systems and intelligent analytics platforms. The company is known for its culture of continuous learning, collaboration, and technical excellence. As a Data Engineer, you will play a crucial role in designing and optimizing scalable data architectures that empower clients to harness the full potential of their data for business transformation.

As a Data Engineer at ExaThought, you will design, develop, and manage scalable data solutions, primarily leveraging Snowflake for data architecture and warehousing. Your responsibilities include building and optimizing data pipelines using Python, SQL, Spark, and Scala, as well as implementing robust data ingestion, processing, and orchestration workflows with tools like Airflow and Informatica. You will ensure data integrity, governance, and lineage tracking while collaborating closely with cross-functional teams such as data scientists, analysts, and business stakeholders. This role is vital to supporting advanced analytics and AI initiatives, driving innovation, and enabling data-driven decision-making across enterprise clients.

2.1 Stage 1: Application & Resume Review

The process begins with a detailed review of your application and resume, where ExaThought’s talent acquisition team assesses your experience in enterprise data engineering, proficiency with tools like Snowflake, Python, and Spark, and your history of building scalable data solutions. Emphasis is placed on demonstrated expertise in designing data pipelines, working with orchestration tools such as Airflow or Informatica, and implementing robust data governance and metadata management practices. To prepare, ensure your resume clearly highlights hands-on experience with these technologies, quantifies your impact, and showcases collaborative projects.

2.2 Stage 2: Recruiter Screen

Next, a recruiter conducts a 30-45 minute phone or video interview to discuss your background, motivation for joining ExaThought, and alignment with the company’s fast-paced, innovation-driven culture. Expect high-level questions about your experience with Snowflake, Python, and data pipeline orchestration, as well as your ability to communicate complex technical concepts to cross-functional teams. Preparation should focus on articulating your career narrative, your interest in ExaThought’s approach to data-driven solutions, and your collaborative mindset.

2.3 Stage 3: Technical/Case/Skills Round

This stage typically involves one to two interviews (each 60-90 minutes) led by senior data engineers or engineering managers. You’ll be asked to solve real-world technical problems, such as designing scalable ETL pipelines, optimizing data ingestion and transformation workflows, and troubleshooting data quality or pipeline failures. Expect hands-on exercises in SQL, Python, and possibly Spark or Scala, including coding challenges, system design scenarios, and case studies involving data warehouse architecture or pipeline orchestration. Preparation should include reviewing your experience with large-scale data systems, practicing code implementation, and being ready to discuss trade-offs in architectural decisions.

2.4 Stage 4: Behavioral Interview

A behavioral round is conducted by a hiring manager or team lead and focuses on your problem-solving approach, adaptability, and communication skills. You’ll be asked to describe past data projects, address challenges faced in pipeline development, and explain how you’ve collaborated with business stakeholders and resolved misaligned expectations. The interview may also assess your ability to present complex insights clearly to non-technical audiences and your strategies for ensuring data quality and reliability. To prepare, reflect on specific examples that demonstrate your leadership, teamwork, and ability to drive successful outcomes in dynamic environments.

2.5 Stage 5: Final/Onsite Round

The final stage often consists of a half-day virtual or onsite session with multiple interviewers, including senior engineers, architects, and business partners. You may participate in deep-dive technical interviews, system design discussions, and cross-functional collaboration exercises. Topics can range from building and optimizing Snowflake data warehouses, implementing CI/CD and automated testing for pipelines, designing solutions for unstructured or streaming data, and troubleshooting complex ETL failures. You’ll also be evaluated on your ability to communicate effectively and adapt technical presentations for diverse audiences. Preparation should focus on integrating technical depth with business context, demonstrating thought leadership, and showing a holistic understanding of end-to-end data engineering lifecycle.

2.6 Stage 6: Offer & Negotiation

If successful, you’ll move to a final discussion with the recruiter or hiring manager regarding compensation, benefits, start date, and team placement. ExaThought values transparency and flexibility at this stage, so be prepared to negotiate based on your experience and market benchmarks. Review your priorities in advance and be ready to discuss how your skills align with the company’s strategic initiatives.

2.7 Average Timeline

The typical ExaThought Data Engineer interview process spans 3-4 weeks from application to offer, with most candidates completing each stage in about a week. Fast-track candidates with highly relevant Snowflake and Python experience, or those referred internally, may move through the process in as little as 2 weeks, while the standard pace allows for additional technical assessments and team interviews. Scheduling for final rounds may vary depending on stakeholder availability, but clear communication is maintained throughout.

Now, let’s dive into the types of interview questions you can expect at each stage.

3.1 Data Pipeline Design & Architecture

Expect deep dives into end-to-end pipeline design, scalability, and reliability. Focus on how you structure ETL processes, handle diverse data sources, and choose appropriate technologies for large-scale ingestion and transformation. Demonstrate your understanding of both batch and streaming architectures, and highlight your experience with open-source and cloud-native tools.

3.1.1 Design a scalable ETL pipeline for ingesting heterogeneous data from Skyscanner's partners Outline the steps for ingesting diverse partner data, focusing on modular ETL architecture, schema normalization, and error handling. Discuss how you would ensure scalability and maintainability as data volume grows.

Example answer: "I would use a modular ETL framework with schema mapping for each partner, leveraging cloud storage and distributed processing to scale. Monitoring and alerting would catch data anomalies early, and versioned data schemas would ensure backward compatibility."

3.1.2 Design an end-to-end data pipeline to process and serve data for predicting bicycle rental volumes Describe the pipeline stages from raw data ingestion to model deployment, emphasizing data validation, transformation, and real-time serving. Address how you would automate retraining and monitoring for prediction accuracy.

Example answer: "I’d set up batch ingestion from rental logs, clean and aggregate data, and feed it into a predictive model hosted on an API. Automated retraining would be triggered by data drift metrics, and dashboards would monitor prediction quality."

3.1.3 Design a robust, scalable pipeline for uploading, parsing, storing, and reporting on customer CSV data Explain your approach to handling high-volume CSV uploads, including validation, error recovery, and efficient storage. Highlight how you would enable flexible reporting and auditing capabilities.

Example answer: "I would use a multi-stage pipeline: initial upload validation, parallel parsing jobs, and incremental storage in a columnar data warehouse. Automated error logs and audit trails would support compliance and reporting."

3.1.4 Design a reporting pipeline for a major tech company using only open-source tools under strict budget constraints Discuss your selection of open-source tools for ETL, storage, and visualization, and how you would optimize for cost and performance. Address governance and scalability concerns.

Example answer: "I’d leverage Apache Airflow for orchestration, PostgreSQL for storage, and Metabase for dashboards, ensuring containerized deployment for easy scaling. Automated data validation and role-based access controls would ensure quality and security."

3.1.5 Design a data pipeline for hourly user analytics Describe how you would architect a pipeline for near real-time analytics, focusing on incremental aggregation, latency minimization, and reliability.

Example answer: "I’d use stream processing tools like Kafka and Spark Streaming to aggregate data hourly, storing results in a time-series database. Monitoring would alert on processing delays or data loss."

3.2 Data Modeling & Warehousing

These questions assess your ability to design scalable and efficient data models and warehouses. Focus on your approach to schema design, normalization versus denormalization, and how you handle evolving business requirements.

3.2.1 Design a data warehouse for a new online retailer Lay out the logical and physical schema, discuss fact and dimension tables, and explain how you’d support analytics for sales, inventory, and customer behavior.

Example answer: "I’d create star schemas for sales and inventory, with dimension tables for products, customers, and time. Partitioning and indexing strategies would optimize query speed for large datasets."

3.2.2 System design for a digital classroom service Describe the core data entities, relationships, and how you’d structure data to support analytics on student engagement and performance.

Example answer: "I’d model students, courses, assignments, and interactions as separate tables, using foreign keys to maintain relationships. Aggregation tables would support fast queries on engagement metrics."

3.2.3 Let's say that you're in charge of getting payment data into your internal data warehouse Explain the ingestion process, data validation, and how you would manage schema evolution and error recovery.

Example answer: "I’d use a staged ETL approach, validating payment records before loading. Schema changes would be managed via version control, and failed ingestions would trigger automated alerts for remediation."

3.3 Data Quality & Cleaning

Expect questions on handling messy, inconsistent, or incomplete data. Focus on your strategies for profiling, cleaning, and validating data at scale, and your ability to communicate the impact of data quality issues.

3.3.1 Describing a real-world data cleaning and organization project Share your approach to profiling data issues, choosing cleaning methods, and ensuring reproducibility.

Example answer: "I began by profiling missing and outlier values, then used statistical imputation and regex-based cleaning. Documented cleaning steps in notebooks ensured auditability and reproducibility for future analysis."

3.3.2 Challenges of specific student test score layouts, recommended formatting changes for enhanced analysis, and common issues found in 'messy' datasets Discuss how you would standardize formats, handle missing or inconsistent data, and prepare datasets for downstream analytics.

Example answer: "I’d normalize score layouts, standardize field names, and use validation scripts to catch inconsistencies. Automated checks would flag missing or anomalous entries before ingestion."

3.3.3 How would you approach improving the quality of airline data? Explain your process for identifying root causes of quality issues, implementing automated checks, and quantifying improvements.

Example answer: "I’d profile common errors, implement automated validation rules, and track data quality metrics over time. Regular stakeholder reviews would ensure improvements aligned with business needs."

3.3.4 How would you systematically diagnose and resolve repeated failures in a nightly data transformation pipeline? Detail your troubleshooting steps, root cause analysis, and how you’d implement monitoring and alerting to prevent recurrence.

Example answer: "I’d review pipeline logs, isolate failure points, and implement automated tests for common error scenarios. Proactive monitoring and rollback mechanisms would reduce downtime."

3.4 SQL, Scripting & Data Manipulation

These questions test your ability to write robust queries and scripts for data extraction, transformation, and analysis. Emphasize your proficiency in both SQL and Python, and your approach to optimizing performance.

3.4.1 Write a SQL query to count transactions filtered by several criterias Describe how you’d structure the query, handle filtering logic, and optimize for large datasets.

Example answer: "I’d use indexed columns for filtering, aggregate with COUNT(), and add WHERE clauses for each criteria. CTEs or subqueries would manage complex logic efficiently."

3.4.2 Write a function that splits the data into two lists, one for training and one for testing Explain your approach to randomizing and splitting data, ensuring reproducibility and balanced distributions.

Example answer: "I’d shuffle the dataset, then slice it based on a defined train-test ratio. Setting a random seed ensures reproducibility."

3.4.3 Write a function to find how many friends each person has Describe how you’d aggregate relationships and handle edge cases such as missing or duplicate entries.

Example answer: "I’d group by user ID and count unique friend IDs, ensuring duplicates are removed and missing values are handled gracefully."

3.4.4 Write a query to get the current salary for each employee after an ETL error Explain how you would identify and correct erroneous records, and ensure accurate reporting.

Example answer: "I’d use window functions to identify the latest valid salary record per employee, filtering out erroneous updates and joining with reference tables for validation."

3.4.5 python-vs-sql Discuss when you’d choose Python scripting versus SQL for data manipulation, considering scalability and maintainability.

Example answer: "I’d use SQL for set-based operations and aggregations, while Python is ideal for complex transformations, automation, and integrating with external APIs."

3.5 System Design & Streaming Data

Questions here focus on architecting solutions for real-time data processing and handling unstructured or high-velocity data. Highlight your experience with streaming platforms, fault tolerance, and designing for scalability.

3.5.1 Redesign batch ingestion to real-time streaming for financial transactions Explain the transition steps, technology choices, and how you’d ensure data consistency and low latency.

Example answer: "I’d migrate to Kafka for real-time ingestion, use stream processing frameworks like Flink, and implement exactly-once processing to guarantee data integrity."

3.5.2 Designing a pipeline for ingesting media to built-in search within LinkedIn Describe how you’d handle media ingestion, indexing, and search optimization for large datasets.

Example answer: "I’d use distributed storage and preprocessing, integrate with a search engine like Elasticsearch, and implement incremental indexing for new media files."

3.5.3 Design a solution to store and query raw data from Kafka on a daily basis Discuss your approach to storing high-velocity clickstream data, enabling efficient querying and long-term retention.

Example answer: "I’d write Kafka streams to a columnar data store like Parquet, partitioned by date, and use Presto or similar engines for fast analytics queries."

3.5.4 Aggregating and collecting unstructured data Explain how you’d design an ETL pipeline for unstructured sources, focusing on parsing, metadata extraction, and normalization.

Example answer: "I’d use custom parsers for each data type, extract key metadata, and store normalized outputs in a NoSQL database for flexible querying."

3.6 Behavioral Questions

3.6.1 Tell me about a time you used data to make a decision that impacted business outcomes.

How to answer: Use the STAR framework to describe a situation where your analysis led to a recommendation or change, quantifying the impact where possible.

Example answer: "I analyzed customer churn patterns and recommended a targeted retention campaign, which reduced churn by 8% over the next quarter."

3.6.2 Describe a challenging data project and how you handled it.

How to answer: Focus on the complexity, your problem-solving approach, and the resolution. Highlight technical and interpersonal skills.

Example answer: "I managed a migration of legacy data to a new warehouse, overcoming schema mismatches by building automated mapping scripts and coordinating cross-team testing."

3.6.3 How do you handle unclear requirements or ambiguity in a data engineering project?

How to answer: Emphasize proactive stakeholder engagement, iterative prototyping, and clear documentation.

Example answer: "I schedule early alignment meetings, build small prototypes to clarify needs, and maintain a living requirements doc to track changes."

3.6.4 Tell me about a time when your colleagues didn’t agree with your approach. What did you do to bring them into the conversation and address their concerns?

How to answer: Show collaboration, openness to feedback, and how you reached consensus.

Example answer: "I invited feedback in a team meeting, presented data to support my approach, and incorporated suggestions to arrive at a solution everyone supported."

3.6.5 Describe a time you had to negotiate scope creep when two departments kept adding 'just one more' request. How did you keep the project on track?

How to answer: Highlight prioritization frameworks and communication strategies.

Example answer: "I used MoSCoW prioritization to separate must-haves from nice-to-haves, communicated trade-offs, and secured leadership sign-off for the revised scope."

3.6.6 You’re given a dataset that’s full of duplicates, null values, and inconsistent formatting. The deadline is soon, but leadership wants insights for tomorrow’s decision-making meeting. What do you do?

How to answer: Discuss rapid profiling, triage, and transparent communication of data limitations.

Example answer: "I quickly profiled the dataset, fixed high-impact issues, and presented insights with clear caveats about data quality."

3.6.7 Describe a situation where two source systems reported different values for the same metric. How did you decide which one to trust?

How to answer: Explain your validation process, stakeholder engagement, and documentation.

Example answer: "I traced data lineage for both sources, validated against external benchmarks, and documented the chosen source with justification."

3.6.8 Tell me about a time you delivered critical insights even though 30% of the dataset had nulls. What analytical trade-offs did you make?

How to answer: Address missing data treatment, uncertainty communication, and business impact.

Example answer: "I used statistical imputation for missing values, highlighted confidence intervals, and flagged sections with low reliability in my report."

3.6.9 Give an example of automating recurrent data-quality checks so the same dirty-data crisis doesn’t happen again.

How to answer: Focus on automation tools and impact on team efficiency.

Example answer: "I built scheduled validation scripts that flagged anomalies, reducing manual review time and preventing recurring issues."

3.6.10 How do you prioritize multiple deadlines? Additionally, how do you stay organized when you have multiple deadlines?

How to answer: Describe your prioritization framework, tools, and communication habits.

Example answer: "I use a Kanban board to track tasks, assess deadlines and impact, and communicate progress proactively to stakeholders."

4.1 Company-specific tips:

Familiarize yourself with ExaThought’s core business areas, such as cloud-based analytics, AI-powered data solutions, and enterprise-scale data transformation. Understand how ExaThought leverages Snowflake for scalable warehousing and why robust, cloud-native architectures are central to their offering. Research recent ExaThought projects, client case studies, and technical blog posts to get a sense of their approach to data-driven innovation and cross-functional teamwork.

Reflect on ExaThought’s culture of collaboration and continuous learning. Prepare to discuss how you’ve worked with diverse teams—including data scientists, analysts, and business stakeholders—to deliver solutions that drive measurable business impact. Be ready to articulate your alignment with ExaThought’s values of technical excellence, adaptability, and proactive communication.

Review ExaThought’s emphasis on scalable, reliable, and actionable data systems. Prepare examples that showcase your ability to design, optimize, and troubleshoot data pipelines that support advanced analytics and decision-making at scale. Highlight your experience with enterprise clients and your ability to balance technical depth with business context.

4.2 Role-specific tips:

4.2.1 Master end-to-end data pipeline design for heterogeneous and high-volume sources.
Practice explaining how you would architect modular, scalable ETL pipelines for diverse data sources, such as partner integrations or customer uploads. Focus on schema normalization, error handling, and strategies for incremental scaling as data volume increases. Be prepared to discuss both batch and streaming solutions, and how you monitor pipeline health and reliability.

4.2.2 Deepen your expertise in Snowflake, Python, SQL, and Spark for enterprise data engineering.
Review your hands-on experience with these core technologies, especially in the context of building, optimizing, and troubleshooting large-scale data pipelines. Prepare to answer questions about performance tuning, query optimization, and integrating these tools for robust data ingestion, transformation, and orchestration. Demonstrate your understanding of when to use Python scripting versus SQL for different data manipulation tasks.

4.2.3 Practice designing data models and warehouses for evolving business requirements.
Be ready to discuss your approach to logical and physical schema design, including star and snowflake schemas, normalization versus denormalization, and partitioning strategies. Prepare examples of how you’ve handled schema evolution, supported analytics use cases, and optimized warehouse performance for large datasets.

4.2.4 Showcase your strategies for data quality, cleaning, and validation at scale.
Prepare to share real-world examples of profiling, cleaning, and validating messy or inconsistent datasets. Discuss your use of automated validation scripts, reproducibility practices, and how you communicate the impact of data quality issues to stakeholders. Highlight your ability to rapidly diagnose and resolve pipeline failures, and your approach to preventing recurring issues through automation.

4.2.5 Demonstrate your system design skills for real-time, streaming, and unstructured data.
Review your experience with streaming platforms like Kafka or Spark Streaming, and be ready to discuss transitioning batch pipelines to real-time architectures. Explain how you handle unstructured or high-velocity data, focusing on parsing, metadata extraction, and normalization for downstream analytics. Prepare to discuss fault tolerance, scalability, and data consistency in your designs.

4.2.6 Prepare to communicate complex technical concepts to non-technical audiences.
Practice explaining your data engineering solutions in clear, concise language suitable for business stakeholders. Highlight your ability to tailor presentations for different audiences, ensuring that insights are actionable and aligned with business goals. Use examples from past projects to demonstrate your collaborative approach and impact.

4.2.7 Reflect on behavioral scenarios that showcase your leadership, adaptability, and problem-solving skills.
Think through situations where you navigated ambiguous requirements, negotiated scope creep, or resolved disagreements within a team. Use the STAR framework to structure your responses, emphasizing your proactive communication, stakeholder management, and ability to drive successful outcomes under pressure.

4.2.8 Prepare to discuss your approach to automating data-quality checks and workflow orchestration.
Be ready to explain how you’ve implemented scheduled validation scripts, monitoring systems, and automated alerting to ensure data reliability and prevent recurring issues. Highlight your experience with orchestration tools like Airflow or Informatica, and your strategies for integrating automation into end-to-end data engineering workflows.

4.2.9 Review strategies for prioritization and organization in a fast-paced, multi-deadline environment.
Prepare to discuss your framework for managing competing priorities, such as Kanban boards or impact-based assessment. Emphasize your habits of proactive communication, transparent progress tracking, and maintaining focus on high-impact deliverables. Use examples to demonstrate your ability to stay organized and deliver results in dynamic settings.

5.1 How hard is the ExaThought Data Engineer interview?
The ExaThought Data Engineer interview is challenging but highly rewarding for candidates with strong technical foundations. You’ll be assessed on your ability to design scalable data pipelines, optimize data warehousing solutions (especially with Snowflake), and handle real-world data engineering problems in Python, SQL, and Spark. The process also evaluates your communication and collaboration skills, as ExaThought values engineers who can work seamlessly across technical and business teams. Success comes from deep technical knowledge, problem-solving acumen, and the ability to connect data solutions to business impact.

5.2 How many interview rounds does ExaThought have for Data Engineer?
Typically, you’ll go through 5-6 rounds: an initial resume/application review, a recruiter screen, one or two technical/case interviews, a behavioral interview, and a final onsite or virtual panel. Each round is designed to assess different dimensions—technical depth, system design, coding proficiency, and cross-functional collaboration.

5.3 Does ExaThought ask for take-home assignments for Data Engineer?
ExaThought occasionally uses take-home assignments, especially for candidates who need to demonstrate practical skills in data pipeline design, ETL troubleshooting, or data modeling. These assignments are meant to simulate real scenarios you’d face on the job, such as building a small pipeline or solving a data quality challenge. However, most technical assessment is done live during interview rounds.

5.4 What skills are required for the ExaThought Data Engineer?
Key skills include advanced proficiency in SQL, Python, and Spark, deep experience with Snowflake data warehousing, and expertise in building scalable ETL pipelines. Familiarity with orchestration tools like Airflow or Informatica, strong data modeling abilities, and a thorough understanding of data quality, governance, and lineage are essential. You should also excel at communicating technical concepts to non-technical stakeholders and thrive in collaborative, fast-paced environments.

5.5 How long does the ExaThought Data Engineer hiring process take?
The interview process usually takes 3-4 weeks from initial application to offer. Some candidates may move faster, especially if they have highly relevant experience or internal referrals. Each stage typically lasts about a week, with clear communication throughout. Final rounds may be scheduled based on team and stakeholder availability.

5.6 What types of questions are asked in the ExaThought Data Engineer interview?
Expect a mix of technical and behavioral questions. Technical topics include designing scalable ETL pipelines, optimizing Snowflake warehouses, coding challenges in Python and SQL, troubleshooting data quality and pipeline failures, and system design for real-time or unstructured data. Behavioral questions focus on teamwork, stakeholder management, navigating ambiguity, and delivering business impact through data solutions.

5.7 Does ExaThought give feedback after the Data Engineer interview?
ExaThought generally provides high-level feedback via recruiters, especially after technical or behavioral rounds. While detailed technical feedback may be limited, you can expect clear communication about your progression and, if unsuccessful, insights into areas for improvement.

5.8 What is the acceptance rate for ExaThought Data Engineer applicants?
While ExaThought does not publish specific acceptance rates, the Data Engineer role is competitive, with an estimated 3-5% offer rate for qualified applicants. Demonstrating deep technical expertise and strong business alignment will help you stand out.

5.9 Does ExaThought hire remote Data Engineer positions?
Yes, ExaThought offers remote Data Engineer roles, with many positions supporting fully remote or hybrid arrangements. Some teams may require occasional onsite collaboration, but the company embraces flexible work models to attract top talent globally.

• Related guides:
  • ExaThought interview questions
  • Data Engineer interview guide
  • Top data engineering interview tips

Ready to ace your ExaThought Data Engineer interview? It’s not just about knowing the technical skills—you need to think like an ExaThought Data Engineer, solve problems under pressure, and connect your expertise to real business impact. That’s where Interview Query comes in with company-specific learning paths, mock interviews, and curated question banks tailored toward roles at ExaThought and similar companies.

With resources like the ExaThought Data Engineer Interview Guide and our latest case study practice sets, you’ll get access to real interview questions, detailed walkthroughs, and coaching support designed to boost both your technical skills and domain intuition.

Take the next step—explore more case study questions, try mock interviews, and browse targeted prep materials on Interview Query. Bookmark this guide or share it with peers prepping for similar roles. It could be the difference between applying and offering. You’ve got this!