MedDotsLab Tech
MedDots × MedRock × Itkan · A 12-week engineering internship

Real Problem.Real Experience.Real Impact.

A real problem at a working compounding pharmacy. Solved by local engineers — you.

§01 · The problem

Compounding pharmacies still weigh every powder by hand.

5 minutes per compound. From 20 mg to 100 g in a single dose. Within ±3%. Thousands of times a day at MedRock alone.

MedRock Pharmacies identified hand-weighing as the bottleneck on their compounding floor. Every prescription that gets built on demand instead of pulled off a shelf starts at the same place: a pharmacist or technician at a scale, scoop in hand, working through one dose at a time. Tedious. Repeatable. Slow enough that the only way to scale that workflow today is to hire more people to stand at another scale. That's the problem this internship exists to solve. Not a school exercise. Not a thought experiment.

Compounding a Melasma Cream Compound, sped up by 20× — real time is 10 minutes.
§02 · Who's behind it

Two engineering teams asked a third group of engineers to help. You.

MedRock — the client + the floor

A working pharmacy, not a demo lab.

MedRock Pharmacies is a working compounding pharmacy. The compounds you'll watch get made are the ones MedRock fills for real patients every day. That's where the test runs happen. That's where the milestone validations happen. That's where Demo Day is.

MedDots — the engineering lead

An engineering firm that builds for clinical floors.

MedDots is the engineering firm spearheading the mechanical development of the Lab Tech machine. Mechanical, electrical, controls, firmware — the full bench. They're not sponsors of this program; they're the engineers running it.

Itkan — the host

The workroom and the local network.

Itkan is the local hub making this possible — the workroom, the workshops, and the connections to schools and engineering programs across DFW and Chattanooga. Itkan isn't on the engineering panel; they're the reason a regional internship program can exist at all.

FIRST in Texas — the partner

The state's engineering on-ramp for kids.

FIRST in Texas runs the robotics competitions and team programs that get high-schoolers their first real engineering reps — CAD, controllers, deadlines. They've been a backbone of regional engineering culture for years, and they're partnering with us to make sure this internship reaches the kids it's built for.

§03 · What you earn

Real money for real work, plus a project that actually goes on a resume.

The money

Up to $5,000 stipend, plus a $10,000 grand prize.

  • ·$1,000 per milestone met, per team. Five milestones — up to $5,000 per team across the cycle.
  • ·Catch-up counts. Miss M2 in week 4, ship it at M3 in week 6, the stipend pays retroactively.
  • ·$10,000 grand prize at Demo Day to the team that hits all 5 milestones AND scores best with the judge panel.
  • ·Stipends are real income. W-9 paperwork, splits among team members per your application — not a gift card.
The experience

A working internship, not a school project.

  • ·Ship physical hardware that runs at a working pharmacy, in front of pharmacists, every two weeks.
  • ·Direct technical feedback from MedDots' engineering staff — controls, mechanical, electrical — every Wednesday and on demand.
  • ·Walk away with five milestones' worth of design documentation, BOMs, firmware, and demo footage you can put in front of any future employer or admissions panel.
The IP trade

Anything your team designs, codes, prototypes, or documents during the cycle is assigned to MedDots and MedRock. That is the trade for the stipend, the pharmacy access, the engineering support, and the grand prize. You keep authorship credit, the experience, the relationships, and the right to talk about your role in interviews and applications. You don't keep commercialization rights to the machine. If that's not your trade, that's fair, and you shouldn't apply.

§04 · How it works

12 weeks. 5 milestones. 5 visits. One machine.

Build

Weeks 1–10

5 milestones spaced every two weeks. Each has a published acceptance checklist (what mechanically has to be working) and expected uploads (CAD, BOM, code, demo video).

Demo Day

Week 10

Live, in-person, on the MedRock floor. The judge panel scores every team that's hit all five milestones.

Review

Weeks 11–12

Judges deliberate. Grand prize announced.

The five milestones

The spine of the cycle. Pass = stipend. Miss = catch up at the next visit. Hit all five and you're grand-prize eligible.

M1
Week 2
Mechanical doser

Build the part that physically moves powder — a mechanism that pulls a controlled amount out of the hopper (the bin the powder sits in). No scale or automation yet; the goal is a dose you can make bigger or smaller and roughly repeat by hand — and a doser that comes apart for cleaning. It's the foundation every later milestone builds on.

Fri, Jun 19
M2
Week 4
Doser + scale closed loop

A focused milestone — fewer boxes than the others, but the one that matters is a big leap: weighing tolerance jumps from ±20% (rough, hand-actuated in M1) to ±3%. Add the controller and scale so the machine weighs powder as it dispenses and stops itself — "closed-loop" control, where the scale's reading feeds back to the controller, replacing hand-counting and guessing on time. This is where rough dispensing becomes real precision.

Fri, Jul 3
M3
Week 6
Single-doser full coverage

Push the single-doser machine hard: prove it's accurate across the whole weight range, handles every powder on the test list — not just the easy free-flowing ones — and repeats run after run. This is the rigor checkpoint before you add more dosers, and where the machine starts driving itself from a basic on-device screen.

Fri, Jul 17
M4
Week 8
Multi-doser compounding

Now more than one powder per recipe. Several dosers feed one scale and build a compound (a mixture of ingredients) where every amount adds up correctly — the machine tracks which powder is loaded in which doser, and the on-device interface grows to build recipes and manage settings.

Fri, Jul 31
M5
Week 10
Autonomous compounding · Final Demo Day

Full autonomy: an operator loads the powders, enters a recipe on the device, hits go, and walks away while the machine makes the compound start to finish — logging every step. This is also the Final Demo Day — the judge panel scores your machine live.

Fri, Aug 14

Who's on the team

  • ·46 people. Bring your own team if you have one. No team yet? Apply solo — we keep a waitlist of individuals and will help match you into a team if a slot opens.
  • ·Anyone with an engineering background. High schoolers with FIRST robotics or maker-space experience, college engineering students, mentors (professors, working engineers, family with the right skills) — anyone who can ship.
  • ·DFW or Chattanooga, TN. That's the local radius for the in-person visits.
  • ·Workspace is your call. School lab, maker space, garage, or ITKAN's bookable workroom — whichever works.

What MedDots provides

  • ·Wednesday open office hours — bring problems, share progress, learn from other teams.
  • ·Private one-on-one consultations — book through the dashboard for confidential help on your specific approach.
  • ·Pharmacy-grade powders for milestone validation — minoxidil, lovastatin, urea. You don't source these. Everyday powders for at-home iteration are on you.
  • ·In-person kickoff at ITKAN on day one of Week 1. Mandatory.
§05 · How to apply

Self-organize a team. Make the case for why you're the ones to solve this.

What we're looking for

We're picking up to 5 teams out of a maximum of 20 applications. We want teams that:

  • ·Cover the disciplines. Mechanical, electrical, software, controls, documentation. You don't need every box; you need most of them between 4–6 people.
  • ·Already get along. This is a 12-week build at pharmacy-grade rigor. We're not assigning chemistry; you bring it.
  • ·Pitch their case. “Why us” matters more than “where we're from.” Your school, your past projects, your FIRST team — all material.
  • ·Don't have a full team? Apply as an individual anyway. If we end up with fewer than three viable teams, we open a waitlist and matchmake people into teams for the cycle.

What the application asks

  • 01The team. Name, lead, school/org, members.
  • 02Per member. Name, email, the engineering disciplines you bring, and a resume URL or upload.
  • 03

    The pitch. Three short prompts on why your team— not your engineering approach, not your design ideas. We're picking the people, not the proposal.

    • Why this team. Who you are, how you work together, what makes you the right group for a 12-week build.
    • How you'll work. Where you'll meet, how you'll coordinate, how you'll keep showing up through 10 weeks.
    • Why you'll be the best. Track record, prior projects, FIRST team, coursework — the case for picking you over the next applicant.
  • 04The split.How the stipend should be divided among members if you're selected.
Open call

Ready to build the machine?

5 teams. 12 weeks. One real machine going onto a working pharmacy floor. Form a team, write a pitch, send it in.

The bar: discipline coverage across 46 people, real prior engineering work, the resources you already have access to, and a pitch that makes the case for your team specifically.