2

No Experience Entry Level Database Administrator Jobs

... experience performing DBA like tasks · Two (2)+ years of broad-based IT experience Desired Qualifications: · Experience with SQL Language (SELECT, INSERT, UPDATE, DELETE) · Familiarity with ...

Datavail is seeking an experienced Oracle DBA to support managed service engagements and maintain the performance, availability, and security of production Oracle databases. * The ideal candidate has ...

Datavail is seeking an experienced Oracle DBA to support managed service engagements and maintain the performance, availability, and security of production Oracle databases. * The ideal candidate has ...

Mindlance is an Information Technology and Services company seeking an Entry Level Database ... experience • Leadership capabilities • Ability to prepare and implement database standards and ...

A Database Administrator (DBA) is responsible for the installation, configuration, maintenance, and ... Experience with database administration tools and utilities - Ability to work with large datasets ...

Datavail is seeking an experienced Oracle DBA to support managed service engagements and maintain the performance, availability, and security of production Oracle databases. * The ideal candidate has ...

... the entry-level and first time move-up markets. The Company also provides mortgage financing and ... Zero to two years' experience as a Production SQL Server or DBA * Strong verbal communication and ...

New

... the entry-level and first time move-up markets. The Company also provides mortgage financing and ... Zero to two years' experience as a Production SQL Server or DBA * Strong verbal communication and ...

New

Showing results 21-40

No Experience Entry Level Database Administrator information

See salary details

$10

$49

$74

How much do no experience entry level database administrator jobs pay per hour?

As of Sep 13, 2026, the average hourly pay for no experience entry level database administrator in the United States is $49.16, according to ZipRecruiter salary data. Most workers in this role earn between $38.46 and $59.13 per hour, depending on experience, location, and employer.

What is a no experience entry level database administrator?

A No Experience Entry Level Database Administrator is a professional who is just starting out in the field of database administration and typically has little to no prior hands-on experience. Their primary responsibilities include assisting with database setup, maintenance, monitoring, and basic troubleshooting under the guidance of senior staff. These roles are designed for individuals who may have foundational knowledge from coursework, certifications, or self-study but are looking to gain practical experience on the job. Entry-level DBAs often work with popular database systems like MySQL, SQL Server, or Oracle, and are expected to learn and grow into more advanced responsibilities over time.

What are the key skills and qualifications needed to thrive as a no experience entry level database administrator?

To thrive as a No Experience Entry Level Database Administrator, you need a basic understanding of database concepts, SQL, and a relevant degree or coursework in computer science or information systems. Familiarity with database management systems like MySQL, Oracle, or Microsoft SQL Server, and willingness to pursue certifications such as Microsoft Certified: Azure Data Fundamentals can be advantageous. Attention to detail, problem-solving skills, and effective communication are important soft skills for learning quickly and collaborating with IT teams. These abilities help ensure data accuracy, system reliability, and a smooth transition into more advanced database administration responsibilities.

What types of training and support can I expect as a no experience entry level database administrator?

As a No Experience Entry Level Database Administrator, you will typically receive comprehensive on-the-job training and mentoring from senior DBAs or IT staff. Many organizations provide structured onboarding programs, including access to database management tutorials, hands-on labs, and internal documentation. You may also participate in team meetings and shadow experienced colleagues to learn about daily tasks like monitoring database performance, backing up data, and responding to user requests. The work environment is usually collaborative, with regular feedback and opportunities to ask questions, helping you build confidence and develop essential technical skills.

What is the difference between No Experience Entry Level Database Administrator vs Data Analyst?

AspectNo Experience Entry Level Database AdministratorData Analyst
Required CredentialsBasic understanding of databases, possibly a certificate or associate degreeDegree in statistics, mathematics, or related field; some certifications beneficial
Work EnvironmentIT departments, data centers, or cloud environmentsBusiness, finance, or marketing teams; office settings
Employer & Industry UsageTech companies, organizations managing large data systemsBusinesses analyzing data for insights, reporting, and decision-making

While both roles involve working with data, a No Experience Entry Level Database Administrator focuses on managing and maintaining databases, whereas a Data Analyst interprets data to provide insights. Entry-level database administrators typically require basic technical skills, while data analysts often need analytical and statistical skills. Both roles are essential in data-driven industries but serve different functions.

More about No Experience Entry Level Database Administrator jobs

What cities are hiring for No Experience Entry Level Database Administrator jobs?

Cities with the most No Experience Entry Level Database Administrator job openings:

What states have the most No Experience Entry Level Database Administrator jobs?

States with the most job openings for No Experience Entry Level Database Administrator jobs include:

What are popular job titles related to No Experience Entry Level Database Administrator jobs?

For No Experience Entry Level Database Administrator jobs, the most frequently searched job titles are:

Infographic showing various No Experience Entry Level Database Administrator job openings in the United States as of September 2026, with employment types broken down into 1% As Needed, 76% Full Time, 19% Part Time, and 4% Contract. Highlights an 87% Physical, 2% Hybrid, and 11% Remote job distribution, with an average salary of $102,260 per year, or $49.2 per hour.

BigQuery Database Administrator (DBA)

Chicago, IL • On-site

Co-Sourcing Partners
51 - 200 employees

Contractor

Re-posted 24 days ago


Job description

Position: BigQuery Database Administrator (DBA)
Location: Chicago preferred; remote within the U.S. considered
Employment Type: 6-Month Contract-to-Hire
Work Authorization: U.S. Citizen or Green Card holder; no visa sponsorship
Overview
The BigQuery Database Administrator will take ownership of the performance, reliability, security, and operational effectiveness of enterprise data environments built on Google BigQuery and Google Cloud Platform (GCP). This person will administer and optimize BigQuery workloads, troubleshoot performance issues, strengthen monitoring and access controls, and help ensure enterprise data remains available, secure, scalable, and cost-efficient. The DBA will also play an important role in data-platform modernization, supporting migrations from legacy database environments into modern cloud-based architectures and validating data throughout the transition. Working closely with data engineers, architects, application teams, and business stakeholders, this person will support integrations using Talend or comparable ETL technologies and recommend practical cloud data best practices. Success requires someone who can move beyond reactive database support to proactively identify risks, optimize the environment, and help build a more scalable and reliable cloud data platform.
Proposition
Purpose: Take ownership of a strategically important BigQuery environment and help transform enterprise data infrastructure into a secure, scalable, high-performing cloud platform. The work will directly influence the reliability, performance, cost efficiency, and modernization of data used across the business.
Growth: Expand beyond traditional database administration into modern cloud data architecture, BigQuery optimization, GCP services, enterprise data integration, governance, and large-scale modernization. The role provides exposure to complex migration and transformation initiatives while working closely with engineering and architecture teams.
Motivators: This opportunity is suited to someone who enjoys solving difficult database and performance problems, improving complex environments, and seeing measurable results from technical decisions. The person will have meaningful ownership, opportunities to establish best practices, and the ability to influence how the organization operates and scales its cloud data platform.
Objectives
1. Stabilize and Establish Operational Control of the BigQuery Environment. Within the first 60 days, assess the existing BigQuery and supporting GCP environment and establish a clear baseline for performance, reliability, security, access, workload behavior, and operational risks. Identify critical issues involving queries, capacity, data structures, permissions, monitoring, availability, or support processes and implement prioritized improvements. Establish proactive monitoring and repeatable troubleshooting practices that allow problems to be identified and resolved before materially affecting users or downstream systems. Success will be measured by improved environment stability, visibility into critical workloads, timely resolution of priority issues, documented operating practices, and reduced recurring incidents.
2. Improve BigQuery Performance, Scalability, and Cost Efficiency. Within the first 3 months, analyze high-impact BigQuery workloads, SQL queries, data structures, usage patterns, and resource consumption to identify opportunities for measurable optimization. Implement appropriate improvements involving query design, partitioning, clustering, data organization, workload management, or other BigQuery optimization techniques while balancing performance, scalability, reliability, and cost. Partner with engineering teams to prevent inefficient patterns from being repeatedly introduced. Success will be measured through documented improvements in priority workload performance, resource efficiency, query reliability, and cost visibility, with baseline and post-improvement results used where data is available. AI-assisted SQL analysis and optimization tools may be used when recommendations are independently validated.
3. Support Successful Data Modernization and Cloud Migration. During the first 3 months and throughout modernization initiatives, support the migration of legacy database workloads and data into BigQuery and related GCP services. Assess source environments, support migration planning and transformation activities, identify compatibility and data-quality risks, and validate migrated data for completeness, accuracy, and expected performance. Work with Talend or comparable ETL/data integration technologies to support reliable ingestion, transformation, and integration processes. Success will be measured by accurate migrations, timely resolution of data or performance issues, validated source-to-target results, minimal disruption to dependent systems, and successful transition of workloads into supportable cloud environments.
4. Establish a Secure, Scalable BigQuery Operating Model. Over the first 3-6months, help establish repeatable standards and best practices for BigQuery administration, security, IAM, monitoring, performance management, data integration, troubleshooting, and change management. Collaborate with architects and data engineers to ensure new solutions are designed for scalability, maintainability, governance, and operational support rather than requiring repeated remediation after deployment. Document reusable practices and recommendations that improve consistency across the data platform. Success will be measured by stronger operational standards, improved security and governance controls, reduced recurring issues, better maintainability, and increased confidence in the platform's ability to support future growth.
Subtasks
1. Assess the BigQuery and GCP Environment. Within the first 30 days, review the current BigQuery architecture, workloads, data structures, SQL patterns, integrations, IAM configuration, monitoring, security controls, and operational processes. Identify immediate risks, performance bottlenecks, recurring incidents, and modernization dependencies and produce a prioritized improvement plan. Success will be measured by a validated baseline, clear priorities, and early resolution of critical operational issues.
2. Establish Proactive Monitoring and Troubleshooting. Within the first 60 days, strengthen monitoring of BigQuery workloads, query performance, failures, resource usage, integrations, and other critical indicators. Develop repeatable troubleshooting and root-cause practices and document recurring issues and resolutions. Success will be measured by faster issue identification and resolution, improved operational visibility, fewer repeated problems, and increased platform reliability.
3. Optimize SQL, Queries, and Data Structures. During the first 3 months, identify high-impact performance and cost issues and optimize SQL, query patterns, schemas, partitioning, clustering, and related BigQuery structures where appropriate. Work with developers and data engineers to improve inefficient designs and establish practical optimization guidelines. Success will be measured by documented improvements in priority query performance, reliability, scalability, or resource efficiency.
4. Strengthen Security, IAM, and Data Governance Controls. During the first 3-6 months, evaluate and improve access management, IAM, permissions, security controls, and relevant governance practices across BigQuery and supporting GCP services. Identify excessive or inappropriate access, support remediation, and ensure controls align with organizational security and compliance requirements. Success will be measured by stronger access controls, documented governance practices, timely remediation of identified risks, and successful compliance with applicable standards.
5. Execute Data Integration and Modernization Activities. Throughout the first 3 months, support ingestion, transformation, migration, and integration workflows using Talend or comparable ETL tools and relevant GCP services. Collaborate with engineers and architects to move legacy data and workloads into scalable cloud architectures while validating data accuracy and resolving transformation issues. Success will be measured by reliable pipelines, accurate migrated data, successful cutovers, and minimal disruption to dependent applications and users.
6. Establish DBA Best Practices and Cross-Team Collaboration. Over the first 3-6 months, document and promote standards for BigQuery administration, monitoring, SQL optimization, troubleshooting, security, migration, and operational support. Participate in architecture and technical discussions and provide practical recommendations to data engineers, architects, and application teams. Success will be measured by adoption of repeatable practices, reduced avoidable technical issues, improved cross-team execution, and a more maintainable enterprise data platform.
7. Continuously Evaluate and Integrate AI to Improve Performance. Within the first 45 days, identify how AI and automation can improve BigQuery administration, SQL optimization, monitoring, anomaly detection, troubleshooting, migration validation, documentation, and operational support. Evaluate approved AI-enabled tools and lead practical pilots where automation can reduce manual effort, accelerate root-cause analysis, or improve platform performance and reliability. Validate all AI-generated recommendations, scripts, SQL, and configurations before production use and maintain required security and governance controls. Success will be measured by demonstrated improvements in DBA productivity, issue resolution, optimization effectiveness, or platform reliability and by embedding responsible AI-assisted practices into ongoing operations.