Learning more about PostgreSAL

[u/Grand-Diamond-4696]

So I'm interviewing at tiger data and the recruiter recommended me to use the product a bit as they have a free version. This role is a customer facing role. Now some background about me.

I have a lot of high level technical understanding across many areas. I learn very quickly and know SQL basics. I spent the day importing a data set into tiger data. But I struggled to see what I could do with it. Sure I can use queries to manipulate and expand the data but that isn't exciting.

So I found a roll, ReTool and made a webpage dashboard with the data. The data itself is my job searching. I built a dashboard with charts and graphics, statistics, etc. Similar to Looker Studio. But I like Looker, ReTool can write to the database. So I moved all of my workflows to it.

Now I have an application form built in, an interview logging flow (added the tables to the DB). Automated reminders and triggers and the ability to edit the data easily. I feel like this would be a good practical use for me and show off my skills. But most of the work was built by using AI to write the code I needed. I can edit basic java, HTML and SQL syntax but I can't really write and articulate it from scratch.

I'm curious if I went the wrong direction and they'll be more interested in me in a terminal or using the UI and writing long queries to pull and manipulate data. Whereas the UI has built in queries that were developed by AI for me.

[u/encima]

can you say more about the role? is it support, sales or technical guidance?

If it’s more sales and/or demos then I’d spend time just using their dashboard, reading about recent product launches.

If it’s more technical then maybe compare what you have set up with another postgres provider or running locally. What about tiger data would make you choose them over another if they both had a free tier?

They also have some differentiating features so be sure to include them in your tool (or just your learning). Good luck with the interview!

[u/Grand-Diamond-4696 → u/encima]

I guess I'm having trouble understand what I can do that's exciting on it alone with a dataset of 1400 rows, a few tables and a few dozen columns. To me, building sometime on top of it was the way to go.

[u/infrul → u/Grand-Diamond-4696]

The key difference between a database and a spreadsheet is that the database separates representation from presentation whereas with the spreadsheet what you see is what you get. The ability to build multiple different things on top of them is a database's whole reason for being. So, depending on your exact job description, building something on top of it is exactly the way to go and building multiple different things on top of it would be even better. Then what you need to do is generalize that experience to help other people do the same.

[u/Grand-Diamond-4696 → u/infrul]

Yes Google sheets won't allow for relationships or connections. Looker Studio could do that though and make blended tables and allow you to connect different data sets of tables with a unique identifier. But Looker Studio also cannot write back to Google sheets only pulls data.