Full-Stack Developer (C# & ReactJS)

EviSmart; Taguig; Presencial; PHP 1 200 000 - 1 800 000; Tempo integral

Resumo da oferta

EviSmart in Manila is building a dental Autopilot platform used across 28 countries, enabling thousands of dental labs and dentists to work more effectively. Our Manila engineering team ships systems that support our in-house AI development, including the application layer for customer-facing products.

We hire engineers who take responsibility for delivering real products; you will own features from discovery through production, across frontend, backend, and database, and you will challenge

Qualificações

• Proven ability to analyze business problems and translate them into technical requirements.
• Willingness to own features from inception through testing and production.
• Strong collaboration and problem-solving mindset; able to challenge requirements when needed.

Responsabilidades

• Figure out problems before coding and communicate with stakeholders.
• Build features end-to-end across frontend, backend, and database.
• Test thoroughly and ensure production readiness.
• Own outcomes and fix issues post-release.
• Contribute to architecture decisions and trade-offs.

Conhecimentos

C# / ASP.NET Core / .NET

ReactJS

SQL Server

REST APIs

End-to-end delivery

Azure

CI/CD

Automated testing

AI-assisted development tools

Descrição da oferta de emprego

We're not looking for developers who simply know how to code. We're looking for engineers who know how to figure out what needs to be built, why it matters, and how to make it work.

You can have 5, 10, or 15 years of experience with C#, .NET, React, and SQL. That's great. But experience alone won't qualify you for this role.

What matters is what you can independently do with it.

WHAT WE'RE BUILDING

EviSmart is building a dental Autopilot platform operating across 28 countries, supporting thousands of dental labs and dentists worldwide.

Our Manila engineering team builds and ships the systems that make this possible, including the application layer supporting our in-house AI development.

These are real products, serving real customers, with real operational consequences when something doesn't work.

We're hiring engineers who can take responsibility for that.

WHAT WE ACTUALLY EXPECT YOU TO DO

1. Figure out the problem before writing code.

You won't always receive perfectly documented requirements or detailed instructions.

You need to be comfortable talking to stakeholders, understanding how the business works, identifying what's actually broken, and translating that into a technical solution.

That means doing business analysis when necessary.

Not because you're replacing a Business Analyst, but because you cannot build the right solution if you don't understand the problem.

2. Build it yourself. From the ground up.

We need engineers who can personally develop substantial features across:

• SQL Server
• REST APIs and system integrations

You should be capable of working across the frontend, backend, and database without depending on another developer to figure out the difficult parts for you.

We're not hiring someone whose primary contribution is researching technologies, recommending frameworks, or delegating the actual development.

You need to be able to execute.

3. Challenge requirements when they don't make sense.

A requirement isn't automatically the right solution.

If you see a better approach, explain it. If something creates unnecessary complexity, challenge it. If a proposed solution solves the wrong problem, say so.

We expect you to understand trade-offs, ask difficult questions, and propose alternatives.

We value engineers who think, not just engineers who agree.

4. Solve problems without waiting to be told every step.

You'll encounter unfamiliar systems, incomplete information, technical constraints, and things that don't work the first time.

Your responsibility is to investigate, understand, experiment, and find a way forward.

Ask for help when necessary. Collaborate with the team. Escalate genuine risks early.

But don't confuse collaboration with waiting for someone else to solve the problem.

5. Own what happens after you build it.

Writing code isn't the finish line.

You need to test your work, validate business requirements, investigate failures, and ensure the feature is actually ready for production.

If it breaks, you help fix it.

If it doesn't solve the original problem, you're not done.

If there's a risk to delivery, you raise it early.

Your responsibility isn't just to complete a ticket. It's to deliver something that works.

THE TECHNICAL FOUNDATION

You should already have substantial hands‑on experience with:

C# / ASP.NET Core / .NET — building production backend services and business logic

ReactJS — personally developing production web applications, not just listing it on your CV

SQL Server — designing schemas, writing queries, investigating performance, and understanding data integrity

REST APIs — designing, building, integrating, and troubleshooting services

End-to-end delivery — taking features from problem discovery through development, testing, and production readiness

Experience with Azure, CI/CD, automated testing, and AI-assisted development tools is valuable.

But tools don't replace engineering judgment.

WHO WILL STRUGGLE HERE

This role is probably not for you if:

• You prefer receiving detailed tickets and implementing exactly what's written.
• You need someone else to define the technical solution before you can begin.
• Your experience is primarily coordinating developers rather than personally building software.
• You avoid questioning requirements, even when you see a problem.
• You consider a feature finished once the code compiles or the ticket is closed.
• You expect seniority, years of experience, or job titles to speak for your capability.
• Your main priority is securing a higher salary without taking on the accountability that comes with it.

This just isn't that environment.

WHO WILL THRIVE HERE

You'll likely enjoy this role if you:

• Get curious about the business problem before discussing technology.
• Enjoy building systems from scratch and figuring things out independently.
• Can move comfortably between frontend, backend, APIs, and databases.
• Take pride in solving problems other people haven't figured out yet.
• Speak up when you disagree and can explain why.
• Care whether your solution actually improves something.
• Want your compensation and career growth to reflect the value you consistently deliver.

We don't expect you to know everything.

We expect you to know how to figure things out — and have the ability to execute once you do.

Tell us about ONE specific time you disagreed with a proposed technical solution on an actual project. What was being built, what solution was originally proposed, why did YOU believe it was the wrong approach, what alternative did you propose and why, and what was ultimately implemented? Please describe what actually happened rather than what you would hypothetically do.

We are looking for concrete examples from your actual experience. Please be specific about the project, your personal contribution and the decisions you personally made. Avoid general or hypothetical answers.

Tell us about ONE specific feature or system you personally built and delivered. Briefly describe the problem it was meant to solve, what YOU personally owned or built, the hardest problem you encountered and how you solved it, and how you determined it was ready for release. Please use an actual project you've worked on rather than describing your general approach.* *