Job Opportunities API

WHY TEXTUS TextUs on a mission to revolutionize business communication by enabling seamless and impactful engagement between workers and consumers. With a focus on innovation, ease of use, and delivering measurable results, our strategy is rooted in creating tools that outperform other messaging solutions while fostering trust and value for our customers and stakeholders. At TextUs, every team member is empowered to make a difference. Our collaborative and data-driven culture, combined with the guidance of a proven leadership team, ensures you have the resources and support to excel. Together, we’re building the future of mobile-first, conversational engagement and redefining what’s possible for businesses and their stakeholders. RESPONSIBILITIES We're moving from a build cycle that hides intent inside Jira tickets to one that puts a spec at the center of every change. AI generates working code from a clear enough spec; if the spec is fuzzy, the code is too. The bottleneck moves from typing to thinking. We run a V-shaped SDLC. The left side is intent: research, vision, spec, tests. The right side is verification: unit, integration, system, UAT. AI is changing the left side fast. Your job is to own the spec-to-verified-software loop so intent actually lands in production. Product owns the upper 40%. They bring the customer research, the 1-3 year vision for where TextUs is headed, and the strategic framing of the bet. Engineering owns the lower 60%: the spec that turns vision into code, the acceptance criteria that defines done, the UAT that proves it works, and the working software at the end of it. What you'll own A feature area end-to-end, from spec authoring through verified production rollout Translating product research and 1-3 year vision into specs the engineering org can build against Specs that explicitly address tenancy, auth, rate limits, cost, observability, failure modes, and rollback Acceptance criteria for every feature in your area, written before code is generated UAT scenarios and the test artifacts that verify the system does what the customer expects The codegen loop: scoping prompts, knowing when to stop and rewrite the spec rather than chase convergence, reviewing AI output against intent Production health for what ships: telemetry, alerts, on-call response, follow-through on whatever broke Pairing on spec authorship with less experienced engineers, raising the floor on what a "good spec" looks like across the team Overall mentorship of junior and mid-level engineers What you'll bring 5+ years building production software in a team that ships fast and owns its own quality Comfort with the customer side of the product, not just the engineering side. You can sit in a customer call, translate what you hear into a spec, and defend the trade-offs you made. Strong fluency with Claude Code or equivalent agentic dev tooling. We expect AI-assisted development to be the default workflow, not a side experiment, and we'll evaluate that fluency directly in the interview loop. Strong written communication. The spec is the artifact. If another engineer or an LLM can't build from what you write, the role doesn't work. Track record of shipping in a Rails or comparable full-stack environment, with depth in at least one adjacent surface (modern frontend, mobile, integrations, data) History of independent ownership: features you took from problem to production with light oversight Bonus: experience with TypeScript, React, React Native, Chrome extension surfaces, or embedded web app contexts Our stack Ruby on Rails Postgres or similar relational database experience ElasticSearch or similar search technology ActiveJob with AWS SQS, Sidekiq or similar background job system AWS How we work Small teams, real ownership. The scope and the runway are there to ship the thing the right way, not just patch the version that exists. AI-native by default