Technical Support Engineer (New York/New Jersey)

We need to output HTML fragment only, with sections for headings where there is real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only if posting has real specific content. We have location info: "Location: This is a hybrid remote/in-office role. Medidata follows a hybrid office policy..." That's location info; we could put in a short

maybe under a heading? There's no heading for location; we could embed in a paragraph maybe under "About the role"? But we have "About the role" heading maybe for description of role. The posting includes "About the Team:" which describes role. Could treat that as About the role. Also "About our Company:" is company description; could be part of About the role or separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (maybe combine company and team). Responsibilities we have a list. Qualifications we have a list. Skills maybe overlapped with qualifications; but we can put skills as separate if there is specific skill list. The qualifications list includes many technical skills; we could treat that as Qualifications. Skills maybe not needed separately if content overlaps. Benefits we have description of benefits: medical, dental, etc. Pay we have salary ranges per location. Schedule maybe not specified; we have hybrid remote/in-office but no specific schedule like days per week. The posting mentions "hybrid office policy ... expected to work on site a certain number of days per week following Company policy." That's vague; not a specific schedule. So we should not create Schedule section unless specific content. So we omit Schedule. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to remove the EEO paragraph, scam warning, etc. Also remove "Note: Please be on the lookout for job scams..." and the EEO block. Also remove "As with all roles, Medidata sets ranges..."? That is part of pay description; we need to keep pay ranges but maybe we can keep that sentence as it's part of pay description. However it's somewhat generic; but it's about pay ranges; we can keep it as part of Pay section. The base pay description is part of Pay. We need to keep location info. Could embed in About the role or maybe a separate short paragraph before headings. Since no heading for location, we can just put a

at start. We must not repeat job title as heading. The job title is Technical Support Engineer; we should not put that as heading. We need to output only HTML fragment, no /, no markdown. Let's structure:

Location: This is a hybrid remote/in-office role. Medidata follows a hybrid office policy in which employees who are hired for an in-person position are expected to work on site a certain number of days per week following Company policy.

About the role

About our Company: Medidata is powering smarter treatments and healthier people through digital solutions to support clinical trials. Celebrating over 25 years of ground-breaking technological innovation across more than 38,000 trials and 12 million patients, Medidata offers industry-leading expertise, analytics-powered insights, and one of the largest clinical trial data sets in the industry. More than 1 million registered users across approximately 2,300 customers trust Medidata's seamless, end-to-end platform to improve patient experiences, accelerate clinical breakthroughs, and bring therapies to market faster. A Dassault Systèmes brand (Euronext Paris: FR0014003TT8, DSY.PA), Medidata is headquartered in New York City and has been recognized as a Leader by Everest Group and IDC. Discover more at www.medidata.com. Listen to our latest podcast, from Dreamers to Disruptors, and follow us at @Medidata.

About the Team: The Technical Support Engineer is a technical expert who acts as the primary contact between different support teams and core engineering teams. They handle work requests (which can be internally or externally generated) that have been routed for diagnosis and implementation while regularly updating internal and/or external customers. The Technical Support Engineer will handle work requests directly, or solicit assistance from the core engineering teams within the R&D team for issues/defect reporting. They also identify application defects, then test and document them for the core engineering teams to fix as part of the product. The Technical Support Engineer is a seasoned analyst who has a proven record of customer satisfaction, a reference point for the entire team on various application topics and is able to resolve most of the items escalated from the previous support teams.

Responsibilities

• Provide support for internal and external customers
• Manage work requests that describe particular issues, software bugs or customer problems
• Develop appropriate fixes or SQL scripts to resolve customer problems, or identify existing scripts or patches that must be applied
• Provide general process analysis and make recommendations for improvements
• Participate in weekly (and occasional weekend) on-call rotations for urgent off-hours issues
• Participate in taking calls (during business hours) from VIP customers for urgent issues
• Distinguish between application database, operating system, network, and hardware problems and properly take ownership of issues through to resolution
• Present complex technical information to non-technical audiences
• Provide accurate and complete problem resolution documentation for future reference and management reporting
• Take part in the creation and maintenance of knowledge base data
• Continually increase subject matter knowledge on Medidata products
• Interact with other Medidata teams to ensure application efficiency, effectiveness and conformance with regulatory and legislative controls
• Reproduce technical problems, debug systems, diagnose causes, identify temporary and long-term solutions and communicate status updates to clients
• Utilize AI generative tools to rapidly draft, format, and publish internal Knowledge Base articles, post-mortem root-cause analyses, and customer-facing resolution summaries.
• Use developer tools like GitHub Copilot within Visual Studio to trace codebase logic, debug application errors, and accelerate code reviews in Ruby, C#, JavaScript, and ASP.NET.
• Utilize advanced prompt engineering with LLMs such as Gemini or Copilot to investigate system logs, interpret API failures within Postman, and generate creative solutions for novel software issues.
• Utilize Medidata's proprietary AI models and internal language tools to securely analyze platform workflows and clinical trial data structures while maintaining strict compliance controls.
• Critically evaluate and validate all AI-generated technical solutions and code snippets against system logs and product documentation to ensure accuracy, safety, and compliance with clinical regulatory standards prior to implementation.

Qualifications

• Bachelor's degree preferably in Computer Science, Information Systems or Life Sciences, or equivalent engineering experience
• Experience with API/web services.
• SQL experience querying and modifying data using MYSQL, MS SQL Server, MongoDB, Snowflake
• Experience with C#, Javascript, Visual Studio, Ruby, Python and ASP.NET
• Experience using Incident Management and/or Project Management software
• Experience with multiple integrated software products/services
• Experience working with customers to resolve complex issues in a professional manner including finding innovative workarounds to issues
• Experience with Git, Visual Studio, Virtual Machines, Excel, Postman or other API/REST client
• Strong interpersonal and collaborative skills
• Proficiency using GitHub Copilot, Gemini, or ChatGPT for technical problem-solving, code explanation, and script generation.
• Familiarity with using LLMs (e.g., NotebookLM) for document synthesis, knowledge retrieval, and technical research.
• Basic understanding of prompt engineering principles to extract accurate, secure, and context-aware responses from AI tools during live troubleshooting.
• Willingness to learn and adopt proprietary Medidata AI systems and specialized clinical platform models.
• Proven ability to exercise 'human-in-the-loop' oversight, identifying potential AI hallucinations or errors in generated technical documentation and code.
• Strong understanding of data privacy requirements when interacting with AI tools, ensuring that sensitive clinical trial information or PII is never exposed to non-compliant or public model environments.

Maybe we also need a Skills section? The qualifications already cover skills; but we could split out "Skills" as separate if there is distinct skill list. However the instruction: prefer a few substantive sections over many thin ones. So we can keep Qualifications and maybe not add Skills. Benefits: we have description: "Base pay is one part of the Total Rewards that Medidata provides to compensate and recognize employees for their work. Most sales positions are eligible for a commission on the terms of applicable plan documents, and many of Medidata's non-sales positions are eligible for annual bonuses. Medidata believes that benefits should connect you to the support you need when it matters most and provides benefits, including medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off; and 10 paid holidays per year." We should keep that as Benefits section. Pay: we have salary ranges per location. We need to include that. Also the sentence about base pay being part of total rewards maybe belongs to Benefits; but we already used that sentence in Benefits. Actually the sentence about base pay being part of total rewards appears before benefits list. We could split: base pay statement could be in Pay section, benefits list in Benefits. But the instruction: we should not create Pay/Schedule/Benefits sections unless posting actually states them. It does state base pay ranges and benefits. So we need both. Thus we need to separate base pay statement from benefits list. The posting: "Base pay is one part of the Total Rewards that Medidata provides to compensate and recognize employees for their work. Most sales positions are eligible for a commission on the terms of applicable plan documents, and many of Medidata's non-sales positions are eligible for annual bonuses. Medidata believes that benefits should connect you to the support you need when it matters most and provides benefits, including medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off; and 10 paid holidays per year." We could put first two sentences in Pay section (base pay and commission/bonus). Then Benefits section for the list. Pay section also includes the salary ranges per location. So we combine. Thus:

Pay

Base pay is one part of the Total Rewards that Medidata provides to compensate and recognize employees for their work. Most sales positions are eligible for a commission on the terms of applicable plan documents, and many of Medidata's non-sales positions are eligible for annual bonuses.

The salary range for positions that will be physically based in the NYC Metro Area is $79,500.00 to 106,000.00

The salary range for positions that will be physically based in the California Bay Area is $84,000.00 to 112,000.00

The salary range for positions that will be physically based in the Boston Metro Area is $78,000.00 to 104,000.00

The salary range for positions that will be physically based in Texas or Ohio is $70,125.00 to 93,