Kỹ sư Phần mềm Backend cấp cao tại Aerostrat
Đã xác nhận còn mở
Aerostrat tuyển kỹ sư phần mềm backend cấp cao tập trung vào kỹ thuật phần mềm backend.
Tìm việc theo công ty: Aerostrat
- Địa điểm
- Từ xa
- Khu vực tuyển dụng
- Seattle
- Loại hình
- Full-time
- Hình thức làm việc
- remote
- Công nghệ
- C#, .NET, AWS, Azure, SQL
Lưu việc làm — tài khoản miễn phí Việc làm đã lưu
Tạo hồ sơ ứng tuyển miễn phí — Lưu kỹ năng và dự án trong một hồ sơ có thể dùng lại. Hồ sơ mặc định riêng tư; bạn quyết định khi nào chia sẻ. Ứng tuyển tin này trực tiếp với nhà tuyển dụng.
Bằng cách tiếp tục, bạn đồng ý với cách xử lý dữ liệu để quản lý tài khoản và hồ sơ của mình. Quyền riêng tư
Tổng quan vị trí
Vị trí tập trung vào kỹ thuật phần mềm backend trong tổ chức công nghệ phân tán.
Trách nhiệm
- Thực hiện công việc kỹ thuật hoặc nghiên cứu cho kỹ thuật phần mềm backend.
- Phối hợp với các bên liên quan về sản phẩm, kỹ thuật, bảo mật và kinh doanh.
- Cải thiện độ tin cậy, kiểm thử, tài liệu và chất lượng vận hành.
- Chuyển yêu cầu kỹ thuật phức tạp thành kết quả dễ bảo trì.
Yêu cầu
- Có kinh nghiệm chuyên môn về IT, giải pháp, kỹ thuật phần mềm, an toàn AI hoặc hạ tầng.
- Kỹ năng giải quyết vấn đề, giao tiếp và hệ thống tốt.
- Có khả năng làm việc hiệu quả trong môi trường remote hoặc phân tán.
Công nghệ trong công việc
- C#: 5+ years of work experience in C#/.NET 5+ years of work experience with SQL databases 3+ years of work experience working on REST APIs 3+ years of work experience working with Azure or AWS cloud projects 3+ years of work experience building technical designs for other engineers .
- .NET: 5+ years of work experience in C#/.NET 5+ years of work experience with SQL databases 3+ years of work experience working on REST APIs 3+ years of work experience working with Azure or AWS cloud projects 3+ years of work experience building technical designs for other engineers .
- AWS: 5+ years of work experience in C#/.NET 5+ years of work experience with SQL databases 3+ years of work experience working on REST APIs 3+ years of work experience working with Azure or AWS cloud projects 3+ years of work experience building technical designs for other engineers .
- Azure: 5+ years of work experience in C#/.NET 5+ years of work experience with SQL databases 3+ years of work experience working on REST APIs 3+ years of work experience working with Azure or AWS cloud projects 3+ years of work experience building technical designs for other engineers .
- SQL: 5+ years of work experience in C#/.NET 5+ years of work experience with SQL databases 3+ years of work experience working on REST APIs 3+ years of work experience working with Azure or AWS cloud projects 3+ years of work experience building technical designs for other engineers .
- C: 5+ years of work experience in C#/.NET 5+ years of work experience with SQL databases 3+ years of work experience working on REST APIs 3+ years of work experience working with Azure or AWS cloud projects 3+ years of work experience building technical designs for other engineers .
- Go: • You have a positive attitude and communication style because we've learned that excellent written communication and attitude go a long way for a remote .
- SQL Server: • You have significant experience with C#/.NET and SQL Server .
- CAN: As a Sr backend software engineer at Aerostrat, you'll play a critical role in expanding our infrastructure and APIs to ensure we can scale with our .
Hướng dẫn đánh giá mức độ phù hợp (tiếng Anh)
Phân tích dựa trên yêu cầu và trách nhiệm trong tin tuyển dụng của nhà tuyển dụng.
Understanding the scope. This Senior Software Engineer (Backend) position at Aerostrat is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “This role focuses on backend software engineering in a distributed technology organisation.” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the software engineering area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.
What the responsibilities signal. The posting specifically names “Deliver technical work or research for backend software engineering.”; “Collaborate with product, engineering, security and business stakeholders.”; “Improve reliability, testing, documentation and operational quality.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.
How to read the requirements. The listed qualifications include “Relevant professional experience in IT, solutions, software engineering, AI safety or infrastructure engineering.”; “Strong problem-solving, communication and systems skills.”; “Ability to work effectively in a remote or distributed environment.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.
Technology and working evidence. The technology terms associated with this listing are C#, .NET, AWS, Azure, SQL. Treat this as a set of posting-derived signals, not a guarantee that every tool is used daily or that the list is complete. For each term relevant to your experience, prepare one concrete example: the system or workflow, the part you owned, the alternatives considered, and how you tested reliability, security, performance or usability as appropriate. If you have not used a named tool, explain the closest related system you have worked with and how you would ramp up; do not relabel that experience as direct production use. If the source describes technologies beyond this list, prioritize its exact wording.
Evidence to put in the application. Tailor the first half of your CV to the named work instead of using a generic summary. Lead with two or three outcomes that match the responsibilities, and include enough context to show complexity, scope and your role. Add technical detail where it substantiates an outcome: architecture, interfaces, data or traffic scale, test strategy, deployment approach, incident response or collaboration, as relevant to your real projects. Keep confidential employer information private; describe the problem and your contribution without disclosing protected data. If the role is in software engineering, make the connection explicit between your past work and this position’s actual requirements. A short, specific cover note can explain why this team and scope fit your experience, but it should not repeat the CV.
Interview preparation. Build a small set of stories from the employer’s stated duties: one about delivering a difficult piece of work, one about diagnosing a failure or unexpected result, and one about working through a design or prioritization decision. Use the examples to explain your reasoning, not just the final answer. Be ready to discuss the technical depth behind any claim on your CV and to draw boundaries around what you personally did. Questions worth preparing include how success is measured in the first months, which responsibility currently takes the most team capacity, how work is reviewed and released, and which technical constraints shape decisions. These are preparation prompts, not claims about Aerostrat’s interview process; the posting does not establish the number or format of interview rounds.
Location and employment details. The supplied listing describes the work arrangement as remote; the displayed location is Seattle. The employer’s source is the authority for where applicants may live, travel expectations, work authorization, compensation, schedule and employment type. Confirm each point before investing time in an application, especially if the role serves a specific territory or customer group. This page does not infer that “remote” means work from any country. Where the official post gives a region, travel requirement or language requirement, use that exact condition when deciding whether the role is practical for you. Where a detail is absent here, use the linked employer posting to verify it.
Questions to resolve with the employer. Use the source posting to separate confirmed facts from unknowns. Ask which outcomes define success for this role, what the team expects the hire to own directly, how collaboration works across functions or locations, and what support is available for onboarding. For Senior Software Engineer (Backend), also clarify the priority among the responsibilities listed above and how the named qualifications are evaluated in practice. If compensation, benefits, reporting line, team size, travel or work authorization is important to your decision, request the precise terms from the employer; this page does not fill in missing terms. Recheck the source listing immediately before applying because vacancies and requirements can change.
Phúc lợi
- Địa điểm và hình thức remote theo tin đăng chính thức.
- Cơ hội làm việc trên sản phẩm bảo mật, AI hoặc công nghệ doanh nghiệp.
Về Aerostrat
As a senior full-stack software engineer at Aerostrat, you'll play a critical role in expanding our product offerings across the tech stack working cohesively on UX, APIs and infrastructure to ensure we can scale with our customers.
As a member of our growing engineering team, you'll need to be a self-motivated, high-impact and driven individual that goes out of your way to learn about and produce the best solutions for our customers. Because our team is so lean, you will have a real opportunity to contribute to the direction of the product and see your ideas make it into production on a regular basis.
Learn everything there is to know about aviation maintenance planning through our on-boarding process (so don't worry if you do not have any experience in this industry!)
Analyze tough customer problems and come up with great designs that you will turn into efficient backend solutions
Design, develop, and maintain scalable systems and well-tested features
Design and implement services that are reliable, high-quality, performant, and sustainable
Trang web nhà tuyển dụngCách ứng tuyển
Kiểm tra tin gốc và gửi hồ sơ trực tiếp qua trang tuyển dụng của nhà tuyển dụng.
Xem tin gốc và ứng tuyểnỨng tuyển trực tiếpNguồn được kiểm tra: 2026-11-08
Khám phá việc làm theo danh mục
Việc làm liên quan
- Kỹ sư Backend cấp cao (TypeScript/Python/C#) tại Kake — Kake
- Kỹ sư backend an ninh bên ngoài cấp cao tại Horizon3 — Horizon3
- Kỹ sư backend cấp cao, Growth và MSSP tại Horizon3 — Horizon3
- Kỹ sư tích hợp backend cấp cao tại Horizon3 — Horizon3
- Kỹ sư backend phòng vệ tự động cấp cao tại Horizon3 — Horizon3
- Kỹ sư backend cấp cao, Precision Defense tại Horizon3 — Horizon3
