Solutions Engineer
Job description
About the role
This role targets unconventional thinkers who deploy testing platforms to break software and prove reliability. The position exists to demonstrate how Antithesis exposes bugs that conventional testing misses. Success is shown through customer workshops and live Proof-of-Concept executions.
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
Proof-of-Concept executions demonstrate product value to new customers during evaluation cycles.
Customer onboarding activities are supported to ensure smooth adoption of testing workflows.
Sales teams receive technical consultations and qualification support for complex deals.
Workshops on Property-based-Testing and methodologies are led to educate prospects and users.
Bugs are found and open source software is broken to validate robustness under varied conditions.
Testing discourse shapes thought leadership that influences how complex systems are validated.
Product demos are built, maintained, and presented to illustrate capabilities and workflows.
The Antithesis platform and testing approaches are explained to customers and prospects.
Requirements
The posting states a bachelor's degree requirement. A degree is required as a baseline qualification for the role.
Native Japanese speaking ability is required with business-level English skills.
Comfort working in tight timelines and high-pressure situations is necessary.
High technical curiosity drives investigation of new tools and failure modes.
Strong written and verbal communication conveys complex testing concepts clearly.
Collaboration with small, highly skilled teams is essential in this structure.
Flexibility to adapt to a fast-paced startup pace is required.
Experience building and running automated integration and end-to-end tests is expected.
Containerization using Docker and Kubernetes is required for environment consistency.
Object-oriented programming practices are used in customer examples and tooling.
Linux-based operating systems serve as the primary execution context for testing.
Scripting languages such as bash, shell, Python, and JavaScript are used for automation.
SQL, NoSQL, or other query engines are used to inspect and prepare test data.
Practical notes
This role involves travel to client sites, conferences, and Antithesis HQ.
The position is full-time and remote with a Japan-based location.
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
The role focuses on testing distributed systems rather than writing production code.
Container orchestration and infrastructure-as-code are common daily tools.
Property-based testing shifts the emphasis from example-based to behavior-driven validation.
Engineers rely on observability and deep technical visibility to diagnose issues.
Startups expect rapid context switching and frequent prioritization changes.
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.