Building an Instrumentation Pipeline for Students: Lessons from an Exoplanet Scientist’s Career

What separates a student who “likes astronomy” from a student who can thrive in exoplanet research, observatory work, or telescope engineering? In many cases, the answer is instrumentation—the practical experience of working with detectors, spectrographs, calibration systems, observing plans, data reduction, and the day-to-day realities of using a telescope. That kind of preparation does not happen by accident. It is built through structured pathways: mentorship, small-observatory projects, observatory internships, and research experiences that gradually increase in complexity.

Johanna Teske’s career is a strong example of how hands-on training shapes a scientist. According to Carnegie Science, Teske has worked with the Planet Finder Spectrograph on the Magellan Clay telescope, studied transiting planets first detected by TESS, and developed expertise with high-resolution optical and near-infrared instruments. She has also expressed interest in future instrumentation for Magellan and the Giant Magellan Telescope, while remaining active in outreach and mentorship. For departments designing better pathways, her career offers a useful model: give students authentic instrument experience early, connect them to mentors, and let them build confidence through increasingly sophisticated projects. That is the heart of sustainable undergraduate research ecosystems.

This guide turns that idea into a practical roadmap. It is written for departments, faculty advisors, and program coordinators who want to create an instrumentation pipeline that students can enter at multiple points and continue through graduation. Along the way, we will use lessons from Teske’s path, current trends in astronomy education, and proven structure-building ideas from other fields such as research-to-career pathways, teacher-centered implementation playbooks, and even pipeline design in sports and operations, where the strongest systems combine coaching, feedback loops, and clear milestones.

Why an instrumentation pipeline matters now

Astronomy programs are growing faster than their support structures

The SURGE report summarized by Astrobites notes that astronomy and astrophysics degrees in the U.S. have expanded sharply since 2000, creating both opportunity and strain. That growth is exciting, but it also means many departments are trying to educate more students without equally mature systems for research access, advising, and practical training. In other words, the field is producing more learners but not always enough pathways for them to become instrument-savvy researchers. A department that wants to stand out needs a ladder, not just a classroom.

That ladder should include observing skills, hardware familiarity, programming, documentation, and communication. Students do not need to become engineers to be useful in instrument-focused research, but they do need to know what a detector saturating looks like, how calibration frames work, why weather and seeing matter, and how software and hardware decisions influence data quality. A careful pipeline can produce graduates who are comfortable at a telescope and credible in a research group.

Instrumentation is where theory becomes practice

Students often enter astronomy through big questions: Are there other Earths? How do planets form? What are stars made of? Instrumentation is the bridge from those questions to measurable evidence. A spectrograph turns a star into a dataset. A telescope schedule turns curiosity into observing time. A calibration plan turns raw counts into a scientific result. This bridge matters because many students who love the concept of astronomy leave the field when they encounter the messy operational side. A good pipeline normalizes that mess and teaches students how to work within it.

For departments building a pipeline, this is where carefully staged experiences help. A first-year student can begin with telescope basics and image inspection. A sophomore can contribute to a small-observatory project. A junior can support a faculty observing run or assist with an instrument lab. A senior can lead a mini-project or take responsibility for a calibration workflow. This progression mirrors the logic behind other structured programs, such as youth sports pipelines, where small skill wins accumulate into elite performance.

Career development becomes more equitable when the pathway is visible

One of the biggest hidden problems in astronomy education is that students with family connections, unpaid summer access, or insider knowledge often learn how to “find the path” faster than others. Structured instrumentation pathways reduce that inequity by making the route visible and repeatable. When a department publishes a clear sequence of experiences—intro lab, mentor matching, observatory internship, summer instrumentation project, thesis support—students do not need to guess what counts.

This is also where mentorship matters. Not every student has the same starting point, and not every student learns the same way. Some need hands-on repetition; others need conceptual framing before they can troubleshoot. A strong pipeline accommodates both. Departments that think carefully about student access, onboarding, and feedback can create a more inclusive environment, something Teske herself supports through outreach and mentorship according to Carnegie Science.

What Johanna Teske’s career teaches departments

Her path shows the value of instrument-centered research

Teske’s work on exoplanet composition relies on observing tools that measure stellar wobble and planetary mass, including the Planet Finder Spectrograph on the Magellan Clay telescope. That detail matters because it reveals a career shaped not just by abstract theory but by direct engagement with observatories and instruments. For students, this demonstrates that a research career can begin with learning how instruments work, not only with reading papers.

Her interests in high-resolution optical and near-infrared spectrographs and imagers also underline a broader lesson: students should be exposed to more than one kind of hardware. A robust pipeline should not lock them into a single instrument or a single project. Instead, it should help them compare devices, understand trade-offs, and learn how scientific goals drive instrument choice. That mindset is especially valuable for students considering careers in observatory operations, research support, or future telescope development.

She benefited from mentoring and institutional scaffolding

Teske earned her B.S. in physics and later a Ph.D. in astronomy, moving through institutions that likely offered intellectual and human support at each stage. Her career illustrates how advanced researchers are usually not “self-made” in the mythic sense; they are developed through repeated access to mentors, projects, and opportunities. Departments should therefore think of mentorship not as an optional extra, but as the infrastructure of career development.

A practical lesson from her path is that students often need several different mentors: one for academic guidance, one for technical troubleshooting, and one for long-term career advice. This is why programs that pair students only with one supervisor sometimes leave important gaps. A multi-mentor model can include a faculty sponsor, a graduate-student or postdoc coach, and an observatory or instrumentation staff member. That trio mirrors how professional teams operate in technical fields, and it can make the leap from classroom to telescope feel much less abrupt.

She connects research with service and inclusion

Carnegie Science notes that Teske is involved in outreach, mentorship, and efforts to make astronomy more inclusive. That is not a side note; it is part of a durable pipeline. Students stay in science when they feel like they belong, when they can see people like themselves in the field, and when mentors actively help them navigate unwritten rules. Inclusion is therefore not separate from instrumentation training—it is what determines whether the pipeline works for only a few or for many.

Departments should also remember that inclusion is operational. It shows up in scheduling, compensation, application processes, and communication style. If observatory internships are unpaid, inaccessible to students who work summers, or advertised only informally, the pipeline reproduces the same exclusions it claims to fix. A good model borrows from fields that systematize access, like the careful evaluation logic in campaign vetting or the trust-building discipline seen in audience recovery strategies.

Designing the pipeline: the core stages

Stage 1: curiosity and exposure

The first stage should be low-stakes, inviting, and concrete. Students need early exposure to telescopes, detector images, sky charts, and simple calibration exercises. A department might host a “first light” night where students learn how a telescope is aligned, what a CCD image looks like, and how basic observing logs are kept. The goal is to replace mystery with familiarity.

This stage can include short modules in introductory courses, campus telescope sessions, and open house events where students shadow staff or senior students. The most important design principle is repetition. Students should encounter the same workflow multiple times in slightly different settings, so they can build confidence. Think of it like learning a language: before fluency comes recognition, then short responses, then real conversation.

Stage 2: guided contribution

Once students are comfortable with the basics, they should contribute to small, well-scoped tasks. These tasks can include reducing archival data, maintaining observing logs, writing calibration scripts, cleaning metadata, or helping with instrument documentation. The project should be big enough to matter and small enough to finish in a semester. This is where observatory internships and faculty-led mini-projects become powerful.

Guided contribution should be assessed through deliverables, not just attendance. For example, a student could produce a one-page instrument note, a cleaned dataset, a before-and-after calibration comparison, or a poster explaining a telescope subsystem. That keeps the work authentic while making progress visible. It also mirrors how professional teams structure work in other fields, such as the iterative methods described in multimodal observability systems.

Stage 3: independent ownership

At the highest stage, students should own a component of a project: an observing run, a reduction pipeline, a small hardware test, or an instrumentation comparison study. Ownership is what turns experience into career development. It teaches responsibility, error recovery, and time management under real constraints. Students who have reached this stage often gain the confidence to apply for graduate school, technical jobs, or competitive fellowships.

Not every student will reach this stage at the same pace, and that is okay. The pipeline should be modular. A student who joins late can still gain meaningful hands-on training if the department has entry points for upperclassmen and transfer students. Strong programs allow movement between stages without penalty, much like the best systems in talent scouting or career coaching, where feedback and iteration matter more than fixed labels.

A practical departmental blueprint

Build a mentor map, not a mentor lottery

Many departments say they support students, but support often depends on who happens to be available. A better system is to create a mentor map that lists faculty, postdocs, grad students, observatory staff, and alumni by expertise. Students should be able to find someone for telescope operations, instrumentation software, data reduction, project management, and career planning. This makes mentorship searchable and lowers the barrier to entry.

A mentor map should also clarify expectations. How often can students meet with mentors? What kinds of questions are appropriate? What is the process for switching mentors if the fit is poor? Clear answers prevent students from feeling like they are bothering busy experts. A transparent structure is similar in spirit to the governance logic in co-op leadership models and the trust-building framework in productizing trust.

Create a semester-by-semester sequence

Students need to see the route from novice to contributor. Departments can publish a simple progression chart that shows what students should know by the end of each term. For instance, by the end of the first year, students might learn telescope basics and data inspection. By the end of the second year, they might support archival research or a campus observatory. By the third year, they might enter a summer instrumentation internship or a faculty research group. By the fourth year, they might complete a capstone using instrument data.

This sequence should not be rigid, but it should be visible. Students often assume they are “not ready” because nobody tells them what readiness looks like. A published roadmap reduces that uncertainty and helps advisors recommend the right next step. Programs in other sectors have learned this lesson too, as seen in reskilling programs and hardware upgrade planning, where staged adoption beats ad hoc change.

Offer credit, compensation, or both

Good intentions do not pay rent. If departments want students to participate in observatory internships or instrumentation work, they should budget for stipends, course credit, or paid summer appointments. Unpaid labor narrows access and can quietly sort students by privilege rather than promise. The best programs reduce that pressure by combining academic credit with paid opportunities when possible.

Where budgets are limited, departments can still make meaningful progress by offering course-linked projects, travel support for observing runs, or funded mini-grants for student teams. A small amount of money can unlock a lot of participation if it is targeted carefully. That approach resembles the resource-conscious planning seen in micro-fulfillment hubs—efficient systems are often about smart routing, not massive scale.

Small-observatory projects that build real skill

Campus telescope maintenance and logs

A campus telescope is one of the most powerful training tools a department can own. Students can learn how to inspect optics, record observing conditions, note hardware issues, and compare expected versus actual image quality. Even if the telescope is modest, it teaches the logic of routine operations. That routine is exactly what many students miss when they only consume curated datasets in class.

Students should be rotated through basic maintenance tasks under supervision. They can check mount behavior, document pointing performance, and record environmental conditions before and after observations. Those habits build the kind of observational discipline that later transfers to larger facilities like Magellan. They also make students less likely to panic when conditions are less than perfect.

Variable-star, transit, and follow-up photometry projects

Small telescopes are excellent for teaching students how to detect changes over time. Variable-star monitoring and transit follow-up are especially good because they connect directly to professional exoplanet science. Students can learn to plan observations, remove bad frames, check time stamps, and look for systematic errors. They also begin to understand why repeated, careful measurements matter more than dramatic single images.

These projects are ideal stepping stones toward exoplanet work because they show how ground-based observations support space-based discoveries. A student who starts with a campus telescope can later understand how a star observed by TESS might be followed up with a spectrograph on Magellan. That continuity is important: it helps students see astronomy as a connected ecosystem rather than disconnected course topics.

Calibration and instrument characterization exercises

Students should not only collect science data; they should learn how instruments are characterized. Calibration exercises can include comparing flat-field responses, measuring detector noise, testing focus across temperature changes, or tracking throughput. These tasks teach students that instruments are physical systems with limits, not magical black boxes.

Departments sometimes skip this material because it seems too technical for undergraduates, but that is a mistake. Well-designed labs can introduce these ideas through simple comparisons and guided reflection. Students do not need to derive the detector equation from first principles to understand that calibration changes the quality of a result. They just need structured practice and a mentor who can translate the technical details into usable concepts.

How to use mentors effectively

Match mentors to stage, not just topic

Students benefit from mentors who are appropriate to their current stage of development. A first-year student may need a mentor who is patient, structured, and able to explain telescope basics without jargon. An advanced student may need someone who can challenge them to design a workflow or write code for data reduction. The same mentor rarely serves both needs equally well.

That is why departments should think in terms of a mentoring team. One person can help with the big picture, another can provide technical guidance, and another can model professional behavior in the field. In many successful programs, peer mentors are especially valuable because they make the invisible visible. A student is often more willing to ask “obvious” questions of a near-peer than of a professor.

Train mentors, not just mentees

Mentoring is a skill. Faculty and senior students may be excellent researchers but unprepared to explain their workflow to beginners. Departments should offer short mentor-training sessions on onboarding, inclusive communication, feedback timing, and how to set realistic expectations. Without this step, the pipeline can become inconsistent even when the scientific opportunity is strong.

Mentor training also reduces student attrition. When mentors know how to define tasks clearly, check in without hovering, and respond constructively to mistakes, students are more likely to stay engaged. This is analogous to the best implementation systems in education and operations, where the process is as important as the outcome. If you want students to become capable, you must teach the people around them how to teach.

Use alumni as long-range mentors

One underused resource is alumni who now work in observatories, data science, aerospace, or graduate programs. They can help students understand what different career paths actually look like. Alumni can also demystify transitions: how to apply for observatory internships, how to talk about instrumentation on a CV, and how to decide between graduate school and technical roles. For students, that kind of advice is often more credible than generic career counseling because it is grounded in lived experience.

Alumni mentoring can be light-touch but effective: a yearly panel, a virtual Q&A, or a short review of student posters. It can also be highly strategic if alumni are placed in a mentor directory. A pipeline becomes stronger when students can imagine where the road leads. Career development is easier when the next step is visible and human.

Comparing common pipeline models

The table below outlines how different program structures compare for instrumentation training. Departments can use it to benchmark where they are and where they want to go.

Notice the pattern: the strongest model is not the one with the most prestige, but the one with the best sequencing. Students need breadth early, then depth later. They need access, repetition, and real deliverables. The goal is not to create a temporary experience; it is to create a durable habit of scientific practice.

Instrumentation internships: what makes them work

They should look like real jobs, with guardrails

Observatory internships work best when students are doing authentic work rather than simplified busywork. That means helping with schedule preparation, calibration checks, instrument logs, or data QA. But “real” should not mean unbounded. Students still need scaffolding, checklists, and a supervisor who can help them recover when something goes wrong. The sweet spot is professional realism plus educational support.

Departments can borrow from workplace design principles to do this well. Clear responsibilities, short check-ins, and documented workflows help students understand expectations without feeling overwhelmed. If an internship involves remote telescope operations or instrument support, students should receive orientation to safety, communication protocols, and downtime procedures. The more professional the environment, the more important structure becomes.

Internships should culminate in a shareable product

Every student should leave an internship with something they can present: a poster, a technical memo, a notebook of procedures, a small code repository, or a conference abstract. This matters because career development is easier when the work can be described concretely. A student who can explain an instrument calibration or a follow-up observing run is much better positioned for graduate applications or technical interviews.

That deliverable also helps the department assess value. Instead of asking whether students “had a good time,” programs can ask whether they can demonstrate competence. This shifts the focus from vague satisfaction to skill acquisition. It also creates a portfolio culture, which is increasingly valuable in science careers.

Internships should feed back into the curriculum

A strong pipeline is not a one-way street. Lessons from observatory internships should inform class content, lab design, and advising. If students repeatedly struggle with time stamps, for example, then that topic should receive more emphasis in the undergraduate lab. If a particular software package keeps appearing in research groups, it should show up earlier in instruction.

This feedback loop is what turns isolated opportunities into institutional strength. Departments that treat internships as disconnected events miss the chance to improve. Departments that treat them as data sources can evolve, just like good technical teams do when they review performance and adjust the system. That mindset is reflected in iterative planning approaches across disciplines, including conversion-driven prioritization and responsible coverage frameworks.

Measuring whether the pipeline is actually working

Track skills, not just participation

Departments often count enrollments, but numbers alone do not show whether students can operate in instrument-rich environments. A better approach is to assess specific competencies: Can the student use a telescope log? Can they identify bad frames? Can they explain what calibration does? Can they communicate a data quality issue to a supervisor? These are measurable and meaningful indicators of progress.

A simple competency rubric can be used across courses, research groups, and internships. Students can be rated on observation planning, instrument literacy, data handling, troubleshooting, and professional communication. The rubric should be shared early so students know what success looks like. That transparency improves learning and makes advising far easier.

Look at persistence into advanced opportunities

Another key metric is whether students continue into deeper opportunities: summer research, advanced instrumentation projects, graduate school, observatory jobs, or technical roles in adjacent fields. If many students enjoy the intro experience but few continue, the pipeline may be entertaining but not developmental. Persistence is often the best sign that students are gaining confidence and belonging.

Departments should also examine who persists. Are students from all backgrounds moving forward at similar rates? Are transfer students, first-generation students, and students with outside work obligations able to participate? If not, the pipeline may need redesign. That is where equity and operations meet.

Solicit student reflections regularly

Numbers matter, but reflections often reveal what metrics miss. Ask students what made them feel capable, confused, welcome, or excluded. Ask which tasks were most useful and which explanations were unclear. These short reflections can uncover small changes that make a huge difference, such as better onboarding, more predictable scheduling, or simpler documentation.

Student feedback also helps departments avoid building a pipeline around the preferences of one faculty member. A healthy system should work even if staff change. Like any durable institution, it should survive leadership turnover because the process is documented and continuously improved.

A sample 4-year pathway departments can adapt

Year 1: orientation and telescope literacy

Students begin with an introduction to observing, basic instrument types, and a campus telescope night. They learn how a detector produces an image, why calibration exists, and how astronomers document conditions. By the end of the year, they should be comfortable discussing the difference between an imager and a spectrograph, and they should have at least one supervised observing experience.

Year 2: guided contribution and small projects

Students join a small-observatory project or faculty-led data reduction task. They begin using software to inspect images, compare observations, and document anomalies. This is also the ideal time to introduce a mentor map and help them identify summer opportunities. Students who complete this stage should be able to explain a project clearly to a peer.

Year 3: observatory internship or instrumentation internship

Students spend a summer or semester in a more intensive setting, ideally at a campus observatory, partner observatory, or research group that uses real instrumentation. They may assist with scheduling, logs, calibration, or follow-up observations tied to a research question. By the end, they should have a presentation or technical deliverable and a stronger sense of whether they want research, operations, or engineering-adjacent work.

Year 4: capstone and transition planning

Seniors use their experience to lead a small project, write a thesis, or mentor younger students. They also receive explicit support for next steps: graduate applications, observatory employment, fellowship searches, or technical job placement. This final year is where the pipeline pays off most visibly, because students become contributors to the next cohort. A good program turns former learners into future mentors.

Final takeaways for departments

Make the path visible

Students cannot follow a pipeline they cannot see. Publish the stages, the skills, the people, and the opportunities. Make the route from novice to contributor obvious enough that a first-year student can picture it. That visibility is one of the most powerful retention tools available.

Protect the hands-on piece

If the pathway becomes all talk and no telescope, it loses its power. Hands-on training is not a luxury in astronomy; it is the medium through which students understand the field. Small-observatory work, instrument characterization, and observatory internships are not side activities. They are the core.

Design for belonging and continuation

Johanna Teske’s career illustrates what becomes possible when instrument-rich research, mentorship, and institutional support come together. Her path through Magellan, exoplanet follow-up, and future instrumentation interests shows why students need early access to authentic scientific tools. Departments that build thoughtful pipelines will not only train better students; they will also strengthen the future workforce of astronomy.

If you are building or revising a program, start small but start structurally: create a mentor map, add one observatory internship, formalize a beginner project, and build a feedback loop. Then expand. The best pipelines are not accidental. They are deliberately designed, continuously improved, and centered on student growth.

Pro Tip: If your department can only fund one new initiative this year, fund the one that creates repeatable student access to a real telescope. A single well-run observing pathway often does more for career development than a dozen inspirational talks.

Frequently asked questions

Related Reading

• The Landscape of Undergraduate Astronomy and Astrophysics Degree Requirements - See how programs are evolving and where students need more support.
• Dr. Johanna Teske - Carnegie Science - Learn more about Teske’s research, instrumentation interests, and outreach work.
• Convert Academic Research into Paid Projects - Useful for thinking about student project value and career transition.
• AI-Assisted Grading Without Losing the Human Touch - A helpful analogy for building systems that preserve mentorship while scaling.
• Scouting the Next Esports Stars with Tracking Data - A strong example of structured pipeline thinking and skill development.