What is a Research Analyst?

A Research Analyst at The Johns Hopkins University is a mission-critical contributor who transforms complex data into scientific insight, operational clarity, and policy-relevant evidence. You will partner with principal investigators, clinicians, and program leaders to design analyses, build models, and translate findings into publications, grants, and decisions that advance health and knowledge. From infectious disease modeling to digital health algorithms and qualitative program evaluation, this role anchors the analytic rigor that powers Johns Hopkins’ global impact.

Your work directly influences how studies are designed, how interventions are evaluated, and how stakeholders—from care teams to funders—act on evidence. You may develop transmission models for pulmonary research, implement AI algorithms in international health, or lead qualitative research in adolescent mental health. The range is wide by design; what’s constant is a high standard for methodology, reproducibility, and ethical conduct that reflects the University’s leadership in research.

This is a role for analysts who want to both build and explain—who can architect robust data pipelines, produce clear visualizations, and author manuscripts, while also mentoring peers and advising faculty on best practices. If you are energized by interdisciplinary collaboration, scientific integrity, and measurable outcomes, you will find meaningful, visible impact here.

Common Interview Questions

Use the interactive practice to rehearse responses to role-aligned prompts and receive structured guidance. Prioritize questions mapped to your target unit’s focus (e.g., infectious disease modeling vs. qualitative program evaluation) to sharpen depth where it matters most.

Getting Ready for Your Interviews

Prepare to demonstrate depth in methods, clarity in communication, and ownership in execution. Interviewers will probe how you design analyses under real constraints, uphold compliance and reproducibility, and partner effectively across highly interdisciplinary teams. Bring concise stories that show you have driven results in academic or research settings.

• Role-related Knowledge (Technical/Domain Skills) - Interviewers will assess your fluency in statistical programming (e.g., R, Python, Stata, SAS), data modeling, visualization, and research methods aligned to the lab’s focus (e.g., infectious disease, pulmonary, digital health, public/global health, mental health, qualitative methods). Show, with examples, how your tools and techniques generated actionable findings for manuscripts, grants, or program decisions.

• Problem-Solving Ability (How you approach challenges) - Expect scenario-based questions about messy data, ambiguous study aims, and time-bound deliverables. Demonstrate structured thinking: clarify the question, define success metrics, outline methods, anticipate risks, and articulate tradeoffs made under constraints (e.g., sample size, missingness, IRB limitations).

• Leadership (How you influence and mobilize others) - Even without formal authority, you’ll need to mentor staff, guide students, and align stakeholders. Share moments when you set analytic standards, created SOPs, improved quality control, or drove consensus on methodology. Be specific about outcomes (e.g., accelerated data entry accuracy by X%, improved model calibration, enabled a successful grant).

• Culture Fit (How you work with teams and navigate ambiguity) - Johns Hopkins values scientific rigor, humility, and collaboration. Show how you seek peer review, handle constructive critique, and communicate limitations responsibly. Illustrate how you uphold ethics, patient privacy, and reproducible workflows in diverse, hybrid research environments.

This visualization summarizes compensation ranges from recent Johns Hopkins postings for Research Analyst and Senior Research Analyst roles across schools and centers. Expect variation by unit, seniority, funding source, and scope; ranges commonly span approximately the mid-$50,000s to the high-$170,000s annually, with targeted salaries set by department. Use this as directional guidance and discuss specifics with your recruiter.

Interview Process Overview

Johns Hopkins interviews for Research Analyst roles are designed to assess how you think, how you work, and how you uphold scientific standards. You should expect a rigorous, collegial process that blends technical depth with collaborative problem-solving. The pace is professional and thorough; many teams coordinate across PIs, staff scientists, and program managers to ensure the fit is mutual.

You will face questions that mirror on-the-job analysis: clarifying study aims, selecting methods aligned to constraints, and communicating results to technical and non-technical audiences. The process often includes both methodological deep dives and behavioral discussions about teamwork, mentorship, and reproducible practices. While formats vary by department, the philosophy is consistent: evidence of impact, integrity, and growth potential outweighs buzzwords.

Expect evaluators to look for end-to-end ownership—how you define the problem, build data pipelines, validate models, and translate findings into manuscripts, grant language, and presentations. Strong candidates bring relevant domain context (e.g., pulmonary transmission models, digital health algorithms, qualitative coding frameworks) and a habit of documenting decisions.

This timeline illustrates typical stages—from initial recruiter/PI screens to technical discussions, stakeholder interviews, and final selection. Use it to timebox your preparation: refine your portfolio before technical rounds, and prepare tailored questions for PI/team conversations. Build in buffer for take-home tasks and ensure your availability aligns with the proposed schedule.

Deep Dive into Evaluation Areas

Technical and Statistical Analysis

This area tests your ability to select and execute the right analytic methods, implement them cleanly, and interpret outputs with appropriate caveats. Interviewers will explore how you move from research questions to models, ensure data quality, and generate publication-ready figures and tables.

Be ready to go over:

• Statistical programming and tooling: R (tidyverse, lme4), Python (pandas, scikit-learn), Stata/SAS; version control with Git
• Modeling approaches: generalized linear models, mixed effects, survival analysis, time series, causal inference basics
• Results communication: effect size interpretation, uncertainty intervals, sensitivity analyses, assumptions
• Advanced concepts (less common): compartmental transmission models, Bayesian inference, simulation frameworks, machine learning for clinical/public health data

Example questions or scenarios:

• “Walk us through how you handled missing data and confounding in a multi-site study.”
• “How would you design and validate a transmission model for a pulmonary pathogen using limited time-series data?”
• “Show us how you’d critique a model that has high AUC but poor calibration.”

Data Engineering, Pipelines, and Reproducibility

Expect scrutiny on how you acquire, clean, and structure data for scalable, auditable analysis. Teams value analysts who pair speed with traceability and security.

Be ready to go over:

• Data ingestion and QC: building SOPs, automated validation checks, reproducible ETL/ELT
• Data management: database schemas, tidy data principles, code/data versioning, metadata
• Reproducible research: notebooks vs. scripts, project scaffolding, environment management
• Advanced concepts (less common): workflow orchestration, containerization, CI for analytics, secure computing environments

Example questions or scenarios:

• “Describe the SOPs you established for data entry and updates across multiple studies.”
• “How do you ensure a pipeline remains reproducible over a multi-year grant with evolving variables?”
• “Given a CSV dump with schema drift, outline your QC and harmonization steps.”

Research Design and Methods (Quantitative and Qualitative)

Interviewers will assess your understanding of study design, bias, measurement, and appropriate analytical alignment. Some teams will also probe qualitative rigor and mixed-methods integration.

Be ready to go over:

• Study design: cohort, case-control, RCTs, quasi-experimental designs; power and sample size considerations
• Validity and bias: selection bias, measurement error, confounding, effect modification
• Qualitative methods: coding frameworks, codebooks, thematic analysis, reflexivity, triangulation
• Advanced concepts (less common): pragmatic trials, implementation science, mixed-methods joint displays, causal diagrams

Example questions or scenarios:

• “How would you evaluate a school-based mental health intervention using a mixed-methods design?”
• “Explain how you’d structure a difference-in-differences analysis with staggered adoption.”
• “Walk us through your approach to building and validating a qualitative codebook for youth advisory data.”

Domain Expertise and Applied Modeling

Your domain depth helps you make sound methodological choices under real constraints. Teams will explore how you’ve applied methods to specific clinical, public health, or digital health contexts.

Be ready to go over:

• Public/Global health analytics: surveillance data, cohort follow-up, health systems metrics
• Clinical/biomedical: outcomes definitions, censoring, EHR data idiosyncrasies, data privacy
• Digital health/AI: feature engineering, model drift, human-in-the-loop validation, explainability
• Advanced concepts (less common): specialized infectious disease models, sensor/telemetry data, external validation across sites/countries

Example questions or scenarios:

• “Design an approach to estimate vehicle speed from video data and validate it for a public health application.”
• “Describe how you’d assess generalizability of an AI model trained on one hospital’s EHR to another site.”
• “How do you calibrate and communicate uncertainty in an infectious disease forecast?”

Communication, Collaboration, and Leadership

Strong analysts translate complexity for different audiences and elevate team practices. Expect to demonstrate influence without authority, mentorship, and stakeholder alignment.

Be ready to go over:

• Stakeholder communication: tailoring to PI, clinicians, program managers, funders
• Artifacts: one-page briefs, figures, QC dashboards, methods appendices
• Mentorship and standards: training junior staff, code reviews, lab SOPs, authorship norms
• Advanced concepts (less common): grant strategy alignment, cross-lab data sharing agreements, data governance councils

Example questions or scenarios:

• “Tell us about a time you persuaded a PI to change an analysis plan—and what changed as a result.”
• “How do you mentor trainees to use reproducible workflows?”
• “Describe a challenging authorship/credit discussion and how you resolved it.”