From working prototype
to reliable product.

1. Understand the whole product

Your job is to turn a user action into a reliable result—and know where that chain can break.

This course uses a hypothetical corded, screenless voice device with Talk, Ride and Food buttons. Your October 25 description is the source for the form, rendering, prototype, resin printers and possible hearing-aid/TV plans. Wall power is an assumption. Chips, voltages, board layout and test limits below are teaching examples, not Bellhop specifications. The original ad was not recovered in this lookup, so its exact tool requirements are unverified.

Walk through a Ride request

A switch changes voltage at a processor input. Firmware filters switch bounce and creates one event. The device provides a local acknowledgement, captures speech, and sends audio or recognized intent to its service. Software confirms destination and price, authorizes the transaction, and sends a booking request. The returned status becomes speech through the audio output. Later notifications must still reach the device and ring it while idle. There is no special “Uber chip”: the vendor integration is usually software.

Distinguish input detected → request sent → booking confirmed. A light or beep cannot truthfully mean “ride booked” before the service confirms it. Repeated presses and network retries must not make duplicate bookings; an idempotent request uses a stable operation identifier so a retry does not repeat the purchase.

Three plausible electronics approaches

A SoC is a system-on-chip; a SoM is a module containing a processor and supporting circuitry. An ESP32-S3-class MCU is an illustrative Wi-Fi/BLE option, not evidence of Bellhop’s design or a recommendation for hearing-aid audio. Its published feature list includes Wi-Fi and Bluetooth LE; that alone does not establish the audio profiles required here. Espressif product overview.

Handset details that change the design

A hook switch detects whether the handset is on its cradle; it might be mechanical, magnetic (Hall sensor), or another sensor. The coiled cable might carry analog microphone/earpiece signals or power and digital signals. Do not infer its pinout from its telephone-like plug. Flex life, strain relief, connector retention, noise pickup and replacement availability matter. A handset microphone near the mouth is a different acoustic problem from a microphone across the room.

2. Electronics and the parts you may find

Learn each part by its job, its connections and a way to prove it works.

The minimum electrical vocabulary

Voltage (V) is potential difference between two points. Current (A) is charge flow. Resistance (Ω) opposes current. For a resistor, V = I × R; power P = V × I. Ground is a circuit reference and return path, not automatically protective earth. An open is a broken path; a short is an unintended low-resistance path. A digital “1” means a voltage within the receiver’s specified high range, not universally 5 V. Check logic levels and absolute maximum ratings before connecting boards.

Worked example: a 3.3 V output drives an LED with a 2.0 V forward drop at a teaching target of 5 mA. R = (3.3 − 2.0) / 0.005 = 260 Ω; 270 Ω is a nearby standard value, giving about 4.8 mA. Confirm the actual LED and output ratings. A processor pin is not a power supply for a speaker or motor.

Power arithmetic you should be able to explain

A teaching example draws 5 V × 1.2 A = 6 W. An adapter rated 5 V, 2 A has a 10 W nominal output capacity; the device draws the current it requires, within limits. Extra current capacity does not force 2 A through the device. Wrong voltage can destroy it.

A linear regulator dropping 5 V to 3.3 V at 0.5 A dissipates approximately (5 − 3.3) × 0.5 = 0.85 W. That can be significant heat. A buck is often more efficient but brings switching-noise/layout considerations. A USB-C connector does not itself negotiate extra power: source, sink configuration, cable and any USB Power Delivery implementation must match.

For an optional 3.7 V nominal, 2 Ah battery, nominal energy is 7.4 Wh. At a 2 W load with an assumed 80% usable conversion factor, illustrative runtime is 7.4 × 0.8 / 2 ≈ 3 hours. This is an estimate, not a qualification result; load peaks, cell age, temperature and cutoff affect it. No battery is established for Bellhop.

3. Bench tools and an oscilloscope refresher

A meter answers “how much?” A scope answers “what happened over time?” A logic analyzer answers “what digital conversation occurred?”

Using the meter correctly

For voltage, connect across the two points. For current with a conventional DMM, break the path and insert the meter in series using the correct fused jack/range. Start conservatively and follow that meter’s manual. Return the red lead to the voltage jack afterward. For resistance/continuity, remove power and discharge capacitors safely first. A beep indicates resistance below the meter’s threshold, not that a complex circuit is healthy. NI measurement fundamentals.

Scope controls translated

• Volts/div: vertical scale. At 1 V/div, three divisions represent 3 V.
• Time/div: horizontal scale. At 1 ms/div, a ten-division screen covers 10 ms.
• Trigger: the event that stabilizes or starts capture. Choose signal, rising/falling edge and threshold. Use single acquisition to catch a one-time event.
• DC coupling: displays DC level and changes. AC coupling: removes DC but can distort slow events; it is not the right starting point for absolute rail droop.
• Bandwidth: analog frequency response. Sample rate: samples per second. Memory depth: how much record you retain. Edge speed matters, not just a bus’s nominal frequency.
• 10× passive probe: attenuates the signal and often loads a node less than 1×. Match the channel setting; compensate compatible probes using the scope’s calibration output.

Ground rule: conventional bench-scope probe ground clips are commonly tied together and to protective earth. Connect only to a verified appropriate reference. Never lift the scope’s protective earth to “float” it. Do not probe the inside of a mains adapter. A bridge-tied speaker output has two driven terminals: neither is automatically ground. Use a suitably rated differential measurement arrangement for that output. Read the instrument/probe ratings. Tektronix probe primer.

Guided case: device resets when the ring sounds

1. Record the board revision, firmware, adapter, cable, volume and reproducible trigger. Obtain the rail’s actual allowed range and reset threshold.
2. With a suitable 10× probe and short ground connection, measure the processor supply at its local decoupling point. Start DC-coupled. Choose scales around the expected voltage and event duration.
3. Trigger on a falling voltage near the suspected threshold; keep pre-trigger data. Use another channel for reset or an event marker when safely possible.
4. Reproduce the ring. Correlate the rail waveform, reset signal and reset-reason log. A drop suggests a power-path problem; it is evidence to investigate, not automatic proof of the root cause.
5. Compare input power and regulator output, swap one known-good cable or supply at a time, and exercise the load. If rails are stable, investigate watchdog, software crash, thermal or interference paths.
6. After a fix, repeat at demanding approved conditions and on several units. Adding a capacitor without understanding startup, stability and inrush can create a second problem.

4. Boards, soldering and first power-up

Recognize the assembly, use a controlled repair process, and bring up one subsystem at a time.

PCB words without bluffing

PCB means the bare printed circuit board; PCBA is the assembled board. A schematic describes electrical connections; layout places parts and copper in physical space. A net is an electrically connected group; a trace is copper routing; a via connects copper layers; a pad receives a component termination. A footprint must match the actual package. Solder mask covers selected copper; silkscreen provides markings. A stackup specifies layer construction. Reference designators such as R12, C8, U3 and J1 identify resistor, capacitor, IC and connector locations.

Soldering refresher: sequence matters

Use a practice board first if equipment is already available; do not learn on the only working prototype. Inspect under magnification. Remove power and disconnect batteries. Use appropriate ESD controls at the low-voltage bench, eye protection and fume extraction. Secure the work, choose electronics-compatible flux/solder and a tip sized to transfer heat to the joint.

1. Clean and lightly tin the tip. Apply suitable flux to the joint.
2. Heat both pad and lead, then feed solder into the heated joint. Look for wetting rather than a bead sitting on top.
3. Remove solder, then the iron; hold the joint still while it solidifies.
4. Inspect wetting, bridges, disturbed joints, lifted pads, polarity and adjacent parts. Lead-free joints can look less shiny; shine alone is not an acceptance criterion.
5. Clean residues according to the flux/process and product requirements, inspect again, then perform unpowered checks before a controlled functional test.

There is no universal correct iron temperature: alloy, tip, joint mass and station behavior matter. Use the process recommendation and lowest effective setting; poor wetting is a reason to inspect cleanliness, flux and heat transfer, not simply keep increasing heat. HAKKO soldering/rework guidance. Wick removes molten solder by capillary action; do not drag it off a cold joint. Hot-air rework needs controlled airflow/heat, protection for nearby plastics and a suitable process. BGA repair is a specialist capability, not something to imply from hand-soldering experience.

First-board bring-up checklist

1. Get the correct schematic, BOM, assembly drawing, board revision, expected rails and programming instructions.
2. Inspect orientation, connector pinouts, missing parts and solder bridges.
3. With no power, check for suspicious rail-to-ground shorts. Capacitors charge from a meter and some processor rails naturally read low; compare the circuit and a known-good unit rather than applying a universal resistance cutoff.
4. Disconnect optional loads where designed to permit it. Apply the specified voltage with a justified current limit; stop for unexpected current or heating.
5. Verify rails, sequence, reset and clocks. Use suitable probes.
6. Connect the supported debugger or serial console; run minimal known firmware and establish boot behavior.
7. Exercise buttons, audio, radios and peripherals separately, then together at realistic load. Save measurements and defects by serial/revision.

What you can honestly say: distinguish production ownership, enclosure/interconnect work and hands-on assembly from schematic design, PCB layout, RF engineering and firmware. A refresher prepares you to discuss a process; it does not establish recent bench proficiency.

5. Audio, buses, hearing aids and connectivity

A product that connects to Wi-Fi can still be unable to hear, speak or recover reliably.

Follow both audio directions

Input: sound → microphone → analog preamp/ADC or digital mic interface → processor → network. Output: network or local audio → processor → DAC/codec or digital-input amplifier → earpiece/speaker. An ADC converts analog to digital; a DAC does the reverse. An audio codec IC commonly combines converters and routing; that is different from a compression codec such as LC3 or Opus. The TI TLV320AIC3204 is one example with ADC/DAC channels, digital audio interfaces and a separate control interface—not a known Bellhop part. TI codec reference.

A MEMS microphone may output analog, PDM (pulse-density modulation) or another digital format. It needs the correct supply, clock if applicable, acoustic port alignment and sealing. A speaker needs an amplifier appropriate to its impedance and power. Class-D amplifiers switch efficiently; their output needs an appropriate measurement method. A headphone driver, line output and speaker-power output are not interchangeable.

Why clear speech is a system test

SNR is signal-to-noise ratio. Clipping is signal overload and distortion. AEC, acoustic echo cancellation, reduces the device’s own playback leaking into its microphone; it needs a usable playback reference and tuning. AGC, automatic gain control, adjusts level; it cannot restore clipped audio. Beamforming combines microphones to favor directions. VAD detects voice activity. Endpointing decides when the person has finished speaking. Full duplex means listening and playing simultaneously; it must be tested with both people/device speaking, not only one at a time.

Test handset and speaker modes separately, quiet and TV-noisy rooms, near/far speech where required, soft voices, long pauses, ringing, mute, maximum allowed volume and switching modes. Use a repeatable acoustic setup for production limits, then representative users and rooms for validation. Loudness alone is not intelligibility.

Hearing aids and TV: important unknowns

Classic Bluetooth audio, vendor-specific hearing-aid paths, LE Audio and telecoil/inductive coupling are different approaches. Establish supported hearing-aid models, direction of audio, pairing/setup and fallback. LE Audio includes hearing-aid support; the Hearing Access Profile defines interoperability requirements. Bluetooth SIG HAP. Auracast is broadcast audio; it does not by itself establish a microphone return channel. A hearing aid containing a microphone does not prove the device can access that microphone. Bluetooth SIG Auracast FAQ.

A TV accessory could use analog line audio, optical S/PDIF, HDMI ARC/eARC or a wireless path; these are alternatives, not confirmed features. Ask whether it only sends TV sound to hearing aids or also handles voice interaction. Measure latency/lip sync, supported formats, volume behavior, reconnection and switching back to a call. Do not add all these ports to an assumed design.

Network isolation

Separate “radio associated” from “received an IP address” (DHCP), “resolved a service name” (DNS), “secure connection established” (TLS), and “service accepted the request.” Wrong device time or credentials can break TLS even with strong Wi-Fi. Test router restart, wrong password, internet loss, server failure and recovery without duplicate transactions. No screen means the recovery instructions must be understandable through the remaining controls and audio.

6. Resin prototypes, assembly and reliability

A beautiful rendering, a working printed prototype and a qualified production enclosure are three different milestones.

Resin printing vocabulary

Vat photopolymerization cures liquid photopolymer with light. SLA commonly uses a scanning laser; DLP projects an image; MSLA uses an LCD mask. People also use “SLA” broadly. Unlike FDM/FFF filament printing, these processes use liquid resin. Ask what printer, resin and post-process they actually use.

Orientation determines supports, visible surfaces and loading during printing. Supports hold features during the build but leave marks. Peel/separation forces can distort thin geometry. Hollow parts need suitable drainage and cleaning access. Small layer height is not a promise of overall dimensional accuracy. Measure critical features after the specified post-process.

Wash off uncured resin using the material’s specified process; dry and post-cure as required. Post-curing changes material properties, so test the final processed condition. Use the resin/solvent safety instructions, suitable gloves/eye protection and ventilation; do not treat liquid resin or wash waste as sink-safe. Formlabs post-processing guide.

What to test in this handset enclosure

From resin to injection-molded plastic

A cured resin prototype is generally not the same material or process as a molded ABS/PC part. Do not transfer drop, snap-fit or heat results automatically. Draft lets a part release from a mold; a parting line is where mold halves meet; undercuts may require side actions. Near-uniform walls help avoid shrink and sink. Ribs add stiffness; bosses support fasteners; thick sections can sink or warp. Tool gates, ejector marks, weld lines, texture and shrink allowances affect appearance and strength. Agree actual geometry with the selected material and toolmaker. Protolabs Network molding guide.

Assembly sequence for the hypothetical device

1. Verify kit, drawings, revisions and component lots; inspect molded/printed parts and PCBA.
2. Load approved firmware, identity and configuration at a controlled station; record success without exposing secrets.
3. Install boards and hardware with specified supports/torque; fit buttons, microphone seals, speaker and hook sensor.
4. Route and secure cables, avoid pinches, keep antenna clearance, connect keyed harnesses and inspect polarity.
5. Perform accessible subassembly checks, close the housing, then run the final test in its assembled state.
6. Record serial, firmware, measurements and result; verify labels, adapter, accessories, packaging and shipment configuration.

Risk-based validation: temperature/humidity operation, thermal cycling, drops, vibration/shipping, ESD, cable/button life, power interruption and prolonged operation may all matter. Set a use case, severity, sample size and acceptance rule with the relevant engineers/lab. Never invent “industry standard” drop heights or guarantee a lifetime from a few prototypes.

7. Component tests, factory gates and shipment evidence

You do not retest semiconductor wafers. You prove purchased parts are suitable, assembled correctly and functioning in the product.

Supplier qualification and traceability address component quality. Board tests address assembly faults. Functional tests exercise useful behavior. Design validation challenges requirements and use conditions. Reliability testing explores degradation over time/stress. Compliance testing addresses applicable obligations. These overlap, but none substitutes for all the others.

Practical component and subsystem test matrix

Every row needs a requirement ID, setup, stimulus, measured result, approved limit, serial/revision, firmware, instrument/fixture version and disposition. The examples below are test methods, not released production limits.

Factory-test vocabulary

SPI can mean solder-paste inspection in manufacturing (different from the serial bus). AOI uses cameras to inspect assembly. X-ray examines hidden joints. ICT checks electrical properties/connections in circuit; flying probe uses moving probes and reduces fixture investment. FCT powers the unit and exercises functions; EOL means end-of-line. A pogo-pin fixture contacts designed test pads. DFT means designing test access, isolation and test firmware before the board is frozen.

Validate the fixture too: use controlled known-good and known-fault samples to check false passes/rejects. Calibrate instruments as needed, track fixture wear, and protect reference samples from uncontrolled changes. A golden sample is a reference, not the sole acceptance standard. A fixture that declares every unit “pass” proves nothing until fault detection is demonstrated.

Production gates and the package a factory needs

EVT: demonstrate engineering functions. DVT: validate the intended design against requirements. PVT: prove the manufacturing process and test system can build it consistently. Companies expand/name these gates differently; agree their exit criteria. A few working prototypes do not establish a finished design.

Request controlled schematics, layout/fabrication files and stackup, BOM with exact manufacturer part numbers and approved alternates, placement and assembly files, mechanical drawings/tolerances, firmware/programming package, work instructions, test specifications, labels and packaging. Define an ECO (engineering change order) path so a supplier cannot quietly substitute a part. Confirm ownership of tooling/files and how revisions are identified.

First-pass yield: if 90 of 100 units pass without rework, FPY is 90%. If 8 are repaired, eventual yield is 98%, but FPY stays 90%. Track failure categories, retest/rework, station time, escapes and field returns. Takt time follows demand; cycle time is how long a process takes. A cheap test that misses defects is not economical.

At interview level, plan RF/EMC pre-scans and a competent lab review early. A certified radio module does not automatically authorize the assembled host: integration conditions and remaining host requirements still apply. Exact obligations depend on markets and design. FCC module/host guidance. Ask the lab to scope electrical safety, ESD/immunity, materials and any battery-related obligations; do not claim compliance from a demo.

8. Technical interview rehearsal and final check

Answer with a hypothesis, a measurement, an interpretation and a verification step.

This is a study assessment, not proof of professional qualification. A realistic objective tonight is to explain the product clearly, choose sensible tests and identify where you need an electrical, firmware, acoustic or RF specialist. Two hours cannot replace years of circuit-design practice.

Use this five-part structure

Clarify the symptom and requirement → isolate a subsystem → choose a safe measurement → interpret evidence → prove the fix. Describe one first test before listing ten possible causes. Say what result would change your hypothesis. Do not call an unmeasured guess the root cause.

Four spoken questions: 60–90 seconds each

Answer before opening each model answer. Award yourself one point per criterion, 4 points per answer (16 total). These are self-assessed; the course cannot judge spoken competence.

Questions worth asking the founder

• Which functions work today on the integrated prototype, and what are its three largest unresolved technical risks?
• What is the current processor/module, audio architecture and connectivity plan? May I see the block diagram?
• Who owns schematic/layout, firmware, acoustics and RF today? What must this hire personally design?
• Does hearing-aid support mean playback only or two-way conversation, and which models/profiles are committed?
• What validation has the current revision passed? Are tooling, manufacturer, test fixtures and compliance labs selected?
• What are the first production quantity, cost target, schedule and release criteria?

Morning review: five minutes

Draw the three paths: power, audio and request/response. Explain DMM versus scope versus logic analyzer. Rehearse the “ring causes reset” diagnosis. Recall I²C versus I²S, PCB versus PCBA, and EVT/DVT/PVT. End with your real manufacturing story and the boundary of your electronics experience.