### You only have free questions left (including this one).

But it doesn't have to end here! Sign up for the 7-day coding interview crash course and you'll get a free Interview Cake problem every week.

A crack team of love scientists from OkEros (a hot new dating site) have devised a way to represent dating profiles as rectangles on a two-dimensional plane.

They need help writing an algorithm to find the intersection of two users' love rectangles. They suspect finding that intersection is the key to a matching algorithm so powerful it will cause an immediate acquisition by Google or Facebook or Obama or something.

Write a method to find the rectangular intersection of two given love rectangles.

As with the example above, love rectangles are always "straight" and never "diagonal." More rigorously: each side is parallel with either the x-axis or the y-axis.

They are defined as objects of Rectangle class:

public class Rectangle { // coordinates of bottom left corner private int leftX; private int bottomY; // dimensions private int width; private int height; public Rectangle() {} public Rectangle(int leftX, int bottomY, int width, int height) { this.leftX = leftX; this.bottomY = bottomY; this.width = width; this.height = height; } public int getLeftX() { return leftX; } public int getBottomY() { return bottomY; } public int getWidth() { return width; } public int getHeight() { return height; } }

Your output rectangle should be a Rectangle object as well.

What if there is no intersection? Does your method do something reasonable in that case?

What if one rectangle is entirely contained in the other? Does your method do something reasonable in that case?

What if the rectangles don't really intersect but share an edge? Does your method do something reasonable in that case?

Do some parts of your method seem very similar? Can they be refactored so you repeat yourself less?

Actually, we don't support password-based login. Never have. Just the OAuth methods above. Why?

1. It's easy and quick. No "reset password" flow. No password to forget.
2. It lets us avoid storing passwords that hackers could access and use to try to log into our users' email or bank accounts.
3. It makes it harder for one person to share a paid Interview Cake account with multiple people.

Actually, we don't support password-based login. Never have. Just the OAuth methods above. Why?

1. It's easy and quick. No "reset password" flow. No password to forget.
2. It lets us avoid storing passwords that hackers could access and use to try to log into our users' email or bank accounts.
3. It makes it harder for one person to share a paid Interview Cake account with multiple people.

time and space.

What if we had an array of rectangles and wanted to find all the rectangular overlaps between all possible pairs of two rectangles within the array? Note that we'd be returning an array of rectangles.

What if we had an array of rectangles and wanted to find the overlap between all of them, if there was one? Note that we'd be returning a single rectangle.