1

State Librarian Jobs in Rochester, MN (NOW HIRING)

State Librarian information

See Rochester, MN salary details

$31.5K

$66.3K

$104.2K

How much do state librarian jobs pay per year?

As of Sep 2, 2026, the average yearly pay for state librarian in Rochester, MN is $66,268.00, according to ZipRecruiter salary data. Most workers in this role earn between $52,300.00 and $76,200.00 per year, depending on experience, location, and employer.

What is a state librarian?

State Librarians are professionals who oversee the administration and management of a state's library system, including public libraries, archives, and library services. They are responsible for setting statewide library policies, managing funding and grants, advocating for library-related legislation, and supporting library development and innovation. State Librarians also serve as liaisons between the state government and local libraries, ensuring that library services meet the needs of all residents. Their work is crucial in promoting literacy, lifelong learning, and equal access to information.

What are the key skills and qualifications needed to thrive as a state librarian?

To thrive as a State Librarian, you need advanced knowledge of library science, management experience, and typically a Master's degree in Library and Information Science (MLIS). Familiarity with library management systems, digital archives, and relevant state and federal regulations is essential, along with professional certifications such as ALA-accredited credentials. Exceptional leadership, strategic planning, and advocacy skills set outstanding State Librarians apart. These skills ensure the effective administration of statewide library services, resource allocation, and advancement of public access to information.

What are some common challenges faced by a state librarian in managing statewide library services?

State Librarians often encounter challenges such as balancing limited budgets while ensuring equitable access to resources across diverse communities. They must also stay current with rapidly evolving technology and digital content to support both urban and rural libraries. Additionally, coordinating statewide initiatives requires strong collaboration with local libraries, government agencies, and educational institutions. Effective communication and strategic planning are key to overcoming these hurdles and meeting the needs of all library users.

What is the difference between State Librarian vs Public Library Director?

AspectState LibrarianPublic Library Director
CredentialsMaster's in Library Science (MLS) or equivalent, relevant experienceMLS or equivalent, experience in library management
Work EnvironmentState government, statewide library systemsLocal public libraries, community-focused
Employer & IndustryState agencies, library associationsMunicipal or regional government, community services
Common Search/ComparisonPolicy, statewide library programsPublic services, community engagement

The State Librarian oversees statewide library initiatives, policies, and services, working with state agencies. In contrast, a Public Library Director manages individual library branches or systems, focusing on local community needs. Both roles require similar credentials but differ in scope and work environment.

What are popular job titles related to State Librarian jobs in Rochester, MN?

For State Librarian jobs in Rochester, MN, the most frequently searched job titles are:

What job categories do people searching State Librarian jobs in Rochester, MN look for?

The top searched job categories for State Librarian jobs in Rochester, MN are:

What cities near Rochester, MN are hiring for State Librarian jobs?

Cities near Rochester, MN with the most State Librarian job openings:

Infographic showing various State Librarian job openings in Rochester, MN as of August 2026, with employment types broken down into 1% As Needed, 69% Full Time, 28% Part Time, and 2% Contract. Highlights an 93% Physical, 1% Hybrid, and 6% Remote job distribution, with an average salary of $66,268 per year, or $31.9 per hour.

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Rochester, MN • On-site

$20 - $30/hr

Full-time

Posted yesterday

New


Job description

Type: Contract, hourly

Location: Remote

Hours: 20–30 per week

Pay: $20–30/hour, based on experience and language coverage

Start: Immediate

ABOUT THE ROLE

We evaluate how well advanced AI coding agents solve real engineering problems. An agent is given a real open source codebase inside a container and a hard task, then works on its own for 80 to 250 steps. A trajectory is the full record of that run — every command, result, and decision.

You will do two jobs, and you should expect either on any given day.

•Annotate — Read a trajectory nobody has looked at yet and judge it step by step.

• Review — Take an existing annotation, written by our AI tooling or another person, and confirm, correct, or reject it.

TASKS YOU'LL SEE

• Feature build — Add a working feature to a live library without breaking anything that already worked.

• Rebuild — Work out what a compiled tool does by running it, then rebuild it to match its output, exit codes, and file effects.

• Bug hunt — Find and fix twenty undocumented bugs across a dozen files with no test suite, then record what caused them.

Mostly Python and Go, with some Rust, C, and Ct+. A trajectory runs about 100 steps.

WHAT YOU JUDGE IN A TRAJECTORY

• Was the command right for the state the environment was actually in?

• Did the agent read the previous output correctly?

• Was the step wrong, or only inefficient — these are scored differently.

• Where did the run first go off course — usually earlier than where it visibly broke.

• Did the agent notice its own mistake and recover, or keep building on a false assumption?

• Did it game the grader instead of solving the task (e.g., weakening a test or hardcoding an expected value)?

WHAT WE NEED FROM YOU

• Experience — 2+ years in software engineering, DevOps, or site reliability, with real debugging in real codebases.

• Languages — Strong in Python or Go, and able to read a language you've never used.

• Linux — Comfortable with logs, running processes, build failures, and containers.

• Workflow — Everyday Git, diffs, pull requests, and issue tracking.

• Debugging — Able to work with no test suite and no error message pointing at the cause.

• Focus — Able to hold context across a long run, because step 74 can depend on step 12.

• Writing — Clear English, since every judgement needs an explanation another engineer can check.