Academic snapshot
Marks: 70% or 7.0+ CGPA (when listed)
Degree: B.Tech/B.E./M.Tech CS/IT/related
Year: Final year + recent grads (~2 years)
Backlogs: None active preferred
CRED Placement Papers 2026
CRED is a fintech startup that rewards users for paying credit card bills on time. Founded in 2018, CRED has built a premium credit card management platform with millions of users. The company focuses on building trust through technology and has a strong engineering team working on payments, gamification, and user experience.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
CRED fresher eligibility for campus drives
CRED hires like a product fintech, not a service-company mass drive. The printed CGPA floor gets you into the funnel; the 90-minute OA and FinTech design talk decide whether you see an offer.
Who this hub is for
- For: Final-year and early-career engineers targeting Software / Backend / Frontend / Product Engineer roles on payments, rewards, and member experience.
- Not the same bar: Pure sales, support, or non-engineering marketing roles - different funnels entirely.
- Intern paths: Some backend intern loops shortlist via contest performance (for example CodeChef) plus resume, then jump into machine coding before full-time style rounds.
Degree, CGPA, and branch reality
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 70% or 7.0+ in 10th, 12th, graduation when listed | Higher GPA helps resume screen; OA still decides |
| Degree | B.Tech / B.E. / M.Tech in CS, IT, or related | Circuital branches appear when DSA is strong |
| Backlogs | None active at application / joining | Clear before offer paperwork |
| Experience | Freshers and ~0-2 years | Intern → full-time conversion also appears |
| Languages | Python, Java, JavaScript | One deep language for OA + interviews |
Is 7.0 enough? It matches the commonly reported floor. A 7.1 with clean timed coding and a crisp payment-design story beats an 8.8 that freezes on graphs. CRED values technical excellence alongside academics - treat CGPA as a gate, not a scoreboard.
Gaps: Short gaps are easier to explain with projects or an internship story than silence. Full-time degrees only on most notices.
Skills bar
Primary filter: Medium-hard DSA under time
Interview differentiator: FinTech system design
Languages: Python, Java, JavaScript
Hub: Bengaluru (hybrid norms vary by team)
Who usually fits and who struggles
Good fit: You enjoy medium-hard LeetCode-style problems, can talk about idempotent APIs and failure retries without jargon soup, and have one project you can defend for 20 minutes. Comfort with Bengaluru relocation helps.
Harder path: You only practiced aptitude MCQs; you skip system design because “freshers don’t get design”; you cannot explain your own project’s data model. CRED’s OA clear rate is often cited around the mid-teens to ~20% - guessing through edge cases fails quietly.
Campus shortlists vs off-campus reality
CRED’s campus volume is not Infosys-scale. Some colleges see a drive; many students enter through careers, referrals, or intern conversion. That changes psychology:
- Fewer seats means OA cutoffs feel harsher even when the problem set looks “fair.”
- Referrals improve the chance a human reads your resume; they do not soften hidden tests.
- Intern conversion may skip a stage but still expects you to defend code and design.
If your college does not have CRED on the calendar, start a careers + referral plan early. Waiting for a PPT that never comes is how a year disappears.
Building fintech intuition without a payments internship
You do not need a fintech internship to clear Round 2. You do need vocabulary backed by diagrams:
- Read CRED’s public product surfaces (bills, rewards, store) as a user and note trust/friction points
- Sketch how a bill payment might move through API → auth → ledger → rewards → notification
- List three failure modes (duplicate callback, partial success, reward mismatch)
- Propose one metric per failure mode
Do this once a week for a month. Interviewers can tell the difference between someone who watched a 40-minute YouTube system-design video and someone who thought about money movement.
Coding themes mapped to CRED OA
| Theme | Why CRED-like OAs use it | Cousin drills |
|---|---|---|
| Hash maps | Frequency, first unique, anagrams | Two-sum family |
| Two pointers / sliding window | Subarray constraints | Longest substring variants |
| Trees / BST | Hierarchical data | LCA, validate BST |
| Graphs | Relationships, dependencies | BFS shortest, cycle detect |
| DP | Optimization under constraints | Knapsack light, LIS, string DP |
After every mock miss, pull two cousins from the same family on coding questions. Theme repetition beats random hard problem hopping.
Behavioral signals CRED managers notice
Beyond STAR templates, managers listen for:
- Ownership language (“I drove” vs “we were told”) without stealing credit
- User empathy for member experience, not only backend cleverness
- Trade-off honesty (“we shipped X knowing Y debt”)
- Learning speed when they change the problem mid-discussion
Practice one story where you were wrong and corrected course. Perfect-hero stories sound fake.
Offer-stage checks
If you clear HR:
- Read equity vesting and location clauses carefully
- Confirm hybrid expectations with the hiring manager if possible
- Do not resign from another offer until the written CRED letter lands
- Background verification expects consistent CGPA and employment dates
Excitement is fine. Process discipline still matters at startups.
CRED previous year paper PDFs
Download 2026 CRED placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What CRED previous year papers actually train
CRED does not publish a permanent official paper bank. Sets on this site are pattern trainers for the OA and early technical rounds - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | 90-min stamina on 2-3 medium-hard coding problems (arrays, strings, DP, graphs) |
| Technical 1 | Live DSA narration: brute force → optimize → edges |
| Technical 2 | FinTech design: payments, wallets, ledgers, credit-card bill flows |
| Managerial / HR | Impact stories, Why CRED?, Bengaluru / hybrid logistics |
Themes that keep repeating (2024-2026)
- 2024: Dynamic programming on arrays/strings, graph BFS/DFS, and interview emphasis on FinTech domain vocabulary. Students who only drilled unsorted “random hard” without timed 90-minute blocks lost easy marks on incomplete solutions.
- 2025: More notes stress optimization and code quality - partial brute force that fails hidden tests is a common reject story. Design chats lean toward scalable payment and rewards systems.
- 2026 prep expectation: Keep medium-hard DSA warm; expect design rounds for many SWE tracks, not only seniors. Some intern/backend paths add machine coding / LLD (2-2.5 hours) where extensibility beats clever one-liners. AI/ML chatter appears in product talk - do not replace DSA with buzzwords.
How to use one paper set in a sitting
- Timed: 90 minutes, 2-3 problems, same language as test day.
- Untimed review: rewrite the cleaner solution; list three edges you missed.
- Map each miss to a theme (DP / graph / two pointers) and pull cousins from coding questions.
- Spend 20 minutes sketching a payment retry or wallet ledger design aloud.
- Log one STAR story the session reminded you of (outage, ownership, conflict).
CRED hiring rounds in 2026
CRED hires through campus, careers portal, and referrals. Major campus volume still clusters in placement season (often August-December); off-campus and referrals run more continuously. Same technical bar either way - referrals mainly improve resume visibility.
How to apply
Campus
Placement cell PPT → resumes → OA → onsite/virtual interviews. Season-aligned slots.
Direct apply
CRED Careers with resume + portfolio. Resume screen then OA invite when roles are open.
Referrals
Employee referrals can shorten the queue; you still clear the same OA and design bar.
Round-by-round walkthrough
-
Online Assessment - 90 minutes
Section Questions Time Difficulty Focus Coding 2-3 90 min Medium-Hard Arrays, strings, DP, graphs Platform is often HackerRank / CodeSignal-style. No negative marking. Hidden tests punish skipped edges. Languages: Python, Java, JavaScript, C++, C. Candidates commonly report ~15-20% clear this stage.
Time boxing: lock one “sure” problem first, then invest in the second for a clear bar, then attempt the third. Three half-broken solutions beat worse than two clean ones with complexity notes.
-
Technical Interview 1 - ~45 minutes
1-2 live coding problems: DSA, arrays/strings, trees/graphs, DP. Interviewers watch approach, code quality, communication, and edge handling. Roughly 40-50% of OA survivors advance in student reports.
-
Technical Interview 2 - ~45 minutes
FinTech system design and project deep-dive: payment processing, wallets, scalability, databases, security. They care how you trade consistency vs availability, handle double-spend / duplicate callbacks, and explain your past work. About 50-60% of Round 1 survivors move on in many write-ups.
-
Managerial Round - ~45 minutes
Behavioral + light technical ownership: impact, collaboration, conflict, CRED culture fit. Success often cited around 60-70% of Round 2 candidates.
-
Optional deep technical / machine coding (role-dependent)
Intern/backend or senior tracks may add LLD-style machine coding (often ~2.5 hours) or extra architecture depth. Correctness and extensibility beat clever tricks.
-
HR - ~30 minutes
Background, Why CRED?, compensation discussion, Bengaluru/hybrid logistics. Most candidates who reach HR with clean prior rounds receive offers if location and integrity checks pass (~80-90% in optimistic student tallies).
Timeline from application to offer
| Phase | Duration | What happens |
|---|---|---|
| Application & screening | 3-5 days | Resume review |
| Online assessment | 1 day | Coding test + evaluation |
| Technical interviews | 5-7 days | Round 1 + Round 2 scheduling |
| Managerial | 2-3 days | Behavioral + ownership |
| HR | 1-2 days | Offer discussion |
| Result | 2-3 days | Offer letter / onboarding |
Total: often 2-3 weeks once you are actively in process (faster for strong candidates). Contest-shortlisted intern funnels can move quicker on calendar but denser on machine-coding intensity.
What interviewers listen for
- OA: Correctness first, then complexity. Narrate assumptions in comments if the platform allows.
- Design: Actors, APIs, data stores, failure modes - not buzzword architecture diagrams.
- Projects: Metrics and trade-offs. “We used Kafka” without why is a red flag.
- Managerial: Ownership language. Impact over title-dropping.
Managerial round: impact language that works
CRED managerial interviews reward specificity. Weak answers sound like campus training slides (“I am a team player”). Stronger answers sound like shipping logs:
- “We cut p95 latency on X from 800ms to 320ms by …”
- “A payment callback retried twice and double-credited; I added idempotency keys and a reconciliation job …”
- “Two teammates disagreed on schema; I proposed a migration plan with rollback …”
Prepare three impact stories with numbers. If you lack production metrics, use project metrics (error rate in tests, load-test RPS, user count in a college deployment). Fake metrics are worse than honest small numbers.
Contests, referrals, and intern funnels
Not every CRED path starts with a campus PPT:
| Path | What changes | What stays hard |
|---|---|---|
| Campus | Batch OA windows | Medium-hard DSA |
| Careers + referral | Resume visibility | Same OA/design bar |
| Contest shortlist (intern) | Faster invite | Machine coding / LLD intensity |
| Take-home (mobile/others) | 24-hour assignment pressure | Clean architecture + follow-up DSA |
If you are contest-strong but design-weak, start FinTech sketches now - the machine-coding round still grades extensibility. If you are design-strong but slow on OA, your referral will not save a failed hidden-test suite.
Comparing CRED to other fintech prep
| Company vibe | Prep you can reuse | What to add for CRED |
|---|---|---|
| PhonePe / Paytm | DSA volume | Member/rewards product sense |
| Razorpay | Payments vocabulary | Premium consumer UX + gamification talk |
| Flipkart/Swiggy | Medium-hard OA stamina | Ledger/idempotency design |
Reuse DSA ruthlessly. Do not reuse a generic “I love fintech” HR answer - CRED interviewers have heard it all week.
Study resources on this site
Use the linked practice pages as drills, not as a second homepage:
- Online assessment for format notes
- Coding questions for theme cousins after each mock miss
- Interview experience for round flavor
- Preparation guide for longer week plans
- Year pages (2024, 2025, 2026) when you want annotated solutions
Download the 2026 PDF for offline timed runs when your hostel Wi-Fi dies mid-mock - it happens.
Where to practise for CRED
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
How to train for CRED this season
If a CRED invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for CRED sits around ₹18-35 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): CRED eligibility for freshers 2026 (from student reports): typically 70% or 7.0+ CGPA in 10th, 12th, and graduation; B.Tech/B.E./M.Tech in CS/IT or related fields; final-year students and recent grads (within ~2 years); no active backlogs. Strong Python, Java, or JavaScript helps. Always verify the careers page or campus JD.
What you are training for: Typical CRED loop: Online Assessment (90 min, 2-3 medium-hard coding problems) → Technical Interview 1 (DSA, ~45 min) → Technical Interview 2 (FinTech system design / projects, ~45 min) → Managerial (~45 min) → HR (~30 min). End-to-end often 2-3 weeks. Some intern/backend tracks add a machine-coding / LLD-style round.
Short version of the prep split: Split time roughly: DSA ~40%, FinTech system design ~25%, timed coding mocks ~20%, project/behavioral prep ~15%. Drill medium-hard arrays, strings, DP, and graphs; practice payment / wallet / credit-card design prompts; keep Python, Java, or JavaScript sharp for live coding.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the CRED previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most CRED drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at CRED usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why CRED?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a CRED-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the CRED story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 CRED PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed CRED papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many CRED papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in CRED-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed CRED paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why CRED. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For CRED, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three CRED mistakes, you are collecting content, not preparing.
Extra drill block (1)
Sit one more mixed CRED set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
CRED fresher CTC in India (2026)
Figures below are candidate-reported as of August 2026. Treat them as bands, not offer letters. Location (Bengaluru primary; also Mumbai/Delhi mentions) and team shift totals.
Software roles
| Level | Experience | Base (approx.) | Total package | Typical background |
|---|---|---|---|---|
| Software Engineer | 0-1 years | ₹15-20 LPA | ₹18-25 LPA | Strong DSA freshers |
| Backend Engineer | 0-2 years | ₹18-24 LPA | ₹20-28 LPA | Systems / design focus |
| Frontend Engineer | 0-2 years | ₹15-20 LPA | ₹18-25 LPA | React / JS depth |
| Senior Software Engineer | 2-3 years | ₹22-30 LPA | ₹25-35 LPA | Ownership + leadership |
Other roles students mention
| Role | Level | Total package | Notes |
|---|---|---|---|
| Product Engineer | Entry | ₹20-28 LPA | Product sense + shipping |
| Full Stack Engineer | Entry | ₹18-25 LPA | FE + BE breadth |
Benefits candidates care about
Health cover for employee & family, stock/equity participation, learning budget, hybrid norms on many teams, meals/snacks at office, wellness support. Equity details vary by level and grant - read the offer letter, do not negotiate from blog averages alone.
Hybrid work and culture questions you should expect
HR and managerial rounds often probe lifestyle fit as much as tech:
- Are you willing to relocate to Bengaluru?
- How do you handle ambiguous product requirements?
- Tell me about feedback you disagreed with.
- What does “premium member experience” mean to you technically?
Prepare honest answers. If you need fully remote forever, say so early - better a clean reject than a mismatched offer. If you thrive in product ambiguity, give a project example where requirements changed mid-sprint and you still shipped.
Intern machine-coding: grading rubric in practice
When candidates say “extensibility mattered,” they mean reviewers looked for:
- Clear module boundaries (not one 400-line main)
- Ability to add a feature without rewriting everything
- Basic validation and failure handling
- Readable names and comments where intent is non-obvious
Clever bit tricks without structure lose. Practice building a parking-lot or library system in 2 hours with interfaces you can extend.
Final 72 hours
| Time | Do | Do not |
|---|---|---|
| T-72h | One light mock + design sketch | Start a new DP textbook |
| T-48h | Project rehearsal aloud | Sleep debt |
| T-24h | Error-log skim + Why CRED? | Caffeine experiment |
| Morning | ID, charger, water | New LeetCode hard |
CRED loops punish heroes who cram and reward students who protect sleep and narration.
Recent CRED placement trends
Hiring shape 2026
Engineering hiring continues across backend, frontend, and full-stack. Payments infra and member experience stay central.
Process notes
System design weight in interviews remains high. Machine-coding / LLD shows up more in intern and some backend notes.
Company context
Series H / ~$4.5B post-money context in mid-2026 - verify live headcount on Careers before assuming campus volume.
Prep implication
Do not wait for a “new pattern” rumor. Double down on timed medium-hard DSA and payment-shaped design talks.
Common questions about CRED hiring
Papers & downloads
Can I download CRED placement papers PDF?
Yes. Free CRED placement papers PDF with previous-year style coding, DSA, FinTech design themes, and interview practice are on this site - no registration. Start with the 2026 PDF and year pages. Papers train patterns; they are not guaranteed clones of your live OA.
Process & rounds
What is the CRED placement process?
Typical fresher loop: Online Assessment (90 min, 2-3 medium-hard coding problems) → Technical 1 (DSA, ~45 min) → Technical 2 (FinTech system design / projects, ~45 min) → Managerial (~45 min) → HR (~30 min). End-to-end often 2-3 weeks. Some intern/backend tracks insert machine coding.
How many rounds are there in CRED interview?
About five core stages for many SWE freshers (OA + two tech + managerial + HR). Exact count shifts by role - intern funnels and mobile tracks may add take-home or machine-coding rounds.
What is CRED online assessment exam pattern?
Usually 90 minutes, 2-3 coding problems, medium-hard, arrays/strings/DP/graphs, on HackerRank/CodeSignal-style platforms, no negative marking. Hidden tests matter. Clear rates often cited around ~15-20%.
What is CRED machine coding round?
A longer LLD-style build (often ~2-2.5 hours) reported on some intern/backend paths. Correctness, design clarity, and extensibility beat clever tricks. Expect production-shaped prompts, not pure LeetCode.
Interview content
What questions are asked in CRED technical interview?
Live DSA; FinTech system design (payments, wallets, scale); project deep-dives; behavioral ownership stories. Interviewers watch approach narration and edge cases as much as the final answer.
What is CRED system design interview like?
~45 minutes on payment-shaped architecture: APIs, data stores, retries/idempotency, consistency, and security. Fresher depth - clear components and trade-offs - not staff-level distributed systems theater.
Eligibility & languages
What is CRED eligibility criteria for freshers 2026?
From student reports: 70% or 7.0+ CGPA when listed across 10th/12th/graduation; B.Tech/B.E./M.Tech in CS/IT/related; final-year or recent grads (~2 years); no active backlogs. Same practical bar as recent cycles - verify your JD.
What programming languages are required for CRED?
Python, Java, or JavaScript are the usual interview languages. Stack familiarity with Python/JS helps day-to-day talk. Pick one language you can debug live under time pressure.
Are backlogs allowed at CRED?
Active backlogs are the usual blocker at application or joining. Cleared historical backlogs are generally fine if the notice does not say otherwise.
Salary & comparison
What is CRED salary for freshers?
Candidate-reported: Software Engineer ~₹18-25 LPA; Backend often ₹20-28 LPA; Frontend ₹18-25 LPA; Senior ~₹25-35 LPA (2-3 YOE). Confirm written offers; bands move by team and year.
CRED vs Razorpay vs PhonePe - which is better?
CRED - premium credit-card rewards / member experience. Razorpay - B2B payments infrastructure. PhonePe - UPI/consumer payments at huge scale. Overlapping high-teens to mid-20s LPA chatter for strong freshers - choose on domain and team, not slogans.
Prep tip
How to prepare for CRED placement?
Rough split: DSA 40%, FinTech design 25%, timed mocks 20%, projects/behavioral 15%. Weekly 90-minute OA simulations + aloud design practice beat passive video watching.
Any pro tip for CRED placement preparation?
Budget real time for FinTech design - especially payments and failure modes. Explain solutions clearly; CRED rewards clean thinking as much as finishing every OA problem.
Is Bengaluru / hybrid work required?
Bengaluru is the primary engineering hub; many teams use hybrid norms. HR will check relocation willingness - answer honestly.
Does CRED ask aptitude MCQs in the OA?
Most fresher reports emphasize coding-heavy OAs (2-3 problems in ~90 minutes). Aptitude may appear on some invites - always read yours. Do not burn your prep calendar on CAT-level quant if your pattern is coding-only; keep light aptitude warm via the mock quiz just in case.
Is CRED only hiring in Bengaluru?
Bengaluru is the primary engineering hub in student reports. Other cities appear in company footprint chatter, but fresher engineering offers usually assume Bengaluru relocation or hybrid tied to that hub. Confirm on the JD.
CRED - recent candidate experiences
CRED’s December 2025 Backend Intern funnel shortlisted via CodeChef contest performance plus resume; one candidate wrote that on 8 December they were invited to a Machine Coding Round for 10 December - a 2.5-hour LLD-style session where “correctness, design clarity, and extensibility mattered far more than clever tricks” (Medium). Expect production-shaped parking-lot/concurrency prompts, not pure LeetCode.
An Android SDE candidate last updated October 2024 on GeeksforGeeks applied via LinkedIn, got a callback in a day, and wrote that “in no time I got an assignment that should be finished and the codebase should be shared in 24hrs” - a Clean Architecture animation-heavy POC with APIs and persistence. Rounds then stacked DSA in Google Docs, a 2.5-hour Core Android discussion, and a Head of Engineering Mobile design of an Analytics SDK before same-day selection.