OBJECTIVE:

To find a challenging role that is vital to the everyday business of an organization as it pertains to the administration, design, warehousing, analysis, manipulation, and/or transformation of application data or data related tasks. I would like to in corporate a more analytical aspect to my responsibilities in order to utilize my mathematical skill set. I am always looking to learn new technologies and be challenged.

SUMMARY:

• Experience with PostgreSQL and MySQL database administration. General database architecture and design experience.
• Experience setting up and maintaining replication for redundant production PostgreSQL and MySQL database servers.
• Experience writing and optimizing complex SQL queries and SQL scripts for reporting and/or data manipulation.
• Experience producing Ad - Hoc reports from queries as requested by the customer or creating scripts and programs to produce reports (internally or for customers).
• Experience working in a Linux (CentOS) environment and Windows environments.
• Experience installing various technologies; including PostgreSQL and MySQL from source code on a fresh Linux OS.
• Familiar with many user-oriented computer programs such as Pervasive, Word, Excel, PowerPoint, Data Analytics
• Reliable, dependable, self-sufficient, detailed, great team worker
• Experience learning new technologies and business ideology from others as well as individually.

TECHNICAL SKILLS:

Familiar with: PostgreSQL(heavy admin, heavy usage experience), MSSQL Server (heavy usage, minimal admin experience), Oracle (occasional usage, very minimal admin experience), MySQL (Minimal usage, minimal admin experience) and Microsoft Access (heavy usage)

Languages: SQL, Perl, VB Script, SVN, C++, C, C#, VB6, VBA, RIFL, Winbatch; exposure to shell scripting

EXPERIENCE:

Reservoir Engineering Technician

Confidential, Austin, TX

Responsibilities:

• The responsibilities of this position include the manipulation, loading, reporting, cleanup and analysis of oil well data for multiple purposes from analyzing the financial impact of each well to assisting the engineers in forecasting how long each well will be economical. I am in charge of the databases that house all of the data for the team.
• Most of the reports that are generated are submitted in MS Excel and we use various queries, formulas, macros and VBA code to reach the desired, formatted output.
• This also involves the creation of programs written in VBA for the specific reporting needs of the engineers as well as manipulating, loading, and reporting of the data in relation to the database.
• Many of the data inquiries are ad-hoc and time sensitive.
• This role requires that I produce accurate results in a timely matter. I have been working intensively to assure the accuracy of our current reserves database for year end reporting.
• The accuracy of this data is imperative to the company’s business plan as the forecasts that will plan the next 30 years by looking at our proved reserves.
• There are multiple oil industry specific software applications that are used in these processes including ARIES, Production Access, Excalibur, and Spotfire (though this one is not oil specific, it can be used to graphically analyze any type of data set).
• While I am a part of the reservoir team, I also assist many of the other teams such as production, geology, land, and midstream.
• Since I have been here, my biggest accomplishment has been creating a database that is being used to relate the unique data between all of the specific disciplines (geology, reservoir, completion, drilling, etc).
• I created the structure to house data that was previously only kept in multiple spreadsheets.
• It is now readily available and can be tied together with other pieces of data for a more accurate and complete analysis.
• There was not a way of doing this before without collecting many spreadsheets and piece-mealing the data together.
• The feedback to this project has been overwhelmingly positive and will get better and be more impactful going forward.
• MSSQL server is the current database technology that is used to store all of our data.

Database Administrator/Architect/Developer

Confidential, Austin, TX

Responsibilities:

• This position is that of a DBA who administers, maintains, and designs the databases (PostgreSQL 85%, MySQL 10%, Oracle 2.5%, MSSQL 2.5%) as well as handles all data-related tasks for hosted international and domestic shipping applications.
• I am in charge of all aspects of the database servers from setting up the physical server in a freshly installed OS to maintaining the integrity of the data that ends up in the tables.
• I am responsible for database design and optimization of SQL queries during the new development cycle of hosted applications.
• I am asked to handle ad-hoc reporting requests of the data which requires an ability to relate and extract the data in a manner that satisfies specific needs; this sometimes requires logical manipulation of the data. Additionally, I troubleshoot database performance issues, actively analyze log files to spot issues, keep current backups, monitor and maintain high availability (redundant failover) clusters for the hosted applications, and take care of customer specific tasks pertaining to data load/manipulation/extraction/etc.
• Projects and tasks involve coding in a scripting language, such as Perl.
• I am responsible for creating, maintaining and running various data load processes that include transformation, manipulation, and regular updates of the data.
• These tasks along with questions and/or requests from colleagues and clients involve a great amount of data analysis.
• This position (when I was full time) required me to be on call and available 24x7. The databases are hosted on Linux servers (CentOS).
• I was initially hired to this position as someone to be trained in all aspects of database administration on PostgreSQL databases, having had no experience with database administration or the use of the PostgreSQL server.
• After 7 months, the person training me unexpectedly left the company leaving me as the only DBA and in charge of all responsibilities of the position.
• There had always been 2 DBAs and initially there was a heavy search for a senior level PostgreSQL database administrator to replace the senior dba who left.
• After a couple of months of not finding an adequate replacement, my manager was impressed and pleased with my progress to the point where he stopped searching for another database administrator in any capacity.
• The Austin branch of the company was shut down and the positions moved to various locations except for the IT department (DBA and 2 system administrators), at which time I accepted my current position for job security reasons.
• I was kept on as a contractor to continue with the tasks and eventually train a replacement.

Data Services Technician

Confidential, Austin, TX

Responsibilities:

• I converted such insurance data as events, claims, payments, reserves, litigation, policy, HR, etc. for the self insured companies that purchased our software.
• This involved being interactive with the client throughout the course of the project (over the phone for data mapping sessions/questions/issues/status meetings, in person for data mapping sessions, or through email), problem solving, working on multiple servers, massive amount of work in databases (SQL, Oracle, Access), writing queries to manipulate and analyze the data, writing code to create a client specific application in VB6 for monthly uploads of data based on the data conversion, writing RIFL(similar to VB script) code in Pervasive to transform and/or clean the data, data mapping from a data set to our systems’ specifications, producing analysis and reports of erroneous data, balancing and producing the financial results and counts from the data conversion in order to ensure accuracy, and detailed documentation of client decisions on the project.
• This type of work requires an extreme attention to detail in order for every piece of data to be converted to the new system with the clients satisfaction.
• Most of the main data conversion work used an ETL (Extract, Transform, and Load) type of process.
• As stated before, there were also additional tasks such as creating monthly upload apps, data cleanup projects (these involved manipulation via SQL queries in most cases), and client specific and unique requests that cannot be planned for.
• Our team strived to maintain billable to the client and in order to do so, all of the techs are working on multiple projects simultaneously.
• Though I was the youngest and least experienced in converting data, I was the pioneer of many of the initial projects that aimed to start automating some of the repetitive processes and I was the first to complete a conversion using a new conversion tool that was written internally by the development team.
• My manager recognized early that some of my strengths are learning and figuring things out on my own; she trusted that I would do just that and come back to teach the team.
• I accepted the PostgreSQL DBA position because it was a good opportunity to learn and because of frequent layoffs occurring within Confidential at the time. After leaving, my manager at the time approached me about my interest in becoming a casual employee to work on an as needed basis.
• I did this for 6 months until she was told she needed to keep the amount of people that she managed at a certain number so I couldn’t maintain the casual employee status. My manager approached me again 9 months later with the same proposition.
• Though the work has not been very frequent lately, they have mentioned a desire to give me more work in the near future if I am up for it.
• The workload of this casual position has been about 2-4 hours per month.

.