3D Computer Vision Engineer for Plastic Surgery Simulation App

# Expert Developer Needed for Realistic 3D Plastic Surgery Visualization Platform I am looking for an expert developer, computer vision engineer, 3D engineer, or small highly specialized technical team to build the first version of a web-based **plastic surgery visualization platform for plastic surgeons**. The purpose of the application is to allow a plastic surgeon and patient to visualize potential cosmetic changes before surgery. For the initial version, the application will focus specifically on **rhinoplasty**. The central goal is simple: A surgeon should be able to capture or upload images of a real patient, view that patient in an interactive and realistic way, make precise changes to the patient’s nose, and immediately show the patient what those changes could look like while preserving the patient’s actual facial identity and appearance. This should feel like a professional plastic surgery consultation tool rather than a generic photo editor, beauty filter, or AI image-generation application. The visualization should be realistic enough that a patient can look at the result and clearly understand the aesthetic change being proposed. ## Main User Experience A surgeon should be able to log into the application, create a patient case, capture or upload the patient’s images, create one or more rhinoplasty simulations, compare those simulations with the patient’s original appearance, and save them to the case. The application should be straightforward enough to be used during a live consultation while the patient is sitting with the surgeon. The surgeon should not need technical or 3D modeling knowledge to operate it. The interface should feel polished, modern, clean, clinical, and relatively minimal. The main focus of the screen should always be the patient. ## Patient Case Creation The surgeon should be able to create a new patient case. A case should be able to contain: * Patient identifier/name * Original photographs * Captured photographs/video * Original facial representation/model * Saved simulations * Different versions of a simulation * Notes if needed * Date created * Date modified Once inside a case, the surgeon should be able to return to previously created simulations without starting over. ## Patient Image Upload The surgeon should be able to upload existing photographs of the patient. At minimum, the application should support the standard views useful for visualizing the nose, including: * Straight-on/front view * Left three-quarter/approximately 45-degree view * Right three-quarter/approximately 45-degree view * Left profile * Right profile Additional images should be allowed if useful. The application should be able to recognize which view is being provided and tell the user if an image is unsuitable because of issues such as: * Face positioned at the wrong angle * Face too far away * Face too close * Significant blur * Poor lighting * Part of the face being obscured * Patient looking away from the required direction * Incomplete face visibility The goal is to make image collection consistent without requiring the surgeon to manually determine whether every photograph is acceptable. # Live Camera Capture The application should also include a **live camera capture mode**. Instead of requiring previously taken photographs, the surgeon should be able to activate a webcam, phone camera, tablet camera, or connected camera and see the patient live on screen. The camera screen should provide guidance for positioning the patient correctly. For example, the application could guide the patient through: **Front → slight left turn → left 45° → left profile → right side → right profile** The live camera view should help indicate when the patient's face is correctly positioned and when a usable image can be captured. Ideally, the application should be able to automatically recognize when the patient reaches the correct orientation. The surgeon should then be able to capture the required views without repeatedly leaving the camera interface. The live camera interface should feel similar to a guided facial scan. It should be possible for the application to eventually support a continuous capture where the patient slowly turns their head and the system collects the necessary visual information. # Interactive Patient Visualization After the patient has been captured, the surgeon should have an interactive representation of the patient's face. The representation should maintain the recognizable appearance of the actual patient rather than replacing them with a generic face. The surgeon should be able to: * Rotate the view * Look straight at the face * View either profile * View three-quarter angles * Zoom in and out * Inspect the nose closely * Quickly return to standardized camera angles The experience should feel smooth and responsive. For example, there could be quick buttons for: **Front | Left 45° | Left Profile | Right 45° | Right Profile** The surgeon should also be able to freely rotate the representation. # Rhinoplasty Simulation This is the most important part of the application. The surgeon should be able to modify individual characteristics of the patient's nose while seeing the result update visually. The controls should be understandable to a plastic surgeon and should correspond to meaningful characteristics of nasal appearance. Rhinoplasty can involve changes to the nose's size and proportions, bridge, nasal profile, nasal tip, nostrils, length, width and symmetry. The application should provide very detailed control over these areas. ## Overall Nose The surgeon should be able to: * Increase overall apparent nose size * Decrease overall apparent nose size * Make the nose appear more proportionate to the face * Increase or decrease overall nasal projection * Make the overall nose narrower * Make the overall nose wider * Make the nose appear straighter * Correct visible left/right asymmetry * Adjust an overall crooked appearance * Change the overall contour while preserving the patient's surrounding facial anatomy ## Nasal Bridge / Dorsum The surgeon should be able to adjust: * Bridge height * Bridge width * Bridge straightness * Dorsal profile * Dorsal hump prominence * Dorsal hump reduction * Small dorsal depressions * Excessively flat bridge * Excessively high bridge * Width of the upper nasal bridge * Width of the middle nasal bridge * Smoothness of the bridge * Transition from forehead into the nose * Transition from bridge into the nasal tip The system should be capable of showing subtle changes rather than requiring dramatic modifications. For example, a surgeon might want to reduce a dorsal hump by only a small amount while leaving the remaining profile essentially unchanged. Professional rhinoplasty references specifically identify lowering a dorsal hump and modifying depressions of the nasal bridge as common aesthetic changes. ## Nasal Radix The surgeon should have control over the upper starting point of the nose between the eyes. This may include: * Increasing radix height * Decreasing radix height * Increasing radix projection * Decreasing radix projection * Changing how smoothly the forehead transitions into the bridge Small changes in this area should influence the profile naturally rather than deforming unrelated regions. ## Nasal Tip The nasal tip should have particularly detailed controls. The surgeon should be able to: * Increase tip projection * Decrease tip projection * Rotate the tip upward * Rotate the tip downward * Refine the tip * Make the tip narrower * Make the tip wider * Reduce a bulbous appearance * Increase tip definition * Decrease excessive tip definition * Correct a drooping tip * Correct an overly upturned tip * Correct a hooked appearance * Correct tip asymmetry * Adjust the apparent position of the tip * Adjust the shape of the tip when viewed from the front * Adjust tip appearance from the profile * Adjust tip appearance from the three-quarter view * Make the tip slightly more pointed or slightly softer/rounder * Adjust the transition between the bridge and tip * Adjust the supratip region immediately above the tip The surgeon should be able to make very small changes. For example: **Tip rotation +2°** should look meaningfully different from: **Tip rotation +8°** rather than functioning as a simple on/off transformation. Tip projection, rotation, width, bulbosity, drooping/upturned appearance and asymmetry are all important variables in rhinoplasty assessment. ## Nasal Length The surgeon should be able to: * Shorten the apparent nose * Lengthen the apparent nose * Shorten only slightly * Modify length while maintaining a natural tip position * Visualize how changing length affects the profile and front appearance Reducing a long nose is another recognized rhinoplasty goal. ## Nostril / Alar Region The surgeon should be able to modify the nostrils and nasal base. This should include: * Narrowing nostril width * Increasing nostril width * Reducing excessive nostril flare * Increasing or decreasing alar flare * Narrowing the overall nasal base * Widening the overall nasal base * Changing nostril size * Adjusting nostril shape * Adjusting nostril position * Correcting asymmetrical nostrils * Adjusting one side independently if necessary * Adjusting the shape of the nostril opening * Adjusting nostril visibility from the front * Adjusting nostril visibility from the profile * Adjusting nostril visibility from underneath the nose Nostril width, size, position and flare are established areas modified during rhinoplasty. ## Alar Base The surgeon should be able to modify the width and contour of the nasal base independently from the bridge. For example, the surgeon may want to: * Narrow a wide nasal base * Reduce flare without significantly changing nostril height * Modify the left and right sides separately * Improve apparent symmetry The deformation should remain smooth and anatomically natural. ## Columella The surgeon should have visual control over the tissue separating the nostrils. This may include: * Increasing visible columella * Decreasing visible columella * Adjusting apparent columellar position * Correcting an excessively hanging appearance * Correcting an excessively retracted appearance * Adjusting how the columella transitions into the upper lip ## Nasolabial Relationship The surgeon should be able to visualize changes in the relationship between the nasal tip/columella and upper lip. This should include changing the visual **nasolabial angle**, which is commonly used when evaluating nasal tip rotation. The surgeon should be able to rotate the tip and immediately see this relationship change in profile. ## Nasal Asymmetry The controls should not assume that every nose is perfectly symmetrical. The surgeon should be able to make adjustments independently to the left and right sides where appropriate. Examples include: * Straightening a visibly crooked nose * Correcting uneven nostril size * Correcting uneven alar flare * Adjusting one side of the nasal tip * Adjusting asymmetric bridge contours * Adjusting asymmetric nasal base contours The application should allow improvement of symmetry without automatically forcing the nose into perfect mathematical symmetry. Rhinoplasty can improve asymmetry, but perfect symmetry should not be assumed or promised. # Direct Visual Manipulation In addition to sliders or numerical controls, I would ideally like the surgeon to be able to directly manipulate the patient's nose visually. For example, the surgeon might click or select the nasal tip and move it slightly. The surgeon might select the bridge and reduce a hump. The surgeon might select the nasal base and narrow it. The application should interpret these actions intelligently so the surrounding anatomy moves naturally rather than looking stretched or warped. Direct manipulation should work together with the more precise controls. # Precision Controls The surgeon should be able to make both: **Very subtle adjustments** and **More noticeable adjustments.** The application should not force surgeons into preset noses such as: “Natural” “Small” “Celebrity” etc. The surgeon should have actual control. Where appropriate, values should also be visible numerically so that the surgeon can reproduce or compare changes. For example: **Tip Projection: -1.5 mm** **Tip Rotation: +4°** **Alar Width: -2 mm** The exact measurement system can be determined during development, but precision and repeatability are important. # Realism Requirements This is one of the most important requirements for the entire project. The simulated patient must still look like **the same person**. When the surgeon modifies the nose, the application should not unexpectedly modify: * Eyes * Eyebrows * Eyelids * Forehead * Cheeks * Lips * Jaw * Chin * Ears * Hair * Skin tone * Skin texture * Facial expression * Apparent age * Face shape * Makeup * Lighting * Background unless a change is unavoidable because the nose physically affects an adjacent area. If the surgeon reduces the dorsal hump, the result should essentially look like: **the same photograph of the same patient, except with the requested nasal modification.** It should not beautify the entire person. It should not make them younger. It should not subtly reshape their jaw. It should not change their eyes. It should not produce a different person who merely resembles the patient. The visualization should preserve identity extremely well. # Natural Appearance The changes should also look anatomically plausible. The nose should not appear: * Melted * Stretched * Artificial * Airbrushed * Blurry * Obviously generated * Detached from the surrounding face Lighting, shadows, skin texture and contours should remain consistent with the original person. The result should look like a plausible photograph or visualization of the original patient with the selected modification. # Real-Time Updating Ideally, modifications should update as close to real time as technically reasonable. When the surgeon moves a slider, they should be able to see what is changing without repeatedly waiting for long processing jobs. If a higher-quality final render requires additional processing, a lower-latency preview can be shown during editing and a higher-quality result generated afterward. The consultation experience should still feel interactive. # Multiple Viewing Angles A change made to the nose should remain consistent from different viewing angles. For example, if the surgeon reduces nasal tip projection while looking at the profile, switching to the three-quarter view should show the same modification. The system should not create completely independent alterations for each photograph. The different views should represent the same proposed nose as consistently as possible. # Before and After Comparison The surgeon should be able to instantly compare: **Original** and **Simulation** Possible viewing modes should include: * Side-by-side * Before/after slider * Toggle between before and after * Overlay/fade * Synchronized viewing angles A surgeon should be able to rotate the original and simulated views together. # Multiple Simulations The surgeon should be able to create several different options for the same patient. For example: **Original** **Simulation A — Conservative** **Simulation B — Moderate** **Simulation C — Alternative Tip** The names should be editable. Each simulation should preserve its own settings. A surgeon should be able to duplicate an existing simulation and make additional modifications without destroying the original. # Undo / Redo The surgeon should be able to undo and redo individual changes. There should also be options to: * Reset an individual control * Reset the entire nose * Return to the original patient * Duplicate the current simulation * Restore a previous simulation # Reference Views It would be useful for the surgeon to have standardized reference views available with one click. For example: **Front** **Left 45°** **Left Profile** **Right 45°** **Right Profile** **Base / underside view** and potentially a freely rotatable view. # Surgeon Workspace The primary editing screen could generally contain: A large patient visualization in the center. A panel containing rhinoplasty controls on one side. A before/after or simulation selector. Camera-angle shortcuts. Undo/redo controls. Buttons for saving and duplicating simulations. The exact UI design is open to the developer/designer, but it should feel considerably closer to professional medical/design software than a consumer photo-filter application. # Patient Presentation Mode There should ideally be a simplified presentation mode. Once the surgeon has finished editing, they should be able to hide the complex controls and simply show the patient: * Original * Simulation A * Simulation B * Simulation C with clean before/after comparisons. This could be used while discussing options with the patient. # Saving All work should be savable. Closing the browser and returning later should not cause the simulations to disappear. The surgeon should be able to reopen a patient and continue editing a previous simulation. # Export The surgeon should eventually be able to export useful consultation visuals. For example: * Before/after image * Front comparison * Profile comparison * Multiple simulation comparison Exported materials should clearly identify the result as a simulation rather than a guaranteed surgical outcome. # Important Product Principle This application should provide a **visual simulation of surgeon-selected changes**. It should not represent its output as a guaranteed prediction of exactly how someone will heal or what their final surgical outcome will be. Actual rhinoplasty outcomes depend on anatomy, surgical technique, healing and other factors; professional sources also emphasize realistic expectations rather than perfect outcomes. The surgeon remains responsible for determining what modifications are appropriate. # Future Expansion The initial contract is focused on rhinoplasty because I want the core visualization technology working extremely well before expanding the application. However, the long-term product may eventually support: * Chin augmentation/reduction * Jaw contouring * Facelift * Neck lift * Eyelid surgery * Brow procedures * Lip procedures * Abdominal contouring * Liposuction * Body contouring * Other aesthetic procedures The initial product should therefore be built cleanly enough that additional procedure types could be added later. # What I Expect From the Developer I am intentionally **not prescribing exactly how this should be engineered**. I want applicants with relevant expertise to explain how they believe the problem should be solved. The developer should be capable of determining an appropriate technical approach for: * Patient capture * Multi-angle facial representation * Highly realistic visualization * Precise localized nasal modification * Preserving patient identity * Maintaining consistency across viewing angles * Interactive performance * Secure patient/case storage I am much more interested in demonstrated ability in computer vision, 3D graphics, facial reconstruction, geometry, image processing or related areas than someone who only builds conventional websites. # When Applying Please explain: 1. What similar computer vision, facial reconstruction, 3D graphics, image manipulation, simulation, or medical visualization work have you personally completed? 2. Please provide links to relevant projects, demos, repositories, videos, papers or portfolio examples. 3. Based on this description, how would you approach the technical problem? 4. Do you believe the level of realism and identity preservation described here is achievable? If so, what approach would you consider? 5. How would you ensure that modifying the nose does not unintentionally change other portions of the patient's face? 6. How would you maintain the same proposed change across front, profile and three-quarter views? 7. Which part of this product do you believe presents the greatest technical challenge? 8. What would you include in the first working milestone to prove that the underlying technology is viable before building the entire application? 9. What timeline would you estimate for a functional rhinoplasty-focused MVP? 10. Will you personally perform the work, or will any portion be subcontracted? Please begin your proposal with “3D SURGICAL VISUALIZATION” so I know you have read the complete project description. The most important thing I am looking for is someone who can make the core visualization genuinely work, not simply create a polished interface around unreliable or fake functionality.