Structural Engineering Specialist
Job description
Structural Engineering Specialist AI Trainer at Meridial.
About the role
This role directs structural engineering expertise toward training data that powers AI for scientific and technical problem solving. You guide large language models to reason reliably about structural behavior and design. The focus is on documenting failure modes and improving model accuracy for engineering questions.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Each failure mode is recorded so that model reasoning is strengthened and future AI performance is improved.
Reproducible error traces are captured, and prompt engineering and evaluation metrics are refined based on findings. Clear communication that shows your work step by step is essential for effective evaluation and model refinement.
Requirements
The posting states a pay range of $8 to $65.
A PhD in structural engineering or a closely related civil engineering field is expected. Peer reviewed publications, field inspections, building information modeling, or large scale structural design projects demonstrate fit for the role. Metacognitive communication that shows the work is mandatory for success in this position. A secure computer and high speed internet are supplied by the contractor to perform remote work.
Nice to have
Clear, metacognitive communication "showing your work" is essential.
Skills & tools
Finite element modeling, building information modeling, and structural analysis tools support high quality training data. Familiarity with building codes and seismic load modeling aids rigorous evaluation of model reasoning.
Practical notes
The position is remote based in the Philippines with a mid senior level seniority designation. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Technical writing for AI training relies on precise, structured explanations of engineering principles. Familiarity with finite element modeling and building codes supports high quality training data. Consistent error documentation improves model reliability in safety critical domains. Clear demonstration of reasoning steps helps models generalize across structural systems. Civil engineering research and analysis methods translate directly into training datasets for scientific AI applications.
Questions to ask
Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.