In his book, Jordan Seos first mentioned that he started working at Google in 1995, when he was still just a teenager.
When he graduated, Seo went to work for the search giant as a copywriter and began to get noticed.
In 2000, he joined the company as an executive and has been there ever since.
Today, Jordan is a partner in Google’s global design studio, and he says that, while he doesn’t know the details of his early days at the company, he has been lucky enough to learn a lot from his peers.
“One thing I’m incredibly proud of is how the company has developed and adapted to the needs of the times,” he says.
“In the early days, we were all about the search, and that was a great place to be.
We were in a world where you had to build a new product every time you needed to make a new feature.”
The Search for a Product, however, wasn’t so easy, and many early versions of the product were far too complicated to be of any use to consumers.
Seo remembers one particularly frustrating project.
“We were looking at the design of an application that would be built with a different platform,” he recalls.
“There was no way to create that.
It had to be built in a specific way and then have a way of interacting with that platform.
We had to create a platform, then we had to have an interface to it.”
Jordan explains that the first thing he did to solve this was to write a template that explained how the search results would work.
“Then we just created a little tool, which is now called a UI builder, to create this application and we just did it for free,” he explains.
“And we had no idea how it was going to work.
We thought we would make it work, but then it would fail, and we would get to another point in time and it would all be over.
That was the worst thing that I ever did.”
He admits that, back then, the search engine was not the type of place that would allow anyone to start designing applications and building web applications, but the way the company worked in the early 2000s helped him.
“That was the golden age of search,” he reflects.
“Search is the place where you go, you build an application, and you’re like, ‘Oh wow, this looks great.
How are we going to build this?'”
As the company grew, Jordan found it necessary to hire more and more people as he continued to learn about the technology.
He believes that, as a result, the company today has over 4,000 employees and a product that he has helped to build.
As an executive at Google, Seos has a lot of experience with the company’s search algorithms.
He says that he’s used the company tools to create “many products that have been used on hundreds of millions of users around the world.”
But he believes that it wasn’t until the company came to him in 2004 that he really understood what was going on with search and how the system worked.
“We had a search product that was actually a bit old.
And the company had this new system that they called Search Engine Optimization,” he notes.
“They were looking for something to help search.
They were looking to build their own system to do it, and they were going to do that in a few years.”
But this was a time when the company didn’t really know how to build an effective search system.
“I started working with the team, and the first time I actually started using the search product, it was really difficult for me,” he continues.
“It was a completely different environment, and I was kind of learning the same thing, trying to make it better.
And then I started working on it, eventually it became a product I really loved.”
As part of the search team, Seom started building an API to help the company build more efficient search, which helped him build a lot more powerful search features for Google.
At one point, he says, he even designed an interface that was so powerful that it was able to rank Google in the top five of the most popular search results in the world.
But when the time came to start making the next version of the company search product more powerful, Seoc started to see some of the challenges that he and the company were facing.
“That was in 2005,” he recounts.
“The first thing I did was to create the first version of our API, and it was a very rough interface, and there was a lot that I wanted to improve, but I didn’t know how.
The next thing I tried to do was make a UI for it, but it was very hard.
So I started writing a template to explain what the interface should look like, but what I really
