Texas Sports Academy Main

Software Engineer

🇵🇭 Віддалено, Філіппіни Віддалено Повна зайнятість Опубліковано Тра 1, 2026
Локація Віддалено, Філіппіни
Формат роботи Віддалено
Тип зайнятості Повна зайнятість
Мова English
Опубліковано 01 травня 2026 р.
Остання перевірка 27 травня 2026 р.
Контекст JobGrid

Огляд ролі від JobGrid

Software Engineer at Texas Sports Academy Main: Віддалено, Філіппіни; Повна зайнятість. This listing is part of JobGrid's Віддалені вакансії software engineer з кар'єрних сторінок. JobGrid adds normalized role facts, source context, and a path to the employer application page so candidates can compare the listing before applying.

  • Location and workplace: Віддалено, Філіппіни
  • Role classification: Повна зайнятість
  • Source freshness: checked by JobGrid on 2026-05-27.
  • Application path: candidates continue to the employer application page with non-personal referral tags.

Software Engineer (AI-Forward)

As a Software Engineer with Texas Sports Academy, you play a key role in building the software that runs our school — student records, academic mastery tracking, training data, parent portals, admissions, and the AI-powered tools our guides and coaches use every day. This is a senior, AI-forward seat. You work directly with the founders, ship code every week with AI in your loop, and own the LLM-powered features that make our school feel nothing like a traditional school.

What you will be doing

  • Designing, building, and shipping product features across the full stack every week, with AI coding tools running alongside you.
  • Building real LLM-powered product features: tutoring agents, parent-facing copilots, coach-facing dashboards, retrieval over student data, evals for every one of them.
  • Working directly with the founders on scope, architecture, and trade-offs — no PM layer in between.
  • Owning the reliability, security, and cost of both classical systems and LLM pipelines.
  • Running your own AI coding workflow — prompts, subagents, custom tools, MCP servers — and raising the bar on how the whole team uses AI.
  • Writing evals and regression tests for AI features the same way you'd write unit tests for classical code.

What you will NOT be doing

  • Pretending AI is optional — if you're not already coding with Claude Code, Cursor, Codex, or an equivalent agent loop every day, this role is not for you.
  • Writing tickets for junior engineers to implement.
  • Sitting in status meetings all day — few meetings, more shipping.
  • Working on a narrow slice of a giant codebase.

Key responsibilities

  • Ship production code and AI features real students, parents, and staff rely on every day.
  • Own at least one major system end-to-end.
  • Move fast — features go from idea to production in days, not quarters — without breaking things.
  • Raise the AI-engineering bar as the team grows.