A database engineer is a person who is responsible for data engineering or data programming in a production database. The skills required include but
A database engineer is a person who is responsible for data engineering or data programming in a production database. The skills required include but are not limited to database programming, object-relational mappings, object-relational mappings, database design, database maintenance, database security, and database maintenance.
That was a little confusing to me, but it really is that basic. If you’re asking us, should you be the one to work in a database, the answer is that it depends on what you’re doing and how you’re doing it. Some jobs in the database world involve technical tasks, some jobs involve people who are good at doing that kind of thing, and others involve people who are great at doing other things.
We were hired by one of those companies, so you can imagine we were in pretty good shape. But for different reasons from what we can remember.
As usual, we work in the database world of Oracle and SQL Server. It’s our job to make sure all our databases work together and perform as a whole. Our job is to make sure that our databases (and the web applications that run on them) are secure, reliable, and scalable.
So if you want a job where you can find yourself in a situation where you have to do a lot of “database-y” stuff, a good place to look is at a company that does “database-y” stuff. Oracle and SQL Server are big names in that field. For those of you that are wondering, I work for Oracle and I’m a big fan of the company.
Database engineers are people that design tables, connect to databases, and write SQL. So there are a lot of things that go into making a database-y system work. One thing that I like to do is work on web applications that need to run on web servers.
There are a lot of database engineers out there. In fact a recent study by the UK’s National Centre for Skills (think CERN for computer nerds) found that 80% of the job titles of databases engineers didn’t really exist in the first place. One of the reasons is that database engineers tend to be people who have spent all their time coding and designing and deploying web applications.
This is why I find myself working with open source software. It’s really easy to learn and once you get your hands dirty you can spend years (or more) developing software. I find that I can do anything I want with databases, which is why I decided to leave my job in the first place. Also, I believe that I could be a much better database engineer than I am and I think I have the skills to do that.
Now that I have more free time I find that I am working with a lot more databases than I used to. There are lots of open source databases out there that I used to work in, but now I spend most of my time working on custom database design and development projects. And I love it.
I would love to be a database engineer. I would LOVE to find a job where I get to work on all sorts of databases and be able to work with some really creative people. The truth is, I don’t have the skills I need to be a database engineer. That is not to say I don’t have the skills. I just don’t have the right tools.