Database Developer - SQL Server
MeridianLink - Costa Mesa, CA

This job posting is no longer available on Indeed. Find similar jobs: Database Developer jobs - MeridianLink jobs

JOB SUMMARY
In this position, you will work closely with developers and system engineers to manage the company’s SQL Server databases. As a valuable member of the IT team, you will address a variety of technical challenges and contribute your talents toward keeping our IT department running smoothly. The DB Programmer/Administrator will:

  • Perform day-to-day monitoring of SQL Servers
  • Utilize proficient database programming skills and experience
  • Maintain database security and patches
  • Install and upgrade databases
  • Provide solutions for database issues including capacity, redundancy, replication and performance tuning
  • Provide development team with technical support and troubleshooting skills relating to database issues

QUALIFICATIONS

  • Bachelor’s or Master’s degree from an accredited college/univeristy in Computer Science, Information Systems, Human Computer Interaction, Informatics, Cognitive Science, Applied Mathematics, Statistics, Engineering, Physics, technical related field
  • 3+ years of database programming/scripting experience
  • Creative, logical, and detail-oriented
  • Good verbal and written communication skills
  • Advanced computer knowledge and problem-solving skills
  • Must be able to code in one computer programming language, preferably C#.
  • Experience in database management

PLEASE ANSWER THE FOLLOWING QUESTIONS WHEN APPLYING TO THIS POSITION.
You may include answers in the message section.
Choose the best answer, not multiple answers.
Cut and paste the entire questionnaire, and indicate which answer you choose with an X after the choices.
Q1: I design new tables
1. Never. I deal with tables other people made.
2. A couple of times a quarter.
3. Once a month.
4. Every week – I’m very familiar with data modeling tools, and I own data modeling books.
Q2: When I write new queries, I
1. Use the same syntax I’ve been using for years.
2. I look in books/blog online periodically to see if there’s a better way to get this done.
3. I regularly watch webcasts/blogs to see how I can improve my T-SQL.
4. I present on things at my local user group.
Q3: When I deploy changes, I
1. Make them live in production. What, is there something else?
2. Script them out first, and test them in development.
3. Script them out, test them, document the change that I’m expecting, and monitor afterwards to make sure I got the change I was expecting.
4. Check the changes into source control, have someone else test them, and then deploy them in an automated fashion.
Q4: When I tune queries:
1. I feel like I’m fumbling around in the dark, groping indexes and execution plans blindly.
2. I know when I should apply a missing index recommendation, and when I shouldn’t.
3. I know how to handcraft an index to improve a query even when there’s no missing index recommendation.
4. I can recognize when I’m getting the wrong join for a query, and I know when I should influence SQL Server to pick the right one.
Q5: When the end-users say SQL is slow, I:
1. Am completely surprised.
2. Know which SQL Server metrics to look at.
3. Know what my server’s normal baselines are for any given metric.
4. Tell them I already knew about it because I have alerting set up correctly, with thresholds configured properly for my baselines, and I don’t have email rules set up to push all alerts into a different folder.
Q6: When SQL goes down, I:
1. Am completely surprised.
2. Remote desktop in and start poking around.
3. Have a rough idea of what logs I need to hit, in what order, and I am confident in how much time it will take to fail over to my secondary servers.
4. Grab my customized First Responder Kit and step through my well-rehearsed troubleshooting steps.
Q7: When I install SQL Server, I:
1. Run setup.exe
2. Google for a setup best practices checklist.
3. Grab my customized checklist that has my company-specific settings.
4. Get my prepped installation files off the file share and run an automated installation.
Q8: When I design SQL High Availability (HA)/Disaster Recovery (DR), I:
1. Wait, what do you mean design? My SQL Server instances are standalones.
2. Use the same HA/DR techniques I’ve been using for years, and I only know those one or two.
3. Have a pretty good idea of what my options are, and I work with the business to pick the right solution.
4. Get the business’s RPO and RTO requirements in writing, then write down a few options with them with budget estimates.

MeridianLink is an Equal Opportunity Employer. We do not discriminate on the basis of race, religion, color, sex, age, national origin, disability or any other characteristic protected by applicable law


Indeed - 6 months ago - save job