We are always looking for talented individuals who wish to be a part of a select team of world-class programmers in a growing multi-national company.

The person will be responsible for: 

• Performing the duties of a Scrum Master as described in the Scrum Guide.
• Ensuring the team implements Scrum in full accordance to the Scrum Guide.
• Ensuring team effectiveness through the application of Scrum and supporting practices. Organizing and being responsible for the team's assessment based on Evidence-based Management (EBM) metrics and organizing continuous improvement processes.
• Organizing and being responsible for the team's maturity growth within the PAL model.
• The team's application of the empirical process, and if necessary, training and supporting the team through mentoring and coaching.
• Removing obstacles that cannot be resolved by the team.
• Serving as a servant leader for the team, including:
• Creating and maintaining conditions for a high-performing team.
• Ensuring a safe environment (as it was originally described by Amy Edmondson).
• Creating the conditions for, and supporting team formation (for example using the Tuckman model).
• Navigating conflicts within the team.

• Provide an evaluation of the team's maturity level and team formation level.
• Provide an evaluation of the team's knowledge and application of Scrum.
• Provide an EBM metrics-based evaluation of the team.
• Provide an improvement plan, presented to and approved by the company management.

• Implement at least two planned improvements.
• Improvement:
• Either: Independent measurements show improvement in one or more EBM metrics.
• Or: The team has a "lessons learned", a commitment, and an improvement plan.

• Independent measurements show improvement in one or more EBM metrics.
• PAL model measurements show improvement in team maturity.
• The team acknowledges the benefit the Scrum Master provides them.
• A plan for the next 6 months of the Scrum Master's work has been prepared and defended.

• Knowledge of Scrum, confirmed by PSM II, DASSM, PMI-ACP, A-CSM, or similar certification.
• Understanding of the Agile Leadership model, confirmed by PAL, CAL, or similar certification.
• Understanding of the EBM model confirmed by PAL-EBM certification.
• Note: Certifications may not be necessary if knowledge and understanding of Scrum, PAL, and EBM demonstrated during the interview are sufficient for the exam, or the person commits to obtaining these certifications within 3 months of starting the job.

• High emotional intelligence.
• Knowledge and application skills of the Radical Candor approach by Kim Scott.
• Practical familiarity with the Crucial Accountability approach by Kerry Patterson.
• Skills in systemic coaching (ideally, familiarity with the Reading the Room model by David Kantor).
• Skills in social coaching (TBR certification would be ideal).
• Technical background (as teams are highly technical, it will be easier to find common ground).
• Familiarity with the Cynefin framework.
• Knowledge of techniques for working with chaos, in addition to difficult systems.
• Knowledge of DevOps culture (DoL certification would be ideal).
• Knowledge of Management 3.0.
• Knowledge/certification in Disciplined Agile (DASM, DAC, DASVC).
• Knowledge of classic process models (e.g., people who had PMP, RUP certifications before getting into Agile).

• Serious coaching certifications such as ICF, ICE-CE, ICE-AC.
• Teaching experience, especially as an ICAgile authorized instructor, PST/CST.
• Understanding of the EBM model confirmed by PAL-EBM certification.

• Extensive experience in SAFe. Individuals with a background in SAFe will have to be carefully evaluated, as to whether they genuinely followed SAFe principles, or just used them to paint classic top-to-down management as "Agile".

The person will be responsible for: 

• The client not only achieved project goals but gained added value in reliability, transparency, and innovation. Investing in us has proved to be the most effective way for the client to invest their money, providing them with maximum value and reducing risks.
• (A2I) A capable PO can now be trusted with any project, old or new.
• (CV) The company now has a PO that can steer a project as well as, if not better than, the company's founders.
• (CV + UV) All parties' interests are considered. Our company doesn't offer free services but seeks expansion opportunities, ensuring clients know we act in their best interest.
• (CV) The client is happy, confident that he will be heard and agreements will be upheld. Our PO can offer solutions superior to the client themselves or other providers.
• (CV + UV) Thorough risk assessment and a strategic vision are in place.
• (CV + A2I) Teams vie for our exceptional PO, seeking his expertise.

• Aligning product goals with company objectives.
• Taking responsibility for the outcomes of all company products.

• Demonstrating leadership within the product domain.
• Serving as a role model in the application of Scrum, Agile, and company standards.

• Contributing to the development of the company's long-term strategy.
• Defining strategies and opportunities for product diversification and increased product profitability.

• Co-creating development strategies with company leadership.
• Actively championing innovations in order to reach goals

• Taking responsibility for post-sales and cross-sales within the company.
• Collaborating with company leadership to define strategies and opportunities for improving Time to Market.

• Collaborating with various company departments (including Sales/Marketing) to improve Time to Market through process optimization.

• Actively managing customer expectations, including selling additional services, across all dimensions—revising CV, developing T2M, expanding UV, and enhancing A2I. Demonstrating growth points in T2M for the customer and establishing agreements within this growth.

Enhancing key project indicators through Evidence-Based Management metrics (Current Value, Unrealized Value, Time to Market, Ability to Innovate)

Anti-requirements: reliance on miracles, hiding information that we can’t make it in time (including the lack of a releasable increment no rarer than once every two weeks) until the last second, falsifying the real state of the development process. The above is strictly prohibited. Attempts to argue for "it’s more convenient/efficient/faster to complete all preparatory work first" will be immediately viewed as attempts to find a way not to do something, which will not do the PO any favors. We’ve heard it all before

• For you, criticism is like a gift, serving as fuel for improvement, rather than a reason to get hurt.
• You trust no one on word alone, not even yourself. You confirm knowledge with exams and practice. A lecture is not enough for you.
• A typo in your document is like a stain on your reputation, and overlooked feedback from the client is like the end of your career.
• Team success is more important to you than any personal achievement.
• You get constantly blamed for setting unrealistic standards, and are told that there is no need to do things that well for anyone.
• Clients invite you to their kids’ birthdays, and trust you with their most sensitive secrets.

No set of instructions can cover every duty or foresee all situations. Therefore, observing engineers must take initiative and, guided by their professional knowledge and situational context, go above and beyond to prove their worth.

• Creation of a Product Vision: A clear conception of what the end product should be. This involves defining goals, understanding customer needs, and outlining a strategy for achieving success
• Customer Interaction: Establishing trusting relationships with clients, collecting feedback, identifying requirements, and ensuring the product adheres to customer expectations. Taking into account the interests of all types of stakeholders.
• Collaboration with the Development Team: Interacting with the development team by providing essential information, clarifying task details, and addressing arising questions.
• Making Decisions on Priorities: Allocating task priorities, ensuring alignment of the developed product with the company strategy and customer requirements.
• Taking Responsibility for project economics: The Product Owner is responsible for the project meeting the company's profitability standards. A project must have a roadmap outlining how it plans to increase revenue. Collaborating with other Product Owners, they are accountable for the company's overall financial metrics and alignment with financial goals.

Performance targets for the probationary period (3 months)

• [Week 1] Conducted a project audit, was dismayed by the state of affairs, and presented a comprehensive and evidence-based plan with a commitment, outlining what needs to be addressed, the priorities (with explanations as to why such priorities are in order), and projected timelines for closure.
• [Month 1] Have a portrait of projects within your responsibility, understand their problem points, and identify all weaknesses and concerns of both the team and the client
• [Month 1] Identify the current project plan with the team and the client. Have a plan in place to achieve these goals.
• [Month 1] Master and demonstrate the practical application of the empirical approach (EBM, Evidence-based Management)
• [Month 1] Understand project economics, actively contribute to budget formulation, and manage client invoicing.
• [Month 2] Identify weaknesses in the team/client project plan, have a plan of improvement and post-sales activities. Started taking action within the post-sales framework.
• [Month 2] Developed a plan to enhance EBM metrics in existing projects.
• [Month 2] The team of the projects within the responsibility scope understands the project direction and the backlog is supported by product increments.
• [Month 3] The software team, project teams within the responsibility area, external and internal stakeholders should come to the conclusion: “We no longer need to address the issue of supply assurance and maximizing value delivery in Projects A and B. The projects are profitable and show growth prospects. We can now focus on our responsibilities.”
• [Month 3] The company employees should conclude: “The work of the Product Owner helps me achieve better results. Thank you for providing such a wonderful person.”

Required

• Experience as a Product Manager/Product Owner/Analyst.
• Experience interacting with international clients.
• Knowledge of Agile and Scrum methodologies, or a willingness to learn.
• Conversational and written English (at a level sufficient to understand what is required, and convey what is needed).
• Ability to formulate hypotheses supported by facts and analyze results.
• Ability to “keep your eyes peeled" (competitor analysis and adjacent areas).
• Practical familiarity with the OKR goal-setting approach.
• Understanding of Servant Leadership principles and how they differ from authoritarian management.
• Emotional intelligence.
• Communication skills (ability to speak the interlocutor's language, engage in constructive dialogue, manage conflict, give and receive criticism).
• Ability to conduct "difficult conversations" without losing patience and composure.
• Certified in Agile techniques no lower than PSPO II, ICP-EPO, IIBA-CCBA, PMI-PBA
• The courage to make decisions and take responsibility for them.
• Respect for the team, the company, and the client.
• Attention to detail.
• Strive for team success.
• Negotiation skills and the ability to build trusting relationships with clients.

Welcome

• Knowledge of Evidence-based Management. It’s okay if there is no knowledge to speak of, as long as you are willing to learn.
• Experience in the IT environment.
• Practical familiarity with Kim Scott’s Radical Candor approach.
• Practical familiarity with Kerry Patterson’s Crucial Accountability approach.
• Understanding of Amy Edmondson's psychological safety model.
• Knowledge of Management 3.0.
• Would be a significant downside:
• Adherence to Daniel H. Pink's Drive! model.
• We are as anti-Pink as possible.
• "Spoiled" corporate pseudo-Agile understanding of a servant leader as a mix of а secretary/entertainer/teacher of a preschool group/mollycoddler.
• We do not need any of this; we will say "thank you, goodbye" immediately.
• Our ideal leader is not a nanny but a good sergeant ("servant to the king, father to the soldiers"©).

Yes, we are the place for the crazy ones who do not settle for less. We are perfectionists who understand the meaning of “enough” (but our enough is another’s perfect). We are idealists who want to do things right. We are life-long learners who think that we are never good enough to stop. We are a wolf pack that values situational leadership and personal accountability. We are the scariest animals in the forest for outsiders, but treat each other well. When working with us, you will never be the smartest person in the room. We deny experts and focus on a scientific approach and data-based and science-based proof. We work in a scary world that constantly changes, and the only way to survive is to be ten steps ahead of everyone else. We don’t care about trends and fashion, but care about customers and serving them with efficiency and due regard. We are different, and that is for a reason. For mediocrity, there are plenty of other places to work. While working with us, you will become a better leader, better specialist, and a better professional because there is no other way to survive.

If you are up for a challenge, if you want to grow and evolve and get things done, then we are the right place for you.

We are Gehtsoft USA, a North Carolina Limited Liability Company with our head office located in the city of Raleigh. The company has been in operation since 1999, and since 2008, we have been represented in the USA.

Our primary focus is custom software development, but not in the conventional sense of "outsourcing" or "outstaffing." We specialize in situations where the client may not have a clear understanding of what needs to be done or how to accomplish it. It would be more accurate to describe our work as "turn-key product development." However, we currently do not have our own products—perhaps because, as the saying goes, "the cobbler's children have no shoes."

Our company operates on five main principles:

• Delight Customers;
• Be Awesome;
• Be Pragmatic;
• Context Counts;
• Enterprise Awareness.

Our expectation is that every action of every employee is guided by these principles. And most of all, we are guided by a definition of professionalism:

“No instruction can list all an employee's duties, provide all individual cases, and give appropriate instructions in advance. Therefore, the supervising engineers must take the initiative and, guided by their professional expertise and the project goals, make every effort to justify their appointment to the job.”

We are looking for a right-hand person for Gehtsoft’s leadership and founders. A closer, a finisher, “a last mile” pusher. A person whose feeling of accomplishment comes from getting things done. A person who can balance “red,” “orange,” and “teal” teams and people and work with them accordingly. A person who is ready to dig in, grind, and fight for a brighter future for us all.

• Ensuring that strategic initiatives are getting done;
• Ensuring that day-to-day operations are efficient and reliable.

This will include (but is not limited to):

• Implementing short-term and long-term strategies that align with objectives established by CEO and founders;
• Day-to-day collaboration with project teams and department heads to ensure successful operation and continuous improvement;
• Monitoring performance and taking corrective action when necessary;
• Partnering with the CEO and Head of Sales to ensure efficient operations and long-term growth of the company;
• Overseeing operations, HR, accounting, and legal to ensure that supporting activities are aligned with short- and long-term objectives and improve operational efficiency;
• Promoting culture and level of standards established by the founders and CEO on a daily basis;
• Getting things done.

Week 1:

• Change us as a business for the better. Think Gemba Kaizen and the new employee practices they offer. Any improvement must be based on a proper theoretical basis, be aligned with company values, and comply with company standards or improve them.
• Ensure that we are a good fit for you and you are a good fit for us.

Month 1:

• Evaluate current operations, propose and implement at least one efficiency improvement that will directly affect business outcomes (based on EBM-metrics);
• Ensure that at least one key strategic initiative (priorities can be discussed with leadership) is on track, properly measured, guided, and worked on by the teams;
• On a small scale, ensure that decisions made or actions initiated on a Monday company sync meeting are getting done on a weekly basis;

Month 2:

• Continue to perform efficiency improvements that result in visible and measurable outcomes every month;
• Lead Q1 objectives and key results review meeting, and plan and establish any corrective actions necessary;

Month 3:

• Show and prove the effectiveness of corrective actions from Month 2 via direct improvement of key results to company-level objectives.

• Solid, results-proven executive leadership experience;
• Understanding of a software development business;
• Excellent leadership skills, knowledge of Radical Candor, and Crucial Accountability (both approaches are company standards for leadership);
• Direct, concise, and clear communication skills;
• Ability to diagnose and fix problems and foresee potential issues;
• Ability to focus on day-to-day operations without losing sight of the long-term goals and objectives;
• Desire to thrive in a competitive environment, which promotes team-level and personal accountability for business-level outcomes, not individual actions;
• Understanding of the difference between working in simple and complicated and complex and chaotic situations (Cynefin framework, we work almost exclusively in left two quadrants);

• A stressful, challenging environment where you can step up and take accountability;
• Ability to push the boundaries of your role and grow and evolve by expanding your knowledge and experience in neighboring fields (and sometimes in fields that you never worked before);
• A highly competitive environment where you can be best at something but for sure will never be best at everything;
• Transparent compensation model that reflects your outcomes and impact on the business;
• Lack of red tape, direct access to decision-makers who are driven and constantly want to improve Gehtsoft;
• Very people-oriented culture, where help is always there as long as you don’t abuse that system in your personal interests. Fool us once - shame on you, fool us twice - shame on us. We are not keen on being ashamed.
• Data-driven decision-making and meritocracy where your opinions are valued by your outcomes, not your title.
• You will be fully supported in your growth as long as your development is pushing the business forward and improves the metrics;

Vacation/sick leave/holidays follow the American model.

Each employee has 15 days off per year, which can be used at their discretion.

• 1 day off can be used at any time; the team will have to approve two or more consequential days.
• Each year worked adds one additional day off per year.
• Official holidays: Christmas holidays (Catholic or Orthodox, so 12/24-1/2 or 12/31-1/7), Independence Day (7/4), Thanksgiving (4th Thursday of November). Holidays can be transferred to a different time if need be. You could say that there are 20 days off a year, and only Christmas (24-25) and New Year (31-1) are holidays.
• Equipment reimbursement: A laptop is provided (to be returned if the person leaves before one year), or a $1000/year budget for personal equipment.
• Training: Internal training is provided and paid for; after training, a certain period of work commitment is required, usually at a rate of 1 month per 200 dollars spent.
• Maternity leave: For employees who have worked for more than a year, the company pays for 15 working days of paternity leave and up to 60 working days for maternity leave.
• Severance pay: For those who have worked for one year - 1 month's salary, two years - 2 months' salary, three years and beyond - 3 months' salary. The salary is paid upon contract termination, regardless of the reason for termination.

For those who are useful and needed, we are ready to provide аdditional benefits such as financial aid, low-interest loans, relocation assistance, etc. Basically, if you treat us well, we'll treat you well :)

Improvement of testing quality on the project and risk reduction of potential issues at higher levels of testing (manual, client acceptance) by implementing automated E2E & API tests in accordance with the testing pyramid.

Consistently high application quality (lack of blocker/highest/high defects, as well as no more than 5% of defects found by the client out of the total number of defects) through reducing the number of bugs missed by API & E2E tests and ensuring their earlier detection.

Enabling daily releases to Production in the AP team.

Saving resources and funds of the AP team through effective test coverage with automation.

Efficiency and productivity increase of AP team developers through relieving them from writing API & E2E automated tests, freeing them to focus on development, support, implementation of component and contract test coverage, closure of technical debt, etc.

Reducing test execution time and increasing product delivery speed by improving test design and transitioning to the Playwright framework, which will enable parallel test execution.

A Senior Automation QA Engineer is an outstanding professional with deep knowledge in test automation, including experience with various frameworks (Cypress, Playwright) and programming languages (JavaScript). The candidate should have experience in creating and maintaining test infrastructure, including configuring environments for test execution, creating and supporting containers (Docker), as well as experience integrating automated tests into continuous integration (CI) and continuous delivery (CD) processes.

A Senior Automation QA Engineer independently organizes their work and actively participates in product requirement analysis, identifies potential risks and creates appropriate test cases and scenarios, ensures their high performance and stability, analyzes test results, identifies defects and their root causes, and optimizes automation processes. They actively document their work, ensuring transparency and accessibility of information for the entire team. The candidate should be ready to train and share experience with other team members, contributing to the professional growth of the entire QA team. Their professional contribution brings undeniable value to the company's project, ensuring high quality and long-term success.

Current Value Increased

The overall cost of quality assurance on the project decreases due to the QA Engineer covering the automation level with API and E2E automated tests.

• The percentage of API & E2E test coverage of new features by the automation becomes higher than the percentage covered by developers - developers cover only unit and integration tests, while the automation covers API and E2E tests (the cost of man-hours for writing tests by developers is higher than through automation),
• a decrease in the number of defects discovered after the implementation and usage of automated tests
• a reduction in the time spent on manual testing

Testing automation reduces manual effort

• a decrease in the number of bugs in new functionality discovered by manual testing and the client
• an increase in the volume of automated tests in accordance with the testing pyramid
• a decrease in the number of regression bugs discovered after running automated tests

Reducing the risk of defects occurring in later stages by improving test coverage with automated tests according to the testing pyramid and optimizing testing processes, confirmed by Quality metrics (Defect Density, Defect Containment Efficiency)

Supporting the product owner in meetings with the client about requirements and strategy

Assisting the client in optimizing and executing the testing plan and strategy, providing their experience and expertise

Providing consultations to the client, helping them better understand and adjust testing and automation processes

Facilitating product changes as automated tests allow quick verification of functionality when code changes are made

Team efficiency increases as team developers have more time for development, support, implementation of component and contract test coverage, closure of technical debt, etc.

By actively implementing an automated testing strategy, they will ensure continuous delivery to the end user.

Must have skills:

• Proven experience with FE and BE automation in JavaScript, using Playwright framework in a software development environment
• Experience with setting up a framework from scratch & moving automation from one framework to another
• Experience with API testing
• Experience with Docker
• Familiarity with GitHub Actions or another CI/CD framework
• Strong understanding of Agile and the software development life cycle (SDLC)
• Proficiency with test planning, requirements analysis, defect tracking and test reporting
• Solid understanding of modern test automation approaches and concepts (Shift-Left Testing, Continuous Testing, Test Pyramid concept etc.)
• Experience in code review
• Analytical skills, and a keen attention to detail
• Ability to learn quickly both business and technical parts of projects
• Excellent communication skills, both written and verbal, for effective collaboration within a cross-functional team
• Self-motivated, with the ability to work independently and thrive in a team-oriented environment

Would be great:

• International testing certifications (ISTQB or other)
• Understanding the empirical approach to software development (Scrum by the book, XP, DevOps by the book), and how it's different from the predictive approach.

NOTE: It is not marked as "mandatory" because the majority of candidates do not know, and there is nowhere to learn. However, it is crucial to be prepared to work in the empirical approach used here. Yes, we will teach, but learning is mandatory, and there is no other option. And you will need to learn quickly.

• Knowledge of trading principles on Stock, Forex, Crypto
• Understanding of how KYC systems work
• Understanding of how integration with credit cards, ACH, Wire payments works

Mandatory Values:

• Openness to new information, including a critical view of their decisions, behavior, and results;
• Commitment to information from official sources such as ISTQB, international testing standards, scrum.org , etc.;
• Striving to achieve the best result based on current conditions;
• Understanding and acceptance of the client's leadership as a key factor in our successful interaction;
• Ability to set goals and achieve them with minimal effort;
• Ability to take responsibility for the end result, even if it can only be achieved through joint efforts;
• A commitment to continuous process improvement;
• Boldness in making decision and taking responsibility for them;
• Respect for the team, company, and client;
• Attention to detail;
• A commitment to team success.

What We Definitely Don't Want to See:

• Lack of initiative
• Lack of communication
• Inability to prioritize in-progress tasks
• Inability to adapt
• Negative attitude towards feedback

• Knows all key developers on their projects, proactive in communication
• Understands the company's Code of Ethics, Our Understanding of Professionalism, Behavior Correction Mechanism in the Company (5R), General Job Description
• Understands the basic business logic of the developed application to a sufficient extent to independently and fully work with project tasks
• Understands the current state of development quality and product testing process
• Set up the Playwright framework for test automation and its integration with GitHub Actions
• Collaborates with developers on current testing automation tasks in the team. Writes FE/BE automated tests for new functionality and support of existing tests. Initiated the migration of tests to the new framework. Analyses test runs, documents defects, added reporting.
• Monitors EBM and quality metrics status on the project together with other team members. Participates in decision-making based on them.
• The team feels the benefit of their work

• Continued work on current tasks (writing FE/BE automated tests for new functionality and supporting existing tests, test parallelization, analysis of test runs, documentation of defects, reporting). Technical debt for transferring automated tests to a new framework is reduced by 10-20%
• Part of the regression test scope is covered by automated tests and regularly runs in the environment
• Increased test coverage on the integration layer of the testing pyramid with automated tests
• Bugs with a root cause - code error, configuration, deployment error - are detected by automated tests and do not reach manual testing level
• The team is capable of reducing manual testing and increasing release frequency without deteriorating product quality

• Fully involved in the product development process and points out potential risks/problems during development
• All new features are covered by automated tests, a significant portion (>=50%) of the technical debt for transferring automated tests to a new framework is closed
• Automation makes life easier for manual QA and speeds up regression testing
• Test execution time is reduced due to improved test design and parallel runs on Playwright
• Fully integrated into the team, and the team trusts and listens to their opinion
• The team gains value from the employee's work in the form of reduced testing costs while maintaining/increasing product quality

• Existing projects are growing in scale and generating higher revenue; overwork is eliminated.
• The current developer is relieved enough to take a day off or a vacation, and the project can go on without losses or reductions in capacity.
• The new employee trains less experienced colleagues.

• Architecture decisions for the app.
• Control over architecture’s application.
• Training/explaining architecture’s application to the team.
• Control over application of general principles of high quality software development (SOLID, TDD, BDD).
• Training/explaining application of general principles of high quality software development (SOLID, TDD, BDD) to the team.
• Participation in all stages of SDLC as a part of the team.
• Participation in sourcing, integrating, and developing employees.

• You are platform-agnostic, and not tied to a specific tech stack.
• You understand the internal kitchen of every part of your work.
• You do your work awesomely.
• You can figure out any technology and make any task interesting for yourself. You understand that the client's wishes are paramount but remain pragmatic.
• You always ask yourself if money put into your work is the best investment for the client.
• You enjoy learning. Acquiring new knowledge is your hobby.
• For you, criticism is like a gift, serving as fuel for improvement, rather than a reason to get hurt.
• You trust no one on word alone, not even yourself. You confirm knowledge with exams and practice. A lecture is not enough for you.
• Team success is more important to you than any personal achievement.
• You get constantly blamed for setting unrealistic standards, and are told that there is no need to do things that well for anyone.
• You are not afraid to make decisions and take responsibility for them.

Increased Current Value

• Each sprint delivers 10% more starting from the third week. An indicator of 20% improvement after a month + a weekly positive dynamic of 10% after a month.

Improved Ability to Innovate:

• Two weeks: the person makes a part of the team’s decisions, provides a product improvement plan, and implements it.
• 1.5-3 months: The new employee makes decisions about architecture, technical risks, code quality, solving complex problems, and discussions with client teams on technical issues. As a result, the Tech Lead can take a vacation in June 2024.

Improved Time to Market:

• Within a month: contractors leave, the team improves the pace and quality of development.
• Review requests do not accumulate in queues.
• Client requirements are processed, clarified and taken into work faster.

First week:

• Connected to all necessary chats and meetings.
• Knows all key developers for their projects, proactive in communication.
• Knows the project goals for the company and the client.
• Knows company standards.

Second week:

• Actively participates in project development.
• Can answer questions regarding Frontend/Backend implementation.
• Independently develops code of any complexity (including cross-platform).
• Develops unit and integration tests.
• Conducts code reviews.
• Independently and optimally organized their own development process as well as the work of subordinate Juniors. Can justify the approach taken.
• Provides and receives feedback from colleagues on code and decisions, in order to ensure quality and improvement of results.
• Contributed to the testing process, including helping to create test cases and fixing errors.

Within the first month:

• Enrolled in the first available ICAgile Professional course.
• Can independently solve emerging problems.
• Actively discusses and makes technical decisions.
• Participates in discussions on ways to improve work processes.
• Considers project economics when making decisions.
• Participates in preparing user documentation with the help of a technical writer.
• Develops integration, load, and user interface tests.
• Applies corporate software patterns (e.g., Cloud Design Patterns).

Other:

• Can justify decisions and proposals to the team and the client.
• Adheres to and requires others to adhere to the company's professional standards (such as the ethics code, Java code requirements, test-driven development, trunk-based development).
• Participates in improving company processes.
• Maintains and develops professional skills.
• Associates with the team and the company, shares responsibility.

• Excellent understanding of algorithm theory, object-oriented analysis and development, SOLID principles, design patterns (GoF, cloud applications, business resilience).
• Understanding the principles and practices of building the application's testing pyramid within BDD/TDD.
• Understanding principles of rapid development (TBD, high degree of automation, daily merges, releases at least once a week).

• Understanding principles of both relational and NoSQL (RDBMS, ACID) databases.
• Any mathematics and engineering related to IT: e.g., graph theory, group theory, AI in all its manifestations, operating system theory.
• Understanding the empirical approach to software development (Scrum by the book, XP, DevOps by the book), and how it's different from the predictive approach.
• Good understanding of UX, ergonomics, and technical aesthetics. Full-stack expertise would be a great advantage.
• Knowledge of trading principles on Stock, Forex, Crypto.
• Understanding of how KYC systems work.
• Understanding of how integration with credit cards, ACH, Wire payments works.