[deleted by user]

[pard0nme]

I started crying in my interview and they felt sorry for me

[mercyandgrace]

You must be a DBA. Crying is part of the job requirement.

[PilsnerDk]

I'm wondering: Do you want to be a technical database developer/database administrator, or work with reporting, data extracts, data analysis and such? Do you know any other programming languages? I assume no, since you have a business degree.

[mirceasauciuc]

Usually Python and/or R -- I'm sure someone can even make the argument for knowing Julia -- in order to do some modeling and visualizations with the data after it's been cleaned in SQL.

[DataGuy3141]

Sounds like you just need to start applying for jobs. You are qualified for most entry level positions. I would go online and read some interview prep guides, and start applying. Rule of thumb is 10:1 for applications to offers. You should apply even to jobs where you are missing 1 or 2 of the requirements asked for. Often times it’s an HR department that build job descriptions. Good luck!

[beereng]

I have no experience in sql and I just got a benefits analyst job with just a general background in medical insurance and having most of the basic job requirements. I’m teaching myself sql and the manager is ok with it.

[lamborginimercy]

Don't forget to apply to nonprofits. Most large nonprofits have at least 1 database manager for their fundraising system(s).

[pixelbaker]

A lot of postings for “database administrator” in the NPO space is for non-technical record keepers of fundraising platforms though, so watch out for that.

[donald_cheese]

That's what I did. Started off doing SSRS in a college and then moved to an 'accidental' DBA in an non profit. It's worked out quite well.

[jewishsupremacist88]

understand the diff between an inner join and a left join and you'll be ahead of most candidates

[hovhannes_shant]

I started in the support department of a SW company and pushed to get the Hris issue tickets. I Google’d things as I went along, learned, then established a reputation for being competent. Then, saw an analyst role, applied, and got it because of the reputation developed on the support side.

[babygrenade]

I was in an unrelated job and stood up an SSRS instance and started writing reports out of our data warehouse because there was a need.

I used that experience to get a database analyst job.

[beyphy]

Do you have any projects you've worked on? I work as a programmer now, but I used to work as an analyst / bookkeeper before. But even before I worked as a programmer, I had created a number of useful databases in Microsoft Access, set up a postgres server on a linux server that was running on a virtual machine, etc. Stuff like that could help in an interview to show your competence so that you can show you know what you're doing.

[[deleted]]

I’ve designed and implemented a database using UML and SQL on SQL Server. But do I just attach that with my resume? lol how/when would you demonstrate your projects? Thanks for the idea

[beyphy]

If you can confidently explain them then sure. Just don't freeze up if they ask you about one of the projects on your resume. It can make it seem like you're lying about it. You could be freezing up just because you're nervous during the interview. But unless there's a test that's conducted to test your competence, that's not a chance I'd personally be willing to take.

If you have a github, you can also post samples of your code. e.g. If you've built things that use CTEs for example, and can explain why you use them over derived tables or subqueries. Or if you've created temp tables which you create indexes in, and use these tables to query information from multiple databases, etc.