Job description template

Full-Stack Developer

We’re hiring a Full-Stack Developer to build and improve end-to-end features across our web applications, APIs, and supporting services. You’ll work independently on well-defined work, collaborate with product and engineering partners, and deliver reliable functionality with clean, maintainable code.

Responsibilities

Design, build, and maintain web application features from user interface through backend services and APIs
Implement and iterate on data models and integrations that power product functionality
Develop automated tests and participate in improving reliability and quality for new and existing features
Review code and collaborate on technical decisions to keep the codebase consistent and maintainable
Diagnose and fix bugs across the stack, including performance issues and edge cases
Contribute to deployment readiness by preparing changes for release and monitoring follow-up work

Must-have qualifications

Hands-on experience building production web applications with a modern frontend framework
Hands-on experience building production REST/GraphQL APIs and backend services
Proficiency with a relational database (e.g., PostgreSQL) including schema design and query optimization
Strong understanding of authentication and authorization patterns for web applications
Experience writing automated tests for frontend and/or backend features
Competence debugging complex issues across frontend, backend, and database

Nice to have

Experience with cloud infrastructure and deploying web applications and APIs
Experience with TypeScript and strongly typed frontend/backend development
Familiarity with observability practices (logging, metrics, tracing) to support production troubleshooting

What success looks like in 12 months

Ship end-to-end features with predictable delivery
Improve reliability and reduce incidents
Strengthen automated test coverage and quality gates
Own performance and correctness for core flows
Operational readiness for your work

Logistics

Full-time (40 hours a week), remote from Latin America.
Working hours overlap with US business hours.

About the company

[About your company: what you build, your stage and team size]

Want it tailored to your stack, seniority and time zone?

Customize with the free generator →

Interview scorecard

Score every candidate against the same bar

Deliver reliable, end-to-end product features across the web application and backend by writing maintainable code, validating with tests, and resolving issues quickly.

Outcomes to measure

What this hire should deliver in the first year. Replace [N] with your own targets.

Ship end-to-end features with predictable delivery. Measure: Deliver [N] production features end-to-end across UI and APIs with no more than [X]% revert/rework rate
Improve reliability and reduce incidents. Measure: Reduce production incidents attributable to your changes by [X]% over 12 months
Strengthen automated test coverage and quality gates. Measure: Add/extend automated tests for [N]% of new features you deliver and maintain/raise test pass rate to [X]%
Own performance and correctness for core flows. Measure: Improve key user/API performance metrics (e.g., response time or throughput) by [X]% for [Y] critical endpoints or pages
Operational readiness for your work. Measure: Increase mean time to resolve issues linked to your components to [X] hours or less

Competencies and weights

What to evaluate, how much it counts and what a strong answer looks like.

Frontend framework delivery · 21%
This role spans UI work; candidates must build and maintain production-quality interfaces. Evaluated in Round 1.

Weak: Builds UI changes that require frequent fixes after release or lacks basic UI validation
Meets the bar: Implements UI features that match requirements and includes appropriate client-side state and error handling
Strong: Produces well-structured UI code with reusable components, clear state management, and robust handling of edge cases

Backend API engineering · 21%
End-to-end delivery depends on dependable backend services and clean API design. Evaluated in Round 1.

Weak: Implements endpoints with unclear contracts, weak validation, or inconsistent behavior under error conditions
Meets the bar: Builds REST/GraphQL APIs with correct responses, validation, and consistent error handling
Strong: Designs scalable, well-documented endpoints with thoughtful data flow, validation, and performance considerations

Database design and queries · 16%
Correct schemas and efficient queries are essential for product functionality and performance. Evaluated in Round 2.

Weak: Relies on inefficient queries or incomplete schema design leading to slow or inconsistent data behavior
Meets the bar: Designs schemas and writes queries that are correct and reasonably efficient for the use case
Strong: Optimizes queries and data access patterns using indexes, query analysis, and careful schema choices

Auth and access control · 16%
Authentication/authorization mistakes create serious security and product risk. Evaluated in Round 2.

Weak: Implements authorization in an ad-hoc way that leaves gaps or unclear ownership boundaries
Meets the bar: Applies authentication and authorization patterns consistently across UI and APIs
Strong: Builds defense-in-depth authorization (server-side enforcement, least privilege, safe failure modes)

Debugging across the stack · 16%
Mid-level independence requires systematic troubleshooting across UI, backend, and data. Evaluated in Round 3.

Weak: Jumps to conclusions, changes multiple things at once, or can’t explain how they verified the root cause
Meets the bar: Uses logs/observations to narrow scope and confirms fixes with evidence
Strong: Employs a structured approach (hypothesis, isolation, verification), prevents recurrence, and documents learnings

Automated testing mindset · 10%
Tests reduce regressions and help teams ship confidently. Evaluated in Round 2.

Weak: Writes little or no automated tests and struggles to reproduce regressions
Meets the bar: Creates tests for critical paths and uses tests to validate changes
Strong: Builds reliable, targeted test suites that reduce regressions and improve iteration speed

Interview questions

Questions for every interview round

Each round has an owner, a time box and questions that test the competencies above.

Round 1: Full-Stack Feature Design
Senior Engineer · 60 min

Describe a recent production UI feature you built. What was the user flow, what components/state did you design, and how did you handle loading and error states?
Walk through how you designed and implemented a backend API for a real feature. What were the request/response contracts, how did you validate inputs, and how did you handle failures?
How do you coordinate changes across frontend and backend to keep releases safe? Give an example of how you reduced integration risk.

Round 2: Data, Security, and Quality
Tech Lead · 60 min

Tell us about a time you improved database performance. What was slow, what data access pattern caused it, and what changes (indexes/queries/schema) did you make?
Explain how you implemented authentication and authorization for a web application feature. What was protected, where was enforcement done, and how did you prevent privilege escalation?
Give an example of automated testing you added for a production feature. What did you test (unit/integration/e2e as relevant), and how did it catch regressions?

Round 3: Troubleshooting and Ownership
Staff Engineer · 60 min

Describe a complex bug you investigated across frontend, backend, and database. What evidence did you use to isolate the root cause, and what steps did you take to verify the fix?
How do you decide where to instrument or add observability when something is hard to debug? Provide a specific example.
Tell us about a time your fix could have introduced a side effect. How did you evaluate the blast radius and confirm safety before rollout?

Red flags to watch for

Cannot give concrete examples of building and deploying production frontend and backend features end-to-end
Trouble explaining how authentication/authorization is enforced server-side and consistently across APIs
Relies on guesswork for debugging without describing evidence, isolation steps, and verification
Avoids automated tests or cannot explain how tests prevent regressions in real scenarios

How much does it cost to hire a Full-Stack Developer in Latin America?

In 2026, a senior Full-Stack Developer in Latin America costs $6,750 to $7,750 a month all-in, versus $14,625 in the US: up to 54% less. Mid-level starts at $4,500.

Country

Mid-level

Senior

Argentina

$4,500

$6,750

Brazil

$5,000

$7,500

Colombia

$4,500

$6,750

Mexico

$5,250

$7,750

United States

$11,875

$14,625

Monthly cost in USD, all-in: the talent's salary plus Teilur's flat 20% fee, from our 2026 rates. The United States row shows what the same role typically costs there.

Compare costs in the calculator →

Frequently asked questions

What does a Full-Stack Developer do?

Typical responsibilities include: design, build, and maintain web application features from user interface through backend services and APIs; implement and iterate on data models and integrations that power product functionality; develop automated tests and participate in improving reliability and quality for new and existing features. The full list is in the template above.

How much does it cost to hire a Full-Stack Developer in Latin America?

In 2026, a senior Full-Stack Developer in Latin America costs $6,750 to $7,750 a month all-in, versus $14,625 in the US: up to 54% less. Mid-level starts at $4,500.

Can I customize this Full-Stack Developer job description?

Yes. Teilur's free Job Description & Scorecard Generator rewrites it for your stack, seniority, time zone and hiring urgency in about 15 seconds. No sign-up needed.

Book a Free Consultation

Full-Stack Developer Job Description Template