About Odessa Technologies
Company Description
Odessa Technologies is a leading provider of software solutions for the asset finance and leasing industry. Founded in 1998, the company has developed a robust platform known as the Odessa Platform, which caters to various business needs ranging from lease management to asset tracking. The work culture at Odessa is characterized by innovation, collaboration, and a commitment to excellence. Employees thrive in an environment that encourages continuous learning and teamwork, fostering a strong sense of community. The company promotes diversity and inclusion, ensuring that every voice is heard and valued. With a focus on professional development, Odessa provides its employees with opportunities to grow their skills and advance their careers.
Software Developer Interview Questions
Q1: Can you describe your experience with programming languages relevant to our platform?
I have extensive experience with Java and Python, which are crucial for developing robust and scalable applications. In my previous role, I developed several modules that improved system performance by 30%.
Q2: How do you approach debugging and troubleshooting code?
I follow a systematic approach to debugging by first reproducing the issue, then isolating the problem area in the code. I utilize debugging tools and logs to trace the source of the error, and I ensure to document my findings for future reference.
Q3: What methodologies do you prefer when working on software projects?
I prefer Agile methodologies as they promote iterative development and flexibility. This allows for regular feedback and adjustments based on user needs, ensuring the final product aligns closely with client expectations.
Q4: Can you discuss your experience with API integration?
I have worked extensively with RESTful APIs to integrate various services into applications. For instance, I successfully integrated payment gateways into a leasing management system, which streamlined transaction processing for users.
Q5: How do you ensure code quality and maintainability?
I adhere to coding standards and best practices, conduct code reviews, and utilize automated testing tools. This ensures that the code is not only functional but also clean and maintainable for future developers.
Project Manager Interview Questions
Q1: What project management methodologies are you familiar with, and which do you prefer?
I am familiar with both Agile and Waterfall methodologies. I prefer Agile for its adaptability and focus on delivering incremental value, particularly in software development projects where requirements may evolve over time.
Q2: How do you handle project scope changes?
I address scope changes by evaluating the impact on timelines and resources, discussing them with stakeholders, and obtaining approval before proceeding. Clear communication is key to managing expectations and ensuring project success.
Q3: Can you give an example of a challenging project you managed and how you overcame obstacles?
I managed a project where the client’s requirements shifted mid-way through development. I facilitated a series of workshops to redefine project scope and priorities, which resulted in a successful delivery that met the new requirements without significant delays.
Q4: How do you ensure your team stays motivated and on track?
I promote an open environment where team members feel comfortable sharing their ideas and concerns. I also set clear goals, provide regular feedback, and celebrate achievements to keep the team motivated.
Q5: What tools do you use for project management and why?
I use tools like Jira for Agile project tracking and Trello for visual task management. These tools enhance collaboration, streamline communication, and help in tracking progress effectively.
Business Analyst Interview Questions
Q1: What techniques do you use to gather requirements from stakeholders?
I employ techniques such as interviews, surveys, and workshops to gather requirements. I also use document analysis to understand existing processes and identify areas for improvement.
Q2: How do you prioritize requirements during a project?
I prioritize requirements based on factors such as business value, stakeholder urgency, and technical feasibility. I often use techniques like MoSCoW (Must have, Should have, Could have, and Won't have) to categorize requirements clearly.
Q3: Can you explain how you would conduct a SWOT analysis?
I would gather a cross-functional team to identify the project or business’s Strengths, Weaknesses, Opportunities, and Threats. This analysis helps in strategic planning and decision-making by providing a clear view of the internal and external factors impacting success.
Q4: How do you handle conflicting requirements from different stakeholders?
I facilitate discussions to understand the underlying needs of each stakeholder. By finding common ground and negotiating compromises, I work towards an optimal solution that aligns with the overall project goals.
Q5: What tools do you use for data analysis and reporting?
I frequently use Excel for data analysis due to its versatility and power. Additionally, I utilize tools like Tableau for data visualization and reporting to present findings in an easily digestible format for stakeholders.
Quality Assurance Engineer Interview Questions
Q1: What is your experience with automated testing tools?
I have extensive experience using Selenium and JUnit for automated testing of web applications. I have developed test scripts that significantly reduce manual testing time, ensuring faster deployment cycles.
Q2: How do you approach writing test cases?
I write test cases based on the requirements specifications and user stories. I ensure that each test case is clear, concise, and includes expected results, covering both positive and negative scenarios.
Q3: Can you explain the difference between functional and non-functional testing?
Functional testing verifies that the software behaves as expected according to requirements, while non-functional testing assesses aspects such as performance, usability, and security. Both are essential for delivering a high-quality product.
Q4: How do you handle defects found during testing?
Upon discovering a defect, I document it with detailed steps to reproduce and severity levels. I then communicate with the development team to prioritize and track the resolution of the defect until it’s resolved.
Q5: What metrics do you use to measure the quality of the software?
I use metrics such as defect density, test coverage, and pass/fail rates to evaluate software quality. These metrics help identify areas for improvement and ensure that quality standards are met throughout the development lifecycle.
Company Background and Industry Position
Odessa Technologies, a name steadily gaining traction in the logistics and supply chain technology sector, has carved out a niche by delivering advanced software solutions that optimize and automate freight management. Founded several decades ago, this company has matured with the evolving landscape of digital freight operations, blending deep domain expertise with modern SaaS offerings. Their influence in the North American market is significant, especially among retail supply chain operators and third-party logistics providers.
What sets Odessa apart is not merely its software but its commitment to innovation in a traditionally slow-moving industry. Their products cater to complex operational challenges, such as transportation management systems (TMS), carrier procurement, and analytics. From an industry standpoint, Odessa Technologies competes with larger enterprise software firms but holds distinct appeal thanks to its specialized focus on freight tech and a mid-size company culture that appeals to professionals craving both impact and career growth.
How the Hiring Process Works
- Application and Resume Screening: Odessa typically screens candidates through their career portal or via recruiting partners. Resumes are scrutinized for relevant experience in logistics software, technical skills, and alignment with job-specific competencies.
- Initial HR Contact: Qualified applicants are then contacted by HR for a preliminary discussion to gauge cultural fit, communication skills, and basic eligibility like work authorization.
- Technical Assessment: For technical roles, candidates usually face a coding or scenario-based assessment designed to test problem-solving aptitude related to freight or logistics challenges.
- Technical Interview Round: This round dives deeper into technical expertise—software engineers might solve live coding challenges, while product managers could discuss roadmap strategies and customer scenarios.
- Managerial Interview: Candidates meet with the hiring manager to explore role expectations, team dynamics, and alignment with Odessa’s values.
- Final HR and Culture Interview: Often the last step, this interview evaluates candidate personality, adaptability, and overall fit within Odessa’s work culture.
- Offer and Negotiation: Successful candidates receive an offer outlining salary, benefits, and other terms, followed by negotiation if necessary.
Interview Stages Explained
Initial HR Screening Meaning
This isn’t just a formality. HR screens are Odessa’s way to quickly ensure candidates meet baseline expectations—eligibility criteria, salary expectations, and communication clarity. It also helps recruiters assess candidates’ motivation and cultural compatibility. When candidates describe this round, many note it’s conversational but expect pointed questions like: “Why Odessa?” or “What do you know about our products?”
Technical Assessment Purpose
The technical assessment is a clever filter, not just a hurdle. Odessa seeks to verify that candidates can handle the core challenges of their roles. For software positions, this might be writing code that solves real-world logistics problems, like route optimization or data parsing. For analysts or product folks, case studies might evaluate analytical thinking aligned with freight operations. Why the emphasis here? Because Odessa’s solutions address complex industry issues—so they want assurance candidates aren’t just book smart but practically ready.
Technical and Managerial Interviews
These rounds are where the rubber meets the road. Technical interviews test depth and creativity by exploring past project experiences and problem-solving approaches. Hiring managers look for candidates who not only know their tech but can also communicate solutions clearly—critical in cross-functional teams at Odessa. Managerial interviews emphasize cultural fit and long-term potential. Observing candidates, Odessa’s managers pay attention to adaptability, teamwork, and passion for logistics technology. They want people who can grow and thrive in a rapidly evolving environment.
HR and Culture Fit Interview
This step often surprises candidates expecting only skill-based assessments. However, Odessa places strong value on cultural alignment. The company’s culture promotes collaboration, innovation, and continuous learning. The HR interviewer might ask behavioral questions like “Tell me about a time you faced failure” or “How do you handle conflicts in a team?” These questions help Odessa gauge if candidates will mesh well with existing teams and the company’s values.
Examples of Questions Candidates Report
- “Explain a challenging technical problem you solved in logistics software.”
- “How would you improve our TMS product based on current market trends?”
- “Write a function to optimize freight routing given multiple constraints.”
- “Describe a situation where you had to communicate complex data findings to non-technical stakeholders.”
- “What motivates you to work in supply chain technology?”
- “How do you stay updated on industry changes affecting Odessa’s clients?”
Eligibility Expectations
Odessa Technologies generally looks for candidates with a relevant educational background—degrees in computer science, engineering, logistics, or business are common. Experience within the freight or supply chain domain significantly boosts your chances, especially for product or client-facing roles. For software engineers, proficiency in languages like Java, Python, or JavaScript, along with understanding APIs and cloud infrastructure, is often essential. Experienced hires are expected to demonstrate leadership or deep domain expertise, while entry-level roles focus more on problem-solving ability and cultural fit.
Work authorization in the country is a non-negotiable baseline. The company operates mainly in the US and Canada, so visa sponsorship is limited and discussed upfront. Odessa also values soft skills—communication, agility, and teamwork are critical because roles often require collaboration across departments and customers.
Common Job Roles and Departments
The hiring landscape at Odessa spans a diverse yet specialized array of positions, influenced heavily by their central focus on freight technology:
- Software Engineering: Backend, frontend, and full-stack roles developing core TMS functionalities and APIs.
- Product Management: Professionals steering product strategy, customer feedback, and feature prioritization.
- Data Analytics and BI: Analysts building dashboards and insights to enhance operational decisions for clients.
- Sales and Customer Success: Teams managing client acquisition, renewal, and ongoing support in logistics sectors.
- Quality Assurance: Engineers focusing on software reliability, automated testing, and user experience.
- Implementation and Consulting: Specialists who help clients onboard and maximize Odessa’s solutions.
Compensation and Salary Perspective
| Role | Estimated Salary |
|---|---|
| Software Engineer (Mid-level) | $85,000 - $110,000 |
| Product Manager | $95,000 - $130,000 |
| Data Analyst | $65,000 - $85,000 |
| Sales Executive | $70,000 - $120,000 (base + commission) |
| Quality Assurance Engineer | $70,000 - $90,000 |
| Implementation Consultant | $75,000 - $100,000 |
Compared to market averages in freight tech firms, Odessa offers competitive pay aligned with mid-sized tech firms, balancing solid base salaries with performance incentives. Benefits and perks, often discussed during the offer stage, include standard health plans, 401(k) matching, and flexible work arrangements, reflecting trends in tech recruitment today.
Interview Difficulty Analysis
From what candidates share, Odessa’s selection process is fair but demanding, particularly for technical roles. The screening and HR rounds feel straightforward for most, although the cultural fit questions can unsettle those not accustomed to behavioral interviews. The technical assessments are challenging, especially because they emphasize problem-solving within supply chain contexts. For some, the hurdle lies in applying generic coding skills to industry-specific logistics problems, which requires preparation beyond standard algorithms.
Managerial interviews are less about right or wrong answers and more about demonstrating thoughtfulness and alignment with Odessa’s vision. So, if you’re a candidate who dreads cold technical grilling but is strong with real-world problem explanations, you might find these rounds a bit more approachable.
Preparation Strategy That Works
- Research Odessa’s products and recent industry trends to discuss them intelligently during interviews.
- Practice technical problems related to routing algorithms, data structures, and API design, keeping logistics scenarios in mind.
- Brush up on behavioral interview techniques, preparing stories that highlight teamwork, problem-solving, and adaptability.
- Network with current or former Odessa employees on platforms like LinkedIn to gain insider insights.
- Prepare thoughtful questions for interviewers about role expectations and company culture to demonstrate genuine interest.
- Review the job description carefully to align your skills and experiences with specific eligibility criteria.
- Simulate interview scenarios with peers or mentors to build confidence, especially for technical and HR rounds.
Work Environment and Culture Insights
Odessa Technologies blends a start-up agility with corporate structure—a balance not easy to find. Employees frequently describe a collaborative atmosphere where cross-team problem-solving is routine. The leadership emphasizes transparency, open communication, and continuous improvement, which helps foster employee loyalty despite the demanding nature of logistics tech.
Candidates often notice that Odessa values curiosity and learning above rigid hierarchy. It’s a place where juniors can speak up, and experienced staff are encouraged to mentor. That said, the pace can be brisk, reflecting the pressure to stay competitive in a changing market. Work-life balance is generally respected but can fluctuate around critical product releases or client deadlines.
Career Growth and Learning Opportunities
One of Odessa’s strengths lies in professional development. The company invests in training programs—both internal workshops and external certifications—especially in emerging areas like AI in supply chain and cloud infrastructure. Career paths aren’t always linear; employees often transition between roles, say from development to product management, supported by leadership’s openness.
Because Odessa operates at the intersection of technology and logistics, employees gain rare hybrid skills that remain highly marketable. This blend creates fertile ground for future career moves, whether in specialized freight tech companies or broader SaaS firms. Mentorship programs and periodic performance reviews help employees identify strengths and areas for improvement, making growth deliberate rather than accidental.
Real Candidate Experience Patterns
Talking to recent candidates reveals a few consistent themes. Many mention the transparency of the process—interviewers tend to be candid about expectations and timelines, which reduces anxiety. The technical rounds often took longer than expected, especially with live problem-solving elements, which some found draining yet rewarding.
Candidates also note the importance of tailoring answers to Odessa’s niche—generic tech answers don’t impress as much as those rooted in logistics understanding. Some junior applicants felt challenged by industry jargon but saw it as a learning opportunity. Feedback turnaround times varied, with some candidates waiting weeks post-interview, so patience is part of the game.
Overall, those who prepared deeply and showed enthusiasm for freight technology had smoother experiences and better outcomes.
Comparison With Other Employers
Compared to broader tech giants or diversified SaaS firms, Odessa Technologies is more focused but offers a unique blend of domain specialization and mid-size company culture. Here’s a quick snapshot:
| Aspect | Odessa Technologies | Large SaaS Firms |
|---|---|---|
| Industry Focus | Specialized in freight and supply chain tech | Broader verticals, less niche depth |
| Interview Style | Mixed technical and behavioral with domain focus | Heavily technical and standardized across roles |
| Work Culture | Collaborative, adaptive, learning-oriented | Structured, often hierarchical |
| Career Growth | Cross-functional exposure, mentorship | Defined ladders, sometimes siloed |
| Salary Competitiveness | Mid-market, balanced with perks | Generally higher, but competitive environment |
In short, Odessa may appeal more to candidates seeking meaningful impact in a specialized field without the overwhelming scale of tech giants.
Expert Advice for Applicants
It’s tempting to focus only on technical preparation when applying to Odessa, but savvy candidates take a holistic approach. Understand the freight and supply chain space genuinely—read industry blogs, attend webinars, or study competitors. When answering interview questions, link your skills back to Odessa’s client challenges.
Don’t underestimate the cultural fit interviews. Odessa values humility, adaptability, and teamwork. Prepare real examples, not rehearsed answers. Show curiosity—ask about product roadmaps or team dynamics. Lastly, patience pays. The process may stretch longer than expected, but consistent communication and follow-up politely demonstrate your enthusiasm.
Frequently Asked Questions
What kind of interview questions does Odessa Technologies ask?
Expect a blend of technical questions tailored to logistics or freight challenges, behavioral questions assessing cultural fit, and scenario-based problems. Software roles focus on coding and system design, while product roles might get case studies.
How many interview rounds does the hiring process usually have?
Typically, candidates go through three to five rounds: initial HR screening, a technical assessment, technical interviews, managerial interviews, and a final HR/culture round.
Does Odessa sponsor work visas?
Sponsorship is limited and generally discussed early in the process. The company primarily hires candidates authorized to work in the US or Canada.
What is the salary range for entry-level software engineers?
Entry-level salaries generally fall between $75,000 and $90,000 depending on experience and location.
How can I best prepare for Odessa’s technical interviews?
Focus on coding problems related to routing, data structures, and APIs. Also, understand logistics concepts since Odessa integrates these into their assessments.
What is the work culture like at Odessa Technologies?
Collaborative, learning-focused, and adaptive. The company encourages open communication and values diversity of thought.
Final Perspective
Landing a job at Odessa Technologies is more than just passing technical tests—it’s about embracing a specialized industry and showing that you can thrive in a company balancing innovation with operational excellence. Candidates who take the time to understand Odessa’s products, mission, and culture tend to shine.
Approach the hiring process as a two-way conversation—not just a test. Prepare thoroughly on technical and domain knowledge, but also be ready to share your story authentically. Odessa may not be the loudest name in tech, but for those passionate about logistics and software innovation, it offers a career path rich with challenge, growth, and impact.
Odessa Technologies Interview Questions and Answers
Updated 21 Feb 2026Technical Support Specialist Interview Experience
Candidate: Emily Zhang
Experience Level: Mid-level
Applied Via: Indeed
Difficulty:
Final Result: Rejected
Interview Process
2
Questions Asked
- How do you handle difficult customers?
- Explain a time you resolved a technical issue under pressure.
- What tools do you use for ticket management?
- Describe your experience with troubleshooting software problems.
Advice
Prepare examples of customer service scenarios and technical problem-solving.
Full Experience
The interview process included a phone screening and a video interview. The questions tested both my technical knowledge and customer service skills. Although I was not selected, the interviewers provided constructive feedback.
Quality Assurance Engineer Interview Experience
Candidate: David Kim
Experience Level: Entry-level
Applied Via: Job Fair
Difficulty: Easy
Final Result:
Interview Process
2
Questions Asked
- What is the difference between manual and automated testing?
- Describe your experience with test case creation.
- How do you handle bug reporting?
Advice
Be clear about your testing knowledge and show enthusiasm to learn.
Full Experience
I met the recruiter at a job fair and submitted my resume. The first round was a phone interview focusing on basic QA concepts. The second round was a technical interview with practical questions. The process was straightforward and welcoming.
Product Manager Interview Experience
Candidate: Clara Martinez
Experience Level: Mid-level
Applied Via: Referral
Difficulty:
Final Result:
Interview Process
3
Questions Asked
- How do you prioritize product features?
- Describe a time you managed conflicting stakeholder interests.
- What tools do you use for product roadmapping?
- Explain how you measure product success.
Advice
Focus on communication skills and demonstrate your ability to manage cross-functional teams.
Full Experience
I was referred by a current employee and had a phone interview followed by a panel interview. The questions focused on my experience managing products and working with teams. The interviewers were interested in how I handle challenges and prioritize tasks.
Data Scientist Interview Experience
Candidate: Brian Lee
Experience Level: Senior
Applied Via: Company Website
Difficulty: Hard
Final Result: Rejected
Interview Process
4
Questions Asked
- Explain the difference between supervised and unsupervised learning.
- How would you handle missing data in a dataset?
- Describe a machine learning project you led.
- Write SQL queries to extract data for analysis.
- What metrics do you use to evaluate model performance?
Advice
Prepare for both technical and case study questions, and have clear examples of your work.
Full Experience
The interview process was rigorous with multiple rounds including a technical test, a case study presentation, and behavioral interviews. The questions were challenging, especially the case study which required real-time problem solving. Although I was not selected, the experience was valuable.
Software Engineer Interview Experience
Candidate: Alice Johnson
Experience Level: Mid-level
Applied Via: LinkedIn
Difficulty:
Final Result:
Interview Process
3
Questions Asked
- Explain the concept of OOP and its principles.
- Write a function to reverse a linked list.
- How do you handle version control in your projects?
- Describe a challenging bug you fixed.
Advice
Brush up on data structures and be ready to discuss past projects in detail.
Full Experience
I applied through LinkedIn and was invited to a phone screening focusing on my technical background. The second round was a coding challenge where I had to solve algorithm problems. The final round was an onsite interview with the team, including behavioral questions and system design. The process was smooth, and the interviewers were friendly.
Frequently Asked Questions in Odessa Technologies
Have a question about the hiring process, company policies, or work environment? Ask the community or browse existing questions here.
Common Interview Questions in Odessa Technologies
Q: A hare and a tortoise have a race along a circle of 100 yards diameter. The tortoise goes in one directionand the hare in the other. The hare starts after the tortoise has covered 1/5 of its distance and that too leisurely.The hare and tortoise meet when the hare has covered only 1/8 of the distance. By what factor should the hareincrease its speed so as to tie the race?
Q: A rich merchant had collected many gold coins. He did not want anybody to know about them. One day his wife asked, "How many gold coins do we have?" After pausing a moment, he replied, "Well! If I divide the coins into two unequal numbers, then 32 times the difference between the two numbers equals the difference between the squares of the two numbers."The wife looked puzzled. Can you help the merchant's wife by finding out how many gold coins they have?
Q: 9 cards are there. You have to arrange them in a 3*3 matrix. Cards are of 4 colors. They are red, yellow, blue and green. Conditions for arrangement: one red card must be in first row or second row. 2 green cards should be in 3rd column. Yellow cards must be in the 3 corners only. Two blue cards must be in the 2nd row. At least one green card in each row.
Q: Consider a pile of Diamonds on a table. A thief enters and steals 1/2 of the total quantity and then again 2 extra from the remaining. After some time a second thief enters and steals 1/2 of the remaining+2. Then 3rd thief enters and steals 1/2 of the remaining+2. Then 4th thief enters and steals 1/2 of the remaining+2. When the 5th one enters he finds 1 diamond on the table. Find out the total no. of diamonds originally on the table before the 1st thief entered.
Q: There are two balls touching each other circumferencically. The radius of the big ball is 4 times the diameter of the small all. The outer small ball rotates in anticlockwise direction circumferencically over the bigger one at the rate of 16 rev/sec. The bigger wheel also rotates anticlockwise at N rev/sec. What is 'N' for the horizontal line from the centre of small wheel always is horizontal.
Q: 3 policemen and 3 thieves had to cross a river using a small boat. Only two can use the boat for a trip. All the 3 policemen and only 1 thief knew to ride the boat. If 2 thieves and 1 policeman were left behind they would kill him. But none of them escaped from the policemen. How would they be able to cross the river?
Q: 36 people {a1, a2, ..., a36} meet and shake hands in a circular fashion. In other words, there are totally 36 handshakes involving the pairs, {a1, a2}, {a2, a3}, ..., {a35, a36}, {a36, a1}. Then size of the smallest set of people such that the res...
Q: T, U, V are 3 friends digging groups in fields. If T & U can complete i groove in 4 days &, U & V can complete 1 groove in 3 days & V & T can complete in 2 days. Find how many days each takes to complete 1 groove individually.
Q: A light bulb is hanging in a room. Outside of the room there are three switches, of which only one is connected to the lamp. In the starting situation, all switches are 'off' and the bulb is not lit. If it is allowed to check in the room only once.How would you know which is the switch?
Q: ABCDE are sisters. Each of them gives 4 gifts and each receives 4 gifts No two sisters give the same combination ( e.g. if A gives 4 gifts to B then no other sisters can give four to other one.)Â (i) B gives four to A.(ii) C gives 3 to E. How much did A,B,C,E give to D?
Q: There is a room with a door (closed) and three light bulbs. Outside the room there are three switches, connected to the bulbs. You may manipulate the switches as you wish, but once you open the door you can't change them. Identify each switch with its bulb.
Q: The egg vendor calls on his first customer and sells half his eggs and half an egg. To the second customer, he sells half of what he had left and half an egg and to the third customer he sells half of what he had then left and half an egg. By the way he did not break any eggs. In the end three eggs were remaining . How many total eggs he was having ?
Q: A long, long time ago, two Egyptian camel drivers were fighting for the hand of the daughter of the sheik of Abbudzjabbu. The sheik, who liked neither of these men to become the future husband of his daughter, came up with a clever plan: a race would dete
Q: Tom has three boxes with fruits in his barn: one box with apples, one box with pears, and one box with both apples and pears. The boxes have labels that describe the contents, but none of these labels is on the right box. How can Tom, by taking only one p
Q: In a Park, N persons stand on the circumference of a circle at distinct points. Each possible pair of persons, not standing next to each other, sings a two-minute song ? one pair immediately after the other. If the total time taken for singing is 28 minutes, what is N?
Q: If I walk with 30 miles/hr i reach 1 hour before and if i walk with 20 miles/hr i reach 1 hour late. Find the distance between 2 points and the exact time of reaching destination is 11 am then find the speed with which it walks.
Q: Given a collection of points P in the plane , a 1-set is a point in P that can be separated from the rest by a line, .i.e the point lies on one side of the line while the others lie on the other side. The number of 1-sets of P is denoted by n1(P)....
Q: Consider a series in which 8 teams are participating. each team plays twice with all other teams. 4 of them will go to the semi final. How many matches should a team win, so that it will ensure that it will go to semi finals.?
Q: Jack and his wife went to a party where four other married couples were present. Every person shook hands with everyone he or she was not acquainted with. When the handshaking was over, Jack asked everyone, including his own wife, how many hands they shook?
Q: An escalator is descending at constant speed. A walks down and takes 50 steps to reach the bottom. B runs down and takes 90 steps in the same time as A takes 10 steps. How many steps are visible when the escalator is not operating.Â