SKYWARE CAREERS
People who understand the problem
and see it through.
We prove value with results, not promises about technology.
Skyware solves business problems with software. We don’t stop at implementing requirements: we ask why they matter, look for better ways, and build results that run reliably in real services.
We want to work with colleagues who think for themselves, respect each other’s expertise and take ownership of their work.
01 · WHO WE ARE
There is a clear reason
behind what we do.
Good technology makes complex problems simple, turns repetitive work efficient, and creates new business opportunities.
Skyware is a software company that understands how businesses run and applies technology to real business.
Enterprise Solutions
We build solutions that fit the business.We analyze diverse requirements and operating environments, then design and develop software systems with stability and scalability in mind.
AI & AX
Using AI well matters more than adopting it.We connect AI to real work and services, focusing on efficiency gains and genuine problem solving rather than adoption for its own sake.
Platform & Integration
We connect different systems and build more efficient structures.From enterprise messaging and platform builds to system integration, we develop the technology that keeps business flowing.
02 · SKYWARE WAY
How We Work
Good results don’t happen by accident.
How we approach work, how we solve problems and how we collaborate add up to what the team can do.
These are the ten principles Skyware cares about.
- Understand the problem first.Before carrying out a requirement as written, we ask why it is needed. The right solution starts with understanding the real problem.
- Look for a better way.The familiar way is not always the best. We cut unnecessary steps and propose and apply more efficient methods.
- Let results speak.What was solved matters more than how long it took. Effort and process count, but so does what was actually delivered.
- Decide for yourself and own it.Working autonomously means taking responsibility for your judgment and its results. We understand the purpose and priorities of our work and act on them.
- The better idea wins, not the higher title.We weigh what is said, not who said it. Different views are respected, and decisions rest on facts and evidence.
- Collaboration starts with clear communication.We share what is needed on time and talk about problems instead of hiding them, so everyone can understand and anticipate each other’s work.
- No compromises on quality and fundamentals.Small errors and minor omissions can grow into big problems. Code quality, system stability and security are basics we take seriously.
- Think from the customer’s side.What is technically possible and what the customer needs can differ. We understand the real usage environment and business goals before finding a solution.
- Learning is completed in practice.Knowing a new technology is not enough. We apply it, verify it and turn the experience into team capability.
- The more we work together, the better the team.Great individuals alone don’t make great results. We respect each other’s expertise, share knowledge and work toward common goals.
SKYWARE PEOPLE · Who we look for
People who find problems themselves and see them through
03 · THE PEOPLE WE LOOK FOR
These are the colleagues
we want to work with.
Years of experience are not all we care about.
We are more interested in what you have experienced, the judgments you made along the way, and which problems you solved and how.
- People who find problems themselvesRather than waiting for assignments, they spot what needs improving and think about how to fix it
- People who own their expertiseThey keep deepening their field and can make the calls it requires on their own
- People who understand the purpose of the workBeyond implementing a feature or completing a task, they think about the value it actually creates
- People who communicate clearlyThey explain their thinking with evidence and can take in other people’s views
- People who see it throughWhen unexpected problems arise they find a way, and turn what they own into results others can rely on
04 · ENGINEERING CULTURE
Technology is a tool.
Solving problems is our job.
At Skyware, adopting a new technology is not an achievement in itself.
We choose technology that fits the requirements and the development environment, and look for ways to cut unnecessary work and complexity. We don’t stop at implementing features; we develop with code quality, maintainability and the real production environment in mind.
- Every technology choice needs a reason.The newest technology is not always the best choice. We first understand the project’s requirements and technical constraints, then choose the technology and architecture that fit, weighing performance, maintainability and scalability.
- Use development tools fully, but verify the results.We use AI development tools such as Claude Code to reduce repetitive work and raise productivity. Checking the behavior and quality of generated code, and making the final call, remains the developer’s job.
- Deployment is not the end of development.What matters is that a feature runs reliably in production. We plan for exceptions and failures, and aim for structures that make it possible to find the cause and improve when something goes wrong.
- We don’t write code only its author understands.Code is read and changed for longer than it takes to write. We share design intent and how problems were solved, and aim for code other developers can easily understand and maintain.
05 · VOICES FROM THE TEAM
Team Interviews
We asked people who work at Skyware: what they do, what they like, and who they hope to work with.
- Q1What are you working on now?
- I work on server development for SCOS and sOMP. Most of my work is implementing the integration needs that differ by customer, and analyzing and resolving issues that come up in operations.
- Q2What do people who do this job well have in common?
- Solid fundamentals. If you really understand Java, SQL and HTTP, you pick up new technology quickly. The other thing is asking right away when you don’t know. A ten-minute question helps the whole team more than a day spent stuck alone.
- Q3Any preparation you would recommend to applicants?
- Have one project you finished end to end, however small. If you have gone from database design to deployment yourself, you will have clear things to talk about in the interview. Use AI coding tools freely, but build the habit of reading and verifying what they produce.
- Q4What is hard about the job?
- Production incidents don’t keep office hours. But we have a culture of sharing immediately instead of shouldering things alone, and looking at it together resolves it faster than you would expect.
- Q1Tell us about your role.
- I manage the schedule, scope and deliverables of customer SI projects. Requirements meetings, weekly reports and acceptance reviews are the daily routine, and most of my time goes to coordinating between the development team and the customer.
- Q2What skill does a PM need most?
- Analysis. Understanding the work and the domain precisely is where everything starts, and you should never proceed without that understanding. Next is a sense of schedule: you have to see delays coming before anyone else. And communication: plain language for the customer, precise language for the developers.
- Q3How do you define leadership?
- Nothing grand. When a problem comes up, offer a solution first instead of assigning blame, make judgments and decisions under uncertainty, and take responsibility for the outcome.
- Q4What is hard about the job?
- Customer requirements change mid-project all the time. Each time, scope and schedule have to be renegotiated, and raising the difficult conversation first is half my job.
- Q1Tell us about your role.
- I organize requirements into screen specifications and policy definitions, and stay responsible with the designers and developers until they become real screens.
- Q2What is the most important skill for a planner?
- Clear communication. You have to understand exactly what the customer wants and get designers and developers looking at the same goal. Even the best-written specification is worth little if its intent doesn’t come across.
- Q3Have AI tools made planning easier?
- Writing documents is certainly faster. But the tools don’t guarantee the quality of the planning. Defining things carefully, from user flows to exceptions down to what a single button does, is still the planner’s job.
- Q4Anything you would say to applicants?
- Small execution beats a perfect specification. Plan, build and use even one small feature yourself. You will see things that never show up on paper.
06 · HIRING PROCESS
A process for understanding each other
Hiring is as much the applicant’s chance to judge the company and the work environment as it is ours to evaluate the applicant.
We aim to understand your experience and technical skills concretely, and to confirm that the way we work suits each other.
- Document ReviewDocument Review
We review your résumé and project experience for relevance to the role and the main work you have done. For development roles we also look at your tech stack, project contributions and portfolio.
- Technical InterviewTechnical Interview
Based on projects you have actually delivered, we discuss your technical judgment, problem-solving process and implementation experience. A short technical task or code review may be included if needed.
- Culture InterviewCulture Interview
We talk about ownership, communication style and collaboration experience. You can also ask about the role and work environment you would actually be joining.
- Offer & OnboardingOffer & Onboarding
We agree on your responsibilities and terms in detail and arrange your start date.
The process may vary slightly by role and experience.
07 · OPEN POSITIONS
Your next challenge starts here.
We are looking for colleagues who bring expertise to their role and solve real problems with technology.
Planning
Listen to customer needs, write screen flows and functional specifications, and align schedules with development and design. Produce specifications and test scenarios for commerce and messaging projects.
Service Planner
Design
Design the UI of shopping malls, admin screens and apps, and build mockups and design systems in Figma. Deliver production-ready HTML and CSS.
UI/UX Designer
Development
Develop everything from storefront screens (React · Vue) to order, payment and messaging servers (Java · Spring · MySQL) and external integrations. You should be able to use AI coding tools such as Claude Code and Copilot in real development.
Software Engineer
Marketing
Plan and run promotions, advertising and messaging campaigns for customer shopping malls. Analyze traffic, conversion and sales data to shape the next campaign, and operate new channels such as WeChat Mini Programs.
Marketing & Data Analyst
PM
Manage the schedule, scope and deliverables of customer SI projects, and coordinate requirements and issues between the customer and the development team. Carry the project through proposals, WBS, weekly reports and acceptance.
Project Manager · Project Management
Responsibilities, requirements, preferred qualifications, working conditions and how to apply are described in each job posting. For open applications, please use Contact Us.
We want to build Skyware’s
next results with you.
Working with good colleagues means learning from each other, making better judgments, and creating results that would be hard to achieve alone. If you want to bring your expertise and make a clear contribution in your work, join us at Skyware.
BUILD WHAT MATTERS.